Dell E6400 and MDT 2008 image not working

[jaredwetmore]

Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.

anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Todd Miller]

If you reboot, does it work?

If yes,
I had this exact same problem with a machine a while back, and I thinkl
this is a problem with the video drivers.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[jaredwetmore]

rebooting does not fix this issue. I am aware of the video driver issue, and
have applied the hotfix for that issue.

Post by Todd Miller
If you reboot, does it work?
If yes,
I had this exact same problem with a machine a while back, and I thinkl
this is a problem with the video drivers.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Preben Justesen]

It works for me on an XP SP3 image that I created before I got a hold of the
E6400 (already including the new chipset and storage drivers from Intel). The
HAL in my image is an acpiapic_up.

/Preben

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Jeff Millar]

jaredwetmore - I came across this post while trying to find resolution to
the same problem which you describe here and your going to love the solution
for the time being as I have escalated this up through Dell engineering. The
solution to the problem is pull the battery before you power on the machine
to go through mini-setup.

I have 3 different Dell E-Series models, E6400, E4300, M4400 which all
experience the same problem. When I evaluated the setupapi.log one of the
last entries indicated the last item it was discovering was the battery
before the system just hung at please wait. I hope this helps.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[unknown]

A better solution (IMHO) is renaming battery.inf works instead of
removing the battery physically. (c:\windows\inf\battery.inf)

Thanks to Mr Martin, for letting me know :)

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com


On Thu, 16 Oct 2008 11:11:03 -0700, Jeff Millar <Jeff

Post by Jeff Millar
jaredwetmore - I came across this post while trying to find resolution to
the same problem which you describe here and your going to love the solution
for the time being as I have escalated this up through Dell engineering. The
solution to the problem is pull the battery before you power on the machine
to go through mini-setup.
I have 3 different Dell E-Series models, E6400, E4300, M4400 which all
experience the same problem. When I evaluated the setupapi.log one of the
last entries indicated the last item it was discovering was the battery
before the system just hung at please wait. I hope this helps.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Timothy Kress]

You may want to try changing the SATA Operation setting in the BIOS from the
default setting (most likely IMSM, or it may be AHCI) to ATA. The problem
may be an issue with the drive setting not being recognized by Windows XP.

Post by unknown
A better solution (IMHO) is renaming battery.inf works instead of
removing the battery physically. (c:\windows\inf\battery.inf)
Thanks to Mr Martin, for letting me know :)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Thu, 16 Oct 2008 11:11:03 -0700, Jeff Millar <Jeff

Post by Jeff Millar
jaredwetmore - I came across this post while trying to find resolution to
the same problem which you describe here and your going to love the solution
for the time being as I have escalated this up through Dell engineering. The
solution to the problem is pull the battery before you power on the machine
to go through mini-setup.
I have 3 different Dell E-Series models, E6400, E4300, M4400 which all
experience the same problem. When I evaluated the setupapi.log one of the
last entries indicated the last item it was discovering was the battery
before the system just hung at please wait. I hope this helps.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Tim Hunt]

Guys,

This issue is truly annoying... but I have a solution, based on Johan's
suggestion:

In the golden image PC (in my case in a VMWare machine) rename the file
battery.inf which resides in c:\windows\inf to something like
c:\windows\inf\battery.inf.old

Create a cmd script called, say, batteryIssue.cmd

This script should contain the following line:

ren c:\Windows\Inf\Battery.inf.old Battery.inf

Now reference this script within your cmdlines.txt file
(c:\sysprep\i386\$OEM$\cmdlines.txt) e.g

[Commands]
"C:\Windows\Support\batteryIssue.cmd"

Now update your Sysprep.inf such that the [GuiUnattended] section contains:

AutoLogon=Yes
AutoLogonCount=1

And reference another cmd script in the [GuiRunOnce] section, e.g

Command0=c:\Windows\support\moreCommands.cmd

This script just needs to contain:

Shutdown -r -f -c "PC now rebooting to complete setup" -t 10

