By CA Unicenter I assume you mean Desktop and Server Management? I run it in a VM Environment. (Note, CA Unicenter is a suite of many different products, I think there are about 20 of them.)
Thus, I suspect you are using the Remote Control feature of "DSM.
Which version are you using?
Can you attach a screenshot of the error?
Note, Unicenter Remote Control uses Microsoft Terminal Services to make the connection, it just adds another layer on top for security purposes. If you can't connect with mstsc.exe, then you won't be able to connect with Unicenter Remote Control either.
I take it you have the agent running on each of the target VMs?
I've attached a screen shot of the error
I'm using Unicenter Remote Control version 6.0.77
Just clarification, I connect via mstsc to the virtual machine then I try to connect to the virtual machine via unicenter, a pop up message comes up on my terminal services session and I select Yes to accept, that's when i get the error.
If I am connected to the VM via VC console it works fine.
by the way, I'm no expert on CA.
thanks for the replies
ca.JPG 135.5 K
Ah, you are running 6, I pity you! I work with 11.2 much more, which is a bit more fun.
First thing to try is to reboot the target machine. In version 6 you need to reboot after the agent install OR reboot after connecting to the machine via terminal services. That is, if someone connects to the machine with Terminal Services it will mess up the Unicenter Remote Control agent and you will get the video error.
That would be the first thing to try on my list.
I guess I am an expert on CA Unicenter as I am a consultant who makes my living off of installing Unicenter DSM r11.2
(Argh, the internets went funny and I double-posted. I think the tubes got blocked with a truck.)
Message was edited by: Mr.Flibble
I rebooted a virtual machine and tried again but still the same error, I've checked with our "expert" here and he has now logged a call with CA. He likes, that an updated to 11 will help...
Well, here is hoping you go to r11. Note, if you do, it will be much easier to perform a full new install than an upgrade. Trust me on that.
Here are a few other solutions I have seen for URC 6:
- From the console, log into the machine, then log out. (Yes, I know, seems strange)
- Run Terminal Server Manager and search for session id then execute the following command :
reset session <SessionID> /server:<servername> /v
A few other things to check:
Is the VM a 64 Bit version of windows? If so, URC 6 won't work on it. You will always get that error message if it is 64 bit. (Works in version r11 though.)
If it is not 64 bit, then under your address book, go to the target machine, then connecte and options. Under options select "color reduction".
I hope this helps!