My friend Mike emailed me:

“Hey Steve,

I thought I might pass along another tool from Nirsoft. I just used it to solve a random crash issue I had with one of our remote servers. It would crash intermittently, and I could never get the staff to look at the machine before they cycled the power. It is called Blue Screen View….”

Blue Screen View is a great tool. Every time windows crashes with a blue screen, it creates a dmp file in the c:\windows\minidump folder. My friend mike was able to pull those dmp files from that remote server over the network, and load them into the Nirsoft tool.

It makes it a breeze to diagnose issues like this. When you launch it – the program will automatically load any dmp files it finds on the local machine:

If you have ever had to diagnose a blue screen crash, you usually have to wait for it to happen…then quickly write down the error code, and then finally get to a machine and do a google search.

With this tool, it is two clicks away:

Man, what a huge time saver.

More importantly it lists the driver that caused the crash. This will tell you almost immediately where to look or what to update to resolve the issue:

You can even view the blue screen as it looked when the machine crashed:

It is free for commercial and personal use. You can download it from here:

http://www.nirsoft.net/utils/blue_screen_view.html

Another great tool to add to your USB flash drive in your pocket.

I got a question from Darren:

“Steve, been using the free edition of Network Administrator. Nice tool, but it is missing something we need. I see you have the ability to shutdown and reboot systems, but what about logging off users?”

Good question. I remember when I would do after hours upgrades – and one of the big issues was a user that would leave an app open that was part of the upgrade. After the it failed we would have to start making the rounds to see who left it up and running.

It would have been great if I could have just hit a few buttons and forced all computers to logoff.

That is now possible with Network Administrator – we have added the option to the shutdown section:

It works on 2000, XP, 2003, Vista, Windows 7, and 2008 – even the 64 bit versions.

Just select the logoff action, pick your machines, and start logging them off:

It is a totally free tool if you don’t need to use it on more than 3 computers at the same time. Get it from our download page:

http://www.intelliadmin.com/index.php/downloads/

I have been getting lots of questions from everyone, and that is great

This week I got a question from Charles,

“Hello Steve,

I have a problem, I need to run a VB Script that will tell users that their password needs to be changed in x days. The Windows 7 balloon is not effective, and users miss it. Also, I do not want it to slow down the login. So what options do I have left?”

This is an excellent question. Other versions of windows might not even tell you.

For example: A user could leave their system on for days and days, and then cross the threshold of the password expiration date – suddenly nothing works for them.

You know what that means – another call to the help desk!

I have a good trick to filling all of your requirements. I have translated them to:

1. Make sure the users logon is swift, and not interrupted by a password expiration notice (Especially because windows just told them about it!)

2. While they are using windows, make it clear that their password expired. Don’t depend on Windows to properly notify them.

3. Do all of this from a script, no extra programs required

I think we can make that happen. First, we need a script to see if and when the users password expires. I found one that Microsoft has provided, and I have modified it to suit our needs.

The script has one function – PasswordDaysLeft. You call it, and it returns the number of days left before the password expires. If the function returns 99999 then the password never expires.

For example, if we wanted to know that in 10 days or less the password would expire, we would call it like this:

if (PasswordDaysLeft() <= 10) then
 MsgBox("Your password will expire in " & PasswordDaysLeft() & " days!")
end if


So now we have the ability to check for password expiration. But what about the original request? We don't want it to pop up at startup, but later.

Here is how we can get our script to do that:

We will loop in our script, and only check every 5 minutes. In addition, we will only start checking 20 minutes after the user logs in:

'Sleep for 20 minutes
WScript.Sleep(20 * 1000 * 60)

bRunning = TRUE
'20 minutes is up, check every 5 min to see if password is too old
while (bRunning)
 if (PasswordDaysLeft() <= 10) then
 MsgBox("Your password is about to expire. Please log off right now and change it")
 bRunning = FALSE
 end if
 WScript.Sleep(5 * 1000 * 60)
wend


This will stay running until the password expires, or the user shuts down or logs off. Once the user is notified, it will exit and not bother them again.

Now we have most of what we need:

-A function that tells us how many days before a password expires
-A script to check it.

How do we get it to run in the background?

That is easy. From the users logon bat file we call our VB Script like this:

start wscript \\server\share\PasswordExpires.vbs

This tells the BAT file to fire up our script, but not to wait for it.

So here is what happens:

The user logs in, the script is launched into the background. It silently waits for 20 minutes, and then on 5 minute intervals it checks if the password expired. If it did, then the user gets a notification and it quits.

