Enabling Post-Connection Scripts to Run Without User Intervention
This article describes the steps necessary for setting up a Windows 2003 server for unauthenticated file share access so that Connect/OnDemand tunnel client post-connection scripts will run on computers that are not logged into a domain. When you define a post-connection script by UNC (\serversharescript.bat, for instance), Connect Tunnel and OnDemand Tunnel will attempt to run that script, but a Windows system will not prompt the user to authenticate to the share. The result is that the script will not run. The following procedure will describe how to set up the fileserver for unauthenticated access so that users can still run this script even if their system is not logged into a domain.
NOTE: The following procedure should be validated against your own security policy.
A file share has been configured and enabled on a Windows 2003 server
The post-connection script UNC (for example, \serversharescript.bat) has been configured in the community to which users will log in.
Run Group Policy on your local computer: in the Start > Run box, type gpedit.msc.
In the Group Policy Editor, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.