Friday, January 09, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
Forgot Password ?



Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Subject: ok what am I missing here?!?
Prev Next
You are not authorized to post a reply.

AuthorMessages
DavidUser is Offline

Posts:50

Send Message
08/29/2008 3:45 PM  

I can't get a custom script to execute in an LTI deployment. I've added a few custom panes to the deployment wizard to collect some info specific to my scenario and all was going great until now... I simply need to add my own script in a task sequence... uh MDT 101 right?

Here is my 'run command line' task:

wscript.exe "%SCRIPTROOT%\Z-test.vbs"

for testing the Z-test.vbs simply does a Wscript.Echo("hello world")

it seems to just get ignored? no errors. I have it right after a standard 'partition and format' task. I then tried to add it as an application with source files and in that case I got this error:

Environment Error! Please restart wizard again

ZTIERROR - Non-zero return code by ZTIApplications.rc = 1
Non-zero return code executing command "X:\Deploy\Tools\X86\TsmBootstrap.exe" /env:SAStart, rc = -2147467259

I also tried it as a 'run command line as' task and specified user credentials, still no go.

What the heck am I missing here? the file is in the deployment point. I named it starting with a 'z' in the main distribution share and did an 'update (files only)', and verified it was copied to the appropriate deployment point.

driving me nuts at the moment. Help is needed, I can't think straight on this anymore today.

KonradUser is Offline

Posts:67

Send Message
08/31/2008 6:33 PM  
I use quite a few custom scripts within my task sequences and I've pretty much done what you describe using a "Run Command Line" task.

I actually use cscript instead of wscript but I can't see how that could make a difference, but you could try it I guess. If you do, you might want to change your test script to use msgbox("hello world") rather than wscript.echo of course, otherwise it will just flash on the screen and go again.

KonradUser is Offline

Posts:67

Send Message
08/31/2008 6:36 PM  
I don't actually name my scripts prefixed with a Z, I use an underscore (so that they'll sort to the top of the folder), although I do use one script I downloaded from the web that does, so it shouldn't be the problem.
DavidUser is Offline

Posts:50

Send Message
09/03/2008 1:08 PM  
thanks Konrad. I changed from wscript.echo to msgbox and now its working. Do you know if mdt forces cscript even if you specify wscript in the command line?
You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > ok what am I missing here?!?



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.



Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt