Hi all,

We're running the 30 day eval and love the package. We'd have bought it already but we've got one major problem that's got us worried. Norton 360 and SEP are both flagging the SC client as WS.Reputation.1 which isn't a virus, just means that it has no "reputation" with Norton. Norton considers this HIGH risk and therefore deletes the file without giving the customer any option to override it. As you can imagine, this scares the crap out of the customer and makes it almost impossible to do remote sessions with customers running Norton/Symantec products.

Norton provides a white-listing service for developers. Are you guys submitting each build with them or is this something we have to just live with? It's very difficult to deal with as it is.

Hi

I am also currently running the 30 day evaluation at present and have been to a customer to load a new Norton 360 installation and have the same problem
as above. I love the product and am ready to buy, but is there a way around this norton reputation issue that will not scare the customer.
The screen connect client program downloads OK but Norton deletes it with no options. Having the customer disable norton before being able to
use screen connect doesnot seem feasible or attractive.

everyone please read comment #2....this is VERY IMPORTANT!

We've added a new 'launcher' that is based on Java Web Start, but it attempts to launch a wrapped up .NET client before it resorts to the java client. This launcher will be now be default for browsers on windows that support Web Start, but not ClickOnce. Hopefully it will cover most of the users who previously got the .NET bootstrapper EXE. We originally developed it for 2.4, but we've backported it to 2.3 and put it in the latest pre-release. It's pretty slick, and depending on your launch options with Chrome and Firefox, it can even be more efficient than a ClickOnce launch.