What we have done here is prevent minisetup from installing the problem
battery driver. Once minisetup completes however, it runs through the
cmdlines.txt and executes a script that 'unbreaks' the battery.inf driver
file (batteryIssue.cmd).

The autologons and GUIRunOnce options ensure the machine boots with Admin
credentials to properly install the battery driver AFTER minisetup (it
autoinstalls the driver since it resides in the standard location for device
drivers). This ensures standard users are not prompted to install a
'unknown' device once they login.

For some strange reason the exact same battery driver that causes
installation issues during minisetup installs fine, if installed later in
setup process.

The final script that we call reboots the machine so we don't leave it
logged in with Admin rights for our end users :-)

I hope this workaround proves useful.

Thanks

Tim

Post by Timothy Kress
You may want to try changing the SATA Operation setting in the BIOS from the
default setting (most likely IMSM, or it may be AHCI) to ATA. The problem
may be an issue with the drive setting not being recognized by Windows XP.

Post by unknown
A better solution (IMHO) is renaming battery.inf works instead of
removing the battery physically. (c:\windows\inf\battery.inf)
Thanks to Mr Martin, for letting me know :)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Thu, 16 Oct 2008 11:11:03 -0700, Jeff Millar <Jeff

Post by Jeff Millar
jaredwetmore - I came across this post while trying to find resolution to
the same problem which you describe here and your going to love the solution
for the time being as I have escalated this up through Dell engineering. The
solution to the problem is pull the battery before you power on the machine
to go through mini-setup.
I have 3 different Dell E-Series models, E6400, E4300, M4400 which all
experience the same problem. When I evaluated the setupapi.log one of the
last entries indicated the last item it was discovering was the battery
before the system just hung at please wait. I hope this helps.

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[oliphanj]

When I upgraded my universal image for the e6400 I had forgotten the intel
video driver. Everything worked but the video, I did have to set the bios to
ATA Sata Operation but that is fine.
Now when I changed the sysprep.inf file with the correct video driver the
screen goes black and no mini-setup comes up.
I tried reimaging without the battery and that is not it. So I reimaged
again without the video driver and it worked again. So I guess I can script
the video driver install or after all devices have been found update the
OemPnPDriversPath after the first reboot. Whats up with the intel video
driver? I am using XP SP3 so that video patch doesn't work..

Thanks,
Jason

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !

[Tim Hunt]

There are a couple of different spec e6400s, make sure you have a nVidia
Quadro driver included in your build - in addition to the intel video driver!

Thanks

Tim

Post by oliphanj
When I upgraded my universal image for the e6400 I had forgotten the intel
video driver. Everything worked but the video, I did have to set the bios to
ATA Sata Operation but that is fine.
Now when I changed the sysprep.inf file with the correct video driver the
screen goes black and no mini-setup comes up.
I tried reimaging without the battery and that is not it. So I reimaged
again without the video driver and it worked again. So I guess I can script
the video driver install or after all devices have been found update the
OemPnPDriversPath after the first reboot. Whats up with the intel video
driver? I am using XP SP3 so that video patch doesn't work..
Thanks,
Jason

Post by jaredwetmore
Currently trying to us a custom wim that i created on MDT 2008 and deploy it
to new Dell hardware Latitude E6400.
Ive updated my sysprep mass storage controllers, and chipset drivers. Ive
re-captured my XPSP2 iamge, and trying to deploy it down to the Dell. It
deploys, I see the nic, and HD.
once the os has been brought down, it reboots, and there it sits.. at Please
wait....
Yes I have the hotfixes that are needed to fix the "please wait" issue.
I belive its an hal issue... In my VM which i create my wim on, I force it
to ACPI, and then run a script that detects the hal on the dell, and it
copies over the correct hal based on hardware type. no luck...
ive even created a wim based and foreced the hal to be a up hal, captured
that, and then bround that down to the dell, and no go... Dell is a
Multi-proc hall.
anyone got one of these working with MDT ? if so... any hlep would be GREAT !