See Configuring the RSCM Server for the procedure on setting up the RSCM Server on Windows.
If the project data is on a remote file system, the iCDBNetLauncher (RSCM Server) must run as a user process that has read/write permissions to the project file location. It cannot run as a System process because the System account does not have write permissions to the remote file system.
Be sure that groups and user accounts have permissions set properly so everyone can access the project data. See File, Folder, and Share Permissions on Windows.
The topic Examples of RSCM Server Configurations for Windows provides practical scenarios for setting up the RSCM Server on Windows.
If your systems are part of an Active Directory or Windows NT domain, you should authenticate your RSCM Service with a domain account if you use the This Account option. This gives the iCDBNetServer processes seamless access to design data with normal domain user, group and share permissions. This is the easiest method to implement and secure.
If you are constrained to using a local account to authenticate your RSCM Service, you must create a local account on the RSCM Server machine and put your design data on a local file system on the same machine. Note that on Windows systems local accounts cannot be included in domain groups.
For an example, see Example C: Using a local account to authenticate the RSCM Server.
The effective rights of a service account that you create to authenticate the RSCM Server credentials work in tandem with the rights of the user account running the client program. Typically, you give the service account full edit rights to the design data and make it a member of all design groups. To resolve conflicts, the most restrictive rights between this RSCM Service account and the user account running the client will be enforced. Giving this account full access does not allow restricted users access to the data through this account.
On Windows machines you can restrict the service account by denying rights to interactive login with it for added security. To accomplish this task you need to have administrative rights on your domain and knowledge of the Microsoft Management Console, specifically the Microsoft Group Policy Management Console. With this you can deny rights for your service accounts to login to any of the computers in your domain while maintaining their ability to authenticate your RSCM Service so it can access remote file systems where you store your data. The specific procedure for defining this security policy is beyond the scope of this document. Please consult your IT professional or Microsoft customer support for information about defining a group policy for your domain.