Posted by Grant Foraker on March 16, 2009 at 07:43:19:
In Reply to: Vista won't run posted by Grant Foraker on March 12, 2009 at 11:41:23:
We're getting off point. I don't know if UAC is on or off. I think the Vista PC has Symantec AV.
Comet was running fine with 393. Broke when upgraded to 397 and the new Comet Console methodology.
Things that need fixing.
1) Comet needs to be signed. That should solve the UAC annoyance. This appears to be REALLY important for all the 64bit OS's. I'll post a newsletter about self-signing.
2) Post 393 problem.
Symptoms.
a) Vista Network Workstation that has never had Comet Server installed gets "server not found" error.
b) Server 2003 with Comet Server installed. After reboot Comet gets restablished fine on the Server Console. When you connect remotely to a second session, you get the "pipes" error, "bad" consoles, and have to close the Comet consoles manually. This may be entirely due to having the console exe's in the Startup folder for all users.
c) From other postings, I gather that something like b) happens when you add a second user to a Vista PC.
For now, if I install Comet Services on the problem PC, what other steps do I need to do to make the workaround invisible to the user.
1) delete the exe's from Startup?
2) change CometServices from Automatic to Manual?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.