Jump to content


  • 0
tgpeppers

Deploying WIndows XP with Microsoft Deployment Workbench 2010

Question

I have run into a pretty annoying issue while deploying a new image that I have recently created including the new Office 2010 package. Before I begin to explain the issue I want to acknowledge the machines and Applications I am using to deploy this image.

 

Our machine pool consist of a number Dell laptops and Desktops in which I am using 2010 Microsoft Deployment Workbench.

 

Laptops: Desktops:

 

Latitude D600 Optiplex GX270

Latitude D610 Optiplex GX280

Latitude D620 Optiplex GX620

Latitude D630 Optiplex GX755

Latitude E6400

Latitude E6410

 

I am 100% successful pushing the image down on to all the machines listed above except for the Optiplex GX620.

After the machine reboots and tries to start windows for the first time it freezes at the windows loading screen. I have tried creating driver profiles for the task sequence to isolate which drivers are injected into the machine throughout the imaging process. The only two ways that I have been able to have windows load after being imaged on the GX620 is by disabling the cdrom..and or booting up into safe mode...

 

Any suggestions?

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

I have run into a pretty annoying issue while deploying a new image that I have recently created including the new Office 2010 package.

<snip>

I am 100% successful pushing the image down on to all the machines listed above except for the Optiplex GX620.

After the machine reboots and tries to start windows for the first time it freezes at the windows loading screen. I have tried creating driver profiles for the task sequence to isolate which drivers are injected into the machine throughout the imaging process. The only two ways that I have been able to have windows load after being imaged on the GX620 is by disabling the cdrom..and or booting up into safe mode...

 

Any suggestions?

 

Had that same issue.

Check the bios and change the drive to compatible. That may fix the issue. But you're probably going to have to create a new task sequence just for 620s... sucks... I've always hated those 620s

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.