Update Asset Field Based on Other Fields with Ticket Rule

This post will attempt to show how to auto-populate and update an asset field based on concatenating other asset fields. The fields/columns will need to change to match the tables and columns from your database. Use the Report Wizard to create a report for the specific Asset Type and select all fields. Then Edit SQL to get the actual field/column names for your environment. 

Note: I use Monitor as an example here but this can be accomplished with any Asset Type.

1. Create Asset Type “Monitor"

2. Add Asset Fields Manufacturer, Type, Size, Description to “Monitor”


3. Create a Monitor Asset with Manufacturer = Dell, Type = LED, Size = 24

4. Go to Service Desk > Configuration > Rules

5. Create a new Rule “Asset Rule – Update Monitor Description”

6. Enter Select SQL:


, ASSET_DATA_14.FIELD_10005 AS Manufacturer

, ASSET_DATA_14.FIELD_10006 AS Type

, ASSET_DATA_14.FIELD_10007 AS Size

, CONCAT(LEFT(ASSET_DATA_14.FIELD_10005,1), "-", ASSET_DATA_14.FIELD_10006, "-", ASSET_DATA_14.FIELD_10007) as Description 





7. Enter Update SQL:



8. Set Frequency to desired amount (15 minutes in my example) then Save

When changing some of the fields, after 15 minutes (or a manual rule run) the Description will update with the new info.

Be the first to comment

Report: Software Catalog Compliance (All ORGs)

I was asked for a report that would gather Software Compliance across all ORG's. If created at the System level of an ORG-enabled K1000, this will show the Software licenses owned vs installed broken down by ORG. This assumes the licenses and software catalog associations have already been created in each of the ORG's. Create a new SQL Report in the System ORG with the following details:

Title: Software Catalog Compliance (All ORGs)

Category: Compliance





















NOTE: Be sure to check “All Organizations”

Be the first to comment

2015 Dell KACE Backyard Boot Kamp Schedule Announced!

Dell KACE Backyard Boot Kamp - Classrooms in a city near you!

You saw it here first! We're extremely pleased to announce the 2015 Backyard Boot Kamp schedule! We'll be in multiple cities from March until October in North America.

LocationDatesRegistration Link
Santa Clara, CAMarch 2-6
Austin, TXMarch 16-20
Herndon, VAApril 20-24
Toronto, ONMay 4-8
Vancouver, BCMay 11-15
Chicago, ILMay 18-21
Austin, TXJune 1-5
Aliso Veijo, CAJune 15-20
Toronto, ONJuly 6-10
Vancouver, BCJuly 13-17
New York, NYAugust 3-7
Chicago, ILAugust 10-14
Santa Clara, CAOctober 5-9
Austin, TXOctober 12-16

We want you to learn all the latest tricks and tips for using your Dell KACE Appliance. That’s why we’re bringing our popular training directly to you. Register today for multiple days of instructor-led training that will refresh or enhance your skill set and empower you to save even more time and money with your Dell KACE Appliances.

Don’t miss the fun and educational event that will enable you to not only extract maximum benefit from your Dell KACE Appliance, but also gain advice for using Dell KACE in your environment — directly from the experts. You'll also get to know your fellow users in the local Dell KACE community, and in many cases- attendees benefit from minimal travel expenses and time away from the office.

How are the classes structured?

  • Dell KACE Boot Kamp training includes 3 days of K1000 Systems Management Appliance training, and/or 1 day of K2000 Systems Deployment Appliance training . You’ll gain step-by-step guidance to help you with initial agent provisioning, software management, patch management, user roles, inventory, scripted installations, native imaging, and deep-dives into many other features and concepts.
  • Each classroom is limited to 15 attendees per instructor, so you'll have plenty of opportunity to interact, ask questions, discuss ideas, and more. Each instructor is a Dell KACE expert and they have more experience than you can imagine. Your classroom equipment will have virtual appliances just for you to explore and learn with- no shared equipment.
  • Each day begins at 9:00 am (earlier if all attendees are present), and we conclude around 4:00 pm. This might seem like a short day, but we pack a lot into the day! This also minimizes impact with attendees who commute.
  • Registration includes classroom and materials only. No meals will be provided. Drinks and light snacks will be available during the day. Meal times are scheduled longer than 1 hour to accommodate off-campus meals, however many locations offer on-site cafes. Travel and accommodations are not provided by, or arranged by Dell.

Should I attend?
We think so, but here's some information that might help you decide. Boot Kamps are designed specifically for new users, or those desiring a skills refresh. They are not intended for advanced KACE users, nor should they be considered a replacement for JumpStart training that was purchased with your appliance. Boot Kamps are usually best attended by:

  • New team members that may not have attended JumpStart
  • Team members seeking overall product knowledge
  • Team members who haven't used the appliance in some time
  • Team members that prefer to practice and learn in a non-production environment
  • Those preparing to implement new features of the appliances that were previously not in use.
  • Anyone seeking to gain new knowledge and experience with the K1000 and K2000 appliances.
  • Anyone wanting to sharpen their skills to gain the most from Dell World User Forum 2015

Seats are extremely limited for these events, so register now!

Be the first to comment

App-V 5 and Drivers

In a hurry and just want the script, click here.

If you're here, then you must have a driver and App-V conundrum. Perhaps you have sequenced scanner software but you still need to find a delivery method to get the driver injected? Maybe it’s a label maker, a noise measurement tool, a 3d printer, timing equipment - the list goes on.


You’re in the right place. I've written a script which will work with App-V to inject and remove the drivers as part of the DeploymentConfig. It will also handle drivers where the certificate is not known in the Trusted Root Certification Authorities.


The script was written with the following in mind.

·         Scalable.

·         Reusable.

·         Low administrative overhead.



A Quick Guide On Drivers

First, some knowledge on drivers, driver signing and how it all works together. After much research I've found drivers fall into three categories.

·         Signed and certificate chain is recognised in the Trusted Root Certification Authorities.
These will silently install with DPIsnt.

·         Signed, but certificate chain is not recognised by Trusted Root Certification Authorities.
These will throw a prompt when you try to install them with DPIsnt.

·         Unsigned or signed but has been modified, the certificate may or may not be recognised by the Trusted Root Certification Authorities.
These will throw an ugly warning which you cannot get around easily.


You can work around the second bullet point, but to work around the third bullet point is either impossible or a lot of work depending on your desired outcome.  If this is your problem, then read "Sign your unsigned drivers - Damn It" for more information, as this script will not help.

At this point I recommend reading the sections below from "Practical Windows Code and Driver Signing" - it will give you a decent insight into driver signing.

·         Anatomy of a signature

·         Signature requirements, specifically the section TRCA requirements for it to look good.

·         Installing a driver package

·         Driver package installation in Windows Vista and 7

Important information: The .cat file contains a cryptographic hash of all the files, if you modify any of the files it will break the hash. eg, editing of the .inf file.

All About The Manage-Drivers.ps1 Script

The script can be found here on my GitHub Gist.

The script can perform the following functions.

  • Inject drivers.

  • Inject drivers and hide Programs and Features entry.

  • Import certificate into Trust Publishers store pre driver injection.

  • Remove drivers.

  • Remove certificate from Trust Publishers store post driver removal.

  • All the above with Logging.

There are a number inbuilt script variables that can be changed as per requirements, they are as follows.

$LogFile, change this to your desired log location. Default is %Windows%\Temp

$DPInst32, name of DPInst 32bit executable.

$DPInst64, name of DPIsnt 64bit executable.

$WithThisErrorCode, set to 0 to gracefully exit or set to 1 to fatally exit.


It’s important to note that if you plan to use $WithThisErrorCode to fatally exit, it needs to be used in conjunction with the DeploymentConfig xml attribute <Wait RollbackOnError="true" Timeout="30"/>.


The script has two mandatory parameters which are as follows.

-DriverSource a token, UNC or relative path to driver source.

-LogName the name for the log file.


The script has two optional parameters which are as follows.

-HideARP, this switch will not add entry to Programs and Features.

-Remove, this switch will remove the driver package from the Driver Store.

If your certificate chain is not recognised by Trusted Root Certification Authorities then you need to add a certificate to the Trusted Publishers certificate store. This functionality has been built into the script, just prefix the certificate with “TrustedPublishers” and store it at the base directory with the drivers.

