Update: The latest releases of VNCScan no longer require this work around for CTRL + ALT + DEL (SUPER).  It is supported natively.

—————————————————

UltraVNC has had some pretty big issues with sending the CTRL + ALT + DEL combination to Windows 7 when UAC (User Access Control) is turned off (or on in some cases).  We have heard from many users that sending this sequence has no effect on the remote computer.

To date, the developers at UltraVNC have not released a fixed version for this.  We’re impatient around here so we decided to create our own working fix and release it in VNCScan Enterprise Network Manager version 2010.9.21.

The updated deployment tool adjusts settings on the remote system during deployment to fix this issue.  This means that if you ever toggle UAC on the remote system for any reason, you will need to re-deploy UltraVNC to it using the deployment tool in VNCScan.  For most people, this is a “set it and forget it” feature in Windows so.

You may also need to deploy again if you have deployed UltraVNC in the past with previous versions of VNCScan or if you installed UltraVNC manually.  Those previous versions do not have knowledge of this work around and the settings were not toggled.

If you do turn UAC on or off after you have deployed UltraVNC to the computer, you will need to first reboot the desktop, then deploy UltraVNC to it again using the deployment tool inside VNCScan.

While this is an exciting development for users of VNCScan, I know that this isn’t the best fix in the world.  It’s the best that we can do until the great developers at UltraVNC release an officially patched release of their server software.

Steps for changing UAC on a computer

1. Turn on or off UAC using the control panel applet
2. Deploy UltraVNC to the computer
3. Reboot the computer

You can download the latest release here.

Twitter This

UserName: Password:

If you’ve been having problems with your groups and computers reverting to the default upon the previous update, this version should resolve that issue.  I apologize for the rough process in the last version upgrade.  Measures have been put into place to prevent this  from happening again.  Please let us know if you experience any problems with this new version.

Just as a reminder, you should always make a good backup of your data before upgrading to new versions.

Download Link

Twitter This

UserName: Password:

We’ve posted the latest release of Bozteck VNCScan Enterprise Network Manager (VENM) to our downloads page today!

If you saw that there was a version 2010.2.3 and downloaded it before we could correct the error, you probably downloaded a (less than stable) beta version instead of this release.  Please re-download the update to be sure that you’re on the stable code base.

We’ve done some more work to make moving your data files around much easier.  You can modify the root location (the folder that contains the data, profiles, and jobs folders) in the main program preferences in the “Support Files” section.

If you’re moving the data to somewhere on the same volume, you can simply hit the “Change” button and browse to a folder where you want them to be.  When prompted, let the program move the files for you into that location.

If you’re moving to a network location or another volume, manually create that destination folder and copy the data, profiles, and jobs folders into that new destination folder.  After this is completed, follow the steps above and answer “No” when asked if the program should move the files for you.

Twitter This

UserName: Password:

We put out an update to the VNCScan Enterprise Network Manager tool yesterday.  This is considered a refresher update with some bug fixes wrapped in.  There is significant development happening in the beta builds but it’s not ready for public consumption yet.

The biggest news with this update is the new release of UltraVNC server and viewer.  We’ve seen a very nice increase in screen performance and stability in this release of UltraVNC.

The deployment tool had been upgraded to deploy this new version seamlessly.  There is no need to recreate your deployment profiles that were configured to deploy the previous 1.0.5 release.

Twitter This

UserName: Password:

We’ve had a lot of request for the ability to automatically reconnect to computers when they are rebooted.  A majority of the requests were resolved with the implementation of the background scanner and the actions that can be performed when the scanner detects that the computer is alive.

To take this a step further, we’ve modified the ping window that happens when you right-click a computer and choose “Ping Computer”.  Instead of just opening a command window with the standard ping command running, we’ve designed our own.  We’ve done this in order to bring you an exciting new feature – automatically running commands or connecting when a computer responds for X number of consecutive pings.

Here’s a quick video showing how: http://screencast.com/t/CqJI7YhE

Download the latest version here!

Twitter This

UserName: Password:

New in version 2009.1.21, the remote screen captures work on Vista desktops as well as XP. More about this in the release notes.

Twitter This

UserName: Password:

New in this release:

• 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).

Download Here

Twitter This

UserName: Password:

What better way to bring in the new year than a new release of VNCScan, right? We took some of our most requested features and rolled them into this update release. Here’s a run down of the release notes for this release:

2009.1.1

• 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

We wish all of you the greatest year ever!

Thank you,

Steve Bostedor
Founder and President

Twitter This

UserName: Password:

• 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.

Twitter This

UserName: Password:

Changes:

• 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.

Twitter This

UserName: Password: