Currently, the AD team is testing the integration of Windows 8, 8.1 and Server 2012, 2012 R2 into the ACCESS domain. Below are some of the problems the team has encountered and are working to resolve. While the team does not currently support Windows 8, 8.1, 2012 and 2012R2 in the ACCESS domain, units are encouraged to begin testing.
- Problem 1: Kerberos Authentication in Windows 8, 8.1, 2012 and 2012 R2: Standalone and in External Kerberos Realm Trusts. Windows 8, 8.1, 2012 and 2012 R2 erroneously receives enctype mismatch errors when encrypting traffic to the Kerberos server.Workaround: Use userid@domain for all authentication attempts for services including, but not limited to, ACESS domain, PASS, and UDrive.Resolution: The team currently has a ticket open with Microsoft to resolve the issue.Update as of August 28, 2013: Resolution: Microsoft has identified the issue as an undocumented security fix to the network logon service that is upper casing the realm. The AD team is continuing to work with Microsoft to develop a patch.Update as of March 10, 2014: Resolution: Microsoft issued a hot fix for Windows 8 and Server 2012, this hotfix is only for Windows 8 and Server 2012. We expect a hotfix for Windows 8.1 and Server 2012 R2 by April 2014. http://support.microsoft.com/kb/2913811
- Problem 2: Windows Software Update Services (WSUS), by default, does not support Windows 8 clients.Resolution: Microsoft has released a patch for both the Windows Update Server and the Administrative console.Note: If you install the patch on your Windows Update Server, but not your Administrative client, Windows 8 machines will report as Windows XP machines on the Administrative client console.
The default Powershell script language for Windows 8 and Server 2012 is version 3. Older Powershell scripts may not work due to this change.
Using Powershell Version 2 in Windows 8 and Server 2012:
- Needs .net 3.5 installed and a shortcut to force the machine to use Powershell 2
- Step 1: Right click to create a new shortcut
- Step 2: Type the location for the item: PowerShell -Version 2
- Step 3: Type a name for this shortcut: PowerShell2
Questions, comments, and requests for assistance may be directed to the Windows Active Directory Team (email AD team).