Tag Archives: Kloser look


K2000 Kloser Look: How driver management works

Drivers are stored on the Samba shares within your K2000 Deployment Appliance. The K2000 exposes 2 driver-related shares:

  • Drivers
  • Drivers_Postinstall

What are these folders for? Each serves a different purpose, but in a nutshell- Drivers is for drivers used during OS install for either starting the installation, or providing drivers TO the installer; Drivers_Postinstall is used after the installation of a Scripted Install, in order to enable

DRIVERS folder: This folder contains a folder for every OS supported, and two folders for KBE (one for the KBE 32-bit and another for the KBE 64-bit).

What’s the difference in KBE folders/drivers and the rest? Well, KBE is Windows PE, and therefore it needs some minimal drivers in order to install Windows.
You may need to include the drivers for storage and network, but not much more. We only recommend including the bare minimum drivers needed for the KBE to be able to access the disks of the device that it is booting from, and the network driver to communicate to the K2000. Do not add to these folders drivers for video, sound or other devices.

Which driver’s platform I need to add for KBE? KBE (KACE boot environment) is a special version of Windows PE based on either Windows 7 or 8, so you need to download drivers for the PE version your boot environment is based upon. The following table clarifies the drivers you will need:

Using PE Version Drivers
WAIK for Windows 7 WinPE 3.0 Use drivers for Windows 7
ADK for Windows 8 WinPE 4.0 Use drivers for Windows 8
ADK for Windows 8.1 WinPE 5.0 Use drivers for Windows 8.1

IMPORTANT Due to the fact that there are only 2 folders for KBE drivers, one for the 32-bit and the other for the 64-bit version, and not a couple of folder for every type of WinPE/WAIK, remember that only one type of drivers at time can be in that folder. Do not mix Windows 7, Windows 8 and Windows 8.1 drivers in these folders.

Drivers_Postinstall folder: Under this folder you need to add all the drivers that the machine will need after the scripted install is finished (Its ‘normal life’) like storage, network, audio, video etc etc… If your machine is a Dell machine the Driver Feed functionality does most of the job for you; Library -> Driver Feed allows us to search for the device and OS to and download the driver packages. If your machine is not a Dell machine, or you need to add additional drivers, you will need to add them under this directory.

See more at: http://www.itninja.com/blog/view/a-syncretic-overview-on-management-works-in-k2000-3-5-3-6

Posted in New Posts, Tech Talk | Tagged , , , , | Leave a comment

K1000 Kloser Look: Uninstalling Applications

Have you been struggling with trying to figure out how to uninstall unwanted applications from your users’ workstations? You know the K1000 can do it – multiple ways, in fact – but which way works best? There are so many unwanted applications – and so many versions! Where to begin?

Managed Installs and Scripting both make it easy to remove unwanted applications. Use the Configuration Policy in the Scripting engine; or use a Managed Install configured manually so you can provide the uninstall command line and switch on the option for uninstalling. ITNinja.com is a great resource for finding uninstall procedures, commands, and tips. Here’s an example of a script that might be useful for defining a text string for the name of a product, then removing all versions of it: http://www.itninja.com/question/google-earth-uninstall

Of course, then you’ve got to ensure they won’t just re-install it all over again, right? Maybe we’ll cover that next month…

Do you want to learn more about application uninstalls? You’re in luck! We’ve got an upcoming KKE on that very topic: Application Uninstalls – Thursday, March 20th!

Posted in New Posts, Tech Talk | Tagged , , , , | Leave a comment

K2000 Kloser Look: Applying User States Using an External Share

If you’ve ever captured User States (profiles) with the K2000 and wondered how to deploy them from an external Windows share without having to re-image that machine, we have the FAQ for you!

You’ll need windows AIK, a windows share on your external device (like the K1000), and some Profiles. Here are the basic concepts and tasks you’ll wak through. See the article on Kace.com for the full details.

  1. Create a folder named usmt like: \\server\share\usmt
  2. Create a folder named users like above
  3. Create a folder named user_backups  like above (Optional, see article for details)
  4. Copy the c:\program files\windows aik\tools\amd64  folder to the usmt folder on your shared drive
  5. Copy the c:\program files\windows aik\tools\x86  folder to the usmt folder on your shared drive
  6. Download the user state file (.mig) from your K2 and place it in the users folder on your shared drive.
  7. Make sure you change the default name USMT.mig to something meaningful, like the user’s name: Jerry_Anderson.MIG.
  8. Now the MIG file could be used manually, via scripting, or other means.

Click here for a link to the article (FAQ# 114327) on the Kace Support site.

Posted in New Posts, Tech Talk | Tagged , , , | Leave a comment

K1000 Kloser Look: New Operators!

One of the great new features in version 5.5 was added into the Reporting and Smart Label modules. Several new Operators were added: For example: is within next, is not within next, is within last, is not within last, before now, after now, etc.

These new options allow you to view data with a date and compare it to the current date for reporting purposes or machine label purposes. Once you’ve selected the proper Operator you can now select your value. You enter a value in the box and the dropdown box gives you the options: minutes, hours, days, weeks, months and years. So you can filter information based upon the last 60; minutes, hours days etc…

This allows you to configure reports to look at items within a specific time in the past, or events that are scheduled to happen within a specific time in the future. This makes life easier when creating helpdesk reports to view “Time Closed within the last XX days”. This feature allows you to filter tickets and many other items with a date stamp easier. While the feature isn’t available for every search criteria, it is there for many of the more commonly selected items in reporting to make life easier!

Posted in New Posts, Tech Talk | Tagged , , | Leave a comment

K2000 Kloser Look: Maintaining System KUIDs

How to Prevent Duplicate Computer Assets from Appearing on your K1000 Appliance After Imaging- Finding duplicate computers on your K1000 due to system imaging and host name changes? This article will help you from preventing this from occurring.

What is a KUID? How does this affect machines checking in?

When the Dell KACE agent is installed on a client machine, one of the first things that happens is the creation of a KACE Unique Identifier or a KUID. This is a hash based on the hostname of the machine at the time the agent software was installed. This is how the K1000 can keep all the inventory information coming into it and associate it to the correct machines. It’s how we keep inventory straight between all machines checking in.

When a machine checks into the K1000 for the very first time, this KUID is checked to see if this machine has ever been seen before on the appliance. If the answer is no, the K1000 will create a new entry for the machine in its computer table in Inventory and also in the Asset Module.

If we re-image that machine and must give a different hostname than what it had before, it can look like a brand new machine to the K1000 appliance. It will create a new entry for it in the database, asset module and it will also consume another seat license.

For example – let’s assume a single Dell Latitude E6430 Laptop that belonged to John. We must re-image that machine, change its hostname and give it to a new hire named Mary who will start in 2 weeks. Our company uses employee names as its PC naming convention.

Hostname: John / KUID: ABC123 – John leaves the company and we must reimage his existing system and rename it to Mary as she starts work on Monday as a new hire. We must re-image the machine and reinstall the Dell/KACE agent, among other software packages and configurations.

Hostname: Mary / KUID: DEF345 – Even though it’s the same physical machine, because the hostname changed, it looks to the K1000 like a brand new machine that’s never checked in before. The K1000 will create new entries for it in its database and also consume another license. It will look like the laptop named John has stopped checking in. It will appear as MIA or Missing In Action, while it is currently checking in as a laptop called Mary.

How can we prevent this?

By using a pre-install task to capture this KUID prior to imaging and using a post-install task to put it back after the new image is laid back down on the hard disk. These tasks are built into the K2000 already. You simply need to ensure they exist as part of your imaging. These tasks will work for both Scripted Installations and System Images. There is a solution for Windows as well as support Mac OSes, too!

Click here for a link to the article (FAQ# 111532) on the KACE Support site.


Posted in New Posts, Tech Talk | Tagged , , , | Leave a comment