Creating Mapped Drives on the Webspace Server

If you want mapped drives to be available for web users, you can use a batch file on the Webspace Server to log on to share these drives, rather than directly mapping them through Windows Explorer.

For iFIX, an example of a batch file, LoginScript.bat, is provided in the C:\Program Files\Proficy\Proficy iFIX\Programs folder. A batch file, such as this example, can run on a global-basis when any user logs on, or on a user-specific basis. For steps on how to add a batch file script to the logon process, either global or user-specific, refer to the Logon Scripts section. If the Administrator wants to change the location of the batch file, be aware that the new location must be accessible to all the web users.

Note: User-specific project paths for Webspace sessions are not supported. For example, you cannot use different directory paths for iFIX files, such as pictures, across multiple users.  If you need to support this, it is suggested that you use iFIX with Terminal Server, instead of Webspace.

If all users require access to the same network share through a drive mapping, the drive mapping will generally need to be defined in a logon script, such as defined in the LoginScript.bat example.

If you are using shared folders with Local Windows users (not on the Domain), make sure that the user is present on both the Webspace Server machine, and the machine which contains the shared folder.

Be aware that the Webspace Server cannot back up logs to a network folder. For example, if you type a UNC path or a mapped network drive in the folder edit box, the following message is displayed: "Please specify a usable Windows folder where log files may be written."

Be aware of the Microsoft limitation on shared directories. Please see article KB5062 on the GE Knowledgebase:

Mark all of the paths (with their folders) that will be shared for the Web Clients as read-only. This will avoid running into the Microsoft's limitation for sharing files.