Skip navigation


12 Posts authored by: Toby Draper Employee
Share This:

The Track-It! Support Team are asked a lot of questions about upgrading the product to the latest version - Track-It! 11.4 Service Pack 1.

We recommend all customers are up to date with this release to benefit from;


  • Improved performance
  • Increased security
  • Being better positioned for future upgrades.


We have provided this post in the hope that it will answer many of your questions before they arise and point you in the right direction to the information and resources that will assist you in this process. Please find links to these resources below. We have produced a short video to guide you on how to use this information.



As discussed in the video, our Docs Portal provides the information you will need to help you in the planning stages of your upgrade.


Home - Track-It! 11.4 - BMC Documentation


Once there, you will need to log in (see video below for help with that). The Release Notes include information on existing and resolved defects in the current version and also new functionality and enhancements. The System Requirements are there so you can decide whether you use approved Operating Systems, SQL Database versions and browsers to allow you to work with the Track-It! product or whether you need to purchase or upgrade any hardware or software



Access our Knowledge Base via Support Central. It is constantly being updated to ensure you have the information necessary to resolve many of the issues TI customers face.

There are lots of articles which support the upgrade process. For example, when you have identified your current version and are unsure about the steps you need to take to upgrade to the latest release, this article will guide you through the process;


How to upgrade from Track-It! 9 or 10.x to Track-It! 11.4 Service Pack 1


... and this article provides a detailed summary of the final step - the upgrade to version 11.4 Service Pack 1


How to upgrade to Track-It! 11.4


If you are unable to access these Knowledge Articles, this video explains how easy it is to register at Support Central - BMC Software and to search the Knowledge Base for articles and to log a case via our portal if you do not find what you are looking for;



Occasionally, you may have an urgent issue where it is necessary to call us to save time. In these scenarios, our Contact Centre will log a case for you at the appropriate priority level and a Track-It! technician will be in touch.  But for the majority of issues that we see in the Support team, it is much more efficient for you to engage with us via our Portal.

There is a Knowledge Base article associated with the majority of the questions we are asked by our customers and, as mentioned, if you do not find what you are looking for, you can click a link to the Self Service Portal and log a case. This will allow you to tell us about the the issue in your own words and provide any screenshots and logs you think will help us resolve the issue.

A member of our team will then contact you.


Here are our Severity definitions on which we base our response times;


BMC Support Severity Level Definitions - BMC Software


... but most of the time, you can count on us to respond to you much more quickly.

Share This:

Since part 1 and part 2 of this series of blogs, I had been building up, reading and preparing for a post where I discuss the steps of building a report from scratch. However, in conversation with quite a few customers who wish to create their own reports, we often advise that they use one of the standard reports from the Track-It! Reports module.


Here’s a basic but useful report that contains both a graph to highlight activity that may need to be reviewed and detail to drill down to individual issues, Overdue Work Orders by Technician.

rep pg1.jpg

rep pg2.jpg

We can edit the report in Crystal. In Teach yourself Track-It!... Reports. Part 2 Crystal Reports and other useful tools I described where to obtain a licensed copy of Crystal Reports from your support profile, if you are a supported Track-It! customer.

In Track-It!, in the Reports module, with a report I wish to edit select, I can click Export Report from the Tasks list in the top left of the screen in the Technician Client and save to the desktop.


When we open the report in Crystal, this is what we see…


… perhaps a little daunting. Let’s go through what we are presented with here in some detail.


On the left is the Design tab. This is where we do the initial formatting and place objects in the sections you want them to appear in. You can configure how particular data is sorted, grouped and how totals are presented.

This is handled quite cleanly as the data is represented in the Design view, rather than having the data appear itself. It also means that while you are dragging groups around or calculating totals, the data is not actively being retrieved so you are not drawing on resources on the database server or the wider network when doing this.


By default, a report is divided into five areas. In the report we are working with, there are some sub sections in some of the sections – you can see, for example, that the Report Header in Overdue Work Orders by Technician has a Report Header divided into Report Header a, b and c. But as a simple summary of these sections you can refer to this;


Report Header

Usually the title or any information printed at the top of the first page. Track-it! reports use this section to return if no records are found when run (Report Header b) and to place the bar chart (Report Header c)

Page Header

Information repeated at the top of each page is placed in the Page Header. This section type is not in use in our example.


The main body of the report

Report Footer

This appears once at the end of the report. Used, for example, for “grand totals”.

Page Footer

Usually page numbers. Any other information that needs to be repeated at the foot of each page.


There are some additional sections used for groupings, summaries and subtotals, as follows;


Group Header

Printed once at the beginning of the group, use it for a title or for charts made of data held in the group

Group Footer

                Appears once at the end of the group. Can be used for charts and cross tabs.


Crystal Reports contains various “Expert” dialogue boxes to assist with organising various aspects of the report in one place. So in order to see a preview of the structure of the sections, click Tools in the menu bar and select “Section Expert”…

section expert.jpg

Another “Expert” view to look at, which leads in to my next post, click Database from the menu bar and select “Database Expert”. This is where we can add tables to our amended report via their data source (an ODBC connection to the Track-It! database). We can also see, in the Links tab, a visualisation of the matching of records of one table with the corresponding records of another table.

database expert links view.jpg

… and this is a nice link back to the tool I discussed in the last post in this series, the Entity Relationship Diagram of the Track-It! database. This gives us a similar visual representation of the relationship between the tables so that we are able to produce reports, such as this one showing data from “Table A” organised by data held in a “Table B” that has a direct correlation with “Table A” (in this case the WorkOrderStatusId, the numeric value given to Statuses in a Work Order).


So now we’ve seen some aspects of editing an existing report in Crystal Reports, next time I’ll develop this further by going through editing an existing report as a basis for a new report.

Share This:

A slightly belated Happy Easter to you! I hope you had as enjoyable break as I did!!


This month, I wanted to take the opportunity to hopefully bring to prominence some of the useful material that has been published in the Track-It! Product page that may take some scrolling to eventually find as more and more members of the Track-It! community post new discussions and ideas. So here’s a chance for you to bookmark some of these posts if you missed them first time round.


Customers with a maintenance contract will have access to our Knowledge Base at;


… although much has been posted here in the community with more of an emphasis on “how to” rather than publishing resolutions and work arounds to known issues. There is content I have used when investigating faults with customers, just to ensure I am being thorough, leaving no stone unturned and I have often sent links to some of these posts to customers who have logged a call with our Technical Support team. All the material I’d like to highlight today was published by members of the Support team or by Product Management.


If there is anything posted by a customer/end user that people use as a point of reference to help them with their everyday running of Track-It!, please do link to it in the comments section below this blog. Also, if anybody working with Track-It! has a particular approach or “aide-memoire” that they think would be useful to others, please do post a discussion. Even if it is something that has been covered in BMC Communities before, it still has value since we are all coming from our own unique perspectives.



I vaguely knew what this meant from my ceaseless addiction to American movies and TV. But I had to use Wikipedia to get a proper definition;


101 (term), The first course in a subject taught at a college or university in Australia, Canada, South Africa, or the United States. By extension, "Topic 101" is used generally to indicate the basics of any subject. Used this way, it is always pronounced "one-oh-one".

My colleague Keith Scarborough posted a series of "101s" on the Track-It! Inventory module. They are a really useful source of reference on the subject and while covering off the basics, they go some way to help develop a more advanced understanding of this module.

Track-It! Inventory 101

Track-It! Inventory 101 – Discovery

Track-It! Inventory 101 - Workstation Manager

Track-It! Inventory 101 - Initiating an Audit

Track-It! Inventory 101 - Audit and Merge

In a similar vein, last September I blogged about triggering audits externally from Track-It!, utilising Group Policies in Active Directory so that a user’s PC is audited each time they log in;

Next up, Keith and another colleague, Chris McLane have written some really useful notes and tips on the subject of incoming and outgoing email…

This is by Chris. I found it useful to refer to in a support call the other day, not for intended purpose but just as a reminder about how Track-It! appends replies to Work order notifications to the relevant Work Order when the Email Conversation feature is used;

E-mail replies cause new work orders to be created even though "RE:" rules are in place

This post serves as my reminder that;The "Use E-mail Monitor Address for e-mail" option should ONLY be enabled in environments where it is necessary to have multiple help desk e-mail addresses that are forwarded to the main E-mail Monitor inbox. Even then, the option should only be enabled if it is absolutely necessary to have notification e-mails appear to come from the address to which e-mails were originally sent."

Notification e-mails from Track-It! appear to be sent from a user rather than the address configured in the Administration Console

As for this setting – I didn’t know about this when I set out to draft this article. I usually advise customers that the Track-It! Event policies cover off most notification requirements and, on balance probably negate the need for an “auto-reply” to mails to the monitor. But now I have seen this setting in the config file, I can think of one or two recent conversations where this change to the config file will be of use;
How to disable the auto-response e-mail sent to the user after successfully appending additional information

Keith has made contributions about database and server management. This piece discusses the warnings generated by Track-It!;

Track-It! Database 101: Index Health Unsatisfactory warning

… this summarises some of the back-end configuration of the SQL database;Track-It! Database 101:

Transaction Logs and Recovery Model

… and here he devised a more user friendly way of moving a Track-It! installation to new hardware;

How to Move or Copy Track-It!; the newer, simpler method

Benny Morrison worked with the Track-It! Product for a number of years. I have enjoyed his whimsical blogs about Track-It! that he wrote before moving on to our Footprints Product team;

