You are currently reviewing an older revision of this page.
Go to current version
Some organizations join Windows 8 client computers to domains that have domain controllers that run earlier versions of Windows Server, such as Windows Server 2003. Windows 8 domain join with domain controllers that run Windows Server 2003 (or later versions of Windows Server) is tested and supported. However, some Windows 8 features might require additional configuration or may not be available. This topic covers some of those issues and other best practices for managing Windows 8 clients that are joined to downlevel domains. Users are encouraged to edit this topic to share their own experiences and suggestions for running Windows 8 in downlevel domains.
  1. Storing BitLocker and Trusted Platform Module (TPM) information in Active Directory (AD) requires a schema update. It is possible to update the AD schema (by running Adprep /forestprep) without installing a new domain controller. For more information about storing BitLocker data in AD, see Backing Up BitLocker and TPM Recovery Information to AD DS. For more information about extending the AD schema to support BitLocker data storage, see Running Adprep.exe.
  2. In Windows 8, Internet Explorer Maintenance (IEM) settings have been deprecated in favor of Group Policy Preferences, Administrative Templates (.admx), and the Internet Explorer Administration Kit 10 (IEAK 10). For more information about which tool to use as a replacement for different IEM settings, see Appendix B: Replacements for Internet Explorer Maintenance.
  3. To configure Group Policy settings that apply only to Windows 8 clients, you should manage GPOs using Remote Server Administration Tools (RSAT) for Windows 8.
Revert to this revision