Archive

Archive for December, 2011

Hyper-V Guests booting to PXE

December 6, 2011 4 comments

To boot to PXE in Hyper-V from an existing Guest operating system:

1-Shut down the virtual machine.

2-Add a legacy network adapter for the Virtual as showing in the figure

 

12

3- Change the boot order to have the legacy network adapter at the top of the boot order, Or noticed the option to install an operating system from a network-based installation server as the following figure.

3

Categories: Hyper-V

Microsoft WDS Error "the service did not respond to the start or control request in a timely fashion"

December 4, 2011 13 comments

If you facing the WDS service stop as the following figure

1 

And after trying to start the service you got this Error as the following figure

2

Just you need the following resolution

Method 1
At the command prompt, type the following command, and then press ENTER:
wdsutil /set-Server /UseDhcpPorts:No

3

Press Enter to see the following

4

Method 2

    Click Start, click Run, type wdsmgmt.msc, and then press OK.
    In the Windows Deployment Services window, expand Servers, right-click the WDS server name, and then click Properties.
    In the Server Properties dialog box, click the DHCP tab.
    Click to select the Do not listen on port 67 check box, and then click Apply.

Note: Method one working 100%

After finish just open the WDS console and start the service it’s will working with you

5

Categories: Uncategorized

Migrating Active Directory Domain Controller from Windows Server 2003 to Windows Server 2008

December 1, 2011 8 comments
In my lab, I have the following:
MACHINE NAME DESCRIPTION SERVICE PACK LEVEL IP Address Architecture
OCI-DC A Windows Server 2003 StandardEdition with Service Pack 2.

This is the domain controller in my lab that I intend to migrate.

SP2 192.168.1.2 X64
OCI-DC2k8 A Windows Server 2008 Enterprise Edition. This is the machine I intend to setup as my new domain controller that will replaceOCI-DC SP1 192.168.1.3 X64

In a nutshell, we will perform the following:

1. Raise Domain Functional Level

2. Prepare your current Windows 2003 Active Directory for Windows

Server 2008 domain controllers.

3. Then, we will need to setup the server OCI-DC2K8 as an additional domain controller.

4. Transfer FSMO roles to the Windows Server 2008 Domain Controller

So lets starts :

1. Raise Domain Functional Level

We need to configure the domain to run in native mode, this is done by:

· On the Windows Server 2003 Domain Controller, run Active Directory User and

Computers snap-in by clicking on Start > Administrative Tools > Active Directory

User and Computers

· Right Click the Domain Name node, then click on Raise Domain Functional Level

clip_image001

If you have Windows 2000 Active Directory domain controllers then choose Windows 2000 native, if you do not have any Windows 2000

Active Directory domain controllers and all of your domain controllers are Windows Server 2003, then choose Windows Server 20003. I don’t have any Windows 2000 Active Directory domain controllers, so using the drop down list, I will select Windows Server 2003 and then click

the Raise button.

clip_image002

· A warning message will be displayed, informing you that the changes

cannot be reversed. Click OK

clip_image003

· A confirmation message will be displayed stating that the functional level was raised successfully. Click OK

clip_image004

· Close Active Directory User and Computers snap-in

2. Prepare current Windows 2003 Active Directory

· Before you can have a 2008 server domain controller in your existing

2003 domain, we will need to prepare both the Forest Level and the Domain level, this is done by running the following commands on the Windows Server 2003 Domain Controller.

· Insert the Windows Server 2008 DVD inside the Windows Server 2003

DVD Drive

· Open Command Prompt, this is done by Clicking on Start > Run > type

CMD > click OK

clip_image005

· Type D:\sources\adprep\adprep /forestprep (Where D: is the drive of

your Windows 2008 DVD)

clip_image006

Click Enter

clip_image007

Read the warning message, in my lab I don’t have any Windows 2000 Active Directory Domain Controllers, so I can simply skip this by typing C and then press Enter, else quite the Forest Preparation step and upgrade Windows 2000

Active Directory Domain Controller(s) to SP4, then run forestperp again.

clip_image008

clip_image009

· After Forest preparation is completed successfully, run the Domain

preparation command

Inside CMD, type D:\sources\adprep\adprep /domainprep (Where D: is the drive of your Windows 2008 DVD)

If you have not Raised the Domain Functional Level from Windows 2000

Mixed to Windows 2000 Native or Windows 2003 as was illustrated earlier in step # 1, then you will receive the following error message after you run domainprep command:

clip_image010

If you did raise the domain functional level, adprep will successfully update

the domain-wide information

clip_image011

· Although adprep /domainprep will update the domain-wide information, you can still run the last command adprep /domainprep

/gpprep

Inside CMD, type D:\sources\adprep\adprep /domainprep

/gpprep (Where D: is the drive of your Windows 2008 DVD)

clip_image012

As you can see, Domain-wide information has already been updated

when we ran the domainprep command, as no Group Policy Object

(GPO) updates needed, or GPO information has already been updated.

3. Setting up an Additional Domain Controller with Windows Server

2008

Now that Windows Server 2003 Active Directory has been prepared for Windows Server 2008 Domain Controllers, its time to Set Up an Additional Domain Controller With Windows Server 2008 and set it as a Global Catalog. If you already have an additional Windows Server

2008 domain controller and you want to check if it is a Global Catalog or not, then check my article Setting a Windows Server 2008 Domain

Controller as a Global Catalog

4. Transfer FSMO roles to the Windows Server 2008 Domain Controller

The last step in migrating a domain controller, is transferring the FSMO roles to the new domain controller. I have covered this part in a detailed step by step as spirit article.

With all the previous four major steps, you will successfully be able to

migrate your old Windows Server 2003 Domain controller to Windows

Server 2008.

Summary

Upgrading Windows Server 2003 domain controller to a Windows Server 2008 domain controller is an easy process if you follow the required steps carefully. The process consist of four major steps and they are : raising the domain level, preparing active directory for Windows Server 2008 domain controllers, setting a Windows Server 2008 as an additional global catalog domain controller and then transferring the FSMO Roles.

Now, you can simply demote the Windows Server 2003 domain controller, if you no longer need it.

Download as PDF

Migrating Active Directory Domain