Systems Deployment

A link to it
The error I am seeing^

I did try the scripted install without the USMT enabled and still got the same windows error but you are right, the command prompt error was no longer there. Seems like there may be two seperate issues going on. We are going to submit a help ticket with Kace and see what they have to say. Having a successful image 1 out of 5 tries is not going to cut it.

i have the same problem too, i wonder if anyone can also help me with this. I have been trying to find some help but to no avail.
Hope someone can help me here.

The NIC is Intel(r) 82567lm Gigabit Network Connection. I will be doing some more testing soon, only made that one attempt with that many machines.

I have the same problem, need to find a fix ASAP getting ready to deploy 2000 workstations.

I am going to be doing some more testing in a day or two, and it will be with a different model. I will get back with my results. Hopefully it is only some weirdness with the E6520... wouldn't surprise me at this point.

I too am getting this error. For me the error is coming up right after the HD formatting is completed and the Windows 7 'Setup' screen loads. It does not even get to the 'Copying/Expanding' Windows files stage. And after I click the OK button I get the following command window with errors.

Weird enough, after this happens 3 or 4 times it will work as normal with no errors. But I still need to figure out what is wrong, we cannot go on trying to image 4 times before having success.


Screen Shot

Hi Bethel03, it looks like you are doing something with user state transfer or something, looking at the screen shot. Maybe take that out of the mix for now? Have you tried another model?

Alright so I worked with my network guys and replaced my 8 port procurve with a 24 port 3550. I also have gigabit to the kbox. I was able to image 10 machines in 35 minutes with no issue at all. The K2000 was putting out about 550Mbps which is way up from the 100ish Mbps I was seeing before. It really does seem that this issue pops up if the throughput drops too low...

Right now I am building 13 machines concurrently, and saw the KBOX throughput as high as 800Mbps.

I'm getting this error too. Upgrading our entire network with gigabit switches is not an option for us at this time.

I'm having the same issue. Didn't notice it until after setting up the Driver Feed Workaround and drivers (found here: http://itninja.com/question/silent-uninstall-oracle-8-cilent9275&mpage=1&key=𓖫)

Just like Bethel03, the error occurs just after my Preinstallation Tasks but before the Copying/Expanding Windows dialog box. I do not have USMT enabled. The only Preinstallation Tasks are as follows:

Upload Hardware Inventory
Create Single Partition
Format C: as NTFS
Install Vista/2008/7 MBR

After choosing OK to close out the error the cmd.exe window shows "Access is denied" and then Executing driverfeed_x86.exe. The driverfeed exe then prompts another error that says: Error on drive. There is an error in that no data is being found that correlates to an OS. This makes sense because the drive is formatted but the Windows 7 install failed.

Choosing OK on the driverfeed exe error reboots the machine.

Here is where it gets weird.

If I ignore the driverfeed exe error (ie don't choose OK) but instead alt-tab to the K2 Deployment Client screen, reselect my scripted install and choose Start installation, the scripted install of Windows 7 works without the original error occurring.

I recorded a camtasia video of the above. A few observations I made while recording:

I can vnc into the booted workstation and select the scripted image.

Once the Windows 7 setup has started but before the original error, my VNC connection is closed. Not sure exactly what the Windows 7 setup is doing at this point. Probably reloading the network drivers and that is what kills the scripted install? To finish the recording I alt-tabbed to the K2 Deployment Clent, selected recovery, command prompt, and mapped a drive to a location where I can run winvnc.exe. Once running winvnc.exe I was able to then VNC back into the machine and continue the recording and therefore continue the scripted install (the weird part above).

Maybe there are newer drivers that the Windows 7 installer is finding and is loading them instead of using the drivers from the boot environment? It's obvious the NIC card is still working after the initial error because I'm able to map a drive to a network share.

Could the second Windows 7 scripted install that I started see that it's newly found NIC card drivers (found at the first error) are already loaded and therefore can continue the network install? It's just a theory but it's plausible.

Is there a way to update the kbox boot environment NIC drivers to whatever the Windows 7 scripted install is finding?
or
Where are the drivers that the Windows 7 script is finding so I can remove them and then do a recache drivers?

The original error is happening on the following machines:
Latitude E5410 - Broadcom Netxtreme 57xx Gigabit Controller - Packet Scheduler Miniport
Latitude 2100 - Broadcom Netxtreme Gigabit Ethernet - Packet Scheduler Miniport
Latitude 2120 - Broadcom Netxtreme Gigabit Ethernet - Packet Scheduler Miniport

The original error is NOT happening on the following machines:
HP/Compaq nx6110 - Broadcom 440x
Latitude D830 - Broadcom Netxtreme 57xx
Optiplex 740 - Broadcom Netxtreme 57xx

Is there a difference between the Broadcom Netxtreme and Broadcom Netxtreme w/Packet Scheduler Miniport? This is how my K1 is reporting the NIC cards on the above workstations.

Does any of the above make sense?

I haven't finished editing the video recording or I would of provided a link to it.

Andy

Update.

After removing all files and folders from the Windows_7_x86 driver directory and recaching the scripted install does not give me any "Windows cannot access the installation sources" error.

I'm going to let the install run over the weekend (cause it's time for me to go home). Not sure what the new driver feed fix (mentioned in my previous post at the top) will do or if it'll install any drivers not found or used in the K2 \drivers folder.