Possible failures after upgrade-upgrade from Windows 2012 to 2016 case 3

3.1 Active directory domain controllers cannot use

Symptom: Active Directory cannot be accessed, Active Directory Users and Computers cannot be used, and domain controllers cannot be found.

Workaround: Restart the AD DS service.

This should be considered a serious failure, after I have tested, if the upgrade after the Windows Server 2016 domain controller, after the restart, the AD DS service status is "started", but the ad service cannot be used, can only be manually restarted. It is not possible to set the AD DS service to "delayed startup". In my previous domain controller upgrade, I have never encountered a similar problem.

At the moment I just upgraded Windows Server R2 in one environment, the other unit production environment has not been upgraded, the problem is accidental or all systems have, still unknown.

(1) After upgrading the current environment to Windows Server 2016, when checking to the DFS service, it is found that both "namespace" and "copy" are Red "X" numbers, as shown in 3-1.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/8E/97/wKioL1jGWG-ygVxPAAFoM26KUOI013.png "/>

Figure 3-1 Dfs is not available

(2) When you check Active directory Users and Computers, you are prompted with "No naming information found," as shown in 3-2.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/98/wKiom1jGWG_BxLC5AACwlY4voo0021.png "/>

Figure 3-2 naming information not found

(3) In services, right-click Active Directory Domain Services, and in the shortcut menu that pops up, choose Restart, as shown in 3-3.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/97/wKioL1jGWHCDrVRpAAMIj0CVrI4818.png "/>

Figure 3-3 Restarting ad DS

(4) in the "Stop Other Services" dialog box that pops up, click the "Yes" button, as shown in 3-4.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/98/wKiom1jGWHGDzuTWAAA5ed6fGio570.png "/>

Figure 3-4 Stopping other services

(5) After the restart of AD DS and its associated services, Active directory is normal and DFS is back to normal, as shown in 3-5.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8E/98/wKiom1jGWHGzq1KuAAF7GWezSF0814.png "/>

Figure 3-5 Active Directory Users and Computers are normal

After upgrading to Windows Server 2016, the RD licensing manager needs to be reactivated, opening the RD Licensing manager to see the "LS is upgraded, requires reactivation" hint, as shown in 3-6.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/97/wKioL1jGWHLDZU1FAACKvYOywts662.png "/>

Figure 3-6 prompting for reactivation required

Right click on the server and select "Advanced → reactivate Server" in the popup shortcut menu shown in 3-7.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8E/97/wKioL1jGWHLxlnPHAADWlv-2fbk243.png "/>

Figure 3-7 reactivating the server

In the Required Information dialog box, select "License server has been upgraded" in the "Cause" drop-down list, as shown in 3-8.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/8E/98/wKiom1jGWHKBbssaAABcRbcPdz4760.png "/>

Figure 3-8 The license server has already been upgraded

3.2 File Sharing server cannot be used

After the upgrade, shared services for mh09 (member servers) cannot be used (the Shared Folders service provided by MH09 is not available on other computers in the network). The check found that Network discovery is not enabled.

(1) Open Network and Sharing Center, click the "Change advanced sharing Settings" link, as shown in 3-9.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8E/98/wKiom1jGWHOh78alAACstsw2kTI857.png "/>

Figure 3-9 Changing advanced sharing settings

(2) In Network Discovery, see the current set to "Turn off Network Discovery", select "Enable Network Discovery" and click "Save Changes" as shown in 3-10. After setting up, click Change advanced sharing settings again to discover that the settings are still turned off network discovery and that network discovery cannot be enabled.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/8E/97/wKioL1jGWHPCMa-mAADU89R82xU451.png "/>

Figure 3-10 Enabling Network Discovery

The following services have been checked for services that do not start (the Startup type is disabled).

Function Discovery Resource Publication

SSDP Discovery

UPnP Device Host

Change these three service startup types to Automatic (delayed start), 3-11, and then start the three services and turn on change advanced sharing settings again, and you can see that enable Network Discovery is enabled.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/98/wKiom1jGWHPSM1C0AABtzXJvr_4825.png "/>

Figure 3-11 Changing the Startup type

3.3 Upgrade domain functional level

Finally, after all the issues have been resolved, switch to the domain controller to elevate the domain functional level to Windows Server 2016.

(1) In Active directory Users and Computers, right-click the domain controller, and in the shortcut menu that pops up, choose Raise Domain functional level, as shown in 3-12.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/8E/97/wKioL1jGWHTx5pXIAAJ6u2WqDr8867.png "/>

Figure 3-12 raising the domain functional level

(2) in the Raise Domain functional Level dialog box, select Windows Server 2016 in the Select available domain functional level drop-down list, and then click the Promote button, as shown in 3-13.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8E/97/wKioL1jGWHSi6Mm-AABG1goPCM4590.png "/>

Figure 3-13 raising the domain functional level

(3) Click the "OK" button in the Pop-up dialog box, 3-14 is shown.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8E/98/wKiom1jGWHWTFLdPAACPASGqStI534.png "/>

Figure 3-14 Determining the elevation

(4) Click the "OK" button in the Pop-up dialog box, 3-15 is shown.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/8E/98/wKiom1jGWHXQsD9wAAE9LDLGbys693.png "/>

Figure 3-15 Ascension Complete

This article from "Wang Chunhai Blog" blog, reproduced please contact the author!

Possible failures after upgrade-upgrade from Windows 2012 to 2016 case 3