I waited even longer and it did eventually move past "setup is preparing your computer for first use" and then proceeded to sysprep /oobe /generalize / reboot as is what I have set in my unattend.xml in the "audituser" pass which is based off the win7x64unattend.xml provided via the landesk pdf here on the community.
My guess is that I shouldnt be having the computer syspreppping to oobe again during the provisioning process.
I'm contemplating removing the audituser pass from my unattend and see if that works. Problem with troubleshooting imaging is that it takes awhile to re-image a machine again and go through all of the steps.
What version of LANDESK are you using? One thing to make sure of is that you create C:\Windows\LDDriverStore either in your image or create it using an action within the provisioning template (I prefer the latter). This is where the HII action will copy all the drivers to. Just make sure the create directory action goes before your HII action
Also, what method are using for HII? UNC or HTTP? In your driver store, have you extracted all the files? I tend to sysprep using oobe /generalize /shutdown to capture an image as it works better when injecting the computername into the unattend.xml. Win7 does go through the 'setup is preparing your computer for first use' process a couple of times during the setup. Also you may want to add <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> to the generalize section of your unattend at the end to prevent Windows from removing all your newly detected drivers during setup.
Post your unattend.xml and your provisioning template and we can take a further look
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
Update - New v2.3 Now with Automated Subnet Rep Selection and Optional Maintenance of LANDESK Reps
The One-Stop Shop for LANDesk Enhancements
Thanks for taking the time to reply Martyn. We are running 9.5 sp 1. I have not been creating the c:\windows\lddriverstore manually or through provisioning as I was assuming that the HII action was doing this. I am currently using HTTP for my drivers and have allowed the config and other file types in IIS.
I have attached my unattend.xml file to this reply. It is my understanding that the "auditsystem" and "audituser" passes of this unattend are not used at all if my image is oobe /generalized and not audit mode.
FAILED.xml 4.9 K
There are many different ways to accomplish this.
Here is how I do it (well, the parts that pertain to what you need to get through mini setup)
Install base image, customize, patch and leave in Audit mode. (I don't run sysprep to enter audit mode, I use ctrl+shift+F3 after new install)
(I don't pre-create and drivers directories or anything. Pretty much install, patch and customize settings)
run sysprep /oobe /generalize /shutdown (I don't point to an xml here)
capture the image after it shuts down being careful to not let it boot up before capture
Deploy the image with your template and include an "inject script" action for your unattend (to create c:\windows\panther\unattend.xml)
Add an HII operation to enumerate hardware and inject drivers. The c:\windows\lddriverstore folder will be created automatically.
That should be enough to get the machine through sysprep (drivers and unattend.xml) Once you have that part working, you can start adding more template actions to meet your end goal.
If you still have hangs/"bluescreen of death", boot back into WinPE and see what drivers were copied to c:\windows\lddriverstore and make sure the appropriate driver(s) were injected.
I'm not sure if you need all that stuff you have in the Audit pass
I have attached my xml if you want to see if it works for you
win7_scrubbed.xml 4.7 K