Net Logon Service won’t start after demoting a domain controller

Today I had to perform a domain upgrade at one of our customers. After succesfully demoting the old Windows 2003 domain controllers, the Netlogon service won’t start anymore.

“Could not start the Net Logon service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.”

After some reserch I found the solution.

1.) Start the registry editor (Regedit.exe).
2.) Navigate to the following registry key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netlogon/
3.) In the right pane, double-click the DependOnService value .
4.) In the Multi-String Editor dialog box, type the following strings on separate lines, and then click OK
Remove any other entries.
5.) Exit the registry editor and restart the server

How to: MDT 2010 change the “Running: Lite Touch Installation” message

If you want to change the message “Running: Lite Touch Installation” in the progress display when deploying a computer, you’ve to change the file LiteTouch.wsf in the folder E:\DeploymentShare\Scripts (in my environment!)

Search for the text “Lite Touche Installation” and replace this with your own text. For example: “Running: Deploy Microsoft Windows 7”. Save the file and update your deploymentshare. Import the new WIM file into Windows Deployment Services (WDS).



MDT 2010 and user credentials??

When you’re deploying a machine using MDT, every time you run the deployment wizard, you’ve to fill in user credentials fore authentication with the deployment share. You can change this by editing the file bootstrap.ini.

1.) Open the DeploymentWorkbench
2.) Right click the MDT Deployment Share (E:\DeploymentShare in my environment)
3.) Open the second tab Rules
4.) Click Edit Bootstrap.ini
5.) Default the file looks like picture 6
6.) Add the following rules to the textfile:
UserDomain=WIN7.LOCAL (your domain)
UserPassword=Pa$$w0rd (your administrator password)

7.) Don’t forget to update the deployment share
8.) Right click the MDT Deployment Share (E:\DeploymentShare in my environment), and select Update Deployment Share
9.) Assign the boot image (E:\DeploymentShare\Boot\LiteTouchPE_x86.wim) to Windows Deployment Services WDS.



Adding drivers into WinPE boot image (WIM-file) for use with Microsoft Deployment Toolkit (MDT)

WinPE is the preinstallation environment which will mostly be used to load an OS onto a new system. This article will explain how to inject LAN drivers into WinPE, allowing you to deploy OS installations to a larger variety of hardware. You will need to have the Microsoft WAIK (Windows Automated Installation Kit) installed to modify the image. WAIK provides the command line tools for working with WIM images, the image format used by Windows and WinPE.

Open the WinPE Command Prompt by Clicking Start -> All Programs -> Microsoft Windows AIK -> Windows PE Tools Command Prompt.

Create an empty folder which you will use to mount the WinPE image:

mkdir D:\mount

Locate your WinPE boot image. For example:

Mount the image using the following command, substituting your own mount path and WinPE image.  (Note: each WIM file can contain multiple images, use the imagex /info command to locate the correct number for your boot image)
imagex /mountrw D:\RemoteInstall\Boot\LiteTouchPE_x86.wim 1 D:\mount

Locate the INF file for your network driver. Use the following command to inject the driver, subsituting your own driver INF and mount path.
peimg /inf=D:\<driverpath>\<driver>.INF /image=D:\mount

Commit the changes to the image.
imagex /unmount /commit D:\mount

Make sure you’ve a copy of the orriginal WIM file, so you can always replace a backup of this file.