User for rrService

Parent Previous Next

What is the rrService user?


If you install the rrClient or rrServer as service, then the service starts the rrClient/rrServer with a different user account.

The user change is required as the local root/system account is usually not able to access the fileserver.



Requirements for the rrService user


In a nutshell, the rrService User has to be able to

  1. Login at the local workstation.
  2. Access to the fileserver share with the RR folder.
  3. Access to the fileserver share with your scene/project data.



Explanation:

The rrClient needs to have access to the files on your fileserver.

And for any file access to a different machine you need to have a user name and password.

So the service starts the client with the login of a "rrService User".

The rrService User can be any user login in your company.

Any user, that is able to access all required data on your fileserver.



Is user XXX the right user?


If you login on your workstation with user XXX and you can access all project data (without entering any further password!), you can use user XXX.

Some companies prefer to create a new user YYY only for RRender (so they can track file access at the file server).



Windows: Test if user XXX can be used:



Windows Notes


Internal/Real User Name:

If you have renamed the display name of you user, then windows still uses the original user name internally.

To check the user name, please right-click on the computer icon (desktop or start menu) and choose "Manage".

Select "Local Users and Groups".

You have listed all users with a "Name" and a descriptive "Full Name".

RR requires you to use the "Name".




Local Admin / Privileges (this does not apply for the rrServer):

The User needs to be either

a) (recommended) in the local group "Administrators" .

(it is not required to be a domain admin, it only needs to be a local admin on the workstation)

OR

b) (not recommended) the user has to be in the group "Performance Monitor" ,

and it requires at least the local privilege "Debug Programs", "Create global objects" and "Replace a process level token".
       (you can change privileges via the tool Control Panel / Administrative Tools / Local Security Policy. In that program "Local Policies/ User Rights Assignment")

Note: You probably need to add additional privileges, otherwise the client can not execute functions like "Shutdown Machine" or "Sync time with server".



These rights are required for:



Local or Domain User?


Are you in a domain and it is a domain user? Then you have to enter the domain name at the installer.

If not, then the "domain" edit line has to be empty.


If you are not in a domain, then you have to manually create the user on each workstation.

If you create a user, check "password never expires" and UN-check "user has to change password on first login".


Please try to login with that user on the workstation after you created the user.

Cause windows could tell you more detailed information if there is a problem.

And it creates user preferences which are required for some renderer or plugins.