I'm running VXC Manager 4.9 on a Windows Server 2008 R2 machine, and I'm using it to manage several 6215 clients in a test environment. The clients get their network configuration from a DHCP server which has all of the correct scope options set to point them to my VXC-M server. I'm noticing some strange behavior when using the VXC manager: Three of my clients are running HAgent version 4.3.115. I've attempted to updated them to HAgent version 4.3.94, but have been unsuccessful. I can push the update package out to those clients, and I see them reboot a couple of times, but when they finally come back online the HAgent version has not been updated. It takes several tries to change the device information on one of the clients. In VXC-M under Device Manager, I right-click the client, choose "Change Device Information", and give the device a new name. When I click [OK], the device reboots, but the name is not changed. I've tried refreshing the view and forcing the client to check in with the server ("Refresh Device Information"), but the name of the client doesn't change. I have one device that sporadically refuses to reboot when issued that command from the VXC Manager. Sometimes it reboots instantly, and other times it won't reboot at all. I've noticed that when I issue a command to one or more clients (whether it be a reboot command, or pushing out a package), the RDP session to the Windows 2008 server that is hosting the VXC-M freezes up for about a minute. I thought this might have something to do with it sending out broadcast traffic on the network, but I'm not sure. I feel as though these problem I'm experiencing might be related somehow, but I've run out of ideas for places to look for the problem. Any suggestions that anyone could offer would be appreciated. Thanks in advance.
... View more