It think that covers everything. The logon is quick, since it launches our script in the background and lets the user get right to their business.

You can download the zip file with the VBS file, and an example BAT logon script here:

http://www.intelliadmin.com/PasswordExpires.zip

We just released Beta 5 of Enterprise Remote Control.

Here are the download links:

Enterprise Server Download (1.0.0.105)

Viewer Download (5.0.0.170)

What is it? – Let me tell you.

Ever have trouble supporting a remote user because it is too hard to get to their machine? You know what I am talking about…finding their public IP, having them open a port or two – if you are lucky you can pull it off, but usually you end up saying “Tell me what you see now”

Wouldn’t it be great if you could get to their computer and control it as if you were standing right there? No matter where they were at – as long as they were connected to the Internet?

I hear you. You are saying, “Sure Steve, but I don’t want to pay some huge monthly fee”.

I say you don’t have to.

Yes, there are many online services out there that will provide this for a monthly fee. Those are great – but you are different.

You know the difference between an IP and a MAC address. You don’t need the “hand holding” these services require. Plus you don’t want your sensitive info passing through a server you have no control over.

Why couldn’t you just run it yourself?

You can. That is what our Enterprise Remote Control can do for you.

Setup the IntelliAdmin Enterprise Server on your network, and install the agent on computers you want to control. From that point on those computers are only a few clicks away. Easily find a computer by name – instead of a constantly changing IP address:

When you go to connect, the system will find the most efficient way to get to it. If you are both on the same local network, then it will make a direct connection. Both of you are behind firewalls? No problem – it can relay the connection. With almost any firewall configuration, you can control that remote machine.

How much you ask? Right now we are still in beta. To reward those customers who support the product while it is being developed, we are offering a special license.

$599 US for an unlimited copy – Unlimited agents, Unlimited viewers. When the product is released on June 1st we will start charging per the number of agents.

Don’t wait, get your pre-order in now:

Pre-order Enterprise Edition today

The beta has been going on for a while now, so why not take a look at the past releases and get up to speed:

Enterprise Edition Beta 1

Enterprise Edition Beta 2

Enterprise Edition Beta 3

Enterprise Edition Beta 4

Where are we with Beta 5?

Last time I promised easy distribution. The distribution tool, and the online agent builder are still being tested – so those are not ready yet. We did not want that to hold this release back. They will be ready soon.

We have fixed quite a few bugs in the Viewer, and improved its performance.

As promised, you can now set the viewer to register with the Enterprise Server when it automatically installs the agent on your LAN:

That little checkbox seems like a small feature, but our team put in many hours to get that to work.

Also, we have added a setting on the Enterprise Server:

This allows you to enable, or disable the “Configure” button in the agent information window (This is what is displayed when the user clicks on the icon by the time):

The need for this will not be apparent right now, but in Beta 6 the agent settings window will allow you to configure the connection to the Enterprise Server – so it will be an important option.

So – Lots of bug fixes in all three components:

The Enterprise Server (We were calling this the reflector before)

-Issue where “Show Tray Icon” setting was not propagating
-Performance issue on networks with +300 agents resolved
-Agents were showing “Offline” when they were actually, online

The Agent
-Agent would crash if the option “Request Permission” was checked
-Agent performance improvements made
-Agent was not receiving the setting for “Show Tray Icon” from Enterprise server

The Viewer
-Viewer was leaking GDI resources if left open for long periods of time
-Viewer would crash on Windows 7 system if the agent connection was suddenly dropped.
-Viewer performance improved on older systems.

What is next?

Between beta 5 and beta 6 we will get those distribution tools out to you for testing. Beta 6 is targeted for the end of April. In that release we have a few bugs to still fix, and a few more tweaks to the viewer

All of the month of May we will continue testing – with no new features added. The final release will be on June 1st.

Pre-order Enterprise Edition today

On one of our servers we have a batch processing program. It is old and clunky, but it gets the job done.

An irritating bug it has is that it leaves temp files around in the c:\windows\temp folder.

One day we noticed the server was getting slow – finally realized that the temp folder had over 100,000 files!

We don’t have the code for this program, so we can’t fix the bug. An easy fix would be to setup a scheduled task to trash that folder every night.

Oscar would like to have all those files every night, but the problem with this solution is it can cause problems with apps that actually are *using* those temp files.

What we needed was a way to delete files that were over 1 day old. This was enough to make sure the temp file was no longer used by any of our processing apps.

After searching around, I found a command line program that Microsoft included with some versions of windows. It is called “forfiles”

