I was fighting with an interesting issue the past few days. I had a single Operating System Deployment (OSD) Task Sequence (TS) that I deployed to three different models of laptops for testing. I 'Auto Apply Drivers' based on the category of the machine and use a WMI Query to determine the model of the machine and apply the task appropriately.
The problem I had was with one particular model that did not join the domain. I logged into the machine locally and saw that it installed all the needed drivers, the TS had no failures, and I was able to join the machine manually. It wasn't a credential issue or an issue with the image because this same TS was completely successful on other models.
What I oddly had to do to fix it is that instead of 'Auto Applying Drivers' based on Category, I had to apply the entire driver package. This completely fixed the issue so the NIC driver must not have initialized correctly through the TS and failed the domain join. Remember that the domain join step in your TS only appends the unattend file with the proper information and then Windows Setup does the actual joining to the domain. The success of that single task is separate from the actual success of joining the domain.
When I have some extra time I'll try to determine if it is a model issue, or driver variation for that particular flavor of NIC. In case you were curious, this was on an HP Probook 6560b with 32-bit Windows 7 and an Intel 82579V NIC.
The problem I had was with one particular model that did not join the domain. I logged into the machine locally and saw that it installed all the needed drivers, the TS had no failures, and I was able to join the machine manually. It wasn't a credential issue or an issue with the image because this same TS was completely successful on other models.
What I oddly had to do to fix it is that instead of 'Auto Applying Drivers' based on Category, I had to apply the entire driver package. This completely fixed the issue so the NIC driver must not have initialized correctly through the TS and failed the domain join. Remember that the domain join step in your TS only appends the unattend file with the proper information and then Windows Setup does the actual joining to the domain. The success of that single task is separate from the actual success of joining the domain.
When I have some extra time I'll try to determine if it is a model issue, or driver variation for that particular flavor of NIC. In case you were curious, this was on an HP Probook 6560b with 32-bit Windows 7 and an Intel 82579V NIC.
3 comments:
I'm having this issue too, although I'm not able to solve it by using a driver package.
Any updates?
Hi This looks like an issue I have been wrestling with for sometime.
SCCM 2012 sp1
MDT 2012 Integration
I am using UDI Wizard along wth customsettings.ini
Goal:
I want to have users get the UDI wizard and choose the settings like what OU they want the computer to go into during the task sequence.
I then want the computer name to be based on the OU that has been chosen eg:
If the user picks Eastern Regions in the UDI Wizard then during the taks sequence the name of the computer will be be based on the OU that the computer is put int for example - EASw7L-%serial%
I need help understand how to setup the variables using OSDDomainOUName if needed and what step to use this in the Join Domain vs Apply Network Settings.
We can do a remote connection so you can see whats going on if that will make things easier.
Thanks for any help with this!
A true friend is one who overlooks your failures and tolerates your success! See the link below for more info.
#failures
www.ufgop.org
Post a Comment