<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><P>Jason,</P>
<P> </P>
<P>I run the Cisco Microsoft security wizard every month and it includes the stand alone CSA update. Wit hthis version of CSA there is no way for me to configure CSA to allow or permit anything. So, if I am using VNC remotely to perfrom maintenance and updates, how does one avoid this pop up with CSA? I unchecked the use vnc hooks to track desktop changes and checked use windows polling.</P>
<P> </P>
<P>Tom<BR>----- Original Message -----<BR>From: "Jason Aarons (US)" <jason.aarons@us.didata.com><BR>To: "Steve Miller" <MillerS@DicksteinShapiro.COM>, "Thomas LeMay" <thomaslemay@comcast.net>, "Peter Slow" <peter.slow@gmail.com>, "Jason Burns" <burns.jason@gmail.com><BR>Cc: "cisco-voip@puck-nether.net" <cisco-voip@puck.nether.net><BR>Sent: Tuesday, February 17, 2009 8:25:50 AM GMT -05:00 US/Canada Eastern<BR>Subject: RE: [cisco-voip] VNC Connection Flakey?<BR><BR>If you choose CSA updates you will experience this, it warns bout this<BR>in the release notes. I've also seen where after reboot the CSA pops up<BR>a permit/disallow VNC which you don't get on the VNC session. <BR><BR>Some NIC driver updates have caused me to reconnect via VNC.<BR><BR>-----Original Message-----<BR>From: cisco-voip-bounces@puck.nether.net<BR>[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Miller, Steve<BR>Sent: Tuesday, February 17, 2009 7:53 AM<BR>To: Thomas LeMay; Peter Slow; Jason Burns<BR>Cc: cisco-voip@puck-nether.net<BR>Subject: Re: [cisco-voip] VNC Connection Flakey?<BR><BR>I have definitely had OS updates when the server "hung" with VNC and I<BR>had to go physically push the power button on the server, but I don't<BR>recall having a server hand on a simple reboot. <BR><BR><BR>Steve Miller<BR>Telecom Engineer<BR>Dickstein Shapiro LLP<BR>1825 Eye Street NW | Washington, DC 20006<BR>Tel (202) 420-3370| Fax (202) 330-5607<BR>MillerS@dicksteinshapiro.com <BR><BR><BR>-----Original Message-----<BR>From: Thomas LeMay [mailto:thomaslemay@comcast.net] <BR>Sent: Monday, February 16, 2009 8:30 AM<BR>To: Peter Slow; Jason Burns<BR>Cc: cisco-voip@puck-nether.net; Miller, Steve<BR>Subject: RE: [cisco-voip] VNC Connection Flakey?<BR><BR>Recently, I discovered that Real VNC caused one of our Unity servers to<BR>hang<BR>on a reboot. This meant that I could not access the server remotely<BR>with<BR>RDP, APC KVM or Real VNC. It would hand right before Real VNC would<BR>display<BR>the prompt for the CRTL, ALT Delete so that I could enter the log in<BR>credentials.<BR><BR>A quick look at the application logs pointed to Unity Cisco Security<BR>Application preventing the Real VNC "hooks" which monitor graphical<BR>changes<BR>on the desktop. Has anyone else experienced this? I selected the<BR>"windows<BR>polling" option to avoid the use the "hooks" option. The server<BR>rebooted<BR>without getting stuck.<BR><BR>Tom<BR><BR>-----Original Message-----<BR>From: cisco-voip-bounces@puck.nether.net<BR>[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Peter Slow<BR>Sent: Monday, February 16, 2009 6:56 AM<BR>To: Jason Burns<BR>Cc: cisco-voip@puck-nether.net; Miller,Steve<BR>Subject: Re: [cisco-voip] VNC Connection Flakey?<BR><BR>...Or make sure your server isn't experiencing outages or crashes due<BR>to running out of memory or CPU. have you checked for anything like<BR>that?<BR><BR>-Peter<BR><BR>On Sat, Feb 14, 2009 at 10:32 AM, Jason Burns <burns.jason@gmail.com><BR>wrote:<BR>> Use Remote Desktop instead? As long as you're not doing any installs I<BR>> prefer RDP.<BR>><BR>> On Sat, Feb 14, 2009 at 8:22 AM, Miller, Steve<BR>> <MillerS@dicksteinshapiro.com> wrote:<BR>>><BR>>> Has anyone ever experienced a problem with VNC connection ability<BR>coming<BR>>> and going? I know that I need to restart the service every once in a<BR>while,<BR>>> but I have a couple Call Manager servers that are doing this a bit<BR>too<BR>>> regularly. Any suggestions?<BR>>><BR>>><BR>>> Steve Miller<BR>>> Telecom Engineer<BR>>> Dickstein Shapiro LLP<BR>>> 1825 Eye Street NW | Washington, DC 20006<BR>>> Tel (202) 420-3370| Fax (202) 330-5607<BR>>> MillerS@dicksteinshapiro.com<BR>>><BR>>><BR>>><BR>>> --------------------------------------------------------<BR>>> This e-mail message and any attached files are confidential and are<BR>>> intended solely for the use of the addressee(s)<BR>>> named above. This communication may contain material protected by<BR>>> attorney-client, work product, or other<BR>>> privileges. If you are not the intended recipient or person<BR>responsible<BR>>> for delivering this confidential<BR>>> communication to the intended recipient, you have received this<BR>>> communication in error, and any review, use,<BR>>> dissemination, forwarding, printing, copying, or other distribution<BR>of<BR>>> this e-mail message and any attached files<BR>>> is strictly prohibited. Dickstein Shapiro reserves the right to<BR>monitor<BR>>> any communication that is created,<BR>>> received, or sent on its network. If you have received this<BR>confidential<BR>>> communication in error, please notify the<BR>>> sender immediately by reply e-mail message and permanently delete the<BR>>> original message.<BR>>><BR>>> To reply to our email administrator directly, send an email to<BR>>> postmaster@dicksteinshapiro.com<BR>>><BR>>> Dickstein Shapiro LLP<BR>>> http://www.DicksteinShapiro.com<BR>>><BR>>><BR>>><BR>========================================================================<BR>====<BR>==<BR>>><BR>>> _______________________________________________<BR>>> cisco-voip mailing list<BR>>> cisco-voip@puck.nether.net<BR>>> https://puck.nether.net/mailman/listinfo/cisco-voip<BR>>><BR>><BR>><BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> cisco-voip@puck.nether.net<BR>> https://puck.nether.net/mailman/listinfo/cisco-voip<BR>><BR>><BR>_______________________________________________<BR>cisco-voip mailing list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR><BR><BR><BR>--------------------------------------------------------<BR>This e-mail message and any attached files are confidential and are<BR>intended solely for the use of the addressee(s)<BR>named above. This communication may contain material protected by<BR>attorney-client, work product, or other <BR>privileges. If you are not the intended recipient or person responsible<BR>for delivering this confidential<BR>communication to the intended recipient, you have received this<BR>communication in error, and any review, use, <BR>dissemination, forwarding, printing, copying, or other distribution of<BR>this e-mail message and any attached files <BR>is strictly prohibited. Dickstein Shapiro reserves the right to monitor<BR>any communication that is created, <BR>received, or sent on its network. If you have received this<BR>confidential communication in error, please notify the <BR>sender immediately by reply e-mail message and permanently delete the<BR>original message. <BR><BR>To reply to our email administrator directly, send an email to<BR>postmaster@dicksteinshapiro.com<BR><BR>Dickstein Shapiro LLP<BR>http://www.DicksteinShapiro.com<BR><BR>========================================================================<BR>======<BR><BR>_______________________________________________<BR>cisco-voip mailing list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR><BR>-----------------------------------------<BR>Disclaimer:<BR><BR>This e-mail communication and any attachments may contain<BR>confidential and privileged information and is for use by the<BR>designated addressee(s) named above only. If you are not the<BR>intended addressee, you are hereby notified that you have received<BR>this communication in error and that any use or reproduction of<BR>this email or its contents is strictly prohibited and may be<BR>unlawful. If you have received this communication in error, please<BR>notify us immediately by replying to this message and deleting it<BR>from your computer. Thank you.<BR></P></div></body></html>