What is Track-It!?


Track-It! is our baby...

… as well as the more conceptual, high level articles he’s written about managing Help Desks in general and how Track-It! may fit into your plans

Getting organized with Track-It! - The top 3 myths about organizing your Help Desk


Cris Coffey is still very much involved in the Product Management of Track-It! and in driving this product page in BMC Communities. You can get a sense of his history with the product here;

15 years. How things have changed.

… and I wanted to emphasise this post Cris made to give you a sense of how important this community to the future evolution of Track-It! and how your Ideas are actively being selected to be integrated in future releases;

First Track-It! release after Ideas module


Finally, more from me. The latest version of Track-It! released is v11.2. If you are planning to upgrade to this version any time soon, you should consider the following;

The Pulse: Track-It! 11.2 Cool Stuff

The Pulse - Track-It! 11.2... Countdown to upgrade

The Pulse - Track-It! 11.x - Office 365 and SMTP and more general Notification troubleshooting tips

Share This:

This month I wanted to talk about Work Order Resolutions. In Track-It! 11.1, we introduced the ability to;



  • Create detailed, highly useful solutions using in line graphics, bullets colored fonts and more with new

Rich Text Solutions feature


  • Attaching new rich text solutions or formatting an individual Work Order resolution with rich text is now

easy with the Rich Text Resolution field


I’ve had numerous conversations with customers who upgraded from version 11 to version 11.2, missing that we’d added this feature. This has impacted these customers, whose Technicians have been used to entering Plain Text resolutions into a Work Order



… in previous versions, historic resolutions could be seen in their entirety if they only used 2-3 lines of text.


After v11.1, a Technician will only see a preview of the resolution entered and needs to click the “folder” icon to see the entire entry.




… we need to click the Edit icon (the folder in the top right of the resolution) to see the entire entry;

edit note.jpg

The new functionality is built in with the intent of giving us an end to end repository of solutions, available to both Technicians and end users in the Self Service front end. In this, we are striving to assist Track-It! customers in helping their users to help themselves. Let’s walk through how that might look…


I created a solution from the text from my previous blog post;


I just copied the article in its entirety, since we are pasting into a Rich Text editor, and all of the formatting and images were pasted from the clipboard.


Now, someone needs to configure Stop The Clock in Track-It!, the are able to search for that test in the Self Service front end;

self service solutions.jpg

Alternatively, that user logs a Work Order rather than searching Solutions in the Self Service portal, the Technician is able to resolve the Work Order and bring the article into the Resolution as the one they brought to the attention of the Requestor in the Resolution tab;

insert solution.jpg

So this is my interpretation of how we can use the Rich Text formatting to add value to our end users and to start the exercise of populating the Solutions with quality, easy to follow information. This enables us to encourage our end users to draw on this resource and query it for information before they log a call with the Service Desk.


In other news…


When I first joined the Track-It! team back in 2008, we had recently release Track-It! version 8.1. At the time, we were assisting quite a lot of customer with the transition from Track-It! versions 6 & 7 to the new release. Part of the challenge was with the changes to the look and feel of the product, which has now remained largely the same through the course of major releases since that point. As each year progress, it surprises me that we still have an amount of customers looking to upgrade from v7 to something more recent. With this in mind, Kevin Dort asked me to issue a reminder.


In Track-It! 7, the attachment repository folders were different. When a server backup takes place, these files are not included (\Track-It! Server\WOAttach). So we recommend to follow the steps to move the attachments into the default Track-It! 8 – 11 location, in the \Track-It! Services\FileStorageData\Repositories folders.


How to move the Track-It! attachments to another location
Article ID: TIA03046

Share This:

This month I wanted to elucidate clearly about configuring Work Order Event Notifications when email in your organisation is hosted in Office 365. I’ll also touch on more general notification troubleshooting advice which is valid if you use a mail solution in The Cloud or host your own.


Work Order Event Notifications and Office 365

The conversation we have in support with customers whose email solution is in the cloud is usually along the lines of “Office 365 requires TLS encryption but Track-It! only supports SSL”. I found a white paper, here, which confirms this;


“The use of TLS/SSL establishes a highly secure client-to-server connection to help provide data confidentiality and integrity between the desktop and the data center. Customers can configure TLS between Office 365 and external servers for both inbound and outbound email. This feature is enabled by default.”


If we go to the outbound email configuration, in Track-It! 11.2 this is in;


Tools > Administration Console > Configuration > Administration > E-mail Configuration > Outgoing E-mail Configuration


… indications are that this is not possible. There is not an option listed for a required TLS encrypted connectection (1).

outgoing e-mail configuration.jpg


This appears to be borne out when using the “Send Test E-mail” (2)and the resulting test email fails to be sent to it’s recipient.


