Recent Change History
- Important - If you experience an error during UltraVNC deployment with the number 1603 please visit this blog post for the fix
- Bug fixes and a slight GUI redesign
- Enhanced remote Powershell scripting support. Remote Pc's need to have Powershell 2.0 (or later) and WinRM enabled for remote powershell scripts to run.
- Remote scripts can now be set with conditions based upon processor and operating system of the remote PC's.
- A new setting for remote scripts allow for the script editor to be opened before being ran on a remote computer. This allows you to adjust variables or other details before pushing the script to the remote computer.
- Remote OS detection is greatly enhanced to allow for the above features. For best results, please ensure that the Remote Registry is running on all managed computers.
- After much testing and tweaking, UltraVNC version 18.104.22.168 is finally available in this version. Install VNCScan, then deploy or re-deploy UltraVNC to your desktops and servers to get the latest version (both viewer and server)
- Many behind the scenes bug fixes that help the console help you better
- Upgraded UltraVNC to the latest version 22.214.171.124 for both x86 and x64 deployments. MUCH faster in Windows 8.x!
- Deployment related bug fixes
- Fixed bugs
- Made things run much faster!
- GUI updates to the main screen moving tabs to the top of the window allowing more room for remote desktop sessions. Main toolbar has been moved to initial tab.
- DNS only updates once per day when double-clicking on the computers from the list. This is for performance reasons.
- Other bug fixes reported by the community
- Added option to disable background DNS scanner in the main program preferences (see blog post)
- VNCScan now automatically backs up your vncscan.mdb file to the data folder daily.
- Eliminated the anoying warning dialogs when connecting to RDP
- prepwork and database upgrades for adding more inventory features into the next release
- MUCH improved method of ensuring that the changed IP addresses in a DHCP environment are recognized by VNCScan. New background worker process that continuously polls all devices for updated IP to hosname resolution
- Coding enhancements in the IP scanner modules for better efficiencies
- Databse updates also improve speed of access for many reads and writes
- We could not include UltraVNC 126.96.36.199 in this release because there were still some instabilities that caused servers in our labs to force reboot upon connection. We will continue to work through those issues with the UltraVNC commnity before including it in this product.
- Updated about box and splash screen look
- Facelift on the main window. Sidebar has been replaced with a better performng side bar
- Bug fixes
- Streamlined many processes in the deployment tool. It should be faster and offer more feedback if something goes wrong.
- Computer context menu was re-arranged in a way that brings the most commonly used tools to the top
- Corrected bugs that were reported since the last release.
- Fixed a bug that prevented the Computer Management MMC from connecting to remote computers on some OS's
- Added groundwork for UltraVNC 1.1.9 to be released in next update
- Better compression for remote screen shots. Faster performance
- Other less notable enhancements and fixes.
- Changed the "Add New Computer" toolbar icon to a dropdown button list
- Added in the above drop down list the ability to pick new computers directly from Active Directory
- Fixed some UI bugs that were annoying related to RDP
- Performance improvements
- Added a button on the RDP tab labeled "Resize". If you connected to an RDP session while VNCScan was at one size and then resize the VNCScan console, you can use this button to bring scale the RDP connection to fit the tab. Be aware that this will disconnect your RDP session and reconnect in order to do the resize.
- Added a toolbar icon (camera) to the computers list that will take a screenshot of the selected computer and present it to the console using our patented Lightweight Desktop Capture (LDC) method. No client software is required on the remote PC.
- Bug fixes
- Fixed initial white screen when connecting to NLA enabled RDP servers
- When closing a RDP session, it no longer cycles through all other tabs
- Applied buffers to remote connection packets to increase performance
- Fixed bugs reported to support
- Applied settings that make things run smoother on smaller Windows 8 tablets
- Added two new connect actions in the computer properties that you can set as the default action when double-clicking on a computer: Web Browser (80) and Web Browser (443).
- Fixed a bug that would cause the RDP tab to lock up when it loses focus until you clicked on the top of the tab or switched between tabs
- Applied some buffering in the RDP protocol that increases speed in many situations
- Upgraded the database so that more fields are indexed yeilding faster results
- More under the hood changes
- Cleaning house of all known bugs
- More performance enhancements
- Improved performance of RDP tabs when running VNCScan on a remote RDP session. Adding a new tab was slow because it seemed to cyce through every tab before showing the new one.
- Database optimizations that will result in better performance for large workloads
- Fixed a display bug on the main form for the script and custom commands sections
- more minor tweaks and squashed bugs
- Fixed a bug when creating a deployment profile for TightVNC
- Improved interface of VNC Deployment window
- Added the choice of deploying UltraVNC 1.1.8 or UltraVNC 1.0.9. While version 1.1.8 has great Windows 8 compatibility, Version 1.0.9 seems to perform better on Windows 7 and XP.
- Other unrelated bug fixes
- Fixed some of the bugs that were reported on the forums and in support emails. If you were experiencing any bugs, there's a good chance yours was fixed in this release. If not, shoot us and email and we'll get right on it.
- Fixed: vncviewer.exe invalid win32 executable on 32 bit systems
- Upgraded UltraVNC viewer to the latest 1.1.8 with Windows 8 support
- Upgraded the UltraVNC installer to deploy version 1.1.8 with full Windows 8 support among many other enhancements
- Fixed a bug that made the background scanner active even if checked to be off
- Fixed a bug that would show if you attempted to delete more than 500 computers at a time
- Many other more minor bug fixes and speed enhancing updates
- Fixed a bug with vncviewer.exe on some upgrades on the last release.
- Added toolbar button on clients list that will open a CMD prompt with access to the remote PC filesystem. The CMD prompt is not visible on the remote computer, only on th management PC.
- Fixed bugs reported by people like you :-)
- Back end optomizations for Windows 8
- The next release will have an even better UltraVNC version for Windows 8 PC's. The current one works great but the new version will improve speed even more. Changes in this version make way for that to happen once it is out of beta.
- Added: refresh computer comment from Active Directory in the context menu
- Updates to the grapical interface to bring common functions up with less clicking
- Speed improvements to the database access
- Bug fixes
- Updated to the latest UltraVNC server and viewer. You can redeploy UltraVNC on your remote PC's to get them to the latest release.
- Database performance improvements
- Imptoved success of the remte workstation renaming feature on domains where WMI is not working as expected
- Imprved the way that VNCscan pushes scripts to remote PC's
- many other performance enhacing fixes and additions
- Moved the custom commands into a drop down for performance reasons. Having them itemized on the task pane didn't live up to our performance standards when refreshing the list.
- Enhanced performance noticeable in many areas buf focusing on the remote scripting and custom command execution
- New back end data operations to lay groundwork for future updates happening more seamlessly
- Fixed reported and unreported bugs
- Performance improvements
- Fixed a problem that cleared the MAC address on rescan
- Fixed a similar problem that cleared "Last User" if no user was logged on at the latest scan
- Modified and improved the Active Directory import tool. Also added a "Browse" button for finding the OU that you want to import
- Database optimizations were done so make sure that you close VNCScan for everyone who is sharing your database before upgrading.
- As usual ... other fixes, also
- Fixed an error that happened when some people clicked on a managed group or created a new group while certain data consistency problems existed
- Other fixes
- Fixed a database error that some people experienced on startup
- Added a mass option to add a maintenance log entry
- Modified the maintenance log window to disallow backdating the logs
- Other bug fixes as a result of the above
- When you disconnect from an RDP session and then reconnect, it will resize the display for the current console size. Before, it would stay at the same resolution even after resizing the console resulting in things flowing off the screen.
- Bug fixes
- In the last few releases, the groups under "Network Places" were duplicated under "Managed Groups". Fixed
- The Company Manager screens now work again
- Importing from CSV would fail under some circumstances.
- Added a refresh button to the groups tree tool bar
- Optimized the code to trap and handle errors better on database calls
- Added the ability to mass set the connection action (right-click computers => Quick Mass Changes)
- Fixed a startup bug on some installs
- Fixed a bug with renaming groups
- Fixed other less noticeable stability bugs
- This is a bug fix rollup release. We've fixed many bugs that were reported over the past month (and then some)
- Made modifications to allow remote desktop to work properly on Windows 8 Customer Preview version
- (8) Fixed the bug that caused an error when refreshing domains under "Network Places"
- Fixed a user reported bug that caused the administrative login information in the group properties not to stick when saved
- Fixed a user reported bug that caused the custom actions in the computer properties not to stick when saved
- Improved the time tracking mechanism that feeds into the "Recent connections" tab on the computer properties. It will update every 1 minute instead of waiting for the connection to close before updating the database.
- Any connection logs prior to 2012.1.26 version are archived in <my documents>\vncscan\data\connectionlogs.xml for your convenience.
- Improved the VNC deployment to Windows 7 x64 computers so that it catches scenarios that caused previous versions to fail
- Made improvements to the remote scripting engine that allows it to work better on Windows 7 computers where UAC is enabled
- Fixed a bug that caused the VNC authentication to be rejected on some installs where the VNC password was saved in the computer properties
- The bug that caused the above problem may have caused instability in other more minor areas
- Improved the performance when flipping between RDP tabs in remote sessions
- This is primarily a bug fix version
- Custom sorting of groups now works properly. Preferences no longer crashes upon launch
- Renaming computers has been improved upon
- Various other small bugs have been killed
- This is the most significant update to the program in over two years
- New database back end for groups, computers, connection logs, and maintenance logs!
- Searching for computers in your groups has gotten over 300 times faster than in previous versions
- Background scanning now uses a tiny fraction of the system and network resources than in previous versions
- Thanks to the new database format, you can share your VNCScan data with all of your team members
- All existing data will be easily imported into the new database upon startup using a one-click wizard tool
- Added some buttons to the main form to make adding users and groups easier
- Many unreported bugs were killed as well as a number of reported ones
- General speed increases all over the program.
- Updated to the latest version of UltraVNC for remote deployment
- Redesigned the main form and various other forms. You can see a screen shot of the new form here.
- Added a button to the main form common tasks to enable RDP Remote Desktop on computers remotely
- Rewrote the XML data handling engine to improve performance when navigating data in the application
- We all hate bugs so we killed a bunch of them
- MUCH more room for the RDP tab. By default, the RDP sessions take advantage of the increased real estate.
- Added an exciting new option to screen capture remote computers individually (much like the tabbed view that already existed). You can now right-click a computer, then choose "Capture Screen" to accomplish this. In that window, you can also adjust the intervals of snapshots and choose to archive them as they are snapped.
Note: This feature does not require VNC or any other pre-installed clients on the remote end to work but you will need to tell VNCScan what the Administrator level username/password is on the remote computer and you will need to make sure that there are not any firewalls blocking the file transfers.
- Improved the performance and reliability of the remote screen shot functionality
- Fixed a bug with the screen capture functions that prevented thumbnails from refreshing in some situations
- Fixed a problem with Wake On LAN that tricked the program into thinking that no MAC address was present in the database even though there was
- Added a trapping for when a user opens the VNC deployment wizard with no deployment profiles created. It now takes you to the screen to create a profile.
- Fixed a bug in the remote process manager (task manager) that caused a crash when killing a task on a remote PC
- Corrected some XML read/write issues that made overall speed improvements in various parts of the program
- Added ability to push VNC to remote computers minus the vncviewer.exe due to popular request. There's a new checkbox for this in the deployment tool.
- New features are being worked on behind the scenes and in the process, we've found areas to enhance for immediate performance enhancements in many scenarios. We've went ahead and released them in this build. :-)
- Some bugs that were reported were squshed.
- Updated to the latest release of UltraVNC server and viewer. Fixes:
*crash chat x64
*AuthRequired=0, passwd=NULL: Warning message block service
*About x64 say win32
*viewer 1082 and server 1096 with localcursor ( no connect, 100% cpu)
*serversite scaling and multiple viewers, framebuffer size get overwritten
(Scale is now lock when multiple viewers are connected to avoid a
framebuffer change, first connected viewer set scale. Site effect is that
the viewer report the unused, incorrect scale, but at least it doesn't crash anymore)
*-connect ip, passed to winvnc running as service is not remembered for
stop the autoreconnect function of the server.
*server mouse moves jump on viewer when screen is idle.
*old_plugin crash ( zlib/ultra)
*plugin (SecureVNCPlugin) used by viewer
server without plugin
give incorrect viewer message. And doesn't ask to reject the connection.
*monitor value is saved, but vncviewer read it as bool (true/false)
Only 0/1 are correct imported
*old plugins fail when zrle encoding is used
*old plugins give incorrect info in statusbox
*-autoreconnect timeout, -reconnectcounter number
(available from gui and commandline)
*autoreconnect timeout was incorrect, updated
*old_plugin detction was incorrect
*autoreconnect was indeed invers, corrected again
*All Messagebox() replaced by a function that put it on the visable desktop ( done for all messageboxes)
*Auth Message dll not found, name corrected and refuse access.
*if all groups are empty check also admin.
*if OS_SHUTDOWN initiated ingore all lock functions.
- Now you can place your scripts folder on a file share so that it can be used by your whole team. You can do this by modifying the location in the main program preferences under the "Support Files" heading. note that in some environments, you may need to map a drive letter to the share location and use it that way as UNC's may cause a problem (depending on what the script is attempting to accomplish)
- Made some sanity checks in a few input fields that have been the source of a number of support requests when filled in incorrectly.
- Bug fixes
- PowerShell support for remote scripting! You can now create and deploy Powershell scripts to computers on your network the same as you have for CMD, VBS, and KIX Scripts.
- Interface enhancements and bug fixes
- Added the ability to push the UltraVNC driver to Windows 7 x64 remotely
- Fixed a bug with the UltraVNC SecureVNC encryption in their latest release. You will need to re-deploy UltraVNC to remote desktops for this fix to take effect?
- Upgraded UltraVNC deployment to the final release of 188.8.131.52. You will need to re-deploy to your desktops to get any bug fixes between the RC version and the final release.
- Fixed a bug that prevented the remote UltraVNC server to auto accept your connection upon timeout (as set in deployment profile)
- Underlying system changes that have resulted in faster deployments and support for future features.
- It looks like the UltraVNC team has resolved most of the bugs that caused the rollback in the previous version so we are releasing this update with the UltraVNC version 184.108.40.206 RC server and viewer.
- Bugs were fixed in the remote scripting portion of the application
- Added support for SecureVNC encryption plugin. This will eventually replace the MSRC4 plugin that VNCScan has used for the past couple of years. It is highly encouraged that you create a new deployment profile for pushing out UltraVNC with encryption and select the option for SecureVNC.
- While fixing and adding the above items, we squashed a few other unreported bugs in the process.
- Rolled back to UltraVNC Server version 1.0.8 because of the bugs in the new 1.0.9 server that were acknowledged here. You will need to re-deploy UltraVNC to any computers that were affected by this bug. The bugs include:
- Encryption not working
- Chat not working
- File Transfers not working
- Bug fixes with the deployment of RealVNC 4 Free
- Fixed a few X64 bugs that were reported
- Other smaller fixes
- Bugs were fixed that corrected VNC Viewer from connecting to some upgraded servers.
- Thumbnail bugs have been fixed.
- Improvements in the scanning engine.
- Fixed the capscr2.exe bug
- Fixed bug in some 32 bit environments that prevented the new VNC Viewer from launching
- Added a startup wizard to request admin credentials. This should prevent "access denied" errors in the future.
- Dual monitors are now captured on XP SP2 computers as long as they have Microsft .NET Version 2.0 or greater (almost every SP2 computer should by now). Previously, only 1 monitor was visible on XP SP2 when using the screen capture (tumbnails).
- Fixed the "Debug Mode" bug. :-) It will now properly go in and out of debug mode when clicking on Help => Troubleshooting menu.
- Other less interesting bug fixes and performance enhancements
- Updated deployment tool and viewer to UltraVNC 220.127.116.11
- Fixed the CTRL+ALT+DEL issue with UltraVNC in Windows Vista and Windows (no longer a work around)
- Other bug fixes and performance enhancements
- Thumbnail screen captures now support up to Windows 2008 r2
- Bug fixes and speed increases
- Fixed the CTRL+ALT+DEL issue with UltraVNC in Windows Vista and Windows 7. This is a work around fix until UltraVNC releases their updated server. Please see the blog post about this release
- Fixed a deployment bug that would prevent the remote service from starting after deployment in some scenarios.
- Speed enhancements and improved program feedback
- Fixed error when deploying UltraVNC in some scenarios.
- Fixed the inability to send CTRL+ALT+DEL to some Windows 7 and Windows Server 2008 computers
- Other more minor error corrections and enhancements
- Fixed error running remote scripts in some Windows 7 scenarios. The symptom would be that the script appeared to run and copy the required files but it would not actually run remotely.
- Fixed "access denied" error when deploying to Windows 7 in some environments
- Improved efficiency of the deployment tools
- Added deployment of TightVNC 2.0.2
- Added support for TightVNC 2.0.2 in the VNC password changer and other management tools
- Improved the GUI for the VNC deployment tools
- VNC version now updates automatically after a deployment has completed
tyle="font-size: small;">Numerous bug fixes and performance enhancements
- Front end GUI changes to facilitate ease of use
- Windows 2008 RDP bug was fixed. Prevented connections to RDP when a Windows 2008 server was set to NLA more authentication
- Behind the scenes bug fixes that improve accuracy and stability
- New: Added a toolbar dropdown for adding new computers to make it easier
- New: Added the ability to create desktop shortcuts of individual computers for VNC
- Change: Added a confirmation box when deleting computers from a group
- Change: Changed the toolbar buttons for adding new groups and network places into a dropdown (user requested)
- Fix: Various bug fixes
- Corrected a problem where the console would revert to the default data location if you set a custom data location in the program settings.
- UltraVNC x64 is now deployed to remote x64 computers automatically
- Fixed: The UltraVNC video driver wouldn’t install properly on some XP systems. Keep in mind that x64 systems have new driver signing requirements that prompt the user upon install. For this reason, we suggest that you manually install the video driver if required on x64 computers.
- Deployment tool remembers the last profile you pushed and selects it automatically.
- Deployment tool chooses the correct system drive letter for the remote system, now. It used to only use c$.
- Moving your VNCScan data to another location is much easier and "just works". Use the Preferences => Support Files to do this.
- Lots of other “just little things” fixes and tweaks all through the program.
- Fixed an error in the LAN Speed Tester that misreported the Send Speed.
- Updated to UltraVNC 18.104.22.168 Their release notes are here.
- New LAN Speed Tester - Transfers a chunk of data of customizable size to and from a remote computer share and reports the download and upload speed. While this is an extremely useful new feature, there are plans to make it even better soon. Great for determining where network bottlenecks are.
- Improved the multi-monito support for the thumbnails
- Added selectable subfolders for remote scripts.
- Fixed some other bugs that affected remote computer authentication
- Interface updates
- Combined the top tool bars and menu into one for more real estate on the screen
- Modified the way that the VNC versions are listed in the deployment tool (to make more sense)
- Updated to the latest UltraVNC 1.0.8 Server and Viewer
- Fixed an annoyance on some computers where selecting an RDP tab didn't directly select the RDP session (causing a beeping sound and no interaction)
- Added an RDP toolbar button for Full Screen
- Added an RDP toolbar button to toggle stretching (stretches the RDP window to size when the whole window is resized)
- Updated the remote screen thumbnails feature to better detect the method of capture based upon operating system and other environmental factors. Should be faster to update and use even less resources on the remote computers.
- Fixed the remote thumnails failure on some Windows 7 computers
- Fixed a bug with the "Deploy to selected" toolbar menu item that caused it to only select the first computer of a multiple selection.
- Interface updates
- Updated the Outlook styke group box for the Managed Groups so that you can collaps and expand it using the << button. This allows for more screen real estate.
- Speaking of real estate, you now have a new (default) sizing option for new RDP connections. You can now choose to automatically size the remote screen resolution to match the size of the tab window.
- You can now select multiple items in the list window and RDP to them in mass.
- Fixed a bug that made the vncmanxp.exe bomb out on some XP boxes
- Many other smaller interface enhancements and bug fixes.
- Optimized some of the XML to load faster. Also laid some groundwork for future features and changes
- Fixed some bugs that were reported since the last version
- This is just a quick update that modifies some of the way that the deployment profiles are created. There's a notice on the Profile Editor about using the correct version for Vista and windows 7. this is to address the error about VNC deploying without a password enabled and the error stating that it can not find flavor.txt while creating a VNC deployment profile.
- Fixed the ability to check who is logged onto remote Windows Vista and Windows 7 computers. XP worked OK already.
- Updated to the latest UltraVNC 22.214.171.124 server release. You can upgrade all of your remote computers by simply deploying your existing profile to them again.
- Added some changes to the deployment script to help UltraVNC using Microsoft Authentication install smoother on some of the more locked down networking environments.
- Various performance enhancing back-end modifications
- Bug fixes in the deployment and scripting sections
- Performance improvements throughout the application
- Bug fixes in the remote screen capture features
- UltraVNC Updated: UltraVNC has been updated to version 126.96.36.199. Please check the release notes for this here.
- Windows 7 compatibility fixes: There have been permission and other fixes to make the Windows 7 experience much smoother.
- Other bug fixes: There have been other bug fixes in the VNC deployment tool and various other places in the program.
- Ping: This feature has been expanded to the Reboot Wizard that is accessible by right-clicking a computer, choosing Windows Management, and then Reboot Computer(s). Here's a screen shot of the feature. Basically, you can choose to have the program ping the rebooting computer(s) until they respond and then reconnect.
- Safe Mode: The safe mode has been fixed for the latest release of UltraVNC. It was not setting up things properly for the service to start in safe mode.
- UltraVNC 188.8.131.52: The deployment process has been updated to deploy the latest UltraVNC server and viewer.
- Mirror Driver: The UltraVNC mirror driver problem has been fixed for UltraVNC 1.0.5.x. It now deploys correctly in Vista and XP.
- New - Enhanced the Ping functionality when right-clicking a computer and choosing "Ping Computer". There is a checkbox to run a command or connect to VNC when the computer responds to X amount of pings in a row. This is one of our most requested features!
- Fix - The export to CSV was not properly exporting the last logged on user name.
- Performance enhancing bug fixes are also wrapped up into this release.
- Performance enhancing fixes - especially in the background scanner
- Updated the VNC deployment packages and methods.
- enhanced the VNC uninstall tool to do a better job on both X86 and X64 operating systems.
- The above enhancement also makes the VNC deployment tool operate reliably
- New ability to schedule reboots on remote computers. Right-click a computer, choose "Windows Management" and then "Reboot Computer(s)".
- Fixed a bug in the deployment process involving the encryption module
- Added an advanced button in the deployment profile editor to generate a cusom rc4.key file. Use this carefully to avoid mismatching rc4.key files between the vnc server and vnc viewer.
- Fixed a bug with MS Authentication settings in the group properties.
- Added a check box in the group properties to force inheritance for all of the computers in that group. This is useful if you get yourself into a situation where connections are failing and you're not sure what setting is overriding what.
- Fixed the deployment tool to deploy VNC properly to X64 operating systems
- Fixed the VNC password changer to set the password and/or Microsoft Authentication properly on X64 computers
- More bug fixes with the deployment process. Everything should be working great, now.
- Fixed a bug where the VNC viewer wouldn't launch in some cases.
- fix: Fixed the problem with MS Login connections where the computer settings was overriding the group settings even if the password was blank. More info here.
- Fix: There were various bugs with the new deployment setup that needed to be fixed.
- New: The VNC deployment process has been revamped to be more intuitive. The wizard driven method in the previous version was adequate for it's day but it didn't scale well to things like diting profiles. There is an overview of what has changed here.
- Fix: There was one more bug that involved determining if VENM should use the IP address or resolved host name when running commands and connecting to VNC.
- Fix: When deploying UltraVNC version 1.0.5, it would not obey the setting to deploy without the shortcut icons
- Fix: When deploying UltraVNC version 1.0.5, the video driver would often not install even if you selected to do so. Be aware, thought, that this video driver is unsigned. This may cause Vista and Windows Server to prompt the desktop user to OK the installation. If you know of a scriptable way to
force unsigned drivers on these operating systems, please let us know in the forums and we'll pass that knowledge around.
- Fix: When setting a custom command line for VNC caused an error to show when connecting using Windows authentication.
- Update: Thumbnails now work without the requirement of the .NET 2.0 framework on Windows XP. If you have been using a previous version and already have thumbnails going, you may want to remove all of the thumbnails and then re-add them again if the thumbnails don't show up pretty quickly after the upgrade. If you have to do this, it is only once. The reason for this is to reset the thumbnail configuration for each computer to use the new method.
- Update: The thumbnail screen catcher now gets both monitors in a multi-monitor situation. In previous versions, it only snapped the main monitor.
- Fix: The VNC password changing wizard has been revamped on the back end to be much more reliable in less than ideal networking conditions. If you tried this feature and it didn't work for you in the past, you'll want to give it another go, now.
- Fix: When deploying VNC to computers using Microsoft's MSAuthenication method, the computer properties for those computers was modified to force windows authentication for VNC but with a blank username and password. This caused a lot of work and pain because it overrode the group preferences. This is no longer being done.
- Fix: Lots of i's have been dotted and t's have been crossed. Version number enhanced.
- Update: Made some finishing touches on the thumbnail screen capture feature. We've dramatically lowered the
number of event log entries that get made on the remote computer while screen captures are being done, There were also a lot of speed optimizations done that should be noticeable.
- Fixed: The thumbnail problem that required the remote user to be logged in as an elevated user has been fixed. While you still need Administrator level access to the remote computers, the person that is logged onto the remote computer can be just a normal user. If nobody is logged on at all, you simply get a blank screen capture.
- Fixed a problem with the email alerts
- New: Screen shots now work for Vista computers! Of course,you still need to supply VNCScan with an administrative login and password in order to have access to the remote desktop but that's it! No VNC needs to be installed for this feature to work.
- New: Email alerting for the service status of VNC, RDP, and Ping. If any of them change state from up or down between background scans, you can be alerted by email or run various commands. This can be set in the group properties and overridden by the computer properties for fine tuning.
- New: You can choose to run one of your remote scripts when a computer is back up on the network. This is an excelent way to schedule a script for laptops or other computers that are not always on the network
- New: You can have VENM automatically connect to VNC for you when the computer comes back onto the network. Once the computer is detected by a background scan and the VNC service is reachable, VENM will open the VNC connection to the computer for you.
- New: Execute local custom commands when a computer falls off the network.
- Fix: Eliminated the old scrserv method of capturing remote screen shots. You should no longer need to fight with oversealous virus scanners for this feature to work. Note that the new method does require that the remotely monitored comptuers have at least the Microsoft .NET Feamework 2.0 or later installed on them. In today's Windows world, that's pretty much a given.
- New: Improved the screen for creating custom commands
- New: Background scanning now looks for VNC and RDP. This is configurable in the group properties.
- Update: Updated support for the latest UltraVNC 184.108.40.206 viewer
- Fix: Fixed a lot of the long standing bugs and annoyances reported in the forums and to support.
- New: SSH has been added to VNCScan due to popular demand! You can rght-click a computer, choose connect and then choose SSH as the method. Alternatively, you can set SSH as the default connection method in the group or computer properties depending on the desired scope. You can expect more development in this area in the future.
- Fix: The Location and User fields have been placed back into the main list of computers
- Fix: The quick edit feature now works as expected.
- Fix: Telnet now works in Vista
- New: You can now select Telnet as a default connection method in the group or computer properties (depending on the desired scope).
- New: Background pinging! Now you can always know when your computers are available or when they need to be booted up before connecting to them. You can keep track of the last time they were polled and the last time that the computer was seen on the network.
- New: Logs the last access time and date and places it in the main computer list for easy access.
- Fix: IP addresses now sort properly
- More fixes and minor enhancements
- FIX: Connecting to RDP used to require XP Sp3 or Vista SP1 to be applied due to a logic bug. Now, the only requirement is that your RDP version is 6.0 or higher. If you attempt to connect to a RDP or Terminal Server and you have RDP 5 or less on your computer, you will be prompted to upgrade and provided a download link. This is happening because Microsoft chantged the way that RDP worked for console sessions in RDP 6.
- Fix: Setting the "console" option in the group properties was ignored. It worked if you set it at the group properties, however.
- Other: Minor fixes and tweaks to improve performance.
- Fixed the "Find Users" menu item when right-clicking a manged group
- Fixed a bug that interfered with the ability to RDP into a console session
- Lots of general bug corrections and other fixes
- Added a "Folders" button to the toolbar of the thumbnail tabs. This allows you to set a custom location for both the archived screen shots as well as the temporary location used when capturing remote screens to thumbnails.
- Fixed a bug with RDP that prevented the ability to connect for some users who upgraded from previous versions.
- Improved the performance and responsiveness in many areas of the program.
- RDP Quick Connect toolbar button now has the option of opening as a tab instead of the standard terminal server client. You can set this option in the main program preferences inder the Terminal Services section.
- Added an option in the main preferences to always minimize to the task tray (http://screencast.com/t/jnYZukIx)
- Fixed the error at startup reported in this forum post.
- Fixed the missing textbox for the UltraVNC repeater selection.
- Bug fixes that enhance stabillity and speed
- Updated the UltraVNC support to the latest 1.0.5 version and made it the default.
- Fixed a bug in the RDP ActiveX control that prevented computers without XP SP3 or Vista SP1 from connecting using the toolbar.
- Fixed a bug in the setup that would fail to copy the correct beyondexecv2.exe file if a previous one existed.
- Fixes: Numerous pesky bugs have been eliminated with this release. Many of them were reported in our forums.
- Change: Due to antivirus and anti-spyware false positives, we're trying to move away from the use of BeyondExec for the scripting engine and defaulting to Microsoft's PsExec. We've tried to make this as seamless of a change as possible and you may not even notice (except that things work better).
- Change: There have been some significant back end changes to make VNCscan work better after changing the location of the groups.xml and other support files. It typically worked pretty well except for a handful of people who had special case issues with their 'My Documents' location.
- New: We've added the ability to export your remote scripts selectively by right-clicking on one of them in the Remote Scripts Manager and choosing 'Export'. It saves to a ZIP file in the place of your choosing. You can share that script with others by simply sending them the ZIP file or posting it to the web. The recipieng simply needs to go into the Remote Scripts Manager and import it with the same ease.
- Fix: The method to resolve the MAC address in the computer properties sometimes caused the program to become unresponsive for a while. This happened because it automatically tried WMI if the broadcast failed. Now there is an option to skip that step to prevent this.
- New: Added to main tool bar buttons for quickly connecting to VNC or RDP on remote computers that are not in any of your VNCScan groups for whatever reason. This replaces the Quick Connect bar in previous versions. We think that this is a lot simpler.
- Change: The default home page for the browser has been changed from the classic support website to our blog. This was done to get more timely information out to you as the blog is updated more often than the support page.
- Fixes: This is more of the same from the last bug fix release. I think that we pretty much have all of the bugs that prevent VNC from being deployed to Vista computers taken care of in this wrap-up release. Please let us know if there is anything that we missed using the Get Satisfaction forums.
- Fix: The deployment wizard now does a much better job of removing all flavors of VNC prior to pushing VNC to a remote computer. There were some instances where one version of VNC would not get fully removed before another was pushed causing two active services on the remote computer. In some instances, the service would not install for the latest UltraVNC 1.0.4 as a result.
- New: VNC Password Changer now works for UltraVNC 1.0.4. If you're running it against Vista computers, be sure that the Remote Registry Service is running on them. We've been seeing that it's set to "manual" startup on most Vista machines.
- Fix: The dialog that presented itself when closing the VNC viewer has been removed. That was quite the annoyance.
- Fix: The RDP Reconnect was broken on the tab menu. Fixed.
- Fix: The menu on the remote process manager was not expanding like it was supposed to.
- Added: The process to report the version of VNC installed on the remote computers now includes checks for 1.0.4.
Notice: We have moved to a new (better) installer. You will need to uninstall from add/remove programs your previous version before installing this upgrade if your current version is older than 2008.6.1
- Fix: Fixed some deployment bugs for Vista. Things would sometimes not go well if you did not supply Windows credentials in the deployment wizard.
- Fix: Fixed a bug that would misreport your number of days for free upgrades when clicking on the "Upgrade" toolbar button
- Beta - Push UltraVNC 1.0.4 to Vista computers! We're proud to be the first network management console that can do this! There are instructions for this at this forum post. Comments are welcome.
- New - Full Vista and XP 64 bit Operating System support
- Fix - Updated RDP to the latest version to support the "console" setting.
- New - Included UltraVNC 1.0.4 as a deployment version option for XP as well as Vista - Encryption and MS Login are both supported.
- Fixes - There are numerous bug fixes in this release. They mostly cover bugs reported in the forums and to our online support.
- New: There is a new feature that allows mass updating of MAC addresses. It tries multiple ways to get the addresses so it should be more successful than the method used while scanning for VNC and RDP. You can see a demo it of it here.
- Fix: The script variables would not apply in some instances while deploying remote scripts
- Fix: This release includes the latest UltraVNC vncviewer.exe that corrected this bug
- Fix: Setting custom command line switches would not have any effect on the color depth of the viewer (e.g. -noauto -256colors).
- New: We put a line in the help/about box to tell you how many more days of free upgrades are left for your product key. Also, when you click the link inside of the console to download an update, it will warn you if your free upgrade period has expired.
- New: Included AutoIt scripting as an available language for remote scripting. If you are running any remote AutoIt scripts that you wish the end user to see, be sure to check the box that tells the script to interact with the desktop.
- Fix: There was a bug that prevented you from using the upgraded version in trial mode if your free upgrade period had expired. This version fixes that.
- Fix: Error during scan. In some cases, the scan would present an error that would close VNCScan. The error happened when it was trying to find who was logged onto the remote systems. This has been corrected
- New: Kixtart support in the scripting module. Just paste or type a KIX script into the scripting window and deploy it to computers. Kixtart is a powerful and easy to learn scripting language. More information about Kixtart scripting can be found here.
- New: You can set a custom RDP port in the computer properties
- New: Deployment wizard supports the TightVNC View Only password when deploying TightVNC
- Update: Updated the deployment wizard to deploy the latest TightVNC server
- Change: When you deploy VNC to a computer, the same brand of viewer is set as the default in the computer properties automatically.
- Change: The remote processes manager starts up at medium speed, now. When it was at the faster speed, it was too fast for most networks.
- Fix: The remote processes manager handles alternate permissions much better, now. There were some problems when VENM was set to connect using the IP address instead of the host name
- Fix: The problem that was reported in this post has been resolved.
- Fix: The VNC password problem that was reported in this post has been resolved.
- Fixed: The installer will now upgrade properly. In some cases, the old installer would appear to upgrade but the previous version would remain in tact. The only work around was to uninstall and then reinstall.
- Fixed: The RealVNC viewer would display an error stating that /nostatus was not recognized. This has been fixed.
- New: Placed some troubleshooting tools under the Help menu. You may be asked to click some of them on or off when troubleshooting issues with VENM
- Change: Using the latest UltraVNC viewer to correct the issue where the host name was not in the window title in the last version.
- Change: Added the "Add New Device" button on the main form for ease of use.
- Fixes: There were quite a few medium to minor bug fixes in this release. Most of them were reported in the forums.
- New: You can save Windows Authentication for UltraVNC in addition to standard VNC passwords for your connections.
- Fix: If you enter an incorrect VNC password, UltraVNC will prompt you instead of displaying the generic settings window.
- Fixes: We've included a number of permission fixes related to Windows Vista.
- Vista Note: The UltraVNC team is working on a VNC server for Vista. They have a stable beta available for download at their website. If you manually install their server onto a Windows Vista computer, you can remotely manage it with VNCScan. The only missing feature is the ability to deploy their beta version from within VNCScan. That will come when they release the final version.
- Note: This should be the last maintenance release before we release the version that will be able to push install UltraVNC onto Windows Vista computers. If you have some Vista computers that you would like to remote control with VNC and VNCScan, you can download their release candidates for UltraVNC 1.0.3 that work on Vista here and install them manually.
- Change: To make this version work even better with Vista, we have moved many of the data files and settings files out of the program folder and into the user "My Documents" folder. If this is an upgrade from an existing version of VENM, it will continue using the data where it sits. All new installs will place data, scripts, commands, etc. into My Documents\VNCScan.
- New: There is a new location for your scripts and commands. They are now located in the left hand Outlook style tool strip on the left along with your Managed Groups. You can activate a script or command on a computer by dragging and dropping computers onto a script name or a command name. This makes running scripts much more organized.
- New: You can now put your remote scripts and custom commands into subfolders for better organization. There is a textbox to enter the subfolder name in both the remote scripts window and the custom commands window.
- Fix: As usual, we have fixed bugs that were reported in the forums and through support emails.
- Fix: Fixed a reported but that would crash the remote scripts manager in some cases.
- New: In Preferences => Support Files, you can set the scripting engine to either be BeyondExec or PsExec. In some situations, one engine works better for some customers than others. It usually has to do with false positives from desktop security software.
- Fix: If you unchecked the box in the VNC Deployment Wizard so that icons would be delivered during the push, the script would fail under some scenarios. This has been fixed.
- Fix: There has been some smaller maintenance and bug fixes in this release. If you were experiencing issues with a previous release, you are encouraged to uninstall it and then install this version. Your data will remain in tact during this process.
- Fixed: There were some more reports of blank message boxes in some parts of the program.
- New: There is a new field in the computer list titled "VNC Version". To populate it, select some computers, then right-click then, then choose VNC Management, and then choose "Check VNC Version". You will notice a flurry of activity in the status tray and when it's finished, the versions will be displayed in that column.
- New: There is a new field in the status tray that shows how many computers are currently selected.
- Fixed: There have been other minor bug fixes to address things reported in the forums
- Fixed: There were some reports of blank message boxes in some parts of the program.
- New: There is a new "Edit Mode" toolbar button to put the managed list in edit or read only mode
- Fix: There were a bunch of other more minor bug fixes in this version
- Fixed: The fix for the thumbnail tabs caused another bug to appear. It has been resolved once and for all.
- Fixed: In some cases, the screen shot of the remote computer would not show at the bottom of the managed list like it was supposed to.
- New: You can directly edit fields on the fields on the list of computers
- Fixed: Authentication wasn't happening properly with the thumbnails so that if you where not logged in as a domain administrator, it was not likely that you would ever get thumbnail images of a remote computer.
- Fixed: Adding thumbnails to a new tab would bring up a dialog asking for a name for the new tab. The textbox was not in focus and you had to click on it in order to type in it.
- New: In Tools => Import => Active Directory, you can now use an LDAP query to limit the results to an OU or you can still use just a domain name and get every computer in the domain. The import is much faster, now.
- New: If you are capturing screen shots (thumb nails) of a computer, clicking on it in the managed list will show the latest screen shot thumbnail at the bottom of the window.
- Major Facelift: The main form and various other places in VNCScan have been given a pretty major UI overhaul. We went with a mix of the Outlook 2007 and Vista feel. More work is being done on some of the older parts to make things easier to get to
- Bug Fixes: There have been a number of bug fixes and updates.
- There where a few bugs fixed and some more performance enhancements in this release
- New: The thumbnails tab will remember the interval and size of the thumbnails on close.
- Enhancement: There where some changes made to the thumbnails feature that significantly increased the performance. It uses much less CPU and memory than previous versions and is especially noticeable if you are monitoring more than 50 thumbnails.
- New: You can set the interval of the remote screen captures right from the toolbar in the thumbnails tab. Each tab has its own interval property.
- New: If you right-click in the blue area of a thumbnails tab, you get three new menu items. You can choose to set all thumbnails to archive, remove the archive property for all of the thumbnails, and also randomize the timer. See next bullet on that one..
- New: In the point made above, you can randomize the thumbnail timer. If you have a lot of thumbnails all refreshing at the same instant, it can really hit your system resources pretty hard. If you randomize them, it will scatter the update times so that less of the thumbnails are refreshing at the same instant.
- Fix: The bug that prevented the auto loading of thumbnail tabs to work properly has been fixed.
- New: You can right-click a thumbnail and select 'Go To Computer Entry' and it will do just that
- New: The computer comment is displayed below the host name in the thumbnail view
- New: Thumbnail view now shows the host name instead of the IP address
- New: There is a new Transparency option under the main View menu
- Fixes: There have been various bug fixes in this version
- Fix: Fixed a problem where a query box would show up on the remote VNC server at unexpected times. This caused the connections to be rejected when they should have been. This addresses the problems reported in this thread and also in this one.
- Fix: There was a problem renaming computers if you are not logged into your computer as a domain administrator. It totally defeated the purpose of inputting alternate credentials for this process. The problem has been fixed and VNCScan will impersonate properly, now.
- Fix: There where also less notable fixes in this release
- New: The "Thumbnails" tab has been removed in favor of allowing you to create as many thumbnails tabs as your system can handle. To add a computer to a new tab, simply right-click it and choose it from the "Thumbnails" menu.
These thumbnail tabs (and the thumbnails) are automatically recreated when you open VNCScan. If you right-click the tab header and choose to close it, you will be asked if you want to save the tab so that it is remade the next time that the program launches.
- New: The export to CSV function also exports the last user and location fields.
- Fix: The installer didn't upgrade very clean the first time around but that has been fixed. As long as you are running version 2006.12.X or higher, the installer will upgrade you and you no longer need to remove the previous version first.
- New: There is a new archive feature for the thumbnail remote screen shots. When you have a computer in the thumbnail view, you can simply right-click the image and check the box to archive them.
The jpegs will be stored in a folder as they are taken for later examination. You can get to the folder location by right-clicking the same image and choosing "Open Archive Folder".
- New: Thumbnails can be resized using the slider bar in the thumbnails view.
- Fix: The new installer failed to register the terminal services control. The new installer will register the control properly.
- Fix: If you delete a group, it would show up again the next time that you restarted VNCScan
- Fix: Made changes to fix a problem where managed groups would randomly disappear under some rare circumstances. If you have experienced this, you are encouraged to update to this release.
- Change: The update notification has been modified. Instead of a pop-up box telling you that there is an update available, a button will show up in the toolbar telling you that an update is available. Clicking on the button takes you to this download page.
- Change: We have moved from the native Microsoft MSI installer to Install Shield. This allows for more graceful and intelligent upgrades. You will need to uninstall the previous version of VNCScan before installing this version one last time and then it will upgrade gracefully from here on.
- New: You can, now, rearrange the columns in the the main list of computers to suit your needs. If you want it to remain that way the next time that you open VNCScan, click on 'View', and then 'Save Managed List State'.
- New: You can set the viewer scale setting in the computer properties and it will override the setting in the main View menu.
- New: Thumbnail View of your computer desktops! You can right-click a computer and choose to add it to the thumbnail view and then view it on the thumbnails panel. You do need Administrator rights on the remote computers that you are thumb nailing. You can set the administrative login credentials in the group properties under the Identification tab. This feature does not require that VNC is installed.
- Fix: The backup/restore tool
has been fixed. It would restore everything except the groups.xml due to the order that it copied files. This has been fixed.
- Fix: Other stability fixes have been included in this release, also.
- Fix: Extra files where copied during a deployment of VNC and it was slowing down deployment over slow links. The script has been corrected.
- Fix: If the system was configured to use large fonts in the display settings, you would get an annoying error when opening the groups or computer properties. Clicking Ignore would get you past it, but it would happen every time. This has been fixed.
- Update: The context menu for the groups has been moved around a little to eliminate some clutter
- New: The deployment script will now open the required ports for VNC automatically while VNC is being deployed to XP computers.
- New: The computer properties is gathered when enumerating Active Directory domains and windows workgroups under the "Local Network" tree.
- New: Remote AutoRun editor - This tool is located under the 'Windows Tools' section of the context menu when right-clicking a computer. It allows you to remotely manage the startup programs on the remote computers that you have administrative access to on your network. You can view AND delete entries from the list.
It will detect auto start started program settings for any user with a profile on the computer. We've done some pretty hard searching and can not find any other tool that does this.
- Fix: If you set a custom command as the double-click action for a computer, the %IP% variable would not resolve properly.
- Fix: There where a few reports that the program was forgetting the registration information and returning to trial mode. This was rare and obscure but we found the root cause and corrected it. Because of the nature of the bug, we decided to release this maintenance release right away.
- Fix: There have been other bug fixes in this release, also.
- Update: Updated the installer to use the latest UltraVNC 1.0.2 again now that a fix has been made for the encryption modules.
- Fix: If you used an upper case %HOST% for the domain name in the deployment wizard, it would fail to substitute it for the computer host address.
- Fix: UltraVNC encryption was buggy with the new version of UltraVNC. The version of VNC server was rolled back one release until the new version of UltraVNC is released
- New: Changing the password in the group properties will prompt you if you would like to set all of the computers to inherit the password from the group or leave them alone
- New: The VNC password reset wizard has a 'Print' button under the log so that you can output your log to a printable format
- New: A column has been added to the main computer list to show the last deployment profile that was used on each computer.
- New: You can set the amount of time that a message is displayed on a remote computer before it reboots. This is available in the last screen of the reboot wizard.
- New: You can edit saved deployment profiles. If you have a really old version of VNCScan, you may need to start with a new profile and then you will be able to edit it from then on.
- Fix: There was an error if you pressed the "Deployment Wizard" toolbar button while a terminal session tab was selected. This was fixed.
- Fis: other minor fixes
- Fix: There was a problem with the processing of lang.ini that prevented some of the pop-up menu's from showing up the first time that VNCScan was ran after a fresh reboot. Closing it and opening it back up resolved it until the next reboot. The problem has been resolved.
- New: The Windows Password Reset wizard will retain a log as it completes and a print button has been added so that you can generate a printable view of the log file. More error reporting has also been included in the log report.
- Fix: When deploying VNC using an alternate port, the default port of 5900 was still being used when adding the computer to a group afterwards. The problem was reported here and has been fixed in this version.
- Fix: When enumerating computers in the "My Network Places", the computers with IP address changes would not update. This was reported here and has been fixed in this version
- New: There is a new maintenance log viewer/manager located under the main Tools menu. This new tool gives you a single location to view all of the logs for all of your computers. You can also export them to a printable view from here.
- New: You can right-click a computer and create a new maintenance log entry. This just makes it easier to use the maintenance logs.
- New: You can right-click a group and export all of the computers to CSV. It exports the hostname, IP address, MAC address, VNC and RDP status, and the computer comments.
- Fix: A bug in the Windows Password Reset wizard prevented the Finish button from ever becoming active after the job had been completed. This has been fixed.
- New: There is a new Refresh button in the web browser
- Update: The MAC to IP address resolving tool has been updated so that you can paste a complete MAC address into the first textbox and all of the textboxes will populate with the correct format.
- Update: Updated the color scheme for the main window so that it looks better with XP themes
- New: Added a toolbar to the managed groups tab for quick access to VNC, RDP, remote scripts, and custom commands.
- New: Added "Scripts and Commands" menu under the main Tools menu for easier access to scripts and commands editing.
- Fix: Fixed error when a new window opens in web browser
- Update: Latest version of UltraVNC and RealVNC applied to the deployment wizard
- Update: VNC Password mass changer also sets UltraVNC Windows authentication settings. More information can be found here.
- Update: Windows Password Wizard allows mass resetting of Windows passwords on the network. More information can be found here.
- Update: The remote reboot wizard has been enhanced for more reliable and easier remote safe mode sessions. More information can be found here.
- New: You can remotely rename networked windows computers from within VNCScan. This wizard also takes care of all of the necessary domain modifications for a renamed computer, also. More information can be found here.
- New: There is an "Outlook Today" style webpage when you click on the root "Managed Groups" tree. You can customize the page that shows up here in the main program preferences under the "Internet Options" tab. The default is the Bozteck Forums. As suggested in this forum post, it is very useful for integrating your call accounting or user tracking system into the VNCScan application.
- Fix: The update notification seemed to pop up a bunch of messages informing you of an update if you left it on over night. This should be fixed.
- Fix: When mass deploying UltraVNC with the domain authentication enabled, there was a bug that presented an authentication error on all but the first computer in the list when you attempted to connect to them after deployment. This happened because the checkbox in the computer properties that tells VNCScan to prompt for the MS Login instead of just passing it your saved standard VNC password was not getting set by the deployment wizard.
- New: The custom commands now has a variable for the MAC address. This makes it possible to use tools like MC-WOL.EXE as a custom command.
- Fix: There were still some cases where the option to use the IP address instead of the hostname was being ignored. This has been corrected.
- Fix: There have been various other bug fixes in this version.
- Fix: It was reported that VNCScan would error and close if you attempted to run it as a normal (non-admin) user. VNCScan will adjust the system permissions to allow a non-admin user to run VNCScan as long as the first time that it is run, it is run as an administrative user.
- Fix: Icons where not being deployed as reported here. This has been corrected.
- Fix: The "connect using IP" feature was being ignored in the group properties but it was working in the main preferences and on the computer properties. This was reported here. It has been fixed.
- Fix: If you didn't enter alternate credentials in the VNC deployment wizard, you where presented with a script error at the end of the deployment script.
- New: The VNC push script will automatically enable the speedy UltraVNC video driver when you deploy UltraVNC. The driver allows the screen to refresh faster and lowers the CPU usage of the VNC server considerably. This is only available when deploying UltraVNC as the flavor.
- Change: There is a new check box in the VNC password wizard that will tell the utility to show command window output while changing passwords on remote computers. We suggest leaving this unchecked unless you are troubleshooting why the VNC password isn't getting changed for a particular workstation.
- Fix: Fixed the bug in the VNC password wizard tool that prevented it from changing the remote vnc passwords in some cases.
- Fix: Fixed the bug that would crash VNCScan after changing an icon in the group properties. The error would happen after pressing the "Close" button for the computer properties.
- Fix: The group names sorting has finally been completed!
- Fix: Other minor bug fixes
- Fix: Fixed a problem with the group properties in some situations
- Change: The VNC password changing tool has been converted into a wizard with more feedback and reliabillity.
- Fix: In some configurations, the scrollbars on the main form where not visible or functioning properly. Corrected.
- Fix: Some of the screens that look strange when the computer is set to 120DPI Large Fonts have been fixed to look better. Some screens still need work.
- Improvements: Made improvements to the groups sorting
- New: You can add custom domains and workgroups to the Local Network tree and enumerate the computers from them. You can specify if it's an Active Directory domain so that it can pull from the directory instead of broadcasts. This does require proper network configuration to work.
- Fix: There have been multiple annoyance bugs fixed. If you found one in a previous release, this one may be the fix.
- Fix: The bug in the deployment wizard that was in the last version has been fixed
- Fix: There where a couple minor errors that where corrected. They where minor because they didn't stop the program from doing what it was supposed to do but they where annoying.
- Important Notice: After the release we found an annoyance that still persists. When you create a VNC deployment profile for the very first time, it gives an error at the very end that prevents the wizard from saving the profile, thus wasting all of the time you took to answer the wizard questions! If you run the same wizard again, it will operate normally from then on.
Work Around: Launch the Deployment Wizard for the first time, close it right away, then open it again. You only need to do this one time and the problem is fixed permanently.
The source of the annoyance has been located and it will be fixed in the next release.
- Fix: Fixed a bug with the scanner. If you did a complete scan of the network, then went back to the main window to launch a connection, it would sit forever at the "Connecting .." state until you closed VNCScan. At that point, the VNC authentication dialog would pop up (X's how many times you double-clicked on the computer). This has been fixed.
- Change: We added the toolbar at the top of the window. A Find function was also added to the toolbar for easy access
- Change: The group boxes in the left column will remain collapsed or opened when VNCScan starts depending on how they where when it closed last
- Change: Updated the Windows account mass password changer. It is now a wizard that can be accessed by right-clicking a computer, choosing Windows Tools, then 'Windows Password Reset Tool'. This tool is very useful for keeping the local Administrator account passwords the same and changing them often for all of the computers in your domain.
- Feature: You can choose the order of the managed groups again. This feature was in 2006.1.5 but was removed temporarily until this version. The tool is located in the main program preferences.
- Change: Moved the Quick Connect feature to the front of the main form for quicker access.
- FIX: The command line options for VNC Viewer was not functioning. It is, now. Remember to use a - instead of a / when supplying custom command line options. For example, -autoscale to autoscale the viewer or -scale 3/4 to put it to 3/4 size.
- Change: When you choose to scan a group and do not have a range of IP addresses entered into the group properties, it will now check to see if there are already computers in the group and re-scan them instead. The prior behavior was just to do nothing.
- New: In all areas where you can specify alternate login, a domain box has been added. This just makes it easier to use than trying to remember the domain\username or %host%\username. If you enter %host% as the domain, the computer address will be substituted so that you are authenticated against the local database on the remote computer.
- New: There is a search button in the main form common tools group to make that function a but more accessible. The search form has been modified for ease of use, also
- Bug Fix: There have been a number of bugs fixed in this version. If you noticed one in the version that you are running, you should check out this version. If it's still there, please let us know.
- Feature: You can set a global option to ping before performing operations such as VNC deployment or remote control. This eliminates some delays and errors when hitting computers that are powered off.
- Fix: If a computer was turned off and you scanned it again, VNC would still be in the list as True. This has been corrected
- Fix: The manual command line settings where not being processed for VNC connections.
- Fix: The update notice was a bit annoying because it wouldn't stop notifying you of a new release unless you shut off update notification completely. This has been corrected and it should only tell you once.
- Improvement: The feature to find who is logged in by right-clicking computers and choosing it from the windows tools menu has been improved. It uses threads, now. In addition, it also updates the database with it's findings and refreshes the list when it's done. Feedback is given in the status bar at the bottom of the window.
- Feature: Not really a new feature but CTRL+A in the computers list will select all of the computers again.
- Fix: If you had a computer that was named COMPUTER and you deployed VNC to it, it would duplicate as COMPUTER.DOMAIN.COM instead of updating the existing entry. This has been fixed.
- GUI Change: We've spent some time putting the XP look and feel back into the application.
- Fix: In come cases, the web browser would launch when connecting to VNC. This has been corrected.
- Fix: Menus reload properly when adding custom commands and scripts.
- Fix: There was an error when trying to import from Active Directory. Gone.
- Fix: If you where deploying VNC to a list of computers and one of them was not pingable, the whole script would just die right there. This no longer happens.
- Feature: When you specify alternate credentials, you can now use the %HOST% variable and it will get replaced with the name or IP address of the computer being worked on when a script or command is run against it. This also works for the VNC deployment wizard.
The purpose of this addition is because if you are operating without a domain on your network, authentication can get particularly nasty - especially when you have multiple local Administrator accounts with conflicting passwords.
When you specify %HOST%\Administrator, You can be sure that you are using the local Administrator account on the remote computer and not your own local Administrator account.
- Fix: Every once in a while, an error would come up at the end of the deployment wizard about a button object being unloaded. It didn't hurt anything but it was annoying. It is gone.
- Fix: When you clicked on the Windows Tools submenu and chose to view installed software, nothing would happen. It works, now.
- Fix: The same tool mentioned above to view remotely installed software would not make use of your provided username/password. It will not work if you supply a user/password in the global, computer, or group properties.
- Change: Moved to the Microsoft .NET 2.0 Framework. The down side of this is that everyone will need to download and install the 30MB runtime for this version to work but the future benefits are countless. The new framework opens a lot of doors for new features to come. You'll need this framework installed for many other .NET based applications, anyways. :)
- Change: New cleaner interface makes it easier to do what you need to do. The old interface was getting cluttered. This is a welcome change for everyone
- Change: HUGE speed improvements! This is evident all over the application and if you're a long time VNCScan user, you'll notice them all right away. It really is quite drastic in some areas.
- New Feature: MAC to IP Address tool. This tool is located under the main Tools menu. It will search your managed groups for the supplied MAC address and return the computer that has it. If it can't find one in your managed groups, it queries the network.
- New Feature: You can import hosts from tab delimited text files just like you could before with comma delimited files. The only two fields that matter are Hostname and IPAddress respectively.
- New Feature: Added threading to the import screens to make them more user friendly.
- New Feature: New front end added for backing up and restoring VNCScan data files and folders. It is accessed from the main File menu.
- New Feature: Added "printable view" for both the connections log and the maintenance logs in the computer properties
- New Feature: Added the ability to delete records from the maintenance log.
- Bug fix: Main form refreshes lists faster and in a more intelligent manner
- Bug fix: The program now deletes all outdated data locks when launching to prevent lockups.
- Bug fix: On some systems, when you attempted to connect to VNC after performing a scan or quick update, it would appear that nothing happened until you closed VNC Scan. At that point, all of the connection attempts would take place at once.
Another side effect of this is that the winvnc service on the remote end would be unresponsive to attempts to stop the service making deployments fail.
This was happening because the scanner was not properly releasing resources on the remote end during a scan.
- New Feature: Added the ability to view software in the add/remove programs on remote computers where you have administrative access.
To get to it, right-click a computer, then choose Windows Tools.
- Updated task manager screen - When you right-click a computer, choose Windows Tools, and then choose View Processes, you are able to remotely manage the processes on computers where you have administrative access.
This screen has been updated to do automatic refreshes and include more information.
- Custom Commands Changes - You can check a box to tell VNCScan to leave the DOS box open or not after executing a custom command. Previous versions always left it open and that proved to be an annoyance.
- Logging Changes - When you execute a custom command or push a script to a computer, a note is placed in maintenance logs for that computer with some minimal information.
- Fixed the Enter and F8 (refresh) keys - When you press enter while a computer is selected in the managed list, it will act as if you double-clicked it. F8 now refreshes the contents of the list.
- Deletes computers faster - The delete of multiple computers happens faster.
- Comments field in HTML export fixed - It was reported that the comments field was not showing up in the HTML when you right-clicked a group and chose to export to HTML. It works, now.
- Fixed NullReference error in search function
- Updated program icon - Thank you, Jamie MacDonald for the art work!
- The status icon in the computer list is now optional - You can set this in the main program options. The default is OFF because the list actually refreshes a little faster that way.
- Corrected bug that would prevent VNC connection in some cases until after VNCScan was closed. - This was a bizarre bug that was pretty rare but thoroughly annoying! The bug has been squashed.
- Added new search to the tools panel - On the left panel of the main screen, you will notice a new section to search for a user or computer within your managed groups. This has been one of the most requested features lately.
- Active Directory import limited to 1,000 fix - Now, I believe that the limit is 10,000 computers.
- Added Active Directory in Local Network - You can now query Active Directory in addition to standard NETBIOS requests in the Local Network tab
- Fixed group naming bug - If certain characters like & where in the group name, bad things happened.
- Huge improvements to the VNC Scanner - There has been a complete rewrite to most of the scanner code to fix some reports of unreliable results. It also allows faster scans with surprisingly accurate results that weren't possible before.
- Change to the reboot screen - Added a checkbox to the normal mode reboot to undo the safe mode settings on a remote computer. Be sure to check this box to reset the remote computer boot.ini after you have rebooted it into safe mode with VNC support.
- Fixed intermittent error after scan - In some situations where computers on your network may have substandard host names with illegal characters in them, VNCScan would crash after the scan while adding them to the database. The program is smart enough to see this coming, now, and takes corrective action instead of crashing.
- New built-in backup procedures - VNCScan backs up all XML files, your deployment profiles, and custom scripts every time that you start VNCScan. They are saved into a folder named "Backups" inside your VNCScan folder.
The default setting is to retain up to 5 backups before overwriting. You can change this setting in the global options.
- PSEXEC download wizard - There is a new wizard under the main Tools menu to help you download psexec and unzip it into the correct locations. It doesn't work behind some proxy servers yet but it should serve a large majority of the user base.
- Modified the vncviewer launch - It launches in its own environment space, now. This corrects a bug that was only reported once but could be a problem further down the road
- Connection Bug Fix - The option to use IP address instead of HostName was broken in 2005.10.20. This feature is set at the global VNC Scan options, group level, or at the individual computer level.
It's purpose is to aid in connecting to hosts where DNS doesn't resolve properly. This is quite frequent over remote connections. If you deploy VNC to remote computers and get an error that says that it couldn't connect or get the address, you may want to set this property on.
- Mass Import from VNC Saved Files - The standard VNC viewers allow you to save your connection settings to a .vnc file. If you have a bunch of these sitting around, you can import them into VNCScan from the main Tools menu, now. This is a HUGE time saver!
- Import computers from Active Directory - You can import your computers from Active Directory, now.
- Custom Actions from right-click menu added to double-click action - All of the custom actions that you assign to your right-click menu in VNCScan can be assigned as the double-click action for each computer. This is a per-computer setting.
For example, if you made a custom action for TELNET.EXE %HOST% and assigned it as the double-click action, you would telnet to the computer when you double-click on it. You get the idea ;)
- Improved the before and after actions for computer connections - In short, they work properly, now. When you set a computer to install VNC before connecting, you can choose a deployment profile in the computer properties and the deployment is done without any prompting. The same is true with the uninstall afterwards.
The install and uninstall will use the alternate credentials that you set in the group or computer properties for the install and uninstall script if set. If not, it will just use your current information.
- Remote Desktop (Terminal Server) Console - Added the option to connect to a remote Terminal Server 2003 in remote console mode. This basically connects to the actual desktop on the remote server much like VNC does. this only works for Windows 2003 Terminal Servers, though.
- Terminal Server settings at the group properties - You can now set terminal server/RDP settings in the group properties and have them apply to all computers in the group that do not have an override set in the computer properties.
- Profile Path is now movable - You can set the path to your deployment profiles in your main VNCScan program options. This allows you to share a single set of deployment profiles on a shared network drive for your entire IT staff.
- Added "Interacts with desktop" to remote scripts - If you edit a custom script or create a new one, you will notice a new checkbox in the authentication section that determines if the script will interact with the desktop or not.
This is only effective if you followed the directions concerning downloading and placing PSEXEC.EXE in your VNCScan application folder.
The purpose was to get scripts that need access to the local display on the computer to work properly or for popping messages up on the desktop of the remote computer. One such script that needs this box checked is the one to deploy the UltraVNC video driver.
- Lots of bug fixes and double checks - VNC Scan is a living application. This means that it's always being developed, fixed, and enhanced. If your bug wasn't fixed in this version, keep an eye on the betas that come out regularly. If you don't see something coming along fast enough, feel free to put a message in the forum to get out attention!
- Connection Bug Fixed - If you had the group set to send Wake On LAN packets before connecting, the connection status box would just sit there and say "Connecting..." and never actually connect. This has been fixed.
- Scanning Changes - There have been some significant changes in the scanning parts of VNCScan.
The most obvious change is the dramatic decrease in CPU usage during a scan. The scan used to consume 100% CPU for the duration of a scan. Now, it is much lower.
Another noticeable change is a "More Info" button on the scan window. Clicking it will toggle the details view during a scan. this just gives a bit more feedback about what's being scanned.
There where some reliability issues with previous versions of the scanner. Some computers with fully functional VNC installed would be listed with a red X indicating that VNC was not responsive. That should be gone in this release.
2005.9.15/12 (Bug Fixes)
- Inventory bug fix - If you opened the computer properties, some of the inventory data would disappear. Fixed.
- Icon error upon startup - In some cases, people where getting an error while loading the icons at startup. This has been fixed
- Current Working Directory when pushing scripts - When you push a script to remote computers, the current working directory on the remote computer is now set to c:\temp\vncscan where the script its self also executes from.
- Script deletes its self after running - When you run a script remotely, it now deletes its self properly after it is finished running. This is more of a security measure than anything else.
- Local Network Drag-n-Drop - This has been fixed along with multiple select drag-n-drop.
- Local Network Enumeration - It used to just try to enumerate the first available domain or workgroup. This caused delays when the tab was selected so it has been changed so that no computers are enumerated until you press the "Enumerate" button next to the selected domain/workgroup.
2005.8.26 (Bug Fixes and enhancements)
- Integrated User Management - You can create company profiles and assign users to that company. Those users can be assigned to computers in your groups.
- User import from Active Directory - You can supply a domain controller and VNCScan will import the users into the built in user database
- Email users attached to computers - If the user attached to a computer has an email address assigned, you can right-click it, choose tools, and then choose to send an email. You can also attach a file to the email.
Note: you must set up the SMTP server and return address in the main VNCScan options.
- Remote Reboot Enhancements - Added a checkbox to force a reboot in
stead of waiting for programs to close inside the remote reboot window. also added the ability to delay the reboot.
- FastPush Fix - Fixed the bug that prevented you from setting the fastpush folder to an alternate location
- Added MSinfo - Right-click a computer and choose Windows tools to access the MSinfo on the remote computer
- Added thumbnail view to right-click menu - You can set the default thumbnail size in the main VNCScan options. Right-clicking on a computer and choosing vnc in thumbnail view launches the viewer in a scaled down window.
You can select multiple computers to open a bunch in thumbnail at the same time.
- Terminal server quick connect - Specifying server:portnumber generated an error in the quick connect box. You can now connect to alternate ports from the quick connect.
2005.8.17 (Bug Fix Only)
- Bug Fixes - We have numerous reports of an error when pushing VNC to computers and of an error that popped up when you first ran VNCScan. Unless you experienced these errors, you don't need to download and install this version.
- Custom Groups List Ordering - There has been a new tab added to the VNCScan settings window that allows you to fully customize the order that the group names are listed in. This feature has been requested by a number of customers and potential customers with a very large number of groups.
- Shared data on a UNC now works - You used to need a drive mapped for the shared data to work. You can now store them on a \\server\share and everything works.
- Speed improvements - The rewrite that took place to enable the shared data on a UNC had a very positive effect on the speed of the data access.
2005.8.10 (Enhancement/bug fix)
- Resizable groups list - You can now resize the groups list. It is an up/down box in the VNCScan Settings window. Very useful if you have a lot of groups!
- New inventory fields - You can put in some basic inventory information such as the user, location, and purchase date for each computer. The information is displayed in the details view of the computer list. This is sortable.
- Bug Fixes - Some minor bugs where fixed in this version. These include the return of spaces to the group names, providing passwords with special characters (i.e | and >), using spaces in the username when deploying scripts, and a few other small bugs.
- Updated UltraVNC - The latest version of UltraVNC has been updated in the fastpush folder.
2005.8.4 (Enhancement/bug fix)
- Status Icon Bigger - The icons that show if VNC was detected on the last scan are bigger.
- Select VNC Viewer in computer properties - You could select the viewer in the global properties and in the group settings but now you can also choose the viewer in the computer properties. The computer properties override the group and global properties.
- Select custom RC4.Key file in VNC deployment wizard - You can select an alternate rc4.key file to be delivered with an UltraVNC deployment that uses the DSM encryption. This is considered an advanced feature and there will be a demonstration video in the support section soon.
- Minimize to tray icon features - You can minimize to the tray icon using the icon in the toolbar or the View menu. When the program is in the task tray, you can right-click it and quickly connect to all of your groups from the pop-up menu. VERY cool!
2005.8.02 (Enhancement/bug fix)
- Enhanced group filtering - At the group properties, you can filter to include computers with text in the host name and to exclude computers with text in the host name. The exclude takes precedence over the include. This was a feature request by multiple users.
- Launch VNCViewer in -listen -dsmplugin mode - This was another user request to be able to use the DSM plugin in listen mode. There is another pending request to have it ask you for port number and that is coming.
- Fixed connection error when "connect by ip" was set - When you attempted to connect to a computer in the scanned list group and had the check box set to use the IP address instead of host name, the port number would never get read and the connection would fail. This has been corrected
2005.7.30 (Enhancement/bug fix)
- UltraVNC DSM encryption Enhancement - You can now check a box in the Local Network tab to enable the UltraVNC encryption on your viewer when you connect that way. Tt also works in the Quick Connect box. Before, the DSM encryption was only applied to the viewer if it was launched from a scan group.
- Passwords with reserved DOS characters now work with VNCScan - If you have Windows passwords with a |, <, or a > in it, the alternate authentication would have thrown fits. It plays nice, now.
- Custom Icons! - In a nutshell, you just copy the icons to a folder called "Icons" under the VNCScan program folder. From there, you can pick the icon for a particular computer by right-clicking a computer and choosing properties.
- Large Icons Return - You can set the scan list to use large icons, now. It will remember your favorite view and return to it every time that VNCScan opens.
- Launch VNC in thumbnail view - Select View from the main menu and choose a scaling size. Any time that you connect to VNC from then on, it will be that scale. To get a viewer that is in thumbnail view back to normal, just right-click the title bar in the viewer and set it back to normal mode.
2005.7.19 (Enhancement/bug fix)
- Windows Password Reset Tool - This allows you to remotely reset local and domain Windows passwords either on a single computer or in mass amounts. The intention for this tool is to allow you to remotely change all of the Administrator user passwords on your network in one quick click. There will be more on this tool in the support section soon.
To access it, simply right click a computer or a group of computers and choose the Windows tools and then 'Windows Password Reset Tool'.
- Enhanced mass VNC password reset tool - It has been retooled to use the same functionality and look as the Windows Password Reset Tool. You can access it by right-clicking a computer and selecting Tools and then Change VNC Password
- Deploy VNC with No Shortcuts created - You can check a box at the end of the deployment wizard to tell it not to create any shortcuts on the remote computer
- No more high CPU usage on some workstations - It was reported many times that VNCScan was using a lot of CPU cycles when it was just sitting idle. This has been fixed.
- Bug Fixes - There have been a number of bug fixes, also
2005.7.15 (bug fix)
- Bugs Fixed - There where some bugs that prevented certain right-click windows from opening. Normally, we wouldn't send out updates this quickly but this is big enough of a mistake that it warranted a new released this morning. I apologize for any inconvenience that this may have caused. If you downloaded 2005.7.14, I encourage you to download this new version before making a decision.
2005.7.14 (Enhancement/bug fix)
- New window to guide Safe mode Reboot - There is a new window to reboot remote computers into safe or normal mode. It just makes things a bit easier to do. You can also select multiple computers to reboot in one shot.
- Process manager fix - It was reported that the process manager was not using the alternate logon information supplied in the group or computer properties. This has been fixed, now.
- Terminal Services Bug - Class not registered error fixed
- MyDetails removed - Removed the adding of MyDetails.exe from the push script per many requests
2005.7.7 (Enhancement/bug fix)
- PSEXEC now used in remote deployment - Windows Scripting Host has limits on some computers that PSEXEC can get around. There is more information in the section on remote scripting above this section.
Without PSEXEC, you may get an error at the end of a deployment stating that an object is required along with some authentication errors.
2005.6.28 (Enhancements and bug fixes)
Deploy UltraVNC with Encryption - FINALLY! This is something that has been on the wish list of every security conscious VNC administrator for a very long time. Now, you can deploy UltraVNC with data encryption enabled and with full support within VNCScan. Read more here.
- Deploying VNC creates maintenance log entry - When you deploy VNC to a computer, you will notice that a maintenance log is created that gives some basic feedback. You can access the maintenance logs by right-clicking a computer in any group and choosing the Computer Properties.
- Setting boot.ini to safe mode also creates undo on remote computer - A file named 'restorebootini.cmd' is created in the c:\ drive of the remote computer. We haven't had any reports of computers getting stuck in safe mode but we thought that it would be best to be safe. (no pun intended ... really)
If you ever find yourself in a situation where the computer just will not go back into normal mode after using VNCScan to set it in safe mode, simply execute this command script and all should be well. It basically restores the original boot.ini.
2005.6.15 (Enhancements and bug fixes)
- 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, click here.
- 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, click here.
- 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.
2005.5.27 (Enhancements and bug fixes)
- Fixed the external tools menu - There where some reports of the external tools menu not populating. After much research, it has been fixed.
- New filtering! - You can now set filters for the results of the scan group based upon the host names of the computers. For example, if you have a training department and all of their computers contain the word "train" in them, you can place that filter on a group name and only those computers will show up.
Click here for more information on this new feature
- Drag and drop from the Local Network list! - Now adding computers from your LAN is as easy as dragging and dropping them from the automatically discovered workgroup or domain list. This has been one of the most frequently requested feature. I'm sorry that it took so long.
- Updating DHCP changes without rescanning! - This has been the second most requested feature lately and not far behind the first. You can right-click on a computer, group of computers, or an entire scan group and tell it to update the IP addresses via DNS. There is no need to do a complete scan of your network for this any more.
2005.5.11 (Enhancements and bug fixes)
- New support for UltraVNC deployment using MS Authentication - You can now choose in the wizard to deploy UltraVNC using MS Auth instead of the standard VNC password. Click here for more information on this feature.
- Include registry export as part of VNC deployment - You can include an exported .reg file as part of the remote deployment profile. This is a very powerful feature that gives you total control over the settings applied to all computers on your network. More information is available here.
- Connect to VNC (view only) shortcut added - This was actually a feature request to make it easier to connect to a computer in view only mode. It has been added to the right-click menu as requested. If you have any feature requests, be sure to let us know.
- Fixed minor bugs - A few bugs where fixed in this version. Two involved buttons not working on the deployment wizard and one was an annoying error that intermittently showed up when the Local Network tab was selected. None of the bugs caused the program to crash. Find a bug? Let us know!
2005.4.22 (Enhancements and bug fixes)
- UltraVNC Repeater support - There is now built in support for setting an UltraVNC repeater for a group of computers. More information on this is available here.
- VNC password .REG file creator - If you're interested in using log in scripts or any other form of scripting to keep your VNC passwords consistent, this feature will be very useful. More information is available in this PDF.
- Optional prompt for log entry when VNC closes - There have been a number of requests for this optional feature. You can turn it on in the group properties box. When it's ticked on, you will be prompted to put in a log entry when the viewer disconnects.
- New option to check status before connecting - It wasn't an option in the previous versions and it was causing some problems on certain networks. If you are having a hard time connecting to computers in the Scanned list but you can connect just fine with the Quick Connect box, you may see an improvement by turning this feature off. It's in the group properties box.
2005.4.15 (Enhancements and bug fixes)
- Fixed some MAJOR scanning problems - Due to some weirdness in the scanner, some hosts where missed and other phantom hosts where "detected" and added to the list. This has been corrected and the scanner should work "as advertised", now.
- Added Block List - You can right-click a computer and add it to the block list. The next time that the group is scanned, that IP address will be skipped. You can edit the ignore list by right-clicking the group name. The ignore list is per-group.
- Removed the IP range requirement from groups - Until now, you where required to enter an IP range when creating groups. This wasn't very user friendly if you just wanted to create a group for manually added computers.
2005.4.6 (Enhancements and bug fixes)
- Local Network Tab Fix - Double-clicking on computers in the Network tab caused VNCScan to bomb out. This has been fixed.
- Scanning bug fixed - If you put in a huge range with more than 8500 computers, VNCScan would lock up and throw an out of resource exception. It was pretty much a rewrite of the whole scanning engine! Those of you with exceptionally large networks should see the difference.
- Connect and Disconnect actions - added connect and disconnect actions in the scan group properties. You can start/stop the VNC service or install/uninstall it.
- Command Line Prefix - Added a prefix to the VNC Viewer command line in the same window of the scan group properties for those of us that like to use SSH to encrypt our VNC traffic. In order for it to work, we need to launch the SSH command before the vncviewer command. This feature makes that possible.
- Custom Double-Click Action - You can now set a per-computer double-click action. Some of your computers may run Terminal Server while others run VNC. You can set this action in the computer properties
- Thread Limit Gone - The rewrite of the scanning engine allows for more threads to take place. Be cautious with this new found freedom, though. If you have too many threads, the scanner will miss computers because they will not have time to respond before it times them out. You should probably increase your timeout value as you increase your threads.
- Register all pingable computers - On the scangroup properties, you can choose to register even the computers that don't have VNC installed on them. Beware that this will slow your scan down drastically so you may only want to check this box every once in a while and leave it unchecked for the most part.
- New Menu Items - When you right-click a computer, you can choose to connect to VNC using the java client. The remote server has to be configured to use the java server for this to connect right.
You can also web browse and telnet to the remote computer via the right-click/tools menu.
2005.3.31 (Enhancements and bug fixes)
- Scanning bug fixed - Technically, using the number 255 as the last digit of an IP address octet creates an invalid IP address but VNCScan wasn't trapping it if you tried to do so. It would actually bomb out in a rather ugly fashion. It is now fixed so that if you enter 255 as the last octet, it will silently substitute it with 254 and carry on.
- Deployment Wizard additions - There have been some UltraVNC and TightVNC specific server options added to the wizard along with an updated interface.
You can also choose to just refresh the passwords and settings without doing a complete push reinstall of VNC on the remote computer(s).
- Bug alert - We've found a bug in this version and it will be fixed in the next release due out within a day or so. The bug makes VNCScan error out if you double-click on a computer inside of the Local Network tab.
- Major change to remote scripting - You can now save your script as a job and include files to be transferred over prior to execution. To deploy the job after you have built it, you simply right-click the computer and choose:
- Script executing changes - VNCScan uses WMI to execute the script on the remote computer. Windows XP service pack 2 has introduced a change in the way that this API works and the changes may get in the way of your script. Sysinternals makes a utility named PSEXEC that you can download HERE.
If you place the psexec.exe file into the folder that VNCScan is installed into, the script engine will use this instead. PsExec is able to work around this new SP2 "feature" and things will operate much smoother.
- New Server Logging - You can add service logs to the computer properties. This is helpful for keeping track of changes to the computers such as reboot reasons and patch updates. This new feature is accessible by right-clicking a computer and choosing Properties.
- VNC and Terminal Server logging - VNCScan logs the connection time when connections are launched and terminated from within VNCScan. The logs can be found by right-clicking a computer and choosing Properties
- Remote Windows password changing - Right-click a computer and choose 'Tools' - 'Windows ... Tools' - 'Change Windows Password' in order to change the Windows password for any account on a remote computer that you have administrative access for.
To change the password of a domain account, simply right-click a domain controller and type in the name of a domain account.
- Edit Scheduled Tasks - This is yet another step towards making it easier to manage remote tasks from within VNCScan. Now, there is a new menu under the Tools menu item. This will allow you to open the Scheduled Tasks node on the remote computer using Windows Explorer. This feature is also unique to VNCScan.
- Slight improvements to the user interface - There have been some eye candy updates to the remote scripts window and to the right pane of the main window. There are also faster and prettier menus all over the place. The old ones where pretty slow and clunky.
- Remote Script can now accept parameters - This was missing from the last release and I think that it's essential that scripts that you push be able to use the command line switches. This makes it easy to paste some of the VBS scripts that come with the resource kit into the script window and push it off to the remote computer along with the required command line switches.
- Known minor bug - There was one lasting bug found after this version was released. It's really minor and you shouldn't run into it unless you make a mistake entering in your scan range. If you put in an invalid scan range for your group of computers, the program may hang once you end the wizard. You will need to go back in and correct the scan range before the program will accept that group without hanging. Until the next release, please just make sure that you're entering in a valid range of IP addresses.
- This one is a pretty significant update. Some of the features that are in this version have been on the wish list of many of us for a long time and their completion sets VNCScan even further ahead of the competition.
- BUILT IN RUNAS! Added the ability to set a windows username and password that works pretty much everywhere in the program. You can set a global Windows/Domain login in any of three locations: The VNCScan settings (global), the group properties (semi-local), and the computer properties (local).
VNCScan works from the computer level up. This means that if you have a domain\user1 that is set at the computer level and a domain\user2 that is set at the group level, VNCScan will use domain\user1 as the user to perform actions upon that computer with. This granular processing of users is awesome for those of us that manage multiple domains and may have many different administrative usernames that we need to supply depending on the situation.
- Enhanced remote scripting! As you can see in the screen shot below, the new scripting features of VNCScan are very powerful. You can create VBS scripts or CMD batch files and push them out to the remote computer, then schedule their execution. These scripts execute ON the remote computer. You can even select multiple computers and push the same script to all of them at the same time!
- Many bug fixes. There have been lots of code cleanups and such that has uncovered bugs and potential bugs. We're pretty sure that we've squashed all of the ones that we could dig up. For example, there where a few functions that operated fine if you ran them on computers in a scan group but failed miserably if you tried to run them against a computer in the Local Network tab.
- Added a choice of Terminal Server and VNC to the quick connect box.
- Added the ability to choose between stretching to scrolling the terminal service tabs after connected. Right-click the tab for the menu to choose.
- Fixed bug where the custom tools XML file didn't act right if you moved the groups.xml to another location.
- Changed it so that if you have a lot of tabs open, it just scrolls to the right instead of layering tabs. Not only was the old way an eyesore because it would give you less space in the window for the terminal server window, it was kind of buggy sometimes.
- New Task Manager - You can, now, right-click a computer, choose tools/view processes. It will open a window where you can view and kill processes on the remote computer.
- A few other minor bug fixes
- The Quick Connect is back with improvements. It's a combo box in the side pane, now. It remembers the computers that you quick connect to.
- Updated the help file
- Added a new information pane to the top of the computer list.
- Added a combo list at the end of the deployment wizard that allows you to add the computer(s) to a scan group. This is useful if you're installing VNC to new computers that are not currently in any group.
- Enhanced the computer properties box to allow for more per-computer options and settings
- You can now edit and resolve MAC addresses via computer properties
- You can override the global Terminal Server settings with per-computer settings if you wish
- Fixed the bug when starting/stopping remote VNC services
- Fixed the bug when attempting to remove VNC from remote computers
- Major speed increase when moving and deleting computers
- Look and feel update - There have been very obvious changes to the look and feel of VNCScan. It's been long overdue. Most of the changes and updates over the past months have been additions to functionality and stability. The current campaign of updates are to make VNCScan as user friendly as possible.
- Warning when deleting groups and computers - added
- Various other minor bug fixes
- New look and feel. Take a look at the screen shot. VNCScan has had a face lift. I've had a few .... notices .... that the interface for VNCScan was very retro and needed some attention.
- New side navigation bar looks very "XP" - complete with animation
- New scanning status window. It doesn't give as much raw information but heck, it's pretty.
- Wake On LAN before connection - This option is set in the properties of the group. When the box is checked, a magic packet is sent over the LAN to the computer to wake it up. VNCScan will wait for up to three minutes for the computer to start responding. Once the computer responds, the connection will be completed. Oh, and the window has a pretty animation. ;)
- Memory Hog Fix - I found an area where VNCScan was being a memory hog during a multithreaded scan for VNC. It has been corrected.
- In a nutshell, lots of things happen faster in this version. There where a lot of places where the code needed some serious optimizing and TLC. For instance, the computer list only refreshes when it has changes and the way that it refreshes is MUCH faster. There are numerous other speed enhancements.
- Included a check for the XP SP2 bug after a scan completes. If VNCScan notices that you only found a partial list of computers during your scan because of the XP SP2 bug, it alerts you how to remedy the problem (by downloading the fix on this page)
- Made some user interface enhancements. Some of the screens such as the computer properties and VNCScan Settings windows have gotten a minor face lift to make things look better and be a bit more accessible.
- Added the option to install VNC to a new computer that you are adding to a group manually. See screenshot:
- Fixed bug that prevented scanner from operating properly with IP ranges greater than 254 hosts and threads less than 4. All IP ranges and thread counts should work fine, now.
- Per suggestion, added text next to the thread count box to show that the max available threads are 10.
- Fixed a bug that prevented the saving of the thread count for some IP ranges. It always defaulted back to a single thread in those cases. This problem is fixed.
- Added multithreaded scanning
- Bug fixes
2005.3.30 (Enhancements and bug fixes)
2005.3.10 (Enhancements and bug fixes)
2005.3.8 (Enhancements and bug fixes)
2005.3.5 (Enhancements and bug fixes)
2005.3.2 (Enhancements and bug fixes)
2005.3.2 (Enhancements and bug fixes)
2005.2.28 (Enhancements and bug fixes)
2005.2.23 (Enhancements and bug fixes)
2005.2.21 (bug fix)
All versions prior to this point are archived