Windows Deployment Service Fail to start in 2003 and 2008 with SCCM

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM.

I have a Windows 2008 Server that has WDS + SCCM 2007 R3 installed.  The Windows
Deployment Services Server Service isn't started and when I try to
Start  it I got a message that says:

Windows could not Start the Widows Deployment Services Server on Local
Computer.  For more information, review the System Event Log.  If this
is a non-Microsoft service, contact the service vendor, and refer to

server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to Start the Windows Deployment Services
server.
 Error Information: 0x906
  
Hear is the Problem Analysis and Resolution of below errors.

CAUSE :

This problem occurs because the location of the computer object that is running WDS has changed in the Active Directory directory service.

A Windows Deployment Services (WDS) server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or Microsoft Windows Server 2003 with Service Pack 2 (SP2). If you move the WDS server to a different organizational unit, the WDS server may not start. Additionally, one of the following error messages may be logged in the System log on the WDS server:

Error Messages :

Error message 1

Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 9 (0x 3).

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter Error message 2

Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 19 (0x13)

One of the following groups of error messages may also be logged in the Application log:

Error message group 1

Type: Error
Event ID: 261
Source: WDSPXE
Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x 3

Type: Error
Event ID: 1800 Source: BINLSVC
Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x 3

Type: Error
Event ID: 1803
Source: BINLSVC
Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Error message group 2

Event Type: Error
Event Source: BINLSVC
Event ID: 1803 Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Event Type: Error
Event Source: BINLSVC
Event ID: 1800 Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 261 Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 265 Description: An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 513 Description: An error occurred while trying to initialize provider WDSPXE from C:\WINDOWS\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 522

Description: An error occurred while trying to shutdown provider WDSPXE. Error Information: 0x6

RESOLUTION :

To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
3. Move the WDS account to Active Directory in the new organizational unit.
4. To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

Enjoy!!!!

0x80070091 error while upgrading Windows XP to Windows 7 by SCCM 2007

Hello Friends,

Today i am trying to updgrade operating system windows xp to windows 7 by using System Center Configuration Magager (SCCM) 2007 R3.
i have made Task Sequence by using Microsoft Deployment tool kit 2010 Update 1 and advertise on collection, but while "wimping C:\ Drive " step task sequence gets failed..... I tried many times with new task sequece and face same error like mentioned in image.

Cause :

This error occured due to task sequece engine may not able to wipe c:\ Drive propperly or some files which is having wrong file extention or ended with # or ended with ( dot .) or some corrupt files.

Resolution :

1) Run chkdsk command if task sequence fail. ( this command may take lot of time to complete operation )
2) Press f8 while facing error and manually delete currept profile.
3) or write Script to delete currupt files.

For more information please refer http://blogs.msdn.com/b/alex_semi/archive/2012/02/22/os-refresh-fails-with-ntldr-can-t-be-found-error.aspx

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter