Re: SMS Installer Open File Security Warning

Can you send me the KB article showing the work around?

When you do the unlock is this something you would need to do on every
machine? Can it be automated? Is it a reg setting? Could AutoIt be used?

Thanks,
Terry

"John J. Jobst" <john.j.jobst@xxxxxxxxxxx> wrote in message
news:%23PlrKJlrFHA.2596@xxxxxxxxxxxxxxxxxxxxxxx
> No, editing the registry does not help. The only thing that actually
> worked was a VB Script which actually changed the Process Environment. I
> think I am stuck with changing the "Unblock" property of every patch I
> want to distribute this way.
>
> Thanks for your help.
>
> "Terry Matthews" <nospam@xxxxxxxxxxx> wrote in message
> news:%23F$13nkrFHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
>> If it works when you have the environment variable added then do the
>> following... by the way you said the name of the variable but not the
>> value of it?? so I just used c:\test change as needed.
>>
>>>>>>>>>Cut and paste below into SMS Installer<<<<<<<<<<<<<
>>
>> item: Edit Registry
>> Total Keys=1
>> Key=SYSTEM\CurrentControlSet\Control\Session Manager\Environment
>> New Value=c:\Test
>> Value Name=SEE_MASK_NOZONECHECKS
>> Root=2
>> end
>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>
>> Good luck,
>> Terry
>>
>>
>>
>>
>>
>> "John J. Jobst" <john.j.jobst@xxxxxxxxxxx> wrote in message
>> news:%23kN6fJkrFHA.2588@xxxxxxxxxxxxxxxxxxxxxxx
>>> I'm having no luck at all.
>>>
>>> I also tried the HCU\Environment and HCU\Volatile Environment keys with
>>> no luck.
>>>
>>> I wrote a .vbs script (which works as described in the KB article) and
>>> paused it in the middle so I could search the registry. There is
>>> nothing in the registry!!!
>>>
>>> The "Unblock" security button in the General Properties of each patch
>>> seems to be the most promising right now. I haven't figured out why
>>> that property does not appear on all patches yet. Some of the Adobe
>>> Reader patch files have it and some don't.
>>>
>>> "Terry Matthews" <nospam@xxxxxxxxxxx> wrote in message
>>> news:%23SPLZRXrFHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Cool, good luck.
>>>> Terry
>>>>
>>>> "John J. Jobst" <john.j.jobst@xxxxxxxxxxx> wrote in message
>>>> news:%23$mUA2VrFHA.2624@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> 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.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Loading