|
|
|
|
Group: Forum Members
Last Login: Tuesday, November 07, 2006
Posts: 2,
Visits: 5
|
I'm currently trying the VNC Manager Enterprise edition. We are thinking about buying it for use in our department. However, I have a couple of questions I need help with first.
First off, we have 1000+ PC's on our domain, and every time I open VNC Manager it has to rescan every one of the PC's, so I have to wait about 5 minutes before I can really do anything with the program. Anyone know of anything to help with this problem?
Also, I need to know what is needed to be able to deploy new VNC releases through your program onto other computers. About half of the computers that it loads in the server list, I click on and it will show a ADMIN$ and a C$ folder on the right side. When this happens I can usually deploy a new version through your software. But some of the computers I click on nothing loads over on the right side, and when I try to deploy it errors out. Is there something that needs to be set on the other end, or a firewall port that needs to be enabled or an exception or something? Any help would be greatly appreciated. 
Hopefully I'll be purchasing this software soon, once I know it will work to our needs.
Thanks for any help!
Adam
adamrgolf@hotmail.com
|
|
|
|
|
Group: Administrators
Last Login: Friday, May 18, 2012
Posts: 1,624,
Visits: 3,043
|
First off, we have 1000+ PC's on our domain, and every time I open VNC Manager it has to rescan every one of the PC's, so I have to wait about 5 minutes before I can really do anything with the program. Anyone know of anything to help with this problem?
I assume you are talking about expanding Network Neighborhoods tree, am I right? If that is so, I would recommend you to register you domain computer in the VNC Manager namespace. This way you won't have to fetch them each time you start the VNC Manager. To do so you can use The Computers Registration Wizard. It allows to fetch computers from an AD and registered all of them.
Most probably in the next v3.6 the Fetching Computers dialog, that's blocking you from working with the VNC Manager, will be gone.
Also, I need to know what is needed to be able to deploy new VNC releases through your program onto other computers. About half of the computers that it loads in the server list, I click on and it will show a ADMIN$ and a C$ folder on the right side. When this happens I can usually deploy a new version through your software. But some of the computers I click on nothing loads over on the right side, and when I try to deploy it errors out. Is there something that needs to be set on the other end, or a firewall port that needs to be enabled or an exception or something? Any help would be greatly appreciated. ?
By default the VNC Deployment Wizard tries to upload a deployment package to a remote computer using ADMIN$ share. The wizard allows to specify different share name. That why the wizard fails on the computers without ADMIN$ share.
We are looking for investors and business partners. Please contact us for more details
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, November 07, 2006
Posts: 2,
Visits: 5
|
ah, great advice, i will try these options and let you know how it goes 
I'll have to get with our network guy and see if he's using a different share name than the Admin$ or c$.
Cool, thanks again
Adam
|