Replicate my Version Control Agent Settings in all my Servers

[orven]

I need to propagate the settings of my Version control agent.

I found out how to do it in my SIM5 where is also my VCRM.

The question is what about the login account and password for some of my legacy VCA. I'm using Windows 2003 with latest VCA as my source. I'm afraid there might be a conflict for those old ones.
Any trick

[Craig McK]

Hi Orven,

I believe the older VCAs use the Administrator/Operator/User logins to contact the VCRM, whereas the new VCAs use domain authentication.

From what I recall you can create a local user on the CMS to match whatever is specified on the legacy VCA, but I'm not 100% on what permissions it needs..

I've found that installing the new VCA and System Management Homepage (SMH) don't require a server restart, so I've been updating as many as possible rather than setting up the reverse compatibility..

Has anyone else set this up?

[orven]

Thanks. If let us say I would your suggestion and upgrade VCA and the SMH can I do it in the console and push ior I have to do it manually.

[Scott_278]

What I would do is first find out what version of the VCA your CMS is running, or decide on a standard version. Then I would pre-configure that package with your settings - the name of the VCRM and credentials to access it. Then I would push out that version of the VCA to your "clients" from SIM. That will simultaneously upgrade and configure them.

[Scott_278]

And to answer your question of whether you have to do it manually or through SIM, the answer is that you can do it either way. However to do it through SIM, you must have the trust relationship set up. To do it manually, you don't have to log into each server. You could use the Remote Deployment Utility to push it from a single console. But you would have to do it one-by-one.

[Craig McK]

I found the CMS wasn't able to update the old VCA even though it's trusted - I just got "Agent Failed Command"
I think was because the VCA hadn't been configured to talk to the VCRM which takes us back to the initial option of configuring the administrator/operator user..

I was just updating them using the remote deployment util in batches =)

[orven]

I have decided will just keep all my legacy for now..

By configuring the option administrator/operator user I can then replicate my VCA settings(SIM5, Windows2003, latest SMH) regardless of versions to my target servers.

so how can I configure my legacy VCA to talk to my VCRM which takes me back to the initial option of configuring the administrator/operator user..

[Scott_278]

Couldn't you configure one of your legacy clients, then replicate the settings from one legacy box to the others?