This new build includes new features that enables hybrid datacenter solutions.
The three main features: Hyper-V Containers, Software-defined datacenter capabilities and increase agility and Enhanced management capabilities:
Hyper-V: Now includes an early preview of nested virtualization, along with Direct Device Assignment, and improved PowerShell support for VM upgrades. Nested virtualization can be used in dev and test scenarios and is a key enabling technology for Hyper-V Containers.
- Networking: high availability for the network controller, better East-West load balancing, enhanced container networking, and support for live migration. New: Virtual Machine Multi-Queue to enable 10G+ performance.
- Storage: Storage Spaces Direct to support all-flash configurations with NVMe SSD and SATA SSD devices, and Erasure Coding for increased storage efficiency. Also in this release, support for Storage Health Service provides easier health monitoring and more streamlined operations, with a single monitoring point per cluster. Storage QoS now supports adjusting the normalization size of the algorithm from the current default 8 KB settings. Additional enhancements are designed for increased control, such as maximum bandwidth settings for a VHD/X.
- Security: Enhancements to shielded VMs and the Host Guardian Service are directed toward ensuring readiness for production environments. Just Enough Administration, which limits administrator rights for additional security, has been expanded to domain controllers and server maintenance roles.
Make innovation easier with Windows Server 2016 and System Center 2016 Technical Preview 4.
Core enhancements in System Center 2016 Technical Preview 4 include:
- Advanced software-defined datacenter support for Windows Server 2016 including new technologies such as patching of hosts while provisioning, simplified logical network creation, scale-out file server with Storage Spaces Direct and SAN storage automation, and improved storage monitoring.
- Protecting customer IP through shielded VM’s and Guardian Host deployment and management
- Easy to use monitoring improvements in Operations Manager through data-driven management of alerts and enhanced visualization
Download Windows Server 2016 Technical Preview 4: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview
Download System Center 2016 Technical Preview 4: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-technical-preview
Microsoft and Red Hat announced a partnership that will help customers embrace hybrid cloud computing by providing greater choice and flexibility deploying Red Hat solutions on Microsoft Azure.
Microsoft Azure will become a Red Hat Certified Cloud and Service Provider, enabling customers to run their Red Hat Enterprise Linux applications and workloads on Microsoft Azure. Red Hat Cloud Access subscribers will be able to bring their own virtual machine images to run in Microsoft Azure.
Customers will be offered cross-platform, cross-company support spanning the Microsoft and Red Hat offerings in an integrated way, unlike any previous partnership in the public cloud. By co-locating support teams on the same premises, the experience will be simple and seamless, at cloud speed.
Red Hat CloudForms will interoperate with Microsoft Azure and Microsoft System Center Virtual Machine Manager, offering Red Hat CloudForms customers the ability to manage Red Hat Enterprise Linux on both Hyper-V and Microsoft Azure. Support for managing Azure workloads from Red Hat CloudForms is expected to be added in the next few months, extending the existing System Center capabilities for managing Red Hat Enterprise Linux
In addition, Expanding on the preview of .NET on Linux announced by Microsoft in April, developers will have access to .NET technologies across Red Hat offerings, including Red Hat OpenShift and Red Hat Enterprise Linux, jointly backed by Microsoft and Red Hat. Red Hat Enterprise Linux will be the primary development and reference operating system for .NET Core on Linux.
That’s right Cloud AD as a services. A fully managed domain by Microsoft : Azure AD Domain Services to manage Azure IaaS workloads.
Azure AD Domain Services It’s a cloud based service which gives you a fully Windows Server Active Directory compatible set of API’s and protocols, delivered as a managed Azure service.
You don’t need to provision a Virtual Machine running Domain Controller on Azure as a IaaS anymore and have those domain controllers synchronize to their on-premises Active Directory servers using a VPN/Expressroute connection.
You can now turn on support for all the critical directory capabilities your application and server VM’s need, including Kerberos, NTLM, GROUP POLICY and LDAP.
For scenarios like Disaster Recovery and hybrid cloud deployments, it is just perfect. It means a full value of Windows Server AD in the cloud domain, without having to deploy, manage, monitor and patch domain controllers.
There are many scenarios that can be explored with this new feature.
You can enable Azure AD Domain Services for any existing Azure AD tenant – the same tenant you use with Office 365 or other SaaS applications. Azure AD Domain Services are available now.
For pricing, please check : http://azure.microsoft.com/pricing/details/active-directory-ds/
- You already deployed Azure AD Connect (to sync identity information from the on-premises Active Directory to your Azure AD tenant. This includes user accounts, their credential hashes for authentication (password sync) and group memberships)
- Create the ‘AAD DC Administrators’ group and then add all users who need to be administrators on the managed domain to it. These administrators will be able to join machines to the domain and to configure group policy for the domain.
- Configure the Network. Select or create the Azure virtual network you’d like to make domain services available in. Ensure the following:
- The virtual network belongs to a region supported by Azure AD Domain Services. See the region page for details.
- Ensure the virtual network is a regional virtual network and doesn’t use the legacy affinity groups mechanism.
- Ensure your workloads deployed in Azure Infrastructure services are connected to this virtual network
- Enable Azure AD Domain Services for your Azure AD tenant, by going to the Configure tab of your Directory, selecting Yes on ‘Enable Domain Services for This Domain’, specifying the domain name and selecting the Azure Virtual Network. Click on Save to confirm.
- Update DNS settings for the Azure virtual network to point to the new IP address of the Azure AD Domain Services you just enabled.
- Enable synchronization of legacy credential hashes to Azure AD Domain Services. This is a required step. By default, Azure AD does not store the credential hashes required for NTLM/Kerberos authentication. You need to populate these credential hashes in Azure AD so users can use them to authenticate against the domain.
A few salient aspects of the managed domain that is provisioned by Azure AD Domain Services are as follows:
- This is a stand-alone managed domain. It is NOT an extension of your on-premises domain.
- You won’t need to manage, patch or monitor this this managed domain.
- There is no need to manage AD replication to this domain. User accounts, group memberships and credentials from your on-premises directory are already synchronized to Azure AD via Azure AD Connect.
- Since the domain is managed by Azure AD Domain Services, there is no Domain Administrator or Enterprise Administrator privileges on this domain.
The Cloud approach addresses elastic scale, agility, costs and time to market, by allowing organizations not only to deploy a solution quickly but also to scale up/down based on demand. Cloud adoption is sky rocketing, there’s no doubt about it. However, when it comes to investments in the Cloud, how are you planning and assessing business and IT requirements?
- Is your current IT infrastructure and resources meeting the required business SLA’s?
- How you foreseeing capacity issues?
- Are you connecting IT resources to business outcomes and unifying IT processes with business cycles?
- How does your business maintain the system availability and resilience?
- How are you maximizing the utilization of the resources within your IT infrastructure?
With this whitepaper, we will help you find the answer to those questions, covering the challenges in deployment, management and automation phases with some tips and considerations.
Download the whitepaper
You can also register for Savision’s complimentary webinar, presented by MVP Alessandro Cardoso on Adopting the Cloud. The webinar will be presented by MVP Alessandro Cardoso, and will be co-hosted by Savision’s co-founder and VP of Product Management, Dennis Rietvink.
Register for the webinar:
The addition of the Cloud has truly changed how we monitor in Microsoft solutions. In this whitepaper, Microsoft MVP Cameron Fuller tackles the elephant in the room and answers the question of the relevance of Operations Manager. Find out whether Operations Manager is still relevant in the world of the Cloud
As you probably are aware of, Windows 2016 Server TP2, comes with 2 installation options. You also probably have noticed as well that the graphical user interface (GUI) is no longer an option in a default install on the Technical Preview 2.NOt even Start Menu.
- Windows Server Technical Preview 2 option, will install the server with MinShell (Minimal Shell no GUI). Assuming that you will manage the host remotely you won’t need graphical interface at all and from a security point of view, it is the better option.
- Windows Server Technical Preview 2 (with local admin tools) option, will install the server again with MinShell, but includes Server Manager and the other GUI administration tools, although no desktop experience (traditional desktop), nor start menu.
To install Hyper-V role in the Windows Server Technical Preview 2 (with local admin tools) option, in the Server Manager console, click on Add roles and features and select Hyper-V.
To install Hyper-V role in the Windows Server Technical Preview 2 option :
in the command prompt, type:
PS: > Install–WindowsFeature Hyper-V
Note: If the installation fails due to “The source files could not be found” error, assuming the Windows Server Technical Preview 2 ISO image connected to the DVD drive (D:), type:
Simple as that!
Wireless network does not connect on Windows Server TP2 after enabling Wireless Services and installing Wireless Drivers
Add the Native WiFi Filter SERVICE in the properties of the wireless adapter
To be more specific:
- In the Network and Sharing Center, click on Change Adapter Settings and then on the network connections, select the Wireless Network, right click and select Properties.
2. In the Properties on the Wireless Adapter, click on Install
3. Select Service and click on Add
4. Select Native WiFi Filter and click on OK
5. Done. You will be able to connect to a WiFi connection now.