VNCScan 2005.6.16 has been released:
You can now remotely control a computer in safe mode!!!
Free download at http://www.vncscan.com
Here is the list of updates in this version:
* Quick Checkup Scan - Basically, you can select some computers or a group and tell VNCScan to do a quick check on them to see if they are all up and responding. This beats doing a full scan just to see if a certain few computers are up.
* New columns in the list - There are two new columns to tell you if VNC or RDP/Terminal Services was detected on the last scan or check up.
* VNC in Safe Mode!!! - This is something that has been a long time coming. You can reboot a computer into safe mode through VNCScan and then remotely control it using VNC once the reboot is completed. This has many uses including a spyware removal aid.
For more information, check http://www.vncscan.com/vs/VNC_in_SafeMode.htm
* Enable XP Remote Desktop or Terminal Server remotely - This is another thing that has been on many wish lists for a long time. Until now, there has been no real way to remotely enable the Windows XP remote desktop or a Windows Terminal Server. Add this to the long list of things that we're proud to say happens here first!
For more information, check http://www.vncscan.com/vs/Enabling_Remote_Desktop.htm
* Drag and Drop Enhancement - When you drop a computer from the Local Network list, the destination group is selected and viewed. This is just a visual aid to make it easier to verify that the correct computer was dropped at the correct location.
* More Flexible VNC Viewer Choices - You can set your VNCViewer in the Group Properties, now. Before, it was only a global setting. The viewer in the group properties overrides the one set in the global settings.
* High CPU usage bug fix - There where some reports that VNCScan used a lot of CPU even when sitting idle. That seems to have been fixed in this version
* Fix when using IP address - If you set in the group properties to use a computers IP address instead of the host name to connect, it was ignored. That has been corrected.
You can now remotely control a computer in safe mode!!!
Free download at http://www.vncscan.com
Here is the list of updates in this version:
* Quick Checkup Scan - Basically, you can select some computers or a group and tell VNCScan to do a quick check on them to see if they are all up and responding. This beats doing a full scan just to see if a certain few computers are up.
* New columns in the list - There are two new columns to tell you if VNC or RDP/Terminal Services was detected on the last scan or check up.
* VNC in Safe Mode!!! - This is something that has been a long time coming. You can reboot a computer into safe mode through VNCScan and then remotely control it using VNC once the reboot is completed. This has many uses including a spyware removal aid.
For more information, check http://www.vncscan.com/vs/VNC_in_SafeMode.htm
* Enable XP Remote Desktop or Terminal Server remotely - This is another thing that has been on many wish lists for a long time. Until now, there has been no real way to remotely enable the Windows XP remote desktop or a Windows Terminal Server. Add this to the long list of things that we're proud to say happens here first!
For more information, check http://www.vncscan.com/vs/Enabling_Remote_Desktop.htm
* Drag and Drop Enhancement - When you drop a computer from the Local Network list, the destination group is selected and viewed. This is just a visual aid to make it easier to verify that the correct computer was dropped at the correct location.
* More Flexible VNC Viewer Choices - You can set your VNCViewer in the Group Properties, now. Before, it was only a global setting. The viewer in the group properties overrides the one set in the global settings.
* High CPU usage bug fix - There where some reports that VNCScan used a lot of CPU even when sitting idle. That seems to have been fixed in this version
* Fix when using IP address - If you set in the group properties to use a computers IP address instead of the host name to connect, it was ignored. That has been corrected.
