Share This:

This month’s Pulse stays focused on the recently released version 11.2.

 

I detailed some of these features last month. This month, I wanted to pick up on the upgrade itself. Whether you are prepared to upgrade and what you should do immediately after the upgrade.

 

The Release Notes are published here. As I discussed last month, the main new features are changes to the email monitor and “stop the clock”. A customer I was speaking to recently suggested that this upgrade should have been a major release – Track-It! 12, his view was that revision was quite fundamental.

 

From customer to customer, Change Management policy varies quite a lot from what I can discern of the Track-It! customers I come into contact with. Some organisations are quite stringent, others less so. Such a policy along with factors such as time and resource both in terms of people and equipment, will inform the decision on how much testing of this release you can carry before upgrading your live Track-It! installation. It may be that the defects addressed in version 11.2 are rather forcing your hand to get this done sooner rather than later. However, the nature of the way features such as the email monitor work now means that how it interacts with your environment is a key facet. If you are able to build a test server, you can download or make a copy of your Track-It! license file and use that to test. If problems arise in your test environment, support will be able to assist without it affecting your service to your user base. You can keep live on the previous version until all issues are resolved in test.

 

So, even disregarding all of the above, you decide to run the upgrade with the minimal preparation. Well, early in the upgrade, we see this;

11.2 upgrade.jpg

… another opportunity to avail ourselves of information identifying what may be needed when the upgrade completes.

 

The first link is fairly standard stuff. When each version is released and Remote Control is updated, we provide updated installers for each of the mods customers can opt to use rather than the default setting, where an icon is displayed in the System Tray and users are asked to confirm that a technician can take control on connection to their PC. There are mods for you to change these options;

 

 

Option 1 - Hide the Remote icon, and keep the "Confirm Access" prompt (unless the computer is locked or a user is not currently logged on)

Option 2 - Hide the Remote icon, and disable the "Confirm Access" prompt.

Option 3 - Show the Remote icon, and disable the "Confirm Access" prompt (unless the computer is locked or a user is not currently logged on).

The next article linked to provides key information to most customers about changes to the email monitor. In previous versions, there was only a minority that used a POP connection in their email monitor configuration. Most used either the MAPI or Exchange options. Both of these required a client to be installed on the Track-It! server, whether that was the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 or a full Outlook or Groupwise client.

If I was to discuss the most common configuration I come across, a customer would be using an in-house Exchange server and have set the email monitor to use the MAPI setting before upgrade to 11.2. I envisage that, in this scenario, customers would use the IMAP option and configure that from within the Administration Console on completion of the upgrade wizard. In this scenario, The Microsoft Exchange IMAP 4 service must be running on the Exchange server.

That about wraps up another Track-It! Pulse for this month. I will return soon with the next in my series covering Track-it! reports. The next Pulse blogspot will be out in around a month. In the meantime, I would be interested to hear about your experiences of Track-It! 11.2.