When I do the full instance name it doesn't work.  When I use MSSQLCLUSTER it likes the first instance name, but the second one says it's a duplicate.

Have you downloaded the new SSMS?  Starting with SQL 2016 SSMS is no longer part of install.  SSMS is starting to be a separate download.  I downloaded the newest SSMS...

Hey Perry,
I basically ran Data Migration Assistant first on the active node, then ran the SQL upgrade on the passive node, rebooted passive node, then failed over to the...

Found the issue guys.  I was not checking the "Possible Owner" setting under the SQL Server Role.  In FailOver Cluster Manager click on left hand side Roles then click on...

@burfos,

Yes the node is already included in the cluster.  Also, yes to checking if server name, ip address, disks are all checked for "Possible Owners".

Found more detailed error message as described above?  I have read that this message is because the "Possible Owners" was not selected and I doubled checked an in my case...

The Cluster events has the same error message.  Nothing from SQL Error logs.

User error my bad.  I was using the VM db server name not sql instance name.

thanks for the reminder of this whole process!

Thanks Thom.  Interesting so why even say it's going to be deprecated when they have been saying that since 2008? haha  Appreciate the information guys.

I also tried changing the compatibility level to 2016 and restarted the services and it still did not change.

Which version of SQL? So your saying you have had replica1 (being a 2 node cluster) point to replica2 (being a different 2 node cluster)?   So in this situation...

I'm not sure were on the same page.  This article talks about how you set up Availability Groups with a single Cluster.  I'm wanting to know we set up Availability...

Long story short is i want to be able to shrink tempdb and release the memory from disk. There are many ways to do this, but I'm looking...