TeamViewer/KACE Integration

I found looking over several different forums and sites how to get the TeamViewer integration for simple click and remote in KACE.  I put together a process how I got it to fully automate the obtaining of the TeamViewer ID and simple two click connection to remote the remote device.  I hope you find this helpful.

TeamViewer/KACE integration

This is done with a few different tasks to do in KACE.  These are the steps I completed after creating and deployed our own custom Host MSI package of TeamViewer with our settings and password built in, however the support technician needs to have the full TeamViewer support client installed.

First step is to add a custom field in KACE to identify the TeamViewer Support ID.


Task 1 (This is for creating custom inventory field for TeamViewer 11 Support ID)

  • Under Inventory>Software, choose New under the Choose Action drop down menu.

  • Give it a name TEAMVIEWERID           

  • Version is 11.x

  • Publisher is TeamViewer

  • Add notes (Captures ID for TeamViewer 11)

  • Select all Windows based operating systems under Supported Operating Systems

  • The Custom Inventory Rule is asking what to look for.  In this case, we are look for the TeamViewer ID in the registry.  Copy and paste:

    • RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TeamViewer, ClientID, NUMBER)

  • Click Save. (After systems begin to inventory, they will populate this field if they have TeamViewer 11 Installed.  This is located under Software>Custom Inventory Fields in Device Inventory.



    Task 2 (This is for adding the TeamViewer Device Actions to the inventory fields)

  • Under Settings>General Settings scroll down to the bottom until you see Device Actions

  • Click Add New Action

  • In the name box, type TeamViewer Remote

  • In the Action drop down, choose Custom Action

  • In the Command Line box, copy and paste this line:

    • "%ProgramFiles%\\TeamViewer\\TeamViewer.exe" -i KACE_CUSTOM_INVENTORY_TEAMVIEWERID --Password P@ssw0rd

  • Click Save and Restart Services (This will cause the K1000 to go offline for a few seconds)



    NOTE: This is only designed to work with Internet Explorer (If you wish to use Firefox or Chrome, you will need to add the IE Tab plugin)

You will also need to have the full TeamViewer Program installed onto your PC.  Several settings need to be applied to the IE Settings for it to work.  These settings can be applied via GPO or manually directly on the support PC.  Here are the security settings that must be done in IE for this to work.:

Tools Internet Options | Security Select Trusted Sites Icon | Sites Button
    -Add the KACE server to the zone (should be in the top box if you have KACE open actively)
    -Require Server Identification (Uncheck)
    -Click Close Click on Custom Level button ActiveX Controls  Plugins
    -Allow previously unused ActiveX controls Enable
    -Allow scriptlets > Enable
    -Automatic Prompting for ActiveX controls > Enable
    -Download unsigned ActiveX controls Enable
    -Initialize & script ActiveX controls not marked safe for scripting > Enable
    -Run ActiveX controls and plugins > Enable Click OK to close Security Settings Window Click OK to close Internet Options Window

View comments (1)

K1000 Inventory Location vs Asset Location

If you are struggling with the new Location and Assigned users fields within Inventory, or if you are looking at implementing Asset Management Best Practice (BSI 55000/ ISO 55001) and Barcode scanning then you may find this blog helpful.

So with the introduction of the Barcode scanning capability in the Go App, came a number of table changes that reflect within the Inventory records of Devices.

The functionality of the Barcode scanner GoApp, for those of you who have not yet investigated, basically distils down to the following:

- Scan a single Asset (Device)
- Update a single Asset (Device)
- Associate a barcode with an Asset (Device)
- Associate a location with an Asset (Device)
- Associate a User with an Asset (Device)

When associating an Asset with a user or a location that data is now shown within the summary area of the inventory record, as well as within the Asset record.

y6DzxL.jpeg                                 lD3qae.jpeg

What KACE have also helpfully done, is rewrite the standard Asset and Inventory listing views, so that they now default to the new values. Therefore if you have been associating a location with an Asset, using the traditional method of adding the Asset Location field into the Asset type, then it may look as if all your data has disappeared.


You can find your Asset Location data by clicking the blue cog and selecting the correct fields to display, but you would need to do that for every tech that logs on ......

As a workaround for customers using the Asset Location as their location fields and in particular our own BarKode customers, we have created the following workaround that we hope will be of help.

If we refer to the location shown in Inventory as the "Inventory Location" and
if we refer to the location shown in the Asset as the "Asset Location" the instructions below will allow customers using primarily the Asset Location for their location value, to duplicate the value into the Inventory location, so that the two locations synchronise. 

The benefit of this is that regardless of what location value you then select on an asset list or inventory list view, it should be the one set by your Asset Management best practice.

To do this we will use a Service desk ticket rule.

First we need to make sure that at least one device in our inventory has an Asset location value set as well as an Inventory Location value set. Choose any asset and within the Asset record add a value to both data fields, but make them different values, then save the asset record.

Next we must establish which data field within our Device Asset contains the Asset Location ID. To find this out, run the following SQL as a report on your K1000.

  ASSET Inner Join

The resulting report will look like the following image


Note the highlighted line shows a location value (column 7) and an Asset ID of 5 (column 9) i.e. a Device; on any line showing these details we can see the Asset Data field reference, in this case 10041. Make a note of the number shown on your report.

Next we will create the ticket rule that will take the Asset Location Value and Synchronise the ID into the Inventory location field

In your K1000 go to ServiceDesk > Configuration - Rules and create a new (SQL) ticket rule in any available queue.

Give the rule a suitable name and description.

Paste the following SQL code into the Select Statement box:

  ASSET Inner Join

Then update the number in yellow with the number taken from your earlier report.

Now paste the following text into the update statement box:


And again update the number highlighted in yellow with the same value taken from your earlier report.

Save the ticket rule and use the Run Now button to run the rule.

If there are no errors, the rule should have at least updated a single record, the asset you set the values for earlier in this process.

If you now check that asset record, the Asset Location value should be replicated into the Inventory Location field.

Now set your ticket rule to run every day or every hour and make sure the rule is enabled before saving.

If you would like to know more about Asset management Best Practice, how to use your KACE box to become ISO 55001 compliant or how you can cut your losses and save money by using our feature rich BarKode scanning product then feel free to contact us:

View comments (2)

Operation Cannot be Performed – Object Deleted Error in Outlook 2016 | 2013

Owing to its commendable features and capabilities, Microsoft Outlook has received an enormous crowd of users. Outlook provides the freedom to work in both offline and online mode in an easy manner whenever they require. However, there is a possibility that while accessing Outlook users has to face some issues. One of the most common error is “The operation cannot be performed because the object has been deleted”  

The error is often caused by the corruption in Outlook PST file. The file can be corrupted due to various reasons like:
  • 2GB size limitation in older Outlook versions
  • Sudden cut in power supply
  • Hardware-related issues 
Issue Faced by the Users
Whenever users face this issue in Outlook, they get this kind of error message as shown below i.e."The operation cannot be performed because the object has been deleted"


Method 1: Re-create Outlook Account
Follow these very simple steps to re-create Outlook account:
1. Firstly, open Outlook and then, delete IMAP email account 
2. Then, create a new account 
3. This will create a new PST file
4. Finally, download all your emails back from the IMAP server

Method 2: Repair PST File
To repair corrupted PST file use Microsoft Outlook Inbox Repair Tool (also known as scanpst.exe). Follow these steps to proceed further:
1. Firstly, close Outlook and open your PST file in scanpst.exe and then, run the scan
2. If you have Outlook 2010 scanpst.exe it is located in below location: 
C:\Program Files\Microsoft Office\Office14

3. By default Outlook, PST files are located in
C:\Users\ <username>\AppData\Local\Microsoft\Outlook

4. Alternatively, the location of PST file can be found in Outlook Account Settings
Outlook >> File >> Info >> Account Setting >> Data Files

Sometimes users of Outlook have to face some challenges due to corrupted or damaged PST files. Some errors that occur all of a sudden can obstruct the work of users. So, in the above section, we have discussed an error “The operation cannot be performed because the object has been deleted” along with the methods to resolve it easily.
Be the first to comment

Best practices for preparing an application packaging environment

Before any packaging starts, a packaging environment should be prepared. As a rule, a packaging environment should be virtual, and the reasons for this will be covered later in this article. Conditionally, we can differ the packaging environments by several criteria:

By a packaging technology. A packaging technology defines a set of tools, which should be preinstalled on a packaging client. The following tools are recommended but MSI packaging process is not limited to them, and it possible to use other software:



PACE Suite

  • MSI Generator
  • MSI Editor
  • Docu Generator
A powerful toolset for almost all packaging needs (MSI/App-V/ThinApp)

Sysinternals Suite (the most required tools)

  • PsExec
  • ProcMon
  • ProcExp


PsExec – command line tool that we will use to start cmd.exe console under built-in system account. This account is usually used in most deployment systems to deploy software.

Process Monitor (procmon.exe) – this tool can be used for analysis of application/installation behavior and it helps to understand the causes of certain application/installer activities.

Process Explorer (procexp.exe) – this tool shows the process tree and helps to understand what child processes are created by an application or an installer.

Some double panel file manager (optional)

  • Total Commander
  • Far Manager
  • Unreal Commander
  • Double Commander
  • Free Commander
  • Etc.

A convenient tool to work with the files during packaging. It has numerous plugins, which can help to work with ftp, archives, editors etc. This is absolutely not a required tool – the choice depends on the demands of each engineer.

By purpose. The two main purposes are:

Packaging. For this purpose, we need to have as clean OS as possible, with a minimal number of preinstalled software. For these needs, it is better to use the OS right after it has been installed, and a minimal set of packaging tools. This is necessary in order to minimize the impact of a third-party software on the packaging process, as well as to identify the possible software dependencies and correctly handle them.

Testing. This environment should be as similar to the end-user environment as possible. It would be better to use a virtual image utilized in the end-user environment where the package will be installed.

After the packaging environment is prepared, the packaging process can start.

The first thing a packaging engineer should do before the actual packaging is the Incoming Check. During this process, the following investigation should be conducted:

  1. Check package sources availability. The discovery document and application sources should be available and copied to the packaging workstation. The best practices for creating discovery documentation will be covered in a separate blog article.
  2. All instructions in the discovery document should be clear and reproducible with given software sources.
  3. After successful installation, an application should also be successfully launched and all required configuration should be available.
  4. Installation should be evaluated in accordance with the estimation complexity matrix. This document is a kind of a questionnaire that contains the objective characteristics of the future package, such as the number of files, registry entries, the size of the installed application, controlled services or drivers, dependencies, etc. Alternatively, you can use PACE Suite where complexity estimation report is one of the features. According to the estimation, we can determine approximate complexity of the packaging and based on the estimated complexity, we can roughly determine the amount of time that will be needed to spend on packaging. This assessment can be used to forecast and assess the packaging costs.
  5. If during one of these stages there are some ambiguities, a packaging engineer should immediately clarify the issues with the software owner or the customer. This is very important to clarify all issues as early as possible to save time on bug fixing in the future.

When everything is clear, a packaging engineer can proceed to the actual packaging.

In case you are looking for an application packaging and virtualization tool, we invite to you to learn more about PACE Suite: Apart from complexity estimation, it offers advanced MSI editing capabilities, package validation and testing, and numerous other application packaging features.

About the author

Dmitry Puzanov is an experienced IT specialist, a leader of Infopulse application packaging team and an analyst in the packaging sphere with 10+ years of experience in support engineering, networking, software installation development, and IT management.

Be the first to comment

Types of Packages: Virtual Packages – Microsoft Application Virtualization (App-V)

In the previous article, we discussed the various types of non-virtual packages and gave some practical advice for application packaging. Now, we will move on to virtual packages and begin with Microsoft App-V as one of the most widely used virtualization formats.

The process of creating virtual packages is called virtualization. Application virtualization is the technique of separating the application configuration layer from the operating system. It enables applications to run on clients – desktops, servers, and laptops – without actually being installed on them and to be administered from a central location. With applications installed on a centralized server using this method, users of application virtualization solutions can access that software from whatever particular operating system their computers are running.

App-V is a widespread application virtualization and streaming solution from Microsoft. App-V enables you to make applications available to the end users without installing the applications directly on end user computers. App-V transforms applications into centrally managed services that are never installed and don't conflict with other applications. This is made possible through a process known as “sequencing the application”, which enables each application to run in its own self-contained virtual environment on the client computer. The sequenced applications are isolated from each other. This eliminates application conflicts, but the applications can still interact with the client computer

App-V is a part of the Microsoft Desktop Optimization Pack (MDOP) and requires additional licensing. The licensing is user-based and is either acquired by licensing Microsoft Desktop Optimization Pack (MDOP) for use on client operating systems or as part of the Microsoft Remote Desktop Server Client Access License for use on Remote Desktop Servers. MDOP is a suite of technologies available as a subscription for Software Assurance customers. There also exists a licensing model that exists for hosting (cloud services) providers.

App-V 5.1 Environment Overview

Microsoft Application Virtualization (App-V) 5.1 enables administrators to deploy, update, and support applications as services in real time, on an as-needed basis. Individual applications are transformed from locally installed products into centrally managed services and are available wherever you need, without the need to pre-configure computers or to change operating system settings.

App-V consists of the following elements:

·       App-V Management Server that provides a central location for managing the App-V infrastructure, which delivers virtual applications to both the App-V Desktop Client and the Remote Desktop Services (formerly Terminal Services) Client. The App-V Management Server uses Microsoft SQL Server® for its data store, where one or more App-V Management Servers can share a single SQL Server data store. In addition, it authenticates requests and provides security, metering, monitoring, and data gathering. Active Directory and supporting tools are used to manage users and applications. The server has a management site that lets you configure the App-V infrastructure from any computer: you can add and remove applications, manipulate shortcuts, assign access permissions to users and groups, and create connection groups. Finally, the App-V Management Server enables communication between the App-V Web Management Console and the SQL Server data store. These components can all be installed on a single server computer, or on one or more separate computers, depending on the required system architecture.

·       App-V Publishing Server provides App-V Clients with entitled applications for the specific user and hosts the virtual application package for streaming.

·       App-V Desktop Client retrieves virtual applications and publishes the applications to the clients. It also automatically sets up and manages virtual environments at runtime on Windows endpoints, as well as stores user-specific virtual application settings, such as registry and file changes, in each user's profile.

·       App-V Remote Desktop Services (RDS) Client enables Remote Desktop Session Host servers to use the capabilities of the App-V Desktop Client for shared desktop sessions.

·       App-V Sequencer is a wizard-based tool that you use to transform traditional applications into virtual applications. The Sequencer produces the application “package,” which consists of:

a)      a sequenced application (APP-V) file;

b)     a Windows Installer file (MSI) that can be deployed to clients configured for stand-alone operation;

c)      Several XML files including Report.XML, PackageName_DeploymentConfig.XML, and PackageName_UserConfig.XML. The UserConfig and DeploymentConfig XML files are used to configure custom changes to the default behavior of the package.

What’s inside an App-V package

To create a package as it has been mentioned in the previous paragraph, you will need a sequencing software. The sequencing process creates virtualized application with the following files:

.appv – the primary package file, which contains the captured assets and state information from the sequencing process. The architecture of the package file, publishing information, and registry are in a tokenized form that can be reapplied to a machine and to a specific user upon delivery.

.msi – executable deployment wrapper that you can use to deploy .appv files manually or by using a third-party deployment platform.

_DeploymentConfig.XML – a file used to customize the default publishing parameters for all applications in a package that is deployed globally to all users on machines that are running the App-V client.

_UserConfig.XML – a file used to customize the publishing parameters for all applications in a package that is a deployed to a specific user on a computer that is running the App-V client.

Report.xml – a summary of messages generated during the sequencing process, including omitted drivers, files, and registry locations.

.CAB (Optional) – a package accelerator file used to automatically rebuild a previously sequenced virtual application package.

.appvt (Optional) – a sequencer template file used to retain commonly reused Sequencer settings.             

App-V for Windows 10

From the Windows 10 1607 build, the App-V for Windows 10 is built into the Enterprise edition of the OS. However, is still requires downloading, installing, enabling the server- and client-side components. Luckily, if you are already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. In other cases, the App-V server components can be obtained with the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO. The App-V client is already included in the Windows 10 1607 and must be enabled with either Group Policy or PowerShell – here’s a step-by-step instruction. Finally, you will require a sequencer – you can use one that Microsoft offers or choose from a wide variety of sequencing software.

If you need help upgrading to App-V for Windows 10, we suggest using this guide from Microsoft. Also, App-V gradually approaches end of mainstream support (more information on this here) so now is a good time to plan the future migration.

Our own application packaging & virtualization tool PACE Suite allows you to sequence and edit App-V 5.x packages, as well as offers full support of App-V for Windows 10. Learn more about PACE Suite:

Be the first to comment
Showing 6 - 10 of 3078 results