Flash8 remote install issue
I'm trying to do a push install of flash player 8 using the redist install_flash_player_active_x.msi. On Win2k systems everything went fine, but on XP SP2 systems, the install hangs.
I went to one of the SP2 systems and ran the install locally and got an openfile - security warning asking if I wanted to run or cancel the file. It's this popup box that is hanging my push installs. There is a check box for Always ask before opening this file, which is checked. I really don't want to have to go around to dozens of systems to install this manually.
What security feature is generating this dialog and what GPO or reg edit can I use to turn it off? I know it's not coming from the SP2 firewall as I created exceptions for both msiexec and the flash installer to no effect.
I went to one of the SP2 systems and ran the install locally and got an openfile - security warning asking if I wanted to run or cancel the file. It's this popup box that is hanging my push installs. There is a check box for Always ask before opening this file, which is checked. I really don't want to have to go around to dozens of systems to install this manually.
What security feature is generating this dialog and what GPO or reg edit can I use to turn it off? I know it's not coming from the SP2 firewall as I created exceptions for both msiexec and the flash installer to no effect.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
yarborg
18 years ago
This has to do with Trusted Sites in SP2. Depending on what server or location you are installing this from XP SP2 will pop up a dialog box. This is especially true if the installation location is an IP address or fully qualified domain name like server.my.domain.net. So if you have \\server.my.domain.net\share\softwarepackage.exe then you will probably get a prompt.
I would try, on one machine, adding the *.my.domain.net (substituting your domain or machine name) to the list of trusted sites in Internet Explorer then try and replicate the error.
Let us know how this turns out.
I would try, on one machine, adding the *.my.domain.net (substituting your domain or machine name) to the list of trusted sites in Internet Explorer then try and replicate the error.
Let us know how this turns out.
Posted by:
Babscoole
18 years ago
That was my finding as well. I did wind up getting the issues taken care of though.
1) First I pushed out a regfile that added the machine hosting the msi to the trusted sites zone at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains.
This may also work if set to HKEY_USERS\.default\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains, but I didn't test it.
2) Then I pushed the msi out and it installed flawlessly.
3) Quick edit to my reg file to set it to delete the new key and sent that out.
Thanks for the pointer and hopefully this will help somebody else.
1) First I pushed out a regfile that added the machine hosting the msi to the trusted sites zone at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains.
This may also work if set to HKEY_USERS\.default\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains, but I didn't test it.
2) Then I pushed the msi out and it installed flawlessly.
3) Quick edit to my reg file to set it to delete the new key and sent that out.
Thanks for the pointer and hopefully this will help somebody else.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.