Let’s try and clear some of this up.


Authenticate on your SMTP host but do not check the box for SSL and apply the changes. If you choose to click the Send Test E-mail and it fails, do not be disheartened. This is because this button is not using the configuration you have entered in this screen. It is checking whether it is possible to send a message via the SMTP host you have configured but it is doing that using the email settings associated with the Windows account you are logged into the computer with.


So in this scenario, please use this guideline to test your connection to your Office 365 SMTP host… once the above is setup and you have ensured that Track-It! is set to send these messages by its schedule - Tools > Administration Console > Configuration > Help Desk >  Work Order Events > Automated Schedule, then create a test Work Order and send a mail to your designated test recipient via the “Email Requestor” button.

email requestor.jpg

We usually find that notifications are sent successfully using the configuration and test outlined above.

Nb – If you have Track-it! configured to “Email Requestor” via your Outlook client, you will need to test outgoing email by matching a Work Order to the Event Policies.


If you continue to struggle with this setup and wish to engage with your local Support team its really useful for us to have a copy of these logs if you have encountered errors while testing;


More General Notification Troubleshooting via the Track-It! Database

While I am on the subject of logs and Notifications, I thought I would quickly share some bits and pieces about where the Notifications register on the Track-It! database. I have learned to rely on these tables when troubleshooting more challenging notification issues.


Open SQL Server Management Studio and connect to the instance where the Track-It! database resides. Expand it in the Object Explorer and then expand the Tables. Scroll down to the “N’s”.


There are three tables I will summarise in this post, NotificationMessage, NotificationStatus and NotificationError.


NotificationMessage contains a line for every notification email that was sent from Track-It!. For the purposes of today’s post, we are concerned with the NotificationStatusId column.



This is the “Automatically generated primary key of the NotificationStatus table”. Essentially, depending on whether the message is in the process of being sent, gets sent successfully, or fails, the NotificationStatus table holds the various statuses that are entered to this column. It is useful to cross reference NotificationMessage with NotificationStatus;



… so if you see a NotificationStatusID of 4 in your NotificationMessage table, you can see that this means “SendFailure” and that will prompt you to look at the NotificationError table;



Obviously, the NotificationMessageId column correlates to the message in the NotificationMessage table. It is easier to insert the cursor into that row’s ErrorMessage entry and select all its contents, copy and paste into Notepad or similar, rather than trying to read the error in SQL Server Management Studio. Here’s some examples;


The requested notification message failed to send. - The SMTP host was not specified.


The requested notification message failed to send. - Mailbox unavailable. The server response was: 5.7.1 Unable to relay for


These errors may match to errors posted to the Service Management log file in C:\Windows\Temp but this method provides an “electronic paper trail” where you can follow through each step of the way for a specific message, rather than scrolling through up to 10 MBs worth of event logging, much of it not relevant to the errors you are looking for.


  Well that’s it for now but I will be posting again quite soon. I wanted to cover Track-It!’s Rich Text editor for Solutions and Resolutions, which some customers are finding irksome. So I will write that up over the next week or so. I just thought it was confusing to have two unrelated topics in this post. I will also be posting Part 3 in the series about Track-It! reports in the coming weeks. I would appreciate any comments to any of my posts, especially if there is anything you would like me to try and explain… I might even be able to coerce a colleague with a bit more specialist knowledge in that particular area to assist us!

Share This:

I recently posted a simple yet powerful means of reporting in Track-It!. The drawback with reports created from extracted data and formatted in Excel is that they are not integrated with the Track-It! application. You could not, for example, automate these reports so that they are sent on a scheduled basis or share these reports via the Reporting Module.


In order to do this with a custom report, it will need to be written in Crystal Report like all of the standard reports that are included in the off-the-peg application. In the coming weeks I intend to start to look at compiling reports using Crystal so by way of preparation, this post summarises the tools we will need to assist us in this task.


Supported Track-It! Enterprise customers are able to download a copy of Crystal Reports from their support profile at;


While visiting the support site, you can go to the Knowledge Base and bookmark!_11.htm – The Track-It! 11 SQL Server Physical Data Model. Here you can see, which tables are used by a particular module and how they are connected to each other as well as definitions of each table and their columns.





Finally, you should already have SQL Server Management Studio installed. This will allow you to run SELECT queries so that you are able to compare and contrast with what is output by any report and keep a check on things as you make progress. Customers with a full version of SQL should have this tool already but those who installed SQL Express when they installed Track-It! will have needed to downloaded a copy for free from Microsoft;


SQL 2005 Express


SQL 2008 Express


… so while you are familiarising yourselves with all of this, I am going to identify some simple reports we can start with in my next post. If anyone has any ideas, please do leave a comment below.

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.

Share This:

In recent months, I have been publishing Pulse articles for Track-It!, reflecting the kinds of queries we are dealing with in support. I will continue to publish those around 20th of each month. Here’s a link to the last one, about new features in Track-It! version 11.2


I also wanted to publish a reasonably regular more personal blog to share tips and tricks to help customers get more from the Track-it! application. Over the next few weeks I wanted to focus on the Reporting module.


We get many customer queries describing requirements for reports that are not included Track-It!

In answering these queries we have quite a well-rehearsed response in the UK support team. These are your options;


  • The data can be extracted from the grid view and then manipulated in an application such as MS Excel
  • Customers can engage with our Professional Services team or a BMC Partner for a quote for some bespoke work done in Crystal Reports
  • Customers with someone knowledgeable in Crystal Reports in-house can design their own reports and import them to the Reporting Module


So I’ll start off in this post by outlining the simple method of extracting data from Track-It! and creating a report in MS Excel. While I describe this as basic, it is actually quite powerful.


For my example, now we are at the start of a new year, Helpdesk managers might wish to know which of their technicians have open Work Orders remaining that were opened, for example, before 1st November 2013.


The first step for this kind of report is to query and filter the Grid View in the appropriate module (in this case Helpdesk) so that we can extract the data required to create our report. So as a starting point, I have set the Current View to the System View named “Open Work Orders”.


I have highlighted the Current View button at the top of the screen and the bar beneath the grid which displays a summary of the data selection. I can then filter my data further, in this case I want to select Work Orders logged before 1st November 2013. I click on the drop down arrow in the Date Entered column header and select “custom” from the drop down.



I am now looking at all issues entered before 1st November 2013. When I create my simple report, I will be only using the data in the ID column for my count with an Assigned Technician on each Row. So in this instance, those are the only columns I really need to export but it is unnecessary to shed those from the view before export. I can just right click somewhere in the grid, select “Export grid Contents…” and from the Export dialogue I can “Save as type” the .xls format to  edit and manipulate in MS Excel. Text would serve just as well for this purpose if I wanted to create or remove some field delimiters when I import into Excel. But I am not doing anything so fancy, so the .xls format is just fine.


I open the file created in Excel and it looks much like the grid I exported it from. I click on the Insert menu and from there, select PivotTable. As mentioned, I want “Assigned Technician” as my Row Labels and ID as my Values. I may need to right click on the object in Values to access the Value Field Settings so that the values are presented as a Count rather than a Sum or Average etc.


value field settings.jpg

So that’s pretty much it – here’s my report “Work Orders opened before 1st Nov 2013 by Technician;



Count of ID


Assigned Technician


Andrew Shain


Brad Halsey


Brian McKenzie


Chris McLane


Chuck Slaughter


David Thibault




Eric Hazeltine




Jack Dobiash


James Lerch


James test


Jamie Hemond


Jamie Hemond1






Kevin Dort


Larry Remington


patrick reed




Rich Curtin


Rilee Lerch


Rilee Mercier


Terry Hartup




Wendell Olson




Grand Total




Please don’t be too hard on any of my colleagues here – this was created using test data rather than our open live Incidents from customers!

Share This:

The Track-It! Pulse blog is back after a brief interruption in its regular publication schedule. Over the last couple of months, I have been transitioning to being a homeworker. It was important that I was able to get comfortable in my new work environment and be handling incoming Incident tickets without affecting our continuity of service. I hope we succeeded in making the move as smooth as possible, but it did mean my activity in the Community was reduced during the transition. Predictably during that time, the UK support team did see a bit of a spike in incidents reported so it has been both a  busy period as well as an interesting experience.


In terms of activity for the Track-It! product from a support point of view, the big news is Track-It! v11.2 has been released. I thought I would have a play around with the Stop the Clock feature, since I have had numerous conversations with customers requesting this enhancement over the years I have been involved with Track-It!. There are also some other bits and pieces of hints and tips I wanted to share that we have picked up assisting customers upgrading to this version in the last couple of weeks.


Stop the Clock

I have to admit I have not logged a call for this feature since it has been introduced. This makes me very optimistic! So this is the first opportunity I’ve had to have a little play with it.

I went into Tools > Administration Console > Lookup Tables > Help Desk > Work Order Statuses and added a new one “Hold”. Straight away, I can see a check box labeled “This status stops the clock” so I tick this.


Next, into Tools > Administration Console > Lookup Tables > Help Desk >Event Policies, I had pre-configured four Event Policies, high, medium and low as well as the built in default enabled. The high, medium and low policies I had created are all linked to the Priority field, to corresponding Priority names that match my Policy Names. Each have different Due Dates, appropriate to each level of severity (all agreed with my fictional customer) and have different email notification rules, also reflecting how I wish to communicate the progress of the varying severity of Work Order. I edit the policy I have named “high” first.



1. Service Level Agreements will often include an agreed Response Time for Work Orders. We’ve added the Date Responded into the Work Order form and this is where you can set the target time from when the issue is first saved.

2. The actual stop the clock setting and that this only affects Due Date.

So I have stop the clock activated on the three priorities lined to Service Level Agreements via the Event Policy interface.


I created a Work Order and made a couple of changes to it, saving it in an “Open” status each time. On my third save, I used my “Hold” status. Perhaps the end user was unavailable when I went back to them with a question or some hardware was out for a repair with a third party. As soon as I save with me on hold status selected, I am prompted;



… and then for a reason;


… then throughout the time my Work Order is on hold, if it is displayed on-screen, the title bar of includes a reminder, saying “Work Order is on hold. The clock has been stopped” though the Due Date in the Applicable Policies section of the Classification and Schedule tab does display the original Due Date set.


This date/time is recalculated when a “non hold” Status is selected and the Work Order saved. I am prompted to fill the reason comments once more, if I so wish.

Please be aware of your settings in Tools > Administration Console > Configuration > Administration > Operating Hours before embarking on this exercise.


Also, just a reflection from personal experience, I remember in a previous life as a Service Desk Manager in a UK outsourcing organisation, on various contracts we had very specific scenarios for when an issue could be placed on hold. This meant an undue proportion of my time was spent reporting on and reviewing on hold calls to ensure that agents were not abusing a “pending” status so that I was not alerted to any lack of progress of difficult and long standing issues. Now in outsourcing, the company providing the service is under a lot more scrutiny than many internal help desk arrangements, with financial penalties written into contracts for missed targets based on Service Level Agreements. I do understand the demand for the on-hold feature and why we responded to demand developing it. But I would say that I would much prefer to factor in “mean time to close” from previous years’ performance, rather than implementing an on hold status for many scenarios. But as long as the rules around its use are clearly stated both for your Technicians and your Users, and understood by them, hopefully you can implement it without being required to police its use too much.


The E-mail Monitor

With the 11.2 release, I was pleased to see that an email client such as Outlook is now not required for Track-It! to read incoming email and turn them into Work Orders. Most of the customers I speak to have their own Exchange Server set up within their organisation’s domain. In this configuration scenario, I have been suggesting customer use the IMAP setting. You must ensure that the Microsoft Exchange IMAP 4 service is running on the Exchange server to utilise this protocol.

Also, during set-up, you will note in Tools > Administration Console > Configuration > Administration > E-mail Configuration > Incoming E-mail Configuration , there are some options under “Incoming E-mail Settings”;


  • Mark e-mail as read,
  • Delete e-mail from the server
  • Move e-mail to folder


It appears from my first few engagements to assist with this set-up that these are rules to be applied on completion. I have seen a couple of instances where we configure “Mark email as read”, mirroring how Track-It! would process email in the previous “Exchange Server” or “MAPI” configuration, but now it wants to process all of the old, read emails once more when I go to the Automated Schedule dialogue and click now. So just a tip, please housekeep all old messages to the email monitor out of the mailbox you have been using if you intend, as I suspect most customers do, to keep using the same mailbox you’ve always used for your email monitor’s primary mailbox.



There has been a change to the audit components in v11.2 that require a PC to be running .NET 4 if you intend to audit that machine. This dependency has postponed one or two of my customers’ plans to upgrade. For one such customer it was necessary to carry out this little test.


If, for example, a group policy/login script is used to trigger audits, where the audit executable is not called from the Track-It! server, in this kind of configuration;


distributed audit.JPG.jpg


… you could retain the old version of audit.exe (or even older, audit32.exe) with the auditcifg.ini and the asset data generated by these components will still merge into the Inventory. track-I


So that’s it for this month. As hinted at earlier, you can now expect a regular post towards the end of each month. This post is intentionally early due to the forthcoming Christmas break.

I plan to continue the theme of version 11.2 in late January, depending on what activity we see across our support teams. If there is anything you would like me to cover then, or expand upon from this post, please do post a comment.


In the meantime, have a wonderful Christmas!



Share This:

I recently posted some options open to users of the Track-It! Inventory when they want to audit many computers in the environment, rather than doing it on each machine individually. I was keen to follow that up and think about what can we do to troubleshoot. Here’s some bits and pieces I've picked up working with Track-It! users in the UK…



A manual audit



To ensure a machine can be audited at the most basic level



Preferably physically on the PC that needs to be audited, or via a Remote connection



Take a copy of this file from the Track-It! server;


:\Program Files\BMC Software\Track-It!\Track-It! Server\audit.exe


Create a folder named “audit” somewhere on the PC you intend to audit. Save the audit.exe file there.