ForFiles will process a command against files and folders that match your criteria. It allows you to set wildcards, pick only folders, or only files…and more importantly it allows you to specify something like “I only want files that are more than 1 day old”

First, let me show you the possible command line arguments for it:


/P Path Name - Indicates the path to start searching. The default folder is the current working directory

/D date Selects files with a last modified date greater than or equal to (+), or less than or equal to (-), the specified date using the "yyyy/MM/dd" format; or selects files with a last modified date greater than or equal to (+) the current date plus "dd" days, or less than or equal to (-) the current date minus "dd" days. valid "dd" number of days can be any number in the range of 0 - 32768."+" is taken as default sign if not specified.


Cool. It has everything we need.

Lets start out with the path. We want it to look in c:\windows\temp

forfiles -p "c:\windows\temp"

I want to include subfolders:

forfiles -p "c:\windows\temp" -s

Using the date option, I tell it anything over 1 day old:

forfiles -p "c:\windows\temp" -s -d -1

I only want to delete the files that end with .tmp:

forfiles -p "c:\windows\temp" -s -d -1 -m *.tmp

And finally, the command I want to execute against the files it finds is del:

forfiles -p "c:\windows\temp" -s -d -1 -m *.tmp
-c "cmd /c del /f /q @path"

Note the use of the @path variable – it is one of the many variables forfiles recognizes.

So there it is – a one line command that will delete files from our temp folder over 1 day old:

forfiles -p "c:\windows\temp" -s -d -1 -m *.tmp -c "cmd /c del /f /q @path"

If your copy of windows does not have forfiles, you can download it from the Microsoft FTP Server here:

ftp://ftp.microsoft.com/ResKit/y2kfix/x86/

I am really impressed with this little utility, and the possibilities are endless. I highly suggest keeping a copy on your flash drive.

We have put the finishing touches on beta 3. To recap: Enterprise remote control is software that allows you to control computers from anywhere. No need to open ports, or get someones IP address. With a few clicks you can support your users – even if they are across the country in a hotel on a free wifi connection. The software takes care of the hard work for you.

Here are the download links:

Agent (Install on the computer you want to control)

http://www.intelliadmin.com/reflector_agent5.exe (Build Number 5.423)

Client (Software you use to control computers)

http://www.intelliadmin.com/reflector_client5.exe (Build Number 5.0.0.127)

Reflector (Server software that manages it all)

http://www.intelliadmin.com/reflector_server5.exe (No update…if you already have it no need to download)

Again, we are still offering our beta pricing. You can get an unlimited viewer and agent license for only $599. Once the beta is complete, this will no longer be available and we will switch to per agent pricing.

Visit our online store to purchase today

For more detailed information about what has been fixed/changed in this release…read below:

For background info…here are the previous posts about the beta

Part 1:
http://www.intelliadmin.com/index.php/2010/08/enterprise-remote-control-beta/

Part 2:
http://www.intelliadmin.com/index.php/2010/08/enterprise-remote-control-beta-1/

Part 3:
http://www.intelliadmin.com/index.php/2010/10/enterprise-remote-contol-beta-2/

Our core concern in this beta cycle is refactoring and improving the agent. The little things. Those little things that annoy you when trying to help someone out with our product.

Nailing down all of these small issues has been more time consuming than we originally thought.

What are some of the annoyances?

Window resizing. When you resize a window you cannot see the selection box:

We studied all versions of windows to find out the right messages to catch. Now it shows that box in a smooth and consistent manner.

Cursors. When you are in a remote control session, you only see an arrow cursor.

This is fine until the system is busy and you can’t tell because the cursor is always an arrow. Unlike other remote control software, we wanted ours to load a real windows cursor…not just a bitmap.

The difference is huge. A bitmap feels sluggish, and disconnected. A real cursor makes you feel like you are there.

We underestimated how difficult this would be. It was very tough to implement, but we got it. And you will love the difference it makes.

Windows 7, Vista, and 2008 shutdowns. These versions of windows have a special shutdown screen that is displayed when an application will not terminate. What happens right now? You just get a screen shot of the last valid screen. You can’t even control the system anymore. It was extremely difficult to get our agent to stay alive after that window was displayed.

Here is what you would see before we fixed this issue:

Now, you have full control, and can see the shutdown screen:

Viewer performance. After we moved from 3.0 to 4.0 our viewer has always lagged in performance. This was due to the addition of a “Stretched” view. We finally took the time to sit down and re-factor that code. It blows away the old version.

