Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Arcuss88

  • Rank
  • Birthday 03/16/1982

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm getting the exact same problem. The OSD Task Sequence completes without errors, but the client is unable to register right away. The only way I'm able to get the machine to register correctly to log in and restart the workstation. I already have a restart as the last step of my TS, but this doesn't help. I don't recall this happening before installing 1702, but I could be wrong...
  2. Thanks for the help, the TechNet article helped a lot and answered some confusion I was also having as well. I am using SCCM 2012 R2 SP1 so WinPE 5.0 is natively supported for customizations. I was trying to take a shortcut and copy the existing boot WIMs and just modify them but that didn't seem to do the trick (and after thinking about it some more I probably shouldn't trust it anyway since the guy I took over the environment from had left me some land mines elsewhere). Solution Summary: I was able to add the WinPE 5.0 from Windows ADK for 8.1 using the "Add Boot Image" wizard. I t
  3. WOW, hadn't seen this TechNet article, This addesses a lot of the confusion I've been having! I'll read up on this and make sure I'm using the correct WinPE version for the SCCM version I have. I'll report back once I get it worked out, thanks a bunch!
  4. Hey all, I'm at my wits end here. I'm trying to add support for a new generation of laptops to my SCCM 2012 R2 TS. I have already gone through the trouble of gathering all the required drivers for the new models and created new Driver Packages only to find that the new models all use a newer\different NIC driver than the previous generation. No big deal I think, I'll just create a new boot WIM for testing, get the appropriate drivers for WinPE and I'm good! Well, not so fast. For some reason when I add the new boot WIM to my testing Task Sequence and try to PXE, the machine is unable to p
  5. Possibly a silly question, but I didn't see it mentioned in any of the above replies or original post, but the NIC driver specified for WinPE was added to the Boot WIM and updated on the DPs right?
  6. Why would you need to use a batch file to uninstall? If you're using SCC '07 just create a collection where that version of Java is installed (Listed in Programs and Features I believe is the option) and create a Package where the Program command line is your msi.exe uninstall string. If you're using SCCM '12 just create an Application with the MSI (if you have it) and the uninstall will be populated. Then just deploy the Application selected "Uninstall" during the wizard. IMO I try to avoid using batch files as it tends to overcomplicate simple tasks sometimes. I can elaborate more
  7. Wanted to provide an update on this question I posed. On the 9th when I posted this question I was at a total loss and didn't know what was wrong or how to fix it. I came in this morning and just for grins and giggles I went ahead and re-ran the Task Sequence on the machine in question. Came back roughly an hour later and it had completed successfully... no issues... All Drivers installed, SCCM Client installed, All Software installed, and BitLocker encryption started! Still don't know what the cause\fix was unfortunately, but I'm thinking whatever it was it was machine specific. Unfortun
  8. I am trying to build support for additional models into my Task Sequence and feel this model is fighting me the whole way. I have been able to identify the drivers required for this desktop and have been able to confirm that my SCCM Driver Package is installing all devices correctly. With that said though I am getting an error during the installation of the SCCM Client only on this model. The same WIM is used on another model without issue. With all that being said here is what I'm seeing. WIM is applied, Driver Package is correctly selected and applied, the "Setup Windows and ConfgMgr
  9. OK, so here's my scenario. I've created two Applications each of which have more than 1 Application Type. When I created and tested them both with a deployment to a collection and during OSD with PXE they work fine. What is "special" I think about them though is that I have made the dependencies for the Application Types are in the same Application. When I try to run the Task Sequence on a Stand-Alone USB drive is NOT connected to the network these two Applications do not install. If I run the same Task Sequence on the same Stand-Alone USB drive the TS fails. So in case I'm not clear
  10. I'm getting the same error. Deploying Win7x86 with SCCM 2012 SP1 CU2. After I install one of the applications required for my laptop model it reboots and then bombs out. I get the exact same errors at the end of the SMSTS log as you provided. Were you able to find a solution\cause? I've been reading around and apparently 0x8007045b can be caused by a bad sector on the drive. Just seams odd that the TS would be hitting the exact same spot in the drive every time. Thanks for any input!
  11. From what I understand the installation requires that an absolute path be used to call the setup.iss file. I've found this to be somewhat tricky since SCCM never has an absolute path when deploying software. If you haven't tried it already just drop the "C:\Windows\" part and call the setup.iss file that way in your program. If that doesn't work you would need to use a batch file in your program and copy the file to a local temp location, run the command using that location, then deleting this file. Now doing it this way is kind of messy because you are copying the package locally, then re
  12. Hmm haven't heard of driver packages being empty like that though. I do know that HP drivers need to be "unwrapped". HP distributes them in EXE's but if you use a compression tool like WinRAR you can extract the actual drivers and use those in SCCM. Not sure if this is much help though to you though. Good luck.
  13. Ok, I think I figured out a workaround that I can use. I commented out all the sections of the MigApp.xml & MigUser.xml that I wasn't going to use anyway and ran it again. No errors came up and it did successfully create the config.xml file. I believe it should be alright since I was going to just exclude a bunch of things anyway but I was hoping to keep the stock xml files as vanilla as possible.
  14. I'm just leery of modifying these files and figured it must be something I am doing wrong.
  15. Yes, I should have been more specific, that is the updated MigApp.xml file that supports Office 2010. I believe I was running into this same problem when I was trying to create a config.xml file with the original migapp.xml file. I have loaded it into both XML Notepad and MS Visual Studio 2010 Express there are a few syntax error that appear even after I apply the schema but none of them are the line referenced in the error log. I've attached the error log and copied it below. This is my first post so not sure which is the preferred method. -------- 2011-06-22 14:02:09, Info
  • Create New...