Hello,
I'm performing system administration for a large medical practice at a remote location. One of hte requirements is that I have remote access to each desktop computer. I have the repeater installed, however, I'm having some difficulty getting a completely unattended install of UltraVNC working.
I've already used the setup switches, but specifically, I need to have the following done:
1. Service installed
2. Default Password set
3. Service started.
I was thinking of placing the files network accessible, and using the windows logon script to perform the automated install. So far, no luck...
Thanks in advance
STS
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Completely Unattended Install
You may want to have a look at [topic=3512][/topic].
It is probably better to push install VNC than to run it as a login script unless all of your users have local administrative access to their PC's.
The login script approach also puts the VNC server password within reach of every single user. We thought about that approach, also, and decided not to do it due to security issues.
It is probably better to push install VNC than to run it as a login script unless all of your users have local administrative access to their PC's.
The login script approach also puts the VNC server password within reach of every single user. We thought about that approach, also, and decided not to do it due to security issues.
I'll vouch for VNCScan. I had to do the samething to 1 Local building, and about 8 Remote Offices. I've gotten VNC deployed to 3 of the remote sites, and haven't had any issues yet.
My setup has all of the clients using Domain Auth to connect, but you can easily use a single VNC password instead. Rolling it out is also 99% unnoticeable by the users, unless they are running some type of Anti-Spyware(we use MS Antispyware) then it trips an "Alert" because of the registry remotely being written too. The antispyware programs also seem to detect any of the VNC flavors as a possible threat.
My setup has all of the clients using Domain Auth to connect, but you can easily use a single VNC password instead. Rolling it out is also 99% unnoticeable by the users, unless they are running some type of Anti-Spyware(we use MS Antispyware) then it trips an "Alert" because of the registry remotely being written too. The antispyware programs also seem to detect any of the VNC flavors as a possible threat.