05-14-2007 06:58 AM - edited 03-09-2019 05:59 PM
I'm noticing some nuances after upgrading a couple of my servers to 5.2. If I connect to a server via Remote Desktop that has been upgraded to 5.2, I am unable to interact with the agent the same way I was with 5.1. For example, I am not able to right click on the tray icon to disable the security. I've done a rule comparison of the 5.1 and 5.2 agent UI rule, but I am not seeing any differences to warrant the behavior I'm seeing.
05-14-2007 11:13 AM
I've had this happen before.
Try running this from a command prompt:
mstsc -v:servername /F -console
If that doesn't work, make sure there is an Agent UI control rule associated with the server group. You need one in order to get the Agent UI.
Tom
05-14-2007 11:22 AM
Yeah, no problem when I use the console switch, but I was just curious as to why Cisco changed the behavior.
We'll see if someone from Cisco replies.
05-14-2007 01:06 PM
I could be wrong but I think it's always been that way. I've had it happen since 4.0.1.
And my memory could also be faulty...
Tom
05-15-2007 09:10 AM
Mine as well. I could have made a change when I migrated to 5.1, but who knows.
I'll keep playing with it.
05-30-2007 06:58 AM
I got around to re-installing the agent and it works as expected. So, there's something flaky here...
05-30-2007 09:11 PM
I was reading the 5.2 user guide and saw that it was supposed to work as you expected it to.
It has always worked for me, I just never thought about it.
My memory is definitely flaky...
Tom
06-01-2007 05:21 AM
Well, I spoke too soon. I attempted to do another server and it's got the same problem. Now the difference between the one that works and the one that doesn't is the service pack version. The one that works is on SP1, and the one that doesn't is running SP2. So, it appears that there may be an issue with SP2 and CSA 5.2.
06-05-2007 12:22 PM
This sounds like a similar issue in which the agent appears to be disabled when RDP'd into the server, however, the service is actually running. When I RDP using the console switch, it appears as it should. I have a TAC case open and this issue is supposed to be resolved with the next 5.2 patch due out any day.
06-05-2007 12:35 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide