Posts Tagged Desktop Deployment

Hotfix: Deployment fails when deploy a task sequence to a Windows XP in System Center 2012 R2 Configuration Manager

SYMPTOMS

When you tried to deploy task sequence with captured image to a Windows XP machine using Operating System Deployment feature in System Center 2012 R2 Configuration Manager, the deployment fails and you may found the following error in smsts.log file:

CreateProcess failed. Code(0x800700C1) TSManager datetime 3048 (0x0BE8)

Command line execution failed (800700C1) TSManager datetime 3048 (0x0BE8)

Failed to install boot image.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Failed to install boot image CCR00004.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Failed to reboot the system. Error 0x(800700c1) TSManager datetime 3048 (0x0BE8)

Failed to initialize a system reboot.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Fatal error is returned in check for reboot request of the action (Restart in Windows PE).

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Solution

To solve this issue install HOTFIX from KB2910552 on the following:

  1. Central Administration sites.
  2. Primary sites.
  3. Administrator consoles.
  4. Clients (Client update package will be created after installing hotfix on site system server).

Finally don’t forget to update Windows PE 3.1 boot images.

Abduljalil Abolzahab

, , ,

2 Comments

PXE fails with “PXE-T04: Access Violation” and “PXE-E36: Error Received from TFTP Server”

Problem

When configure PXE Service Point in Microsoft System Center Configuration Manager 2007, booting may fail with the following errors:

PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom

You also may notice missing entries in the SMSPXE.log

Cause

This can occur because of wrong DHCP configuration.

Solution

You may need to configure IP helper (BOOTP) settings on the routers OR configure DHCP scope options in case you have Cisco DHCP instead of Microsoft DHCP.

To Configure DHCP Scope on Cisco Routers, add the following to DHCP Scope:

next-server ‘IP Address of PXE Service Point’

filename \boot\x86\wdsnbp.com

Abduljalil Abolzahab

2 Comments