Jump to content


Mavtech

Established Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Mavtech

  1. I've been scouring the net for 2 days now fighting this issue. This is a Bare Metal XP deployment. I have 2 images. One was captured from an Optiplex 790. The other was captured from a Hyper-V VM. Both images deploy fine back to the 790. But, not to a laptop. I'm working with a Latitude E6420 as my test machine. At first, XP was blue screening with the error 0x0000007B. After applying the correct mass storage drivers in the Task Sequence, it's getting past that point. But, now it's just hanging at Windows XP Setup. I tried the OSDBiosCompatibility TS variable change to true. I've tried to apply a HAL change script. What could be causing this to hang at Setup? What am I missing for the laptop?
  2. You mean running it in the PSEXEC command line? Isn't running it on a VM going to be a problem with no wireless chip present? There is no "Manage Wireless Networks". I have 2 laptops here that I am testing it on. I'll run it on one of those. EDIT: I copied the xml file to C:\temp on the test computer and then cd'ed to that directory using the PSEXEC Command line in ConfigMgr Console on my computer. The Wireless profile created perfectly fine using: cmd.exe /C netsh wlan add profile filename="CTM-CORP1.xml" user=all EDIT2: I just ran the OSD (with this install in the task sequence) on a computer that has never been connected to SCCM. The wireless profile created perfectly. So, this seems to have something to do with the computers previously being known to SCCM. How do I change this?
  3. Do you mean the execmgr log from the client? If so, here it is: This was previously working in the "install software" part of the task sequence during OSD. EDIT: I changed the program to run with the user's rights (mine) and updated the DPs. Same exact error happens. I verified in the log that it tried to install as me. execmgr.txt
  4. I've been searching forums all day. I can't find an answer to my issue. I had our wireless network on my reference computer for OSD. But, Sysprep deletes it. So, the consultant (from Catapult) and I previously had this working successfully. We exported the wireless network profile from Windows 7 and created a program to install it (through advertisement and in Task sequence). But, for some reason, it no longer works on my test computers (it works locally but not through an advertisement). In the execmgr log, I am seeing this: Looking for MIF file to get program status Script for Package:VPK00019, Program: Create Corp1 failed with exit code 1 a couple lines down: Execution is complete for program Create Corp1. The exit code is 1, the execution status is FailureNonRetry I have the program set to always rerun. The below command works from Windows. cmd.exe /C netsh wlan add profile filename="CTM-CORP1.xml" user=all Where do I go from here? Thanks!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.