Finally, our toughest issue was the overall capture performance of the agent. We spent many late nights optimizing and making the capture process as efficient and complete as possible. When I say complete I mean that it does not miss updates and show garbled screens. Efficient means CPU time is as low as possible on that old XP system from 2001.

That brings us to a new addition to the agent – a mirror driver.

What is it? A mirror driver is a special video driver that can sit between Windows and the video card. It helps on both counts – a reduction of CPU usage, and very fast updates.

Right now we use a hook. Using a hook only allows an approximation of changes on the screen. This causes the view to slow down, and sometimes miss an update.

This means we have two options for capturing changes – a mirror driver, or a hook.

The down side of a mirror driver is that on Vista and Windows 7 systems it will disable glass, and other nice graphical features while it is active. Additionally, it can cause the screen to flicker slightly when you connect. Some of you use our remote control to monitor user activity – without their knowledge. The mirror driver is less than ideal in this situation because it allows the user to immediately know that you are connected.

We wanted to give you the choice. Remote Desktop speed with the mirror driver, or sightly less performance…but less effect on the users view with hooks.

Those of you looking for faster response times will be pleased with the mirror driver performance.

There are other little fixes I am missing here, but you get the picture. We want to make sure that your remote control experience is as smooth, and fast as possible.

Bugs – One of the most annoying bugs in beta 2 is computers that still show offline, when they are not. Another difficult problem to solve, but we got to the bottom of it. This is a tough one since we have not been able to reproduce locally. Only beta 3 will let us know if it is fixed.

Distribution – Nothing on this front yet. One thing that holds us back is we don’t know what our final settings will be in the agent and viewer. I know many of you need distribution solutions badly. We will get there…just not yet. Our plans are to allow registration and installation from the viewer, a distribution tool, and an online system where you can generate an MSI file for the agent. We will try to make distribution of the agent as simple as possible.

That is all I have for now. We can’t wait to release it.

The same deal is in place during our beta: $599 US for an unlimited version of the product.

Unlimited means unlimited viewers, and agents.

Once the final product is released, we will charge per agent.

You can pre order from here:

Visit our online store to purchase today

Thanks again for your support and help testing our software.

Many of you have been asking when we will release beta 3. I don’t have a release date, but it will be before the end of the month.

If your beta has expired, let us know and we can get you a reset.

For background info…here are the previous posts about the beta

Part 1:
http://www.intelliadmin.com/index.php/2010/08/enterprise-remote-control-beta/

Part 2:
http://www.intelliadmin.com/index.php/2010/08/enterprise-remote-control-beta-1/

Part 3:
http://www.intelliadmin.com/index.php/2010/10/enterprise-remote-contol-beta-2/

Our core concern in this beta cycle is refactoring and improving the agent. The little things. Those little things that annoy you when trying to help someone out with our product.

Nailing down all of these small issues has been more time consuming than we originally thought.

What are some of the annoyances?

Window resizing. When you resize a window you cannot see the selection box:

We studied all versions of windows to find out the right messages to catch. Now it shows that box in a smooth and consistent manner.

Cursors. When you are in a remote control session, you only see an arrow cursor.

This is fine until the system is busy and you can’t tell because the cursor is always an arrow. Unlike other remote control software, we wanted ours to load a real windows cursor…not just a bitmap.

The difference is huge. A bitmap feels sluggish, and disconnected. A real cursor makes you feel like you are there.

We underestimated how difficult this would be. It was very tough to implement, but we got it. And you will love the difference it makes.

Windows 7, Vista, and 2008 shutdowns. These versions of windows have a special shutdown screen that is displayed when an application will not terminate. What happens right now? You just get a screen shot of the last valid screen. You can’t even control the system anymore. It was extremely difficult to get our agent to stay alive after that window was displayed.

Here is what you would see before we fixed this issue:

Now, you have full control, and can see the shutdown screen:

Viewer performance. After we moved from 3.0 to 4.0 our viewer has always lagged in performance. This was due to the addition of a “Stretched” view. We finally took the time to sit down and re-factor that code. It blows away the old version.

Finally, our toughest issue was the overall capture performance of the agent. We spent many late nights optimizing and making the capture process as efficient and complete as possible. When I say complete I mean that it does not miss updates and show garbled screens. Efficient means CPU time is as low as possible on that old XP system from 2001.

That brings us to a new addition to the agent – a mirror driver.

What is it? A mirror driver is a special video driver that can sit between Windows and the video card. It helps on both counts – a reduction of CPU usage, and very fast updates.

