What’s New?

• Fixed the Windows Logon (mslogon) in UltraVNC fo x64 – When pushing a deployment of UltraVNC to a remote x64 system, the mslogonacl.exe tool was refusing to apply the correct permissions.  This has been fixed.

Download Here

Twitter This

UserName: Password:

What’s Changed:

• 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$.
• Lots of other “just little things” fixes and tweaks all through the program.

Please give some feedback about how well or not-so-well it works for you in the Forums

Download It Here

Twitter This

UserName: Password:

View Video

The LAN tester does the following:

1. Created a dynamically sized file specified by you
2. Sends the file to a specified share on the remote computer (default is ADMIN$)
3. Times the transfer
4. Downloads the same file from the destination
5. Times the transfer
6. Cleans up the files from both ends
7. Reports the results to you

Twitter This

UserName: Password:

View Video

Learn how to use the AutoRuns style feature that is built into VNCScan.  You can use it to remove startup programs from remote computers in just a few clicks!

Twitter This

UserName: Password:

View the Video

Learn how to remotely enable RDP Terminal Services on remote computers using VNCScan!

Twitter This

UserName: Password:

This is the second release in a week from Bozteck.  Here’s what’s in this one:

Twitter This

UserName: Password:

From the release notes:

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

Here are some screen shots of the interface changes:

You can grab the latest release HERE.

Twitter This

UserName: Password:

In the early years of VNCScan, all of the data was stored in a Microsoft Access database and the settings were stored in INI files.  This worked well but required that I distributed a lot of additional runtime files to access the database(pardon the pun).

In late 2003, I decided to move away from Access in favor of flat XML.  To this day, I still debate with myself which was better because each have their issues.  The XML file format for data made it possible to ship a smaller product with less dependencies but it severely limited the multi-user capabilities for sharing data.

The XML format is just plain text files. When one console reads the data and then writes a change, there’s a chance that another console that is also reading from that same textual XML file can write back what it thinks is accurate data and overwrite the first consoles changes.  It can get messy real fast.

At least with the Access database, you could have a few users adding and reading data at the same time without overwriting the whole file just for one change to a single field. 

I realize that Microsoft is steering its developers to their mini desktop SQL server instead of Access but it just seems like a lot of overhead for the type of data being stored. 

Today, all of the routines needed to read and write to an Access database is built into the existing DotNet Runtime.  What drove me to this XML format is no longer a problem. 

So, what do you think?  Should we make the move back to the Access database to facilitate a better multi-user experience or stick with the XML?

Twitter This

UserName: Password:

There are currently a number of websites that are hosting cracks for the latest version of this software. I want to put out an alert to anyone who may try it out that their “crack” contains a pretty nasty trojan that lets them spy on your computer and use it as a zombie. I guess that’s the risk that you always take when using keygens and cracks. This one in particular is really nasty, though.

With that being said, I also want to let everyone know that Bozteck isn’t some huge company that the Pirates are “sticking it to”. Every license purchase puts food on my family’s table and every theft of the software is felt by the entire family.

I work as hard as I can to support this software even better than those huge companies that compete with Bozteck. VNCScan costs a tiny fraction of what theirs does, too! While I don’t believe that all software should be free, I believe that it should be affordable by all. That is why the price is only $59 for the per-admin license. I also refuse to charge for each managed computer. With that one per-admin license, you can manage thousands of computers at no added costs.

If my hard work has made your life easier in any way, please consider buying a very inexpensive license for this software. My whole family thanks you.

Steve Bostedor
VNCscan Author

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: