Unsolved
This post is more than 5 years old
45 Posts
0
183778
vWorkspace 8 User Service Accounts
Hi, I'm building production vWorkspace farm and I'm wodering if I need seperate domain user account for vWorkspace services? For example, I'm about to add the Hyper-V server and its asking for Root Node Credentials, should I create a seperate account or use my own. In the DEV enviroment I used my account without thinking about it too much, but in production, I'm afraid that if my account is disabled everything will stop....
Do I need a dedicated domain user account for anything involving vWorkspace? If so for which roles/services? What is recommended practice?
thanks
Dejan
DELL-David Y
228 Posts
1
June 27th, 2013 20:00
Hi Dejan,
We would recommend that you do use a seperate account for vWorkspace Services and also the vWorkspace Administrative user. The account(s) should ideally have a non-expiring password and should be exempt from lockout due to incorrect password so as to allow the services to run without interruption.
Regards,
David
dkgcb
45 Posts
0
June 28th, 2013 11:00
David, thanks for reply. Is there any documentation that would outline which services and roles I would have to run under the separate domain accounts?
dkgcb
45 Posts
0
September 5th, 2013 18:00
Hi David,
Just to follow up to this question, I came up with the list of Quest Services that run under Local System account by default in the VW farm. Since Local System account has full permission to the local machine, would you be able to tell me if any of the following services need to stay under Local System? I would like to change all services to run as regural Domain Account due to security reasons.