RE: Unsigned batches / scripts Never Run
- From: Matthew Hudson <MatthewHudson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Jul 2007 12:52:02 -0700
to show the dos popup box you will need to enable "allow users to interact
with program" otherwise it will be hidden from view and just time out.
and make sure it isn't set to hidden but maximized or normal.
--
-----------------------
http://sms-hints-tricks.blogspot.com/
"SuperScriptMan" wrote:
Thanks for taking the time. Programs is not disabled (good idea though)..
Right now we are doing a simple model package that just opens a DOS window
and then
opens Notepad. When we were starting out some years back this was our
"health check" after sp updates, rebuilds etc... Web report indicates
"running" though it doesn't show up in the task list and then the dreaded
"run time exceeded" shows up after some time. All other packages, MSI,
executables are fine. No issue.
Thanks again.
"Matthew Hudson" wrote:
I have never signed my scripts (batches, vbscript,exe) and I have never had a
problem. I am running exactly that same structure as you mentioned.
When you say it downloads but never runs, could you tell me the error. I
assume you checked the package to make sure the program and a part of the
chained programs was not disabled. This would create the senerio of SMS
downloading the files but not kicking it off since it is disabled in the
program section of the package setup.
--
-----------------------
http://sms-hints-tricks.blogspot.com/
"SuperScriptMan" wrote:
Team,
Our SMS team has written many batches / small exe's to punch down registry
keys, copy files etc... Our environment has been at XP-SP2 for some time.
Suddenly (likely Policy change at AD level) our homegrown files will download
but never run. Patches and signed executables continue to work well and have
been for over 3 years , running 2003sp2, adv-sec, schema-extended.
What is the community doing about this , is everybody signing their own
scripts ?
Is this an unusal problem ?
I can't find much on this. I know it can't be a hard fix, but it is eluding
me.
Any idea appreciated.
TIA
- Prev by Date: SMS Client on Win 2000 Server - Failure
- Next by Date: Re: A failure exit code of 1603 was returned - ACROBAT 6.0 STD
- Previous by thread: SMS Client on Win 2000 Server - Failure
- Next by thread: Discovery and SWD Recommendations
- Index(es):
Relevant Pages
|