TOTD: How to turn off VMM Console auto-connect

Hi, folks!

Here is the new tip of the day with a little trick inside that can save your time.

VMM Console has an ability to auto logon to the selected VMM server with predefined credentials. It works like a charm and is a really useful feature.
But if you have more than 1 role in VMM (for instance, you are assigned to 2 different roles/tenants and don’t have a global administrator rights) auto-connect can cause some inconveniences during connection.

VMM console settings are located in registry (HKCU hive)  and with auto-logon enabled console uses the last role/VMM server address as targets.
To connect to another instance and cloud (or in some other cases) we need to turn off auto-connection (‘cause VMM won’t show you drop-list with assigned roles as available for choosing).

Unfortunately, you cannot change this behavior from GUI (VMM starts connection without any timeouts on it’s execution)..but PowerShell and registry can help us. Update: see the comment from Michiel 🙂

To quickly revert auto-connect settings back to default just run these lines from PS:

#Path for AutoConnect string key
$path='HKCU:\Software\Microsoft\Microsoft System Center Virtual Machine Manager Administrator Con

#Turns off AutoConnect in VMM Console
Set-ItemProperty -Path $path -Name AutoConnect -Value $false

Note: administrator rights are not required

Gallery :

Weekly News Digest | Windows Server 2016 Scalability and more

Windows Server 2016 compute maximums

The new post in Windows Server blog is published on 08/25 and confirms the following scale changes in Windows Server 2016:


So, Windows Server 2016 delivers the new-leading scalability to virtualize any and every workload without any exception.

What about vSphere 6.0? vSphere 6.0 maximums are far short of the WS. But I’m almost sure for 99% VMware will update their maximums as soon as possible (next major release). May be we will see updated vSphere 6.0 scalability before WS 2016 RTM.  HA scale digits are the same for both  WS/vSphere so far (FT/resource pools are excluded)

The difference between vSphere 6.0 and Windows Server 2016 compute values are below:


*12 TB is supported on specific OEM certified platform

New VMware migration offer for Windows Server 2016

If you are really interested in Windows Server 2016 or plan migration from VMware, Microsoft has a special offer to you.

From September 1, 2016, through June 30, 2017, customers who switch workloads from VMware to Hyper-V can get free Windows Server Datacenter licenses when buying Windows Server Datacenter + Software Assurance. That ultimately means customers only pay for Software Assurance, which provides multiple benefits.

To be eligible for the VMware migration offer, customers must follow these steps:

  • Step 1: Engage your account executive or sales rep to begin the process.
  • Step 2: Identify virtualized workloads to migrate and specify the Windows Server Datacenter cores required.
  • Step 3: Provide your account executive proof of eligibility. (Offer applicable to customers migrating from VMware to Microsoft).
  • Step 4: Engage your partner to start the migration process.
  • Step 5: Receive free Windows Server Datacenter licenses with Software Assurance and pay only the cost of Software Assurance to kick start your migration.

Check out the new VMware Shift website for more detailed information as well as technical comparisons and more reasons to choose Microsoft over VMware.

Continue reading “Weekly News Digest | Windows Server 2016 Scalability and more”

%d bloggers like this: