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;
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;
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;
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.
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;
… indications are that this is not possible. There is not an option listed for a required TLS encrypted connectection (1).
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.
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 firstname.lastname@example.org
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!
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 http://downloads.numarasoftware.com/support/11erd/Track-It!_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;
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;
… 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.
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.
So that’s pretty much it – here’s my report “Work Orders opened before 1st Nov 2013 by Technician;
Count of ID
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!
I will be back with part two sometime in the next month to look at the tools that will help us to create more complex reports in Crystal Reports. In the meantime, if you have any questions or any particular requirements for a report you would like to create yourself, please leave a comment.
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;
… 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.
Track-It! 11.2 was released in late November and is now available. Thank you to all of our loyal Track-It! Beta testers for once again kicking the tires and helping to get the product ready. You can learn more about the product by visiting the What's New area of the Track-It! site.
Some highlights of the new release are:
Manage SLAs and end user expectations with Stop the Clock.
Keep accurate record of time spent on tasks with the Work Order Timer
Track time to first response with the First Response SLA
Create integrations with other software/systems with the Track-It! Web Service
Detect installed anti-virus products, versions and whether definitions are up to date
Obtain regular PC inventory information from users who work remotely using disconnected audits
IMAP and Exchange Web Service support added for e-mail monitoring
Further refine which emails Track-It! will accept with the new White-list
We work hard to deliver things that our customers ask for and we hope you like this release of Track-It!
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;
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;
… 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.
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;
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.
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;
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.
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.
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.
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
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.
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
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.
I am very excited to announce that the new release of our award winning Track-It! Help Desk and Asset Management software, Track-It! 11.1 has been released and is now available for download.
This release was focused on more functionality in Track-It! Web, Track-It! Mobile and some key usability enhancements that should make customers very happy. Here are a few highlights from the release.
Track-It! Technician Client for Windows and Track-It! Web updates
Rich Text Solutions was added to the Windows and Web clients, allowing Track-It! technicians to generate solutions containing rich content, custom fonts, font colors and embedded in-line images. Work order resolutions now support rich text formatting as well.
Conditional Required fields are now available to allow administrators to required certain fields to be populated when work orders are closed.
Track-It! Web and Mobile updates
Two Track-It! modules, Training and Reporting were added to Track-It! Web. Technicians can now manage their end-users training course schedules and history from the web as well as have access to print and preview any of the Track-It! reports that are available in the system.
The Track-It! Web and Track-It! Mobile interfaces now support work order templates for commonly occurring work orders.
There are many other usability enhancements that were also included in the release. For more information or to download a trial, please visit the what's new section of the Track-It! page here.
We recently had a few new partners asking about what type of resources it takes to setup and manage Track-It! I realized that it had been a little while since I had blogged about this type of thing so I figured it was time for a refresher.
Some time back, I started talking about this Zero to Help Desk in 60 minutes concept with prospects and partners and the idea was picked up by marketing shortly after. The reason this has resonated so well with customers and prospects is because as we all know, most IT shops are overworked and understaffed and the idea of saving time and money while also implementing a tool that helps save time and money, is a very welcome thing. Track-It! is extremely easy to install, configure and maintain and takes most users less than an hour to setup and configure so the tag line stuck. After that, it only takes a small part of one persons time to manage the system from then on. Many of our competitors have products that require a dedicated resource or multiple resources. That is not true for Track-It! The product is specifically designed to be easy to manage and use.
Ease of Installation
Lets talk about installation first. The full Track-It! installer is the same one that you can download right now from BMC.com and try out in a demo mode. The demo is the full product with some limitations on the number of users that can log in, the number of devices that can be scanned and with a 30 day expiration. Track-It! includes the free Microsoft SQL Server 2008 Express edition for customers that don't want to buy or cannot afford to buy the full blown MS SQL server product. SQL Server express works fine for most Track-It! implementations. The entire installation process takes about 15 minutes to install all the components. If you installed the product in demo mode and wish to then move to production later on, the process is very simple. When you purchase a license for the Track-It! product, a license file will be e-mailed to you. Once that license file is copied into the Track-It! server directory, the product becomes a live version. NO reinstall required.
Accessing the application
Help Desk Technicians can use the Windows client, Web client or Mobile client and Self Service end users can access the self service web portal. All 3 interfaces are included with the base product. Administration functions must be performed with the Windows client but it is installed on the Track-It! Server by default during the main installation.
Basic configuration is simple. You can manually enter your users and create accounts or import them from your LDAP or Active Directory server. Once the users are in the system, a few other items like Priority levels, Work Order Types, Departments and Locations should be configured and then you are ready to start managing your IT Assets and using the Help Desk. This process takes a very short amount of time and usually takes most users longer to decide exactly which work order types and priorities they want to create than it does to actually create them in the system.
The entire system in a basic setup takes less than an hour to install and configure. If you have a complex environment where you want to split the IIS server apart from the database and Track-It! servers, things can take slightly longer but not much. If you are scared of systems that require consulting services and full time management, then Track-It! is what you are looking for.
Support and Online Community
If you have any questions or need pointers while installing or using Track-It!, there are two great places to get help.
Track-It! 11 was just released 2 weeks ago and you may have noticed a
change to some of the ideas posted on the Idea tab here in the BMC Track-It!
Several of those ideas had their status changed from Active to Delivered as they were included with the new Track-It! 11 release.
This is a very exciting time to be a product manager or a customer of BMC Track-It! For the first time there is true visibility into features that customers are requesting, which features customers like and don't like, which features are likely to go into the next release and ultimately which features are actually delivered.
Thank you to everyone who submitted an idea, commented on an idea and/or voted on an idea.
You are all helping to shape the product for the benefit of all users.
Every so often I hear questions from customers and prospects about deploying a Track-It! Server in a test environment. Some of our customers have processes in place that require any changes, updates, patches, etc, be tested in a staging environment before being rolled into production. The question we usually get is whether it is ok to install a 2nd copy of Track-It! into this staging environment even though they only own 1 copy of the product.
The answer here is pretty simple. Yes.
If you own a copy of Track-It!, you are licensed for one production installation of the product and if your production processes call for a test staging environment, you are permitted to install a 2nd copy of Track-It! into that test environment as well. As long as the test installation is really for testing, then you have nothing to worry about.