Search the Community

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