Understanding the client computer privileges

All Meridian users require the following minimum privileges on their own computers:

• Membership in the Administrators group to install the Meridian software. See the following note.

• Internet Explorer security settings as described in the BlueCielo Meridian Enterprise User's Guide.
• Internet Explorer security settings enabled for the Local Intranet zone to download, install, register, and activate DLLs and ActiveX components that might be required by PowerUser extensions. See the additional information that follows and the note.

• Read access to C:\Program Files\BC-Meridian and subfolders
• Read access to C:\Program Files\Common Files\Cyco Shared
• Read access to C:\Program Files\Common Files\Autodesk Shared
• Read access to C:\Windows\System32

• Read and Write access to C:\Windows\Downloaded Program Files. This folder is the ActiveX cache for user interface extensions that are downloaded from the Meridian server as needed. Extensions are only needed by users of vaults in which the extensions have been registered as described in the BlueCielo Meridian Enterprise Configuration Guide.

  Note    By default, user interface extensions are installed in this folder for all users of the computer. For information about installing extensions only for a specific user, see the BlueCielo Meridian Enterprise .NET API Reference Guide. When user interface extensions are installed for a specific user, the extensions are placed in a sub-folder of the folder that is specified by the Windows environment variable LocalAppData.

• Full access to the C:\BC-Workspace folder. They must also have full access to the sub-folder that matches their user name.
• Modify access to the folder specified by the Windows TEMP system variable or if a TEMP user variable is defined, that folder, which overrides the system variable.

Note    Ideally, users should be a member of either the Administrators or Power Users group of their own computer, unless read/write access has been granted for a lower group for which the user is a member. If this is prohibited by your organization’s security policy, an alternate method for installing Meridian and deploying extensions must be used. Common alternatives include manual installation performed by a system administrator or using a centralized application deployment system such as Microsoft Systems Management Server (SMS).