Right now we use a hook. Using a hook only allows an approximation of changes on the screen. This causes the view to slow down, and sometimes miss an update.

This means we have two options for capturing changes – a mirror driver, or a hook.

The down side of a mirror driver is that on Vista and Windows 7 systems it will disable glass, and other nice graphical features while it is active. Additionally, it can cause the screen to flicker slightly when you connect. Some of you use our remote control to monitor user activity – without their knowledge. The mirror driver is less than ideal in this situation because it allows the user to immediately know that you are connected.

We wanted to give you the choice. Remote Desktop speed with the mirror driver, or sightly less performance…but less effect on the users view with hooks.

Those of you looking for faster response times will be pleased with the mirror driver performance.

There are other little fixes I am missing here, but you get the picture. We want to make sure that your remote control experience is as smooth, and fast as possible.

Bugs – One of the most annoying bugs in beta 2 is computers that still show offline, when they are not. Another difficult problem to solve, but we got to the bottom of it. This is a tough one since we have not been able to reproduce locally. Only beta 3 will let us know if it is fixed.

Distribution – Nothing on this front yet. One thing that holds us back is we don’t know what our final settings will be in the agent and viewer. I know many of you need distribution solutions badly. We will get there…just not yet. Our plans are to allow registration and installation from the viewer, a distribution tool, and an online system where you can generate an MSI file for the agent. We will try to make distribution of the agent as simple as possible.

That is all I have for now. We can’t wait to release it.

The same deal is in place during our beta: $599 US for an unlimited version of the product.

Unlimited means unlimited viewers, and agents.

Once the final product is released, we will charge per agent.

You can pre order from here:

Visit our online store to purchase today

The beta 3 download links and update will be out before the end of the month…When we release it will be in my newsletter, and on the website.

Thanks again for your support and help testing our software.

We have not said much about Enterprise Remote Control since Beta 1. That is because we have had our heads down in our keyboards busy improving and fixing.

Before I get into what has been updated, where we are going, etc…I want you to know that during the beta you can get an unlimited copy for $599. Zero limits on the number of hosts or viewers. After the beta is complete, It will be licensed per host.

Here is the purchase link:

Purchase an unlimited edition for $599

To get a detailed look at what this product is all about, check out my announcement of beta 1:

http://www.intelliadmin.com/index.php/2010/08/enterprise-remote-control-beta-1/

I want to give a shout out to Matthew P. He has been invaluable in his testing, and reporting to us. Many of these bugs would have been much more difficult to find without beta testers like him.

Chris G – Thank you for being so patient with those reflector lockups. You were not the only one, but you were the only one to respond so quickly and help us resolve it asap.

Download Links

Reflector Server (Build 1.0.0.59)

Reflector Agent (Build: 5.332)

Reflector Client (Build: 5.0.0.123)

Please visit the Beta 1 announcement for installation instructions.

What have we fixed?

-Reflector lockup. This was an issue with testers that had over 30 computers. It took us quite some time to resolve this problem, but it has been fixed. We appreciate the patients of those dealing with it. Thanks for all your help.

-Reflector memory footprint – We have reduced the amount of memory needed for the reflector in half. It was already pretty low. Now it is even lower than before. With about 200 connections you might see 10 to 14 MB of memory usage – equal to less than a single session of FireFox or IE running!

-When no port was specified for the reflector, the agent never reported to the server. For example, in the setup wizard you provide your reflector host name like this: ref.domain.com – instead of this ref.domain.com:443. It would zip through the wizard with no problem…but then the agent would never report. Fixed

-Speed improvement on Vista and Windows 7. In the old version it did not disable the glass effect. It is almost impossible to get a good refresh rate with these turned on. (Notice that MS remote desktop disables these too while connected). It will automatically turn it off while you are connected, substantially improving viewer speed.

-Automatic install for non reflector agent not working on 64 bit machines. Even though this is a beta for our reflector, these binaries are for our standard edition product too. Lets say you try to automatically install the agent to a host on your network that is 64 bit machine…in beta 1 it would fail. Fixed

-Administrator access – When you install the agent it does not add any local user access. If you try to connect to the machine directly, instead of the reflector, it would keep asking for a password. We have set it to add windows administrators for local connections. This will be a configuration option on the reflector in a future beta release.

-Viewer crashing during disconnect. This was a tough one. Thanks to our persistent beta testers we were able to resolve it. Usually it would happen if you left the viewer open over night. Close the session, and bam it would crash. Fixed

What is new in this beta?

