originally posted this over on the scripting forum, might have been the wrong place :S

Im creating a script on our k1000, mainly a batch file with a number of dependencies, to help with building our new pcs. Part of that process involves removing unwanted Windows components, and the best way I can see is using Windows' sysocmgr.exe
Ive created the answer file, and have run the command which works a treat, but deploying the script via k1000 it fails, sysocmgr (Windows XP Setup) starts up but fails with error "The application could not be initialized". Heres the command im using:

start /wait sysocmgr /q /r /i:%windir%\inf\sysoc.inf /u:"\\path\answerfile.txt"

ive tried running the batch manually, and even tried running it manually using the SYSTEM account using the AT command and it does run fine.
also tried creating a vbscript which uses runas with the sysocmgr command to try and run it as another user, but that too fails when run through k1000 script.
Im stuck and out of ideas as to why its doing this when run via k1000, anyone else had experience scripting sysocmgr on K1000? have any suggestions where the problem is?
any help or ideas are welcome. thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I've gotten sysocmgr working out of the k2....

A couple of things that stand out for me.

What type of script is this (kscript or shell)?

Also is you answerfile on a network share?

Have you tried adding it as a dependency.
Answered 02/09/2012 by: dchristian
Red Belt

Please log in to comment
0
thanks for the suggestion dchristian,
have added the command as a post install task on the k2000, worked a treat.
still unsure why it wasnt working via k1000, spent enough time trying to work out, so am leaving at that.
Answered 02/13/2012 by: rjonesdj
Orange Senior Belt

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