How to change the Default RemoteInstall folder for Windows Deployment Services

While reconfiguring my WDS servers storage, I inadvertently changed a drive letter that contained my RemoteInstall folder. This prevented the WDS service from starting. Below is the event log error that I received:

Log Name: Application

Source: ESENT

Date: 6/23/2011 12:07:13 PM

Event ID: 494

Task Category: Logging/Recovery

Level: Error

Keywords: Classic

User: N/A

Computer:

Description: svchost (1116) DDP: Database recovery failed with error -1216 because it encountered references to a database, I:\RemoteInstall\Stores\Drivers\Metadata\DdpDb.mdb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message. Event Xml: 494 2 3 0x80000000000000 123686 Application 2008Server.MCTExpert.com svchost 1116 DDP: -1216 I:\RemoteInstall\Stores\Drivers\Metadata\DdpDb.mdb

The new drive letter is now J:. To fix this I opened a command prompt with administrative credentials and executed the following commands.

wdsutil /Uninitialize-Server

wdsutil /Initialize-Server /REMINST:"J:\RemoteInstall"

A refresh of the WDS console showed the WDS server was back online.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all. Take a look at the drive mapping below. The red triangle is what threw us off. It is not an error. It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle. This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the

Jason Yoder, MCT

Search This Blog