Run the audit.exe from this location. Because the file that contains all of your settings set in the Administration Console’s audit settings is not present (auditcfg.ini), you will be presented with an audit dialogue which you  click through.



Once this is complete, your “audit” folder will contain a subfolder named “data”. Copy the contents of this folder to;


:\Program Files\BMC Software\Track-It!\Track-It! Server\data


… then run Merge Audit Data from within the Inventory Module of the Technician Client


So hopefully we have established that if we have removed all of the automated, environment influenced aspects of auditing, an audit can take place.

What next?

The Auditing configuration



To see if any information has been logged against recent historical attempts to audit



The Technician Client, logged in as an Administrator in Tools > Administration Console > Configuration > Inventory > Auditing




Click on Queue, then the Queue History tab. If you have a reasonably recent entry where the Status is Audit Failed, click it and then click the button labelled “View Extended Information”. Here’s an example where there was a problem with the Setup Credentials;




Go to Setup Credentials and click Test Login. Nb, this will only test these credentials on the PC you are working on, which might be fine. With errors like the one above, it’s probably just a matter of resetting a password in AD and entering the new password into Setup Credentials.

We might need to do further testing to ensure this admin user is the appropriate for the task at hand.


So what now?

An in depth test of the user set in Setup Credentials



To ensure it has the correct level of access to the machines you are trying to audit



The Track-It Server



Log in to the Track-It! server using the account saved in Setup Credentials.


If the machine has been discovered but not audited before, can you connect remotely to the admin share and create a file? Click;

Start > Run > \\hostname\admin$ (swapping “hostname” for the name of the PC we are troubleshooting).

  • Are you able to create a file and a folder there when browsing from the server?
  • Is there are directory present named TIRemote?

Run registry editor and then click File > Connect Network Registry. Are you able to connect to a machine in your Inventory’s registry?

Run services.msc and right click on the server’s services in the left hand panel. Select Connect to another computer and enter it’s hostname. Can you connect? Can you see the Secondary Login Service ruinning on that machine?

Other things to check while logged in on the server… Early in the audit process, Track-It! goes to DNS to do a reverse lookup to resolve the IP Address of a machine wuth it’s hostname and then verify it. On the server, from the command prompt, type;

ping –a hostname

... after the (hopefully) successful ping by hostname, use the IP address returned in the previous set of results in;

ping –a ip_address

Ensure that both sets of results match. If they don’t, flush the cache in DNS.

Also, ensure that File and Print sharing is enabled on all your PCs and that port 10597 is open and accessible to the Track-It! server.

Next up we’ll look at the various log files Track-It! writes to and see how different auditing issues get logged to the different files. In the meantime, this article on our Knowledge Base gets referred to a lot when we are figuring what's not quite right when auditing;

Share This:



Over the next month or so, I am going to post some bits and pieces focusing on the Auditing functionality in the Track-It! Inventory module. First up, a number of customers identify they need to automatically audit their user’s PC. Track-It! can schedule audits, but there are drawbacks to this, identified below. So what alternative is there?


Scheduled Audits vs Logon Scripts

The audit can be scheduled to automatically run on specific days of the week, a specific day of the month or on a specific date, or a combination of these settings.




However, your user base may not all be logged in at the same time, some may be off site, using a laptop. There are quite a few reasons why a PC might not be available in the environment to be audited at the appointed time that Track-It! is configured to carry out this task.


One alternative to using the schedule set in the Administration Console is to use logon scripts, set up in Active Directory. The benefit of this is that you will no longer be queuing audits blindly for a machine that may or may not be available for auditing. This excerpt is from an article supporting an older version of Track-It! (hence references to Windows 2000) but they are still valid and the support team often shares them with customers who have identified that this solution is the most effective way of updating their Inventory;


To Implement Logon Scripts on a Windows 2000 Server (Active Directory):


  • The logon script itself must be present in the sysvol share (%winroot%\sysvol\sysvol\domainname\scripts) of whatever domain controller the user authenticates on. If you want to implement a logon script and you have replication set up among your domain controllers, save the script in the %winroot%\sysvol\sysvol\domainname\scripts directory on the primary domain controller (PDC) in order to replicate it across the other domain controllers.


  • Open the Group Policy snap-in:
  • Click Start  Run, type mmc in the Open field, and click OK.
  • Click File  Add Remove Snap-in from the Console's main menu.
  • On the Standalone tab, click Add.
  • Select Group Policy from the list, and click Add.
  • Either click Local Computer to edit the local GPO or locate the GPO that you want to edit.
  • Click Finish, and then click OK.


  • In the console tree, select Policy_name Policy/User Configuration/Windows Settings/Scripts (Logon/Logoff).
  • Click Scripts, and then double-click Logon in the right pane.
  • Click Add.
  • Configure any of the following settings that you want to use, and then click OK:

     o   Script Name: Type the path to the script or click Browse to locate the script file in the Netlogon share of the domain controller.

     o   Script Parameters: Type any parameters that you want to use in the same way that you type them on the command line.

     For example, if the script includes the //logo parameter (display banner) and the //i parameter (interactive mode) parameters, type;

