Number 1, I am talking more about the fact that when you refresh settings shouldn't the script actually just stop the service, update the registry settings and ACL for the profile that's installed to that machine. This will help make any recovery process faster. Or even what about putting a check to see if the files exists in that location and based off certain critera resend the files, aka corrupted or don't exist.
Number 2, I was talking more about the Venm console not showing that a station has been deployed to. I was able to duplicate the problem by moving groups locally, deploying to a machine, then just changing the location of the groups back to the network shared location where it shows that station hasn't been deployed to. When you try to connect from the console that shows it's not deployed, I get the same error. Whats actually happening in our case though is that from the shared location the console looses the information about what deployment was made to a machine, so instead of showing say deployement of Default made to a machine, it will list nothing and have VNC or RDP as false.
Number 3, awesome.
Number 4, what about creating a directory that is used privately by VENM and when you set the location of the files to a network location, it copies the files from the main location and uses that cache in a read-only mode. and have it write any updates to the network location. Or just copy the files from the main location to the cache, and then subscribe to the network location for all updates etc. Or, even writing a small module that resides on the machine with the network share that the other consoles report to and it handles all of the XML transactions between the consoles.( just a few ideas)
Number 5 where you reference the forum at sysinternals, I found this; If you use psexec to execute a command on a remote machine, wherever possible try to avoid using the psexec -i option. The -i option will create a visible window on the remote machine.
Is it possible to prevent the window from popping up at all? This would prevent this issue altogether?
Number 6, I switched the push engine to PSEXEC rather the Beyond exec, and don't think I've encountered the error yet. Not sure if this will help or not, but I am using the console on Vista.
Thanks again,
EricJ