Windows Server 2012 R2 installation notes

1. Obtain Windows Server ISO
   1. We may obtain it at Technet Evaluation Center.
2. Install as usual.  Perform all Windows Update to update to latest version.
3. The evaluation can be used for 180 days.  If you want to convert the Evaluation version to full version, use the below command:
   1. Use this command to check the version:
      • dism /online /get-targeteditions
   2. Use this command to convert to full version
      • dism /online /set-edition:serverdatacenter /productkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /accepteula
   3. It may require a reboot after change the edition.
   4. CD key can be obtained at technet(AVWA) or technet (KMS).
4. After installation, you may find that the network adapter is under "Public" network.  You may want to change it to "Private" network by below command in PowerShell: (please change InterfaceIndex as it differs from server to server.)
   • PS C:\Users\Administrator> Get-NetConnectionProfile
   • 
     
   • Name             : Network
   • InterfaceAlias   : Ethernet
   • InterfaceIndex   : 12
   • NetworkCategory  : Public
   • IPv4Connectivity : Internet
   • IPv6Connectivity : NoTraffic
   • 
     
   • PS C:\Users\Administrator> Set-NetConnectionProfile -InterfaceIndex 12 -NetworkCategory Private
5. If you have enabled Remote Desktop but it cannot be connected, probably it is because your NIC is configured as in "Public".  You can either:
   1. Change it to "Private" network using the above step.
   2. Turn off Windows Firewall
      1. go to: Control Panel - Network and Internet - Network and Sharing Center
      2. At the lower left corner, click "Windows Firewall".
         
      3. At left, click "Turn Windows Firewall on or off"
         
      4. Follow the instruction on screen.
   3. Open an firewall exception for Remote Desktop:
      1. go to: Control Panel - Network and Internet - Network and Sharing Center
      2. At the lower left corner, click "Windows Firewall".
      3. At left, click "Allow an app or feature through Windows Firewall"
         
      4. In the list, find "Remote Desktop".  Make sure the checkboxes for "Private" and "Public" are checked.
         
6. To have "Disk Cleanup" utility inside Windows Server 2012, follow this instruction to enable Disk Cleanup Utility.
   
   
   
   
   By using Disk Cleanup, I am able to delete 200+ MB of Windows Update Files.
     
7. To clean up WinSxS folder
   1. [for Win 7, Win 2008] dism /online /cleanup-image /spsuperseded
   2. [win2012R2 only] [analyse only] Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
   3. [most powerful!!][win2012R2/Win8.1 only] [removes the ability to uninstall any update] Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
8. Remember to enable Telnet Client.
9. Join domain
10. To join as Domain Controller (reference: Interworks Blog)
1. Add AD DS and DNS server role in Server Manager
2. Promo the server as a DC.
   
3. If you encounter "server extended error 8366" during verification of prerequisites, it might be caused by undeleted DC, please try below steps:
   Delete Failed DCs from Active Directory (Petri) 
11. If SYSVOL share is not created, follow KB947022 so that netlogon service will re-create the SYSVOL share.
12. Server Manager by default will only see the local server.  If there is other servers in the domain/network, follow this instruction to manually add servers into Server Manager.
13. To setup Remote Desktop Service, follow this tutor to setup.
    1. Note: the tutor suggested to install SQL 2012 Express on a domain controller.  But my experience is installing SQL on DC generates a lot of error.  The Database Engine cannot be started after installation.  One of the reason is a DC does not have “local” credential for use.  I numerous error, such as “FallBack certificate initialization failed with error code”, “TDSSNIClient initialization failed”, “cannot find e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf” error.  These error gone after when I install on another non-DC error.
    2. Suggest to install with Mixed Authentication.  So that when there is an error, we can use sa account to logon.
14. Setup CA
    1. Install CA role
    2. Push root CA into domain by Group Policy
       1. Export the root CA
       2. Put it into Group Policy