//logo //i      


  • In the Logon dialog box, configure any of the following settings that you want to use, and then click OK:
  • Logon Scripts for: This box lists all of the scripts that are currently assigned to the selected Group Policy object. If you assign multiple scripts, the scripts are processed according to the order that you specify. To move a script in the list, select the script, and then click either the Up or Down key.
  • Add: Click Add to specify any additional scripts that you want to use.
  • Edit: Click Edit to modify script information such as the name and parameters.
  • Remove: Click Remove to remove the selected script from the Logon Scripts list.
  • Show Files: Click Show Files to view the script files that are stored in the selected Group Policy object.


Important Notes:

In the Active Directory Users and Computers dialog, it is recommended that you select a group, because it contains multiple users.


Please bear in mind, when logon scripts are triggering the audit, the data will not merge to the Inventory automatically. You will need to set the merge to run on a schedule. Go to Tools > Administration Console > Configuration > Inventory > Merging > Schedule


Set to “Automatically Merge Daily” and set for a time outside of peak use times for the Track-It! application. Merging audit data can have quite an overhead on system performance. So if assets have been audited at logon at various points throughout the day, set the merge to run overnight and you will see updated record in your Inventory grid view the next working day.



We’ll take a look at some hints and tips that are regularly used to troubleshoot the auditing feature.

Share This:

As a member of the Customer Support team, I thought it would be good to take a look at what has been trending over the last three months since we released Track-It! 11.1. I used this data to identify three areas and I would like some share some tips I’ve learned from working closely with our Track-It! user base on each of these.


Self Service

The Self Service portal had a makeover back in Track-It! 10 but there are some things you can do to make it “your own” with regional settings, logos and company branding. These articles in our Knowledge Base provide all you need to know;


Article ID: TIA05444

How to change the currency, date, time, and number format in New Track-It! Web


Article ID: TIA06397

How to add a company logo to the Track-It! 11 Self Service page


Article ID: TIA06383

How to change the company name shown in the welcome message in Track-It! 11 Self Service Web



Often, customers Discover Assets on a schedule in the Network Discovery tool. In theory this is fine but this can present problems, so here’s an approach to avoid them. Issues arise after multiple discoveries have been run without consolidation to the Inventory. We should be running “Manage Discovered Assets” after each discovery. To assist with running your asset discovery successfully, please consider this;



  •        Configure your automated discovery to notify a technician when it has completed in Tools > Administration Console > Configuration > Inventory > Network Discovery > Automated Schedule,
  •         Or navigate to the above configuration dialogue to disable the scheduled Asset Discovery. If you choose to disable it, you can then manually run "Discover Assets Now" when you know that new equipment has been activated in your environment and you wish to add it to your Inventory.


admin discovery.JPG.jpg

Note that the interval between automated discoveries is set to one week (10080 minutes) to give me time to manage the last set of results for discovered assets. This is often set to 1440 (1 day) which I would suggest does not give sufficient time to carry out the task of managing the assets to the Inventory before the next Discovery

Email Monitor

We can troubleshoot most E-mail Monitor issues by analysing logs created on the Track-It! server in;


... (there may be slight variations in that file name in different environments but you will note a file with a similar name and with the extension ".log" as one of the most recently modified in that location if you have been experiencing email monitor issues).


If you edit that file in Notepad, you may be able troubleshoot the issue. Here is a simple example;


2013-08-21T11:21:57.434 | SERVERNAME |  28 | ERROR | PlugInRequestMonitor | Numara.TrackIt.Core.ServiceManagement.ServiceManagementImpl.PlugInRequestMonitor+TIHostExecutor.Run() | Could not execute TIHost.exe.  Reason: Could not log user on: Logon failure: unknown user name or bad password |  |  |


To resolve this, you should log in to the Technician Client on the Track-It! server itself. The Windows account associated with the mailbox Track-It! reads from should be a local admin on the Track-It! server. You should log in with this account to troubleshoot E-mail Monitor.


Once done, please go to Tools > Administration Console > Configuration > Help Desk > E-mail Monitor > Monitor Configuration (in this scenario either Exchange or Mapi is selected in the "E-mail Type" drop-down).


Correct the credentials you are prompted with after clicking the Settings button. You may have to reset the password for the corresponding account in AD and then enter the new password here.


If after analysing the Service Management log file, you are unable to identify the cause of the interruption, please attach this file if you wish to raise a call your local Support Team.

Filter Blog

By date:
By tag: