VC agents with 7.2

[nathan_78]

I have been reading the post with all the security changes with SIM4.2 and understand how the SMH will work.

Our delima is how are the 7.2 agents supposed to connect to the repository?? We are currently using a SIM admin account or the one we setup originally. How is this supposed to work with a domain account. Does it have to be a domain admin?? If we do create that account how have any of you set it up?? We do not want to create a domain account for this because of password changes on such accounts.

Kind of confused on how this will work or best practices for makin this work?!?!?!

[Rob Buxton · Accepted solution]

I set up a local account with admin privs on the Server with the VCRM installed.
The VCA is then configured to use this local account.
Set up one remote Server then replicate the changes to the other Servers.

[Rich Purvis]

Unfortunately I have not been able to find the documentation on this - if I can get a link or point to it in the VC install I will post it here.

Your Q:
"Our delima is how are the 7.2 agents supposed to connect to the repository?? We are currently using a SIM admin account or the one we setup originally. How is this supposed to work with a domain account"

Answer: If the VCRM that the VCA points to was a legacy or old-style Adminstrator/Operator/User account setup then you can continue to use the Adminstrator or Operator account that you had originally configured. There is a backwards compatibility function built into the SMH to recognize VC and allow the old credentials to work if the VCRM was originally setup prior to SMH 2.0. The reason this was done was to allow people to install SMH 2.0 on their systems and *not* immediately break the already functioning VC.

Your Q:
"Does it have to be a domain admin?? If we do create that account how have any of you set it up??"

Answer: The above answers some of your question. If you are on new installations that are using SMH 2.0 you do *not* have to use domain admin accounts. They just need to have "admin" access to the SMH. A way to do this is to create an account called VCAdmin. This account does not need to have any special priviledges in the domain - it does not need to be an Admin account. You then place this account in a group such as MySMHAdmins. You then tell the SMH on the system with the VCRM that MySMHAdmins group should have Admin authority - it is a configuration setting you can do for SMH. This way you have a relatively "harmless" ID - no special priviledges in the domain but acts as an Admin *only* for the SMH.

Kind of a long response - I apologize.
Hopefully that makes sense.

-Rich

[Rich Purvis]

The HP Version Control Installation Guide has some suggestions for this, here is the link:
http://h200007.www2.hp.com/bc/docs/support/SupportManual/c00293375/c00293375.pdf

-Rich