Skip to main content

How To Migrate Windows Server 2008 R2 Active Directory Domain Services To Windows Server 2012

fonte:http://www.elmajdal.net/WindowsServer/How_To_Migrate_Windows_Server_2008_Active_Directory_Domain_Services_To_Windows_Server_2012.aspx

 

To perform the below steps, you will need to use a domain account which is member member of Domain Admins and Enterprise Admins Groups and member of the Schema Admins group. I will be using the domain Administrator account which is already a member of all these groups.

Migrating your Domain Controller from Windows Server 2008 to Windows Server 2012 undergoes a few major steps, which are discussed in details below :

Step 1 : Check Forest and Domain Functional Level

  1. The Forest Functional level and Domain Functional Level must be at least Windows Server 2003

  2. To Check The Functional Levels, read my article : How to Raise the Forest and Domain Functional Levels in Windows Server 2008/R2

Step 2 : Preparing Active Directory Schema

The schema has to be upgraded and prepared for Windows Server 2012. To do this you have to run the adprep command.

  1. Insert the Windows Server 2012 /R2 DVD into the DVD drive of the Windows Server 2008 / R2 Domain Controller

  2. Open command prompt in administrative mode, and type adprep /forestprep and press enter.

  3. Open the Directory of the DVD drive and navigate to adprep directory and then type : adprep /forestprep

    You will receive a warning that all active directory domain controllers in the forest must be running at least windows server 2003. click c  andEnter to confirm and continue.

    Adprep will successfully update the forest

  4. Then type adprep /domainprep and press enter

Step 3 : Install Windows Server 2012 and join it to the Windows Server 2008 Domain

  1. For Installing Windows Server 2012, read this article :  How To Install Windows Server 2012

  2. For Joining Windows Server 2012 to the domain of Windows Server 2008, read this article : How To Join Windows Server 2012 to a Domain

Step 4 : Setting Up Additional Active Directory Domain Controller With Windows Server 2012

By now you already have your Windows Server 2008 Domain Controller, and you have installed Windows Server 2012 and is now a domain member. Now we need to introduce our first Windows Server 2012 domain controller in our network. This has been discussed in a previous article, read it here :Setting Up Additional Active Directory Domain Controller With Windows Server 2012

Step 5 : Transferring the Flexible Single Master Operations (FSMO) Role

You have your Windows Server 2008 Domain Controller ( in my lab its called : ELMAJDAL-DC ) and have an additional Windows Server 2012 domain controller ( in my lab its called : ELMAJDAL-DC13). To complete the migration , we need to transfer 5 FSMO roles to the new domain controller.

The five FSMO roles are:

  • Schema Master

  • Domain Naming Master

  • Infrastructure Master

  • Relative ID (RID) Master

  • PDC Emulator

To check who is currently holding FSMO, run the following command : netdom query fsmo

The FSMO roles are currently with the Windows Server 2008 R2 domain controller : ELMAJDAL-DC

The FSMO roles are going to be transferred, using the following three MMC snap-ins :

  • Active Directory Schema snap-in : Will be used to transfer the Schema Master role

  • Active Directory Domains and Trusts snap-in : Will be used to transfer the Domain Naming Master role

  • Active Directory Users and Computers snap-in : Will be used to transfer the RID Master, PDC Emulator, and Infrastructure Master roles

Lets start transferring the FSMO roles.

  • Using Active Directory Schema snap-in to transfer the Schema Master role

You have to register schmmgmt.dll in order to be able to use the Active Directory Schema snap-in

  1. Open Command Prompt in administrative mode and type regsvr32 schmmgmt.dll

  2. Open Microsoft Management Console , mmc

  3. Click File > then click Add/Remove Snap-in…


  4. From the left side, under Available Snap-ins, click on Active Directory Schema, then click Add > and then click OK

  5. Right click Active Directory Schema, then click Change Active Directory Domain Controller…


  6. From the listed Domain Controllers, click on the domain controller that you want to be the schema master role holder and then click on OK

    You will receive a message box stating that the schema snap-in is not connected to a schema operations master. That is for sure, as we have not yet set this Windows Server 2012 domain controller as a Schema Master role holder. This will be done in the next step. Click OK


  7. In the console tree, right click Active Directory Schema [DomainController.DomainName], and then click Operations Master…


  8. On the Change Schema Master page, the current schema master role holder will be displayed ( ex. ELMAJDAL-DC.ELMAJDAL.COM) and the targeted schema holder as well (ex. ELMAJDAL-DC13.ELMAJDAL.COM). Once you click Change, the schema master holder will become
    ELMAJDAL-DC13.ELMAJDAL.COM
    , click Change

    Click Yes to confirm the role transfer

    The role will be transferred and a confirmation message will be displayed. Click OK

    Then click Close, as you can see in the below snapshot, the current schema master is ELMAJDAL-DC13.ELMAJDAL.COM which is the Windows Server 2012 DC


  • Using Active Directory Domains and Trusts snap-in to transfer the Domain Naming Master Role

  1. From the Start Screen, open the Active Directory Domains and Trusts

  2. Right click Active Directory Domains and Trusts, then click Change Active Directory Domain Controller…


  3. From the listed Domain Controllers, click on the domain controller that you want to be the Domain Naming master role holder and then click onOK


  4. Right click Active Directory Domains and Trusts, then click Operations Master…


  5. On the Operations Master page, we are going to change the Domain Naming role holder from ELMAJDAL-DC.ELMAJDAL.COM toELMAJDAL-DC13.ELMAJDAL.COM, Click Change

    Click YES to confirm the transfer of the Domain Naming role. The role will be transferred and a confirmation message will be displayed. ClickOK , then click Close


  • Using Active Directory Users and Computers snap-in to transfer the RID Master, PDC Emulator, and Infrastructure Master Roles

  1. From the Start Screen, open the Active Directory Users and Computers console

  2. Right click your domain and select Operations Masters

  3. In the Operations Masters window, ensure the RID tab is selected.

    Click the Change button. Select Yes when asked about transferring the operations master role. Once the operations master role has successfully transferred, click OK to continue.

  4. Ensure the Operations Master box now shows your new Windows Server 2012

  5. Repeat steps 4 to 6 for the PDC and Infrastructure tabs.

    >>
    >>

    Once completed, click Close to close the Operations Masters window.

