650. Cách sửa lỗi không thể thêm Roles và Feature cho Server 2012 R2

Nguồn:650. Cách sửa lỗi không thể thêm Roles và Feature cho Server 2012 R2

Windows Server 2012 prompts for a restart when installing WSUS or RDS

PROBLEM

Adding the Remote Desktop Services role or the Windows Server Update Services role fails with the error:

The operation cannot be completed, because the server that you specified requires a restart.

Restarting the server provides no solution.

SOLUTION

The solution is to grant the 'log on as a service' right to some addition built in accounts. Start the Group Policy Management Console on your management PC (see the Remote Server Administration Tools download page at Microsoft).

Open the Default Domain Controllers Policy or your specific server management policy. Open the Computer Configuration –> Policies –> Windows Settings –> Security Settings –> Local Policies –> User Rights Assignment branch and then double click the 'Log on as a service' setting. Add the IIS_WPG, NETWORK, NETWORK SERVICE, and SERVICE accounts (via the Browse option).

Once these settings have been applied the server needs to update to the current Group Policy version. On the server command line you can type

gpupdate /force

Once updated the installation should progress smoothly.

649. Hướng dẫn chuyển domain controller từ Server 2003 qua Server 2012 bằng hình ảnh

Hướng dẫn chuyển domain controller từ Server 2003 qua Server 2012 bằng hình ảnh

Migrating Sever active directory from Server 203 R2 to Server 2012 by video.

Source: https://community.spiceworks.com/topic/304023-adding-server-2012-as-dc-to-server-2003-domain-getting-adprep-error

oh no.

Phần 2: Nguồn: http://blogs.technet.com/b/canitpro/archive/2014/04/02/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx

Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2

Anthony Bartolo

1 Apr 2014 10:04 PM

• 6

With the end of support for Windows XP, Office 2003 and Exchange 2003 now upon us, April 8th 2014 to be exact, attention now turns to Windows Server or specifically Windows Server 2003.  End of support for Windows Server 2003 is currently slated for July 14th 2015 and a great many organizations still utilize said offering as the cornerstone to their infrastructure to this day.  One question to keep in mind though is that with the move on the client end to Windows 8.1, will Windows Server 2003 or 2003 R2 be robust enough to properly enable employees and provide secure access to the plethora of devices in a world now dominated by BYOD?  Alternatively an IT administrator might ponder on the further enablement invoked via the deployment of Windows Server 2012 R2 should it be deployed in said organization.  Lets explore this possibility via the cornerstone of access enablement offered via Windows Server by investigating the evolution of the Active Directory offering now found in Windows Server 2012 R2

As you may know, Active Directory provides authentication and authorization mechanisms as well as framework from within other related services that can be deployed. As an LDAP compliant database, it commonly contains the most used objects such as users, computers, and groups organized into organizational units or OUs by any number of logical or business needs. Group Policy Objects or GPOs are then linked to OUs to centralize the settings for various users or computers across an organization. Part of the quandaries that IT professionals face is taking advantage of nuances provided in Active Directory in newer server offerings such as Windows Server 2012.  As detailed in Pierre's post, "Windows Server 2012 Active Directory – What’s New?", Active Directory provided in Windows Server 2012 R2 is provided impactful enhancements.  Yet some organizations choose not to migrate due to reasons of uncertainty.

This Step-By-Step has been created to assist with that uncertainty and provide guidance for IT professionals looking to migrate their organizations Active Directory offering from Windows Server 2003 to 2012 R2.

Prerequisites

1. Download Windows Server 2012 R2 and create your lab environment. (Instructions can be found here)
2. Complete Step-By-Step: Adding a Windows Server 2012 R2 Domain Controller to an Existing Windows Server 2003 network

Transferring the Flexible Single Master Operations (FSMO) Role

1. Open the Active Directory Users and Computers console on your new Windows Server 2012 R2 computer.
2. Right click your domain and select Operations Masters in the sub menu.
3. In the Operations Masters window, ensure the RID tab is selected.
4. Select the Change button.
   
   
5. Select Yes when asked about transferring the operations master role.
6. Once the operations master role has successfully transferred, click OK to continue.
7. Ensure the Operations Master box now shows your new 2012 R2 Windows Server.
8. Repeat steps 4 to 6 for the PDC and Infrastructure tabs.
9. Once completed, click Close to close the Operations Masters window.
10. Close the Active Directory Users and Computers window.

