Jump to content


JoinedForHelp

Established Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JoinedForHelp

  • Rank
    Newbie
  1. Hello. I'm wondering if it is possible to create a collection limited to all discovered systems based on IP subnet. But I need the systems that DO NOT have the client installed yet. We have about 2k systems and are in the testing phase of our client install and we do not want to push the client out to the whole district at once. We are just wanting to push it to one campus/site at a time. We only have 1 MP and 1 DP right now located at our main site. Lately I have been having to go get all the computer names of the systems I want to test client installation on and do a search under all systems and right click-install client one by one. There has to be a better way of doing this?
  2. The issue was due to some miscommunication between me and a co-worker. They told me they disabled secure boot so I took their word for it without checking and guess what the problem was... they didnt. Thanks guys.
  3. Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all. Task Sequence Steps (in order): Capture Windows Settings Capture Network Settings Install Operating System Restart in Windows PE Format and Partition Disk Apply Operating System Apply Windows Settings The rest doesn't really matter since the task sequence is failing at "Apply Operating System" (On the HP Probook 430 G3) This issue only occurs on the Probook (laptop) and NOT the Prodesk (desktop). The way we are managing OSD here at my company is to have a "Golden" Task Sequence, then just copy that same task sequence for as many different model of systems we have and insert the corresponding driver package as well as rename the task sequence for whatever new model we discover we have or receive. So we received our new shipment of Probooks (laptops) and I did what I always do when we get a new model. I grabbed the Windows 7 drivers for it (Note: These systems come with Windows 10 installed. Our image is Windows 7 Enterprise x64 SP1.) and created/copied a task sequence for the new model by simply switching out whatever driver package was in the task sequence that I just copied with the correct package for that model (a lot of this is irrelevant since again, the task sequence is failing at "Apply Operating System" before it even tries to install drivers.) Things I Have Done: Made sure all content called for in the task sequence is on the DP Deployed the TS as Available (PXE,Media,Blah blah) to All Unknown Computers Read through the provided smsts.log and could not make sense of it. Seems error 0x80004005 is a "beat around the bush" error Created a task sequence from scratch then tested. Still same issue at the same place Thought maybe its an issue with my .wim but I dont think so as this has worked on some of our other models tested Came here for help I am at a total loss as of where to start to troubleshoot this error. Most of the info you will need to help asses the issue is probably contained in the log(CMTrace it). Please let me know of anything I left out that could help. Thank you! smtsprobook
×
×
  • Create New...