If you would like to check if the roles were properly transferred, open command prompt and type: netdom query fsmo. If you see your new server listed in each role, you have successfully transferred all of your FSMO roles to the new server

Related Articles

How To Join Windows Server 2012 to a Domain

How to Raise the Forest and Domain Functional Levels in Windows Server 2008/R2

Setting Up Additional Active Directory Domain Controller With Windows Server 2012  

WSUS not working on SBS2011

http://www.sbsfaq.com/wp-trackback.php?p=3331

**** rimuovere \\ da filtro isapi ****

WSUS not working on SBS2011

I was investigating a fault today for a client – their new SBS 2011 server had stopped working with WSUS.  As my investigation went on I found that this issue would also affect the SBS Client Connect as well as other web based applications on this server.

The SBS console was reporting “An error occured while retrieving updates information.” as the screen below shows.

image

I did some digging and found that the WSUS console was broken too.

The event logs showed the error below.

Source: IIS-W3SVC-WP

Event ID: 2274

ISAPI Filter ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

Look closely and you will notice above that there’s a double \\ in the path name.

image

Once I’ve modified it to remove the double \\ and done an IISRESEt – it’s all working just fine.  The picture below shows the problem line AFTER I’ve modified it.

image

Reinstall and Reset TCP/IP (Internet Protocol) in Windows with NetShell

fonte:https://techjourney.net/reinstall-and-reset-tcpip-internet-protocol-in-windows-with-netshell/

If you facing network connection issue, or more accurately unable to access or connect to Internet or network problem in Windows operating system such as Windows 2003, Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server and etc, you can try to reinstall and reset TCP/IP stack or Internet Protocol, one of the core component of the operating system, which cannot be uninstalled.

Again, with a corrupt TCP/IP stack, the same woes may happen – unable to establish a connection to the server, unable to load a web page, unable to browse and surf the Internet, even though network connection to broadband router or wireless router appear to be OK.

When all means run out, try to reinstall the IP stack with NetShell utility. NetShell utility (netsh) is a command-line scripting interface for the configuring and monitoring of Windows networking service.

To reinstall and reset the TCP/IP stack (Internet Protocol) to its original state as same as when the operating system was first installed, simply use the following command in a Command Prompt (Cmd) shell. In Windows Vista or newer, open an elevated Command Prompt with Administrator privileges instead. A log file name must be specified where actions taken by netsh will be recorded on newly created or appended if already existed file..

netsh int ip reset [ log_file_name ]

Example:

netsh int ip reset c:\resetlog.txt

Restart the computer once the command completed.

The command will remove all user configured settings on TCP/IP stack and return it to original default state by rewriting pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol. The registry keys affected are:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

and

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCP\Parameters\

It’s also possible to use the Easy Fix wizard provided by Microsoft to reset TCP/IP automatically.For Windows 8.1, Windows 8, Windows RT, Windows 7, Windows Server 2012R2, Windows Server 2012, Windows Server 2008 R2: MicrosoftEasyFix20140.mini.diagcab

For Windows Vista, Windows XP, Windows Server 2008 or Windows Server 2003: MicrosoftFixit50199.msi

altri riferimenti:

Repair and Reset Windows Vista TCP/IP Winsock Catalog Corruption

Windows Server Backup FilterManager Event id 3

Quando si utilizza Windows Server Backup si potrebbe incorrere in questo errore:

Gestione filtri: collegamento al volume ‘\Device\Harddisk10\DR28’ non riuscito. È necessario riavviare il sistema affinché il volume sia disponibile per i filtri. Stato finale: 0xc03a001c.

Per risolvere il problema si può usare il tool DevNodeClean
 (http://bytesolutions.com/Support/Knowledgebase/KB_Viewer/ArticleId/35/DevNodeClean-Download-remove-phantom-storage-device-nodes.aspx)