To make use of the script, the DeploymentConfig will need to be edited. The script is launched via PowerShell in ExecutionPolicy ByPass mode, passing the required arguments to the script to locate the drivers and name the log file.

To inject drivers, where the drivers are located on the VFS.

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "..\Root\VFS\ProgramFilesX86\DriverFolder" -LogName "Example.log"</Arguments>


To inject drivers, where the drivers are located in a zip archive.

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "" -LogName "Example.log"</Arguments>


To inject drivers and hide the Program and Features entry.

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "" -LogName "Example.log" -HideARP</Arguments>

To remove a driver, where the drivers are located on the VFS.

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "..\Root\VFS\ProgramFilesX86\DriverFolder" -LogName "Example.log" -Remove</Arguments>


To remove drivers, where the drivers are located in a zip archive.

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "" -LogName "Example.log" -Remove</Arguments>



Step By Step Guide

Best to do the steps below in a virtual environment as it’s easy to step back to a clean snapshot for testing.

Remember, always do a standard vendor install to ensure the software/drivers work as required.

I'm assuming intelligence on the reader’s part to fill in the gaps.

  1. On a clean machine inject the drivers manually using DPInst.
    lbu1wt.jpeg NQPMwN.jpeg

    If you get prompted “Would you like to install this device software?” then check the “Always trust software from…” check-box and click install.


    Open the DPIsnt log to double check it installed ok. Returning with code 0x100 means DPInst injected one driver, 0x200 means two drivers injected and so on.

  2. If you received the “Would you like to install this device software?” prompt, it means the certificate chain was not recognised in the Trusted Root Certification Authorities. Hopefully you checked the box “Always trust software from…” as we now need to export the certificate from the certificate store.

    In a nutshell you need to start MMC -> Certificates -> This Computer -> Trusted Publishers -> export the certificate.

    If you’re a bit unsure then have a look at the two links below for more detailed information, no point reinventing the wheel.

  3. After the above steps one and two you should have similar files below ready for the App-V package, to either add during sequencing or afterwards during finalisation of the App-V package. 

  4. Time to sequence your application and add the files to the VFS or scripts collateral folder depending on your desired implementation.

    You should have something similar below after you have sequenced the application.

    1. VFS implementation.

    2. Scripts collateral implementation.

  5. It’s now time to edit the DeplymentConfig.xml, the implementation you chose in step four will determine the PowerShell arguments you need to pass to the script.
VFS implementation.
<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "[{ProgramFilesX86}]\Contoso Scanner\SL1000 Digital Film Scanner" -LogName "ContosoScanner.log"</Arguments>
<Wait RollbackOnError="true" Timeout="30"/>

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "[{ProgramFilesX86}]\Contoso Scanner\SL1000 Digital Film Scanner" -LogName "ContosoScanner.log" -Remove</Arguments>
<Wait RollbackOnError="false" Timeout="60"/>

Scripts collateral implementation.
<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "" -LogName "ContosoScanner.log"</Arguments>
<Wait RollbackOnError="true" Timeout="30"/>

<Arguments>-ExecutionPolicy ByPass -File Manage-Driver.ps1 -DriverSource "" -LogName "ContosoScanner.log" -Remove</Arguments>
<Wait RollbackOnError="false" Timeout="60"/>
      6. Test your App-V package, and don’t forget to enable package scripts.



Edit Log

29/01/2015: Initial release.

Be the first to comment

Job Opportunity - Project Manager

To Apply: visit our website



Vital, a Toshiba Medical Systems Group Company, is a market leader in advanced visualization software solutions for physicians and healthcare specialists. The company's sophisticated technology gives radiologists, cardiologists, oncologists and other medical specialists productivity and communications tools that can be accessed throughout the enterprise and via the Web at anytime and anywhere for patient care and treatment planning.  Vitrea®software has been installed at more than 5,000 hospitals in over 80 countries. Established in 1988 and headquartered in Minneapolis, Vital Images also has offices in Europe and Asia. For more information, visit



