If SnapManager is installed on a Windows Server system and you want to launch a script from a UNC (Uniform Naming Convention) path, you need to add the host where the script is located to the Internet Explorer list of trusted sites.
About this task
- If SnapManager is installed on a Windows Server system, and you attempt to launch a script from a UNC (Uniform Naming Convention) path, SnapManager might hang. When this happens, the log file shows no indication of the failure and the last line of the log text “The specified command has been launched successfully.” does not appear.
- Windows Server 2003 or Windows Server 2008 ships with Internet Explorer's Enhanced Internet Explorer Security Configuration enabled. This setting is restrictive and prevents batch files located on a network share from running. The network location needs to be added to Internet Explorer's list of trusted sites.
- The system you log on to can be the same system that is running SnapManager, or it can be a different server. Log on using the same user account that SnapManager is configured to use.
- The security settings are specific to each user account on each machine. You need to repeat this procedure for on all machines that are used to run scripts and for all users who might launch the script on each machine. You will also need to repeat these steps if you start using a different user account to run SnapManager.
Steps
- Log in to the Windows Server 2003 or Windows Server 2008 system that will be running the script.
- Launch Internet Explorer.
- In the menu bar, select .
- In the Internet Options dialog box, select .
- In “Add this Web site to the zone,” enter the host name of the machine from which the script will be launched and click Add.
- Click OK.
- To verify your changes, browse to the network on which the script resides and launch the script.
The script should now run normally without security prompts. The script might fail to complete properly because the SnapManager variables are not passed to the script in this test.