The biggest change in this beta is an automatic update feature for the agent (the host). We had a few setbacks, but now it is running smooth. Our first attempt included using a standard setup package that would run in the background. This turned out to be too rigid, and did not allow for failures – it would kill the service and never come back during a failed install.

This forced us to go back to the drawing board and build a custom packager from scratch. It was worth it. Now, the automatic update will periodically check and see if there is an update. When it finds one it will attempt to update the agent. It will keep all of the old files in place until that it is sure that the upgrade was successful. If there is a failure, it will roll back the install and bring it right back to the version it had before. That way there is no interruption in connectivity.

This means you can install on a wider set of systems without having to push that agent out again when newer versions are released.

Currently you cannot control the update process. I know that this will be troublesome for some of you – not to worry…before the final version is released you will be able to control this process from the reflector, and choose from these options:

-Never update

-Prompt to update only when connecting to a host

-Automatically update without prompting.

This will allow you to set an update mode that fits within your policies.

What are we working on in Beta 3?

Currently the software is running quite smooth, it gives us a chance to add some improvements:

-The find computers window will have a way to view only specific sets of computers. For example, just computers registered with the reflector, or just those that it found locally on your domain, or even remove the offline computers from view

-Settings from the reflector. We will add the ability to change global settings for the agent on the reflector. What would these be? Showing the tray icon when the service is active, or automatic update settings for the agent.

-Code re-factoring on the agent side. We are going to dig deep into the agent code and look for some speed improvement. We also have long term plans of supporting other platforms. This will not make it into the final release, but we need to build the foundation for OSX. iOS, Windows 7 Phone, and Android support. In addition to that, this strengthened foundation will include the framework for file transfer and many other goodies. Much of it will not be visible, but the improvement will make for much shorter development cycles and allow us to get cool features to you more quickly.

-Improved computer listing on the reflector. Currently the computer listing on the reflector is hard to navigate. We are going to improve this section to make it easier to identify machines that are offline, and no longer used.

When will beta 3 be released?

Unknown. We know it will be less than 120 days, since that is the limit set into the viewer right now. This keeps old betas from floating around. We will not move to the next beta until we are confident that all of the bugs reported by you are fixed, and it is working smoothly.

What about a distribution tool?

We are working on this. I know that many of you have asked us about it. It will get released before the final version

Any questions, comments please send them to us at support@intelliadmin.com

Thanks again for all of your support, and help making this an awesome product.

A few weeks back we released Remote Control 4.4.

Since that time, we have received reports of a few more issues that needed to be corrected:

-Mouse movements were not shown on the remote side
-ALT Key getting stuck in certain situations when CTRL-ALT-INS was pressed
-CAPS lock not being transmitted during remote control session
-Start menu only responds to one instance of RC client when multiple instances are running

I am happy to say these all have been fixed, and you can get the latest from here:

http://www.intelliadmin.com/setupex.exe

(Trial version build number is: 4.4.27.47)

If you are a current customer, you can use the download link you received when you purchased. It will automatically point to the latest full version

(Full Version build number is: 4.4.27.49)

If you have any questions or issues, please send us an email at support@intelliadmin.com

Hello All,

A quick post to let you know that we have released Remote Control 4.4.

This is a bug-fix release. We made sure we cleared through all of the issues raised by current customers before moving forward with anything new.

Here is what we fixed:

-Shutdown under Vista/Windows7/2008 does not disconnect the remote client (Fixed)

-Windows 2000 machines with NVidia cards show strange graphics when connecting (Fixed)

-ALT key gets stuck when pressing CTRL-ALT-DEL while a client window is open (Fixed)

-Client crashes on reconnect attempts under Windows XP SP2 (Fixed)

-Intermittent Connection issues with Windows 2000 (Fixed)

-CTRL-SHIFT-ESC not sent from client to agent (Fixed)

-Crash when clicking the find button under Windows XP SP2, while a reconnect in progress (Fixed)

-ALT, CTRL, or Windows keys get stuck at intermittent times. (Fixed)

The key sticking issue was a big one, and we apologize to any of you who have experienced it. The issue has been resolved – you just need to update the client to fix it.

You can download the latest version from here:

http://www.intelliadmin.com/setupex.exe

Make sure the client is closed when you install. When you are finished, you can check the build number by clicking on settings and then moving over to the about tab:

Note that if you have the trial version it will be 4.4.27.10

Current customers may get the latest version by simply visiting the same download link that was sent in the license email. If you do have trouble finding it, simply send us an email and we will take care of you asap.