Just updated to 3.6 over the weekend, and we're having issues deploying WIM images created prior to 3.5. For those that remember, WIM imaging used to be a workaround, with mid-level tasks that called VBS files to apply the WIM file from a subfolder in PETEMP.

I just get errors now stating that the file can not be found. Any ideas? I have a ticket open, but still waiting for a call back.

Here is a list of errors when deploying one of my regular WIM images:

  • WIM images - wont deploy via mid-level task. File not found.
  • Win 7 MBR (set to deploy after WIM)- file not found *
  • Script to allow me to set reboots during post-install tasks (call runonceex_converter.bat). This was also a work around posted by KACE a while back. This generates a completely different error.
* - MBR code:
 bcdedit /store C:\boot\bcd /set {bootmgr} device partition=C:
bcdedit /store C:\boot\bcd /set {default} device partition=C:
bcdedit /store C:\boot\bcd /set {default} OSdevice partition=C:
3 Comments   [ + ] Show Comments

Comments

  • We just got new replacement kbox's, have not had time to play with 3.6 yet. Going on vacation for the month of March and do not want to cause major changes prior. One idea I have you can try is to move your mid level tasks up to the preinstall level so all the work is done there before the new imaging engine kicks in.
    An alternative is to manually deploy the wims to a pc and do not reboot it, turn around and capture them back into the 3.6 system.
  • Thanks for the info - I could always do that. Do you know of imageX is built into the KACE WinPE environment? If so, how would I manually deploy? Not familiar with deploying WIM images manually...
  • Hmmm so I guess imagex is built into WinPE K2 environment. I'm trying to deploy the WIM image by the following:

    1) net use z: \\x.x.x.x\petemp\ImageStore
    2) imagex /apply z:\390sysprep.wim 1 C:\

    Going to let it deploy, then immediately capture again in 3.6. Let's see if this works...
    • yea that is the exactly it
Please log in to comment

Answers

0

add 'cscript' before the .vbs file name, so:

cscript apply_wim.vbs

Corey
Lead T3 Enterprise Solutions Consultant, K2000

Answered 02/24/2014 by: cserrins
Red Belt

  • Thanks, will try that. To do it properly, should I deploy the WIM files to the machines and recapture? I don't want to break support in future releases either, so I'd rather get on the same page.
  • But don't add //nologo after it, I had that and the Task Engine didn't like it... I'm sure this will be a good addition/upgrade once I get all the syntax fixed!
Please log in to comment
0

no, a recapture is not necessary, this change has to do with how pre/mid/postinstall tasks are now handled by the task engine.

Corey
Lead T3 Enterprise Solutions Consultant, K2000

Answered 02/24/2014 by: cserrins
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share