Changing the Active Directory Domain Controller 

1. Open the Active Directory Domains and Trusts console on your new Windows Server 2012 R2 computer.
2. Right click your domain and select Change Active Directory Domain Controller... in the sub menu.
3. In the Change Directory Server window, select This Domain Controller or AD LDS instance.
4. Select your new 2012 R2 Windows Server.
   
   
5. Click OK to continue.
6. Back in the Active Directory Domains and Trusts window, hover over the Active Directory Domains and Trusts found in the folder tree on the left hand side to ensure the server now reflects your new 2012 R2 Windows server.
7. Right click Active Directory Domains and Trusts found in the folder tree and select Operations Manager... in the sub menu.
8. In the Operations Master window, click Change to transfer the domain naming master role to the 2012 R2 Windows Server.
9. When asked if you are sure you wish to transfer the operations master role to a different computer, click Yes.
10. Once the operations master is successfully transferred, click OK to continue.
11. Click Close to close the Operations Master window.
12. Close the Active Directory Domains and Trusts console.

Changing the Schema Master

1. Open a command prompt in administration view on your new Windows Server 2012 R2 computer.
2. On the command prompt window, enter regsvr32 schmmgmt.dll and hit enter.
3. Once completed successfully, click OK to close the RegSvr32 window.
   
   
4. Close the command prompt.

Add the Active Directory Schema Console from MMC

1. Open a MMC console on your new Windows Server 2012 R2 computer.
2. Click File > Add/Remove Snap-in...
3. In the Add or Remove Snap-ins window, select Active Directory Schema and click the Add > button.
   
   
4. Click OK to continue.

Change the Schema Master

1. In the same MMC console, right click Active Directory Schema and select Change Active Directory Domain Controller... in the sub menu.
2. In the Change Directory Server window, select This Domain Controller or AD LDS instance.
3. Select your new 2012 R2 Windows Server.
4. Click OK to continue.
5. A warning will appear stating that the Active Directory Schema snap-in in not connected. Click OK to continue.
6. Hover over the Active Directory Schema folder in the folder tree to ensure the new Windows Server 2012 R2 computer is shown. 
7. Now right click Active Directory Schema and select Operations Master... in the sub menu.
8. In the Change Schema Master window, click Change to transfer the schema master role to the 2012 R2 Windows Server.
9. When asked if you are sure you wish to transfer the schema master role to a different computer, click Yes.
10. Once the schema master is successfully transferred, click OK to continue.
11. Click Close to close the Change Schema Master window.
12. In the MMC, click File > Exit.
13. When asked to save the console, click No.

 Once completed, open the Active Directory Users and Computers console to verify that the Active Directory database successfully replicated to your new Windows Server 2012 R2 computer.  Be aware that the database replication may take some time depending on the number of objects in Active Directory.

Removing the 2003 Windows Server from the Global Catalog Server

1. Open Active Directory Sites and Services on your new Windows Server 2012 R2 computer.
2. Expand the Sites folder, then the Default-First-Site-Name folder, then the Servers folder.
3. Expand both listed servers. One should be your new 2012 Windows Server and one should be you 2003 Windows Server.
4. Right click NTDS Settings found under your old 2003 Windows Server.
5. In the sub menu, select Properties.
6. Under the General Tab, unselect Global Catalog and then click the Apply button.
7. Click OK to continue.
8. Close the Active Directory Sites and Services window.
9. Verify that your new 2012 R2 Windows Server is running the FSMO role by opening the command prompt in Administrative view and running the following command: Netdom query fsmo.
10. In the Network and Sharing Center, be sure to change the Preferred DNS server to match the Alternate DNS server, then delete the IP address listed under the Alternate DNS server should it currently be pointed to the old 2003 Windows Server.

All that's left is to demote the old 2003 Windows server by first adding the new 2012 R2 Windows Server as the Primary DNS, followed by running DCPROMO to demote the old 2003 Windows server. Be sure to also visit Microsoft Virtual Academy created to further enable IT professionals in regards task such as migrating to Windows Server 2012 R2.