/build/static/layout/Breadcrumb_cap_w.png

k2000 Postinstall Tasks not deploying to our x64 Images

We have recently updated our k2000 unit to 3.5 from a much old version. Currently I have worked to get the driver store working, and for the most part deploying to our workstations both x64 and x86. However with our x64 images none of the post install taskes are not deploying, and the post image cleanup is not occuring on our images. I have tried going through and modifying the images with the various suggestions on the forums here.

I have re-deployed the scripts with our installs running call, start /wait msiexec, and what our scripts where previously.

Summary:
x64 bit images our not naming using wsname, deploying any secondary software. The strange part of this is the x86 images are all still working correctly. Any help on this would be greatly appreciated.

 

Note: i have been using the x64 bit images as wim over the K-image if it makes a difference I will swap back.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: nheyne 8 years ago
Red Belt
0

Sounds like something is not deploying correctly and is halting the postinstalls.  Can you list what postinstalls you are using?  You can try narrowing it down by only including the first postinstall, and if that works add the next one, and so forth.


Comments:
  • I agree with this. It's usually a .bat file you uploaded as an app. Make sure you are calling the .bat file in the command line rather than just entering <name>.bat. - dugullett 8 years ago
  • Task 1:

    start /wait wsname.exe /N:$CHASSIS[DE;LT]-$SERIALNUM[7+]

    Also Tested:

    call wsname.exe /N:$CHASSIS[DE;LT]-$SERIALNUM[7+]

    Also Tested: (Which is the original that worked)

    wsname.exe /N:$serialnum[7+] /logfile:rename.log

    Task 2:

    call package1.exe

    Also tried

    package1.exe

    Task 3:

    start /wait msiexec /qn /i "Package2.msi"

    Task 4:

    start /wait msiexec.exe /qn /i ampagent-5.3.53177-x86.msi HOST=server.com

    Task 5:

    call shutdown -r -t 03


    These are our core basic software deploys. Once I can get these working I would like to expand it out. I was getting used to making and deploying pre-built installers. - rattrap 8 years ago
    • So in this case, since I don't know what your package.exe tasks are doing, I would start with just WSNAME and verify that it works. Then add the 2nd task only and see if it completes successfully. If it does, add step 3 and so on. You should be able to narrow down which step is the culprit. - nheyne 8 years ago
  • In case any one come across the issue, I was unaware that when updating images there is a tag file left over. In C:\windows\setup\ there is a folder called script. After working with support on this, and removing the folder on the image the post install tasks all ran successfully. On testing on our other images that had the same issue the removal of this folder seemed to fix everything. I just wanted to let you all know that the issue was not in the scripts but in a tag file.


    thanks for all your help with this! - rattrap 8 years ago
    • I just ran into something similar, there was a batch file in the scripts folder that was halting sysprep from finishing. I think it was related to the postinstall converter because I only had an issue when I wasn't using it. - nheyne 8 years ago
Posted by: SMal.tmcc 8 years ago
Red Belt
0

deply an image and do not reboot the box

from the main screen go to recovery - open a command window copy the bat file from the c:\kace to a stick and post that, it will show your post tasks.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