When you configure your first DirectAccess server in an Active Directory domain, the wizard will automatically create for you two Group Policy Objects. One of these policies applies to the DirectAccess servers and the other to the DirectAccess clients. I’m in the process of setting this up on my Windows Server 2012 R2 Essentials server so my server is latest and greatest as far as operating system version goes and even to date, it appears that the WMI Filter created for the Group Policy Object has not been updated.
If you are running Windows Server 2008 R2 servers and you find yourself randomly being disconnected from RDS (Remote Desktop Services) sessions on your servers, or sometimes find your servers completely inaccessible you could be impacted by an issue as a result of servicing order (AKA, the order in which you install Windows Updates). The issue effects servers running Windows Server 2008 R2 with Service Pack 1 and with KB2667402 (Update for Terminal Service Denial of Service Vulnerability).
For companies (or homes) using roaming profiles and folder redirection, Microsoft gave you are great new feature in Windows Server 2012 called Primary Computer. This feature hasn’t been talked about that much although it really should have been. The Primary Computer feature allows you to define the primary computer for a user in Active Directory on a user object. Once applied to a user account it prevents the distribution of their roaming profile on non-primary devices and for folder redirection, disables the ability to sync the folders with Offline Files for non-primary devices.
Windows Server 2012 R2 has some nice new features and improvements on existing features for users of Storage Spaces so there is a definite appeal for users of Windows Server 2012 to want to upgrade to Windows Server 2012 R2. If you opt to do an in-place upgrade to preserve your existing Storage Spaces so that you can get your service up and running with the hope of being able to use them straight off the bat in Windows Server 2012 R2, you may encounter an error Read-only by user action and you need to perform some corrective steps to use them again.
With each new release of Windows client and server operating systems nowadays, comes an update required to allow your on premise KMS host to activate those clients using volume license activation.
After the general availability on Windows 8.1 Enterprise client and Windows Server 2012 R2, Microsoft released the update for KMS host for Windows Server 2008, 2008 R2 and 2012 to allow these down level operating systems to activate the latest and greatest.
Today, I was looking at an issue where one of my clients at home was reporting that the internet connection was unavailable yet other clients were working perfectly fine. The client in question was a Surface Pro tablet running Windows 8.1. This issue turned out to be the Routing and Remote Access PPP RAS Adapter registering in my Windows Server 2012 Essentials domains’ DNS in addition to my local network adapter. Here’s how to spot the issue and to resolve it.
As all good IT Pros have done, I’ve upgraded my home client computers from Windows 8 to Windows 8.1. You have upgraded your machines to Windows 8.1 right?
As I frequently proclaim and preach on here, I run Windows Server 2012 Essentials on my home network, acting as my DNS Server, DHCP Server in addition to the out of the box features that you can get from Windows Server 2012 Essentials like roaming profiles, folder redirection, automated computer backups and network file sharing (all of which I use).
When I was building out a test environment this week to practice how I might migrate from Windows Server 2012 Essentials to Windows Server 2012 R2 Essentials without the benefit of a second server with 19TB of available storage to hand (how many homes do have 19TB of storage let alone a spare 19TB) I was experiencing an issue.
My attention was brought to a greenbutton.com (http://www.greenbutton.com/blog/index.php/2013/10/30/why-windows-azure/) today when it was tweeted by @WindowsAzure (https://twitter.com/WindowsAzure/status/400669888823697408) in which the author, Dave Fellows speaks of how they believe Windows Azure is going to overtake Amazon as the leader in cloud computing within two to three years.
Microsoft have today released KB2887595 which is a 199.7 MB rollup update for Windows 8.1, Windows 8.1 RT and Windows Server 2012 R2.
You can see the release notes for the update and the updates included within it at http://support.microsoft.com/kb/2887595. The update looks tasty including one update which sounds of interest for users of roaming profiles which addresses incompatibility issues between profiles initially created on earlier versions of Windows (KB 2890783 http://support.microsoft.com/kb/2890783).
As part of the project I’ve been working on for the last six months to deliver a new public website (hint www.primark.com) using Windows Azure we needed to be able to monitor the site performance and alert on warning and critical thresholds for certain counters. At the start of the project, our intention was to use SCOM (System Center Operations Manager) as the cleanest way to get data out of Windows Azure but by the time we went live two weeks’ ago, Microsoft had made available the Windows Azure Alerts feature preview.