OSD Fails when installing the first package/application

[P.Keen]

Hi,

 

Firstly "anyweb" you have been a unbelievable help with me and my sccm journey, honestly you have no idea how much your blogs and articles have helped me!! So a massive Thank you! You should set up paypal donation account SERIOUSLY!!!

 

We are moving into SCCM 2012 and well our SCCM 2007 environment wasn't built correctly and was very unreliable. So we were almost forced to move to 2012 it has been different but exciting, where some things are in SCCM 2012 defiantly makes more sense than in 2007.

 

Anyways I have moved my custom built .wim file accross and imported all my packages manually (didn't trust the old config and starting fresh will be good) all have distributed fine. Wim applies fine (didn't originally because we didn't have network drives in our winpe image, that was fun trying to get that to happen I got the famous "couldn't inject drivers OSD binaries etc etc" got past that eventually. Got another error about applying the .wim think this was related to not having our NAA set which we do now. Now I'm at the stage where config manager client installs and restarts all fine however when it says "downloading package" it fails with 0x80070002 from memory (not at work at the moment) I could not find smsts.log in c:\windows\system32\ccm or C:\windows\temp.

 

I was hoping to be able to set the TS to run from distribution point instead of downloading so I followed this thread http://www.windows-noob.com/forums/index.php?/topic/5414-packages-downloading-during-osd-instead-of-running-from-server/ and recreated my config manager client using create from definition and set my TS to use that package instead. I also set each package to "copy the content in this package to a package share" and left the custom name unconfigured. Then I left work so didn't get to see the result, I searched for logs but couldn't find what I needed. Anywhere else I should look? Also to complicate things I cannot login to the system even though I should technically be able to, please don't ask me why

 

I have set the NAA in the permissions of our "PKGSource$" as well as "domains machines". I can supply more details and logs when I return to work tomorrow.

 

Regards

Pete

[Oneone]

Could you post the logfile? and where in the TS are youtrying to install the application? could you provide a screenshot of your ts?

[P.Keen]

Which log and where would it be saved? I will supply a shot of the TS tomorrow.

[Rocket Man]

Wim applies fine (didn't originally because we didn't have network drives in our winpe image,

 

This will allow the image to be applied and also boot successfully.

I had a similar problem with a specific TS. It had similar symptoms to yours...it would install image and then after 1st reboot it would bomb out. I dont download..I use run from DP and it still had the same problem..

My Fix was to add the specific driver package to the TS also with a query for the model.(instead of using the default apply drivers)...after I did this it picked up the software on the DP share and installed it.

 

I came to the conclusion that the driver injected into the boot.wim only was suffice for getting the initial connection for PXE booting & applying OS...after the reboot it lost the connection as it did not have the NIC driver added to the OS via the apply driver package......maybe this is your problem also.

[Rocket Man]

Also to complicate things I cannot login to the system even though I should technically be able to, please don't ask me why

 

This is the client machine you are talking about?

Did you set a local administrator password in the TS if you are not using an answerfile or vbScripts to set local admin accounts?

 

I can assume that it has not joined the domain either?

[P.Keen]

I knew someone would ask Correct client machine, The password is set in the .wim but the expiry is also set and there fore expires. It is fixed by a vb script but obviously isn't applying because packages arent running. How do I confirm if its a driver issue? F8 isn't enabled because I'm not booting into winpe but the OS.

 

Correct it doesn't join the domain either.(I will check though)

[P.Keen]

I'm at work now, I have specified the "Enable the account and specify the local admin password" and can log in using those details. So I will try and find smsts.log.

 

I have noticed that two devices aren't installed "Ethernet Controller" and "H3521gw" guessing my problem is the same as Rocket Man. What would be the best solution I have been told that all our laptops use the same network driver which is added to SCCM fine , well says it has.

 

So the best solution would be to Add all the drivers needed into the one package and have that package install, instead of "apply device drivers",

 

WAIT - I just looked and for some reason it was only looking in certain categories, One of those catagories that wasn't ticked contains the network drivers :S , retrying now.

[P.Keen]

Tried it again, got the "downloading" phase for the first package and I pulled up command prompt and still no network.

 

How do I get my network card to install correctly? Any ideas?

 

I created Driver packages for each model earlier I will just select "install this package" for my model and see if it gets us through. Then if that works I will combine all laptop driver packages into one package and install that just to get us by until I have some downtime to resolve this issue. Fingers crossed this works, the manufacturer said that all network cards for our laptops use the same driver so it may work.

 

Question relating to drivers I know when you select "install driver package" it actually installs the drivers in the OS so that they can be used later on etc, and will blow out the image size potentially. Would it be safe to delete and duplication drivers from the "all laptop driver package" that are the same version? Will SCCM install the same driver twice? and there fore waste HDD space?

[P.Keen]

Failed at installing driver package. I will retry but ticking all my driver packages that have laptop drivers in it. Hopefully I can get this bloody thing working today.

[P.Keen]

Do drivers need to be "distributed" before being able to be installed? I know SCCM doesn't package drivers and just links the driver to the source files (IE don't delete your driver source files when importing drivers).