Ignite 2016 Key Announcements

Windows Server 2016 and System Center 2016 are GA

Windows Server 2016 is available for evaluation and will be on the October price list. Volume licensing customers will be able to download fully licensed software at General Availability in mid-October.

Windows Server 2016 also comes with the built-in support of containers and commercial version of Docker engine without additional charge!

System Center 2016 Evaluation is here . What’s new in System Center 2016?

UPDATE (10/12): WS2016 and SC2016   became available @MSDN and @Azure + UR1 for System Center 2016 and CU for WS2016 + https://support.microsoft.com/en-us/kb/3192366

Windows Server 2016 and System Center 2016 Ignite Announcement+ today MS has published pre-configured VHDs to help you quickly evaluate new SC 2016 features

See my previous posts to get what’s new in Windows Server 2016 (Hyper-V, RDS, MultiPoint)  and also check the updated technet articles : WS 2016 and SC 2016

TIP: I’d not recommend to use evaluation version in production. Wait while fully licensed media becomes available.

Azure Stack Technical Preview 2

In fact, Azure Stack TP2 announcement was described earlier in this blog post (TP2 rolled out for some “vip” customers). At Ignite MS confirmed GA for Azure Stack TP2.

And now you can try this new preview here + read what’s new in Azure Stack TP2 and review Azure Stack Architecture

More info about this announcement: New ideas, new solutions, new technical preview of Azure Stack

SQL Server supports Storage Spaces Direct

SQL Server 2016 will support deploying databases on Storage Spaces Direct (S2D).To build up S2D you need from 2 to 16 servers with local-attached SATA, SAS, or NVMe drives and dedicated network between hosts (10+GbE with RDMA is recommended)

storage-spaces-direct-with-sql-server

Continue reading “Ignite 2016 Key Announcements”

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
sole\Settings\Shared'

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

Note: administrator rights are not required

Gallery :