It’s here! As part of the general availability of Windows Server 2012 R2 Essentials, I’m releasing a new how-to guide. This guide is for installing Windows Server Update Services on Windows Server 2012 R2 Essentials. Windows Server Update Services is a valuable tool in any IT professional’s toolkit, and can be used to manage the distribution of updates to clients, be very useful in low-bandwidth environments where it is not a good idea to have 20 clients downloading the same files 20 times from the internet, and is a great way to get basic reporting about systems.
If you have feedback, either leave it in the comments or send me an e-mail (tom at tomontech dot com). NOTE: I can not provide individualized installation support, I simply don’t have the time.
WARNING: By viewing and / or downloading this guide, you assume all responsibility and liability in case anything goes wrong. You agree that I can not and will not be held responsible for any data loss or other issues resulting from the installation or use of Windows Server Update Services. This guide is intended to be a sample and is not representative of every scenario. Please consult with a qualified professional if you are unsure about any of the steps herein.
To view the guide, click here, or view the embedded version below. To download a PDF copy of this guide, click here.
This post is intended to be a supplement for the Installing WSUS on Windows Server 2012 R2 Essentials guide.
To configure your client workstations to connect to WSUS, it is highly recommended to use Group Policy. Below I have included examples of Group Policy settings and the necessary WMI filters that can be used as a baseline policy in any environment.
The Default Windows Update Settings policy is intended to the base / default policy that is applied to all systems in the domain.
The Windows Update Settings – Servers policy is intended to supplement the default settings and apply server specific installation settings to server OSes. This policy requires the Servers WMI filter.
The Windows Update Settings – Workstations policy is intended to supplement the default settings and apply workstation specific installation settings to workstation OSes. This policy requires the workstations WMI filter.
The following filters will work with Windows 7, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.
|Servers (applies to domain controllers and member servers)
||select * from Win32_OperatingSystem where (Version >= “6.1%”) and ProductType = “2” or ProductType = “3”
||select * from Win32_OperatingSystem where (Version >= “6.1%”) and ProductType=”1″
Might be old news for some, however, in advance of General Availability this week for Windows 8.1 and Windows Server 2012 R2, I wanted to highlight a couple items relating to the new Windows Server Essentials Experience.
From the Release Notes:
· The Windows Server Essentials Experience only works in a single-domain environment that does not include a read-only domain controller. There is no workaround at this time.
· If you install Windows Server Essentials as a virtual machine, and if your server is not connected to the network (or the DHCP service is not available) while running the Configure Windows Server Essentials Wizard, Anywhere Access functionalities (such as Remote Web Access, virtual private networking and DirectAccess) are blocked.
To avoid this, ensure that your server has a network connection when you install Windows Server Essentials as a virtual machine and run the Configure Windows Server Essentials Wizard. If this has already occurred, manually configure the DNS settings.
Today, in a change of heart, Microsoft has released the RTM Windows 8.1 bits to MSDN and TechNet subscribers.
In a blog post published by Steve Guggenheimer, Microsoft notes that they are working through how to best support developers and IT pros as they align to a faster release cadence.
In my opinion, it would have been much better to release the bits to developers and IT pros back around the original RTM timeframe, but this is better than nothing.
For the build curious amongst us, the build string for Windows 8.1 RTM is 9600.winblue_rtm.130821-1623. The SHA1 hashes for the ISO have been posted below along with steps to check the integrity of the downloaded ISO.
Hashes for today’s release:
To run MSCDCRC against an ISO file that you have downloaded follow these steps.
- 1. Download MSCDCRC to the same folder that you downloaded the ISO to. (Click here to download MSCDCRC)
- 2. Open a Command Prompt window and navigate to the folder from Step 1
- 3. Type “MSCDCRC InstallDVD.iso” (without quotes)
- 4. The integrity check will take a few moments to complete. After the check is complete compare the CRC and SHA hashes to the hashes posted above
- 5. If the hashes match then you have successfully downloaded the ISO
In this R2 wave of Windows Server products, Microsoft is taking the time to update its “first server” version, Windows Server 2012 Essentials.
The Essentials SKU historically has been intended to be the entry level server for a small or midsize business. With Essentials R2, Microsoft is extending this feature set into the enterprise. Because the Essentials feature set is now an available role in the Standard and Datacenter editions of Windows Server 2012 R2, companies with more than 25 users can backup their PCs, seamless integrate with cloud services or on-premise Exchange servers, and provide remote access to company data.
Besides the Essentials features now being available as a role, there are number of additional new features.
- Full PC Restore over the network is now supported
- Mobile Devices can be managed in the dashboard using Exchange ActiveSync
- Quotas can be set on shared folders in the dashboard
- The client connector can trigger a VPN connection so clients can always be connected to the network
- Now supported as a member server in a domain
- Health monitoring and reporting is now built-in
- Remote Web Access theme now follows in the style of SkyDrive
What I like about this release is that its the small things that really make it all come together. There is now an option in configuring the remote access website to allow direct RDP access to the server or only access to the dashboard. PXE boot restores of client computers is awesome and is something I’ve been asking for since the Windows Home Server days. The dashboard now lets customers integrate with Office 365, Windows Intune, and Windows Azure Backup. BranchCache is now supported as well. If a company has multiple servers, the connector will now let users switch between them.
These are just a few of the many examples of what Microsoft has brought to the R2 release of Windows Server 2012 Essentials. Over the next few days and weeks I’ll be posting some tours of the new functionality.
If you’ve been keeping up with Microsoft related news, you’ve probably heard that Microsoft announced new features in Windows Azure, announced Windows Server 2012 R2, System Center 2012 R2, and SQL Server 2014. For many of these products, they are here less than a year after their predecessors. This is a huge accomplishment for Microsoft.
According to a blog post published by Brad Anderson, Corporate Vice President for Windows Server and System Center, Microsoft is able to do this because they are building for the cloud first.
By building for the cloud first, Microsoft says that they are able to do couple things:
- Battle harden what is built. By deploying in Windows Azure first, Microsoft can ensure that they are delivering a solid product both in the cloud and on-premise.
- Unify the planning and delivery across multiple products. With this wave of releases, Microsoft has brought together Windows 8.1, Windows Server 2012 R2, System Center 2012 R2, Windows Azure, and Windows Intune.
What this means for you as a Microsoft customer is that scenarios are being designed for better integration end-to-end, using real world feedback from people like you and I, and validated in the Windows Azure cloud.
It’s an exciting and interesting time for both Microsoft and its customers. I’m encouraged by the products I’m seeing and the scenarios that are being unlocked.
Microsoft has released the public preview of Windows Server 2012 R2 Essentials. Windows Server 2012 R2 Essentials is Microsoft’s “first server” solution.
Included in Windows Server 2012 R2 Essentials are:
- Backup of client computers
- Support for Windows 8 and Windows 8.1 File History
- Support for Storage Spaces
- Remote Web access to files, folders, and computers
- Remote Domain Join
- New Modern-style app for Windows 8 and Windows 8.1 for accessing files and folders stored on the server
- Integration with Office 365 or on-premise Microsoft Exchange
- Improved dashboard
- and more!
To download the preview of Windows Server 2012 R2 Essentials, go to http://technet.microsoft.com/en-us/evalcenter/dn205288.aspx
For additional resources go to http://technet.microsoft.com/en-us/evalcenter/dn205289
Tonight Microsoft has made available the public preview release of Windows Server 2012 R2. With this release, Microsoft is laying out its vision for what it calls the Cloud OS.
The Cloud OS is the platform that Microsoft is building with the release of Windows Server 2012 R2, System Center 2012 R2, SQL Server 2014 and Windows Azure. The four key tenets of the Cloud OS are:
- Transform the Datacenter
- Enable modern business applications
- Empower people-centric IT
- Unlock insights on any data
New to Windows Server 2012 R2 are such features as:
- Storage Tiering within Storage Spaces
- Software-defined networking
- Virtual IP Address management
- Windows Powershell 4.0
- Windows Server Essentials Experience
To get started with the Windows Server 2012 R2 Preview, go to http://technet.microsoft.com/en-us/evalcenter/dn205286.aspx
Happy New Year everyone! I am pleased to announce that Microsoft has chosen me as a 2013 Most Valuable Professional. It is a real honor, I’d like to thank Microsoft for selecting me, and I look forward to working with the community and my fellow MVPs in the year ahead.
I thought I’d share something that I ran into after I installed the Office 2013 Customer Preview on a Windows 8 system.
Before Office 2013 was available, I’d been using the Mail Metro-style app. After I installed and configured Outlook 2013 I noticed something strange. When I’d click on e-mail addresses in messages from Outlook 2013, I’d be prompted to either open the Mail app or use them in Outlook 2013. This got annoying fast. Fortunately, there is an easy fix.
From the start screen, show Charms (either swipe or press WinKey-C) and click Search. Search for “default.” Click on Default Programs.
Click on Set your default programs
Click on Microsoft Outlook and then click on Set this program as default