The Research and Development (R&D) Project Manager is responsible for all aspects of product development, security, and customer support related projects .  The R&D Project Manager will lead cross-functional teams through the entire project lifecycle process (Project Initiation, Planning, Executing, Monitoring and Controlling and Closing) in order to achieve R&D software development objectives.  The R&D Project Manager serves as the single point of contact for all matters related to the project and is expected to interface with all areas of the business that are impacted by the project and its deliverables.  The R&D Project Manager works closely with Product Management, Customer Support, Development, and Verification and Validation teams to ensure project deliverables are completed on time, within budget while adhering to strict quality and regulatory guidelines. 



In this position, you will perform several roles including but not limited to: 


Ensuring adherence to worldwide quality, regulatory, and security standards.

·         Manage the production and delivery of all required quality and regulatory deliverables, and ensure project team is ready to respond to FDA and BSI audits with little or no advance warning.

·         Establish project plans and execute on the plans for hardening, securing, and obtaining DIACAP clearance for Vital’s products.

·         Responsible for technical communication between government agencies and Vital Images.


Ensuring project deliverables meet customer expectations.

·         Ensure project deliverables meet quality standards defined by Verification and Validation and other Quality Systems Processes.

·         Lead Sustaining Engineering Projects to address customer reported software defects and feature requests.

·         Lead defect trend analysis activities to determine the underlying root causes for customer reported software defects and provide defect trend reports to Sr. Management.


Effectively manage multiple projects.

·         Lead project startup and initiation activities that identify the project team, project goals, scope, and success criteria.

·         Develop and execute comprehensive project plans that ensure projects meet established quality, schedule and budget targets.

·         Collect development and test effort estimates and resource availability.

·         Develop and manage effective project communication plans intended to keep key business stakeholders abreast of project status, risks and opportunities.

·         Drive project execution tasks and activities against established baseline plans in order to provide accurate and timely project status reports and forecasts relative to project schedule and budget.

·         Actively manage and control project scope utilizing company change control procedures.

·         Continually monitor identified project risks, identify new potential risks, and influence teams to complete corrective actions to mitigate risks as needed.

·         Prepare project related documentation.  Documentation could include formal plans, service update reports, 510(k) submissions, DIACAP submissions, etc.

·         Ensure projects close on time and that relevant project information and training is provided to downstream teams.  For example, coach, mentor, and educate organization on security and hardening requirements.

·         Lead project retrospectives, capture key lessons learned, make recommendations to R&D Management relative to process improvement, and implement accepted process improvement initiatives.

·         Capture and analyze key project performance indicators specifically Defect fix rate, Duration Estimates, Effort estimates vs. Actual Effort, Actual Project Budget and Costs vs. Forecasts

·         Administer and maintain effective project sites utilizing Microsoft SharePoint and Atlassian Confluence.



Reports to:  Senior Manager Research and Development



·         Bachelor’s degree in either a Technology or Business focused discipline

·         Strong understanding of Project Management methodologies

·         2+ years of experience with Agile software development methodologies.

·         4+ years of Project Management experience, delivering commercial software



·         Certified Scrum Professional or Program Management Professional (PgMP)

·         Certified Information Systems Security Professional (CISSP)

·         Focus on quality and detail.

·         Excellent organizational skills.

·         Ability to adapt to changing priorities.

·         Excellent verbal and written communication skills.

·         Visible leadership skills and comfortable leading cross-functional projects.

·         Experience with DoD DIACAP certification (STIGs, OS/Network level hardening).

·         Demonstrated initiative and commitment to ongoing process improvement.

·         Proficient with Microsoft SharePoint Server, Microsoft Project, and Microsoft Excel.



·         Proficient with Atlassian Jira and Confluence.

·         Experience with FDA regulatory and ISO standard procedures.

·         Experience with the development and/or implementation of enterprise software solutions.

·         Experience with Windows Server 2008/2012 Security Standards.

·         Experience with Windows SQL Server 2012/2014 Security Standards.

·         Experience with Healthcare informatics domain knowledge including: DICOM, HL7, HIS, RIS, PACS, EMR.



Must be able to lift up to 50 lbs. No unusual physical requirements



Regular business hours are Monday through Friday, 9:00 a.m. to 6:00 p.m. Hours can vary and expand as dictated by project demands.

Vital is an Equal Opportunity/Affirmative Action Employer of Minorities, Females, Individuals with Disabilities, and Protected Veterans.

To Apply: visit our website

Be the first to comment
Showing 1 - 5 of 2660 results