Re: SMS Installer Open File Security Warning

I've found environment variables in
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment. I'll try
setting it there.

I'm simply doing an execute program script item on just the patch
executable, not calling c/wscript. I'm using SMS Installer scripting to
determine if it is a workstation or server so I can automatically reboot
workstations, but make the server reboot an option for an administrator who
comes along after the thing runs. I also make sure to launch the patch with
"silent" options. And some patches come in different flavors for different
OSs, so I use the scripting to determine which patch to launch. I know I
could do all of this in any number of different scripting languages, but SMS
Installer scripting is the one I'm using right now.

Thanks for the hint, I'll be giving it a try today.

"Terry Matthews" <nospam@xxxxxxxxxxx> wrote in message
news:OuOH8AOrFHA.3596@xxxxxxxxxxxxxxxxxxxxxxx
> You can add the environment variable through the add registry keys area,
> instead of using the script item to get around that.
>
> I remember posting the registry location a while back answering someone
> else's question, but cant seem to find it right now. Let me know if you
> cant figure it out and I'll track it down.
>
> By the way how are you executing the security patch? Are you doing a
> execute program script item and directly launching the exe? Are you
> calling cscript or wscript first? Are you "repackaging" the original
> install or just launching the executable?
>
> Good luck,
> Terry
>
> "John J. Jobst" <john.j.jobst@xxxxxxxxxxx> wrote in message
> news:OS95z5KrFHA.2596@xxxxxxxxxxxxxxxxxxxxxxx
>>I am repackaging a patch I have downloaded with an SMS Installer (32-bit,
>>v2.0.148.00) script. I am trying to run the patch silently. When it
>>runs, it gives me the Open File Security Warning dialog box. If I respond
>>to that, then the patch will run silently. I found an article, 889815
>>(The Open File - Security Warning dialog box is displayed when you try to
>>silently install a hotfix or an update by using a Visual Basic script in
>>Windows XP Service Pack 2), which describes what is happening, except I am
>>using SMS Installer instead of Visual Basic. The workaround is to set an
>>environment variable before running the patch. The environment variable
>>name, SEE_MASK_NOZONECHECKS, is longer than 14 characters, and the SMS
>>Installer gives an error when compiling. Is there a different workaround
>>for this? Thanks.
>>
>
>


.

Relevant Pages

  • Re: SMS Installer Open File Security Warning
    ... You can add the environment variable through the add registry keys area, ... instead of using the script item to get around that. ... By the way how are you executing the security patch? ... >using SMS Installer instead of Visual Basic. ...
    (microsoft.public.sms.installer)
  • Re: SMS Installer Open File Security Warning
    ... I've been doing this procedure for every patch I've been downloading form MS ... > I'm simply doing an execute program script item on just the patch ... but SMS Installer scripting is the one I'm using ... >> instead of using the script item to get around that. ...
    (microsoft.public.sms.installer)
  • Re: SMS Installer Open File Security Warning
    ... I'm having no luck at all. ... The "Unblock" security button in the General Properties of each patch seems ... >> I'm simply doing an execute program script item on just the patch ...
    (microsoft.public.sms.installer)
  • Re: [PATCH x86] [5/16] Replace hard coded reservations in x86-64 early boot code with dynamic ta
    ... Can't you just convert them using a script on new if you care so much about those? ... i'm not sure how you manage patches - if you have some 'refresh patch' ... improve clean _looking_ code than messy looking code. ...
    (Linux-Kernel)
  • Re: Retrieve installation path of a software using VBScript
    ... Your script is fine, ... I think the Windows Installer (MSI) system has got ... Planning to build on this script once it succeeds at the uninstall. ...
    (microsoft.public.scripting.vbscript)