Tag Archives: K2000

Jul
23
2014

Mile High Backyard Boot Kamp

Oh, how we love Denver! There’s so much to see, so much to do, and so little time. We thought about skipping class and going to explore the city, but we would much rather explore the KACE appliances with you! Registration is open, and we’ve got a few seats remaining for the Denver Backyard Boot Kamp. More details and registration can be found at https://www.regonline.com/KaceDenver14.

We want you to learn all the latest tricks and tips for using your Dell KACE Appliance. We’ll be using K1000 v6.0 and K2000 v3.6 in the classroom, so if you aren’t using them yet, this is the perfect opportunity to get comfortable with them!

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 much more. Visit the event website for the full list of upcoming events and cities. Remember – seats are extremely limited for these training events, so register now for the city or time frame that best suits your needs!


Posted in Featured, New Posts | Tagged , , , , | Leave a comment
Jul
7
2014

K2000 Kloser Look: Disable/Enable UAC

So you have upgraded your K2000 to 3.6 (and if you haven’t, why not?!), initiated a deployment to check out the new Task Engine, and noticed new tasks called “Disable UAC” and “Enable UAC” were added into your installation plan. Perhaps you had wanted UAC disabled in your deployment?  At first glance, these tasks look like they are going to enable UAC. However, the names of these tasks are not giving you the entire story.

First, lets understand why these tasks exist; These tasks were added so that UAC would be disabled when the Task Engine goes to install your Postinstallaion tasks in Windows. This was a common issue when deploying Postinstallation tasks without explicitly disabling UAC, so K2000 v3.6 added it into the deployment process. Since we did not want to disable UAC permanently, the Disable UAC task actually checks the current status of UAC and writes that value to a text file. UAC is then disabled and your Postinstallation tasks are processed.  Once the Postinallation tasks are finished we run the Enable UAC task, which reads the value in the above mentioned file and restores UAC to the previous setting. If UAC was enabled in the deployment, then it will remain enabled. If UAC was disabled in the deployment, it will remain disabled.

Deployments might have UAC enabled by default, such as a basic Scripted Installation. Maybe you want the deployment to have UAC disabled. This can be achieved by directly editing the value contained in the written text file, so when Enable UAC comes back around it will instead leave UAC disabled!  To find out more about the Disable/Enable UAC tasks, check out KB121713.

To find out more about the Task Engine, watch this recent KKE from the archives.

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

Best Practices for Migration from Windows XP – Phase IV: Ongoing Maintenance

It has now been over two months since Microsoft ended support for Windows XP.  If you are still running any PCs on Windows XP, you are leaving yourself open to significant security and functionality concerns.   Nonetheless, Windows XP is still the second most popular operating system globally at around 25%[i].  If you have not started your XP migration project, it is urgent that you start now.

Dell Software has established a four-phase process for successful and timely migration, and ongoing maintenance, of your devices from Windows XP to Windows 7 or 8, and provides the tools to automate and simplify each step:

Phase I – Planning: Inventory, analysis, and rationalization

This is the fourth and last in a series of four blog posts discussing each of these phases.

Phase IV – Support: Ongoing maintenance

Once you have migrated your PCs off of Windows XP, the next phase you have to worry about is continuing support of these PCs in their new OS.  Support of your new Windows environment begins as soon as the first user’s system is migrated from Windows XP. Even though a modern release of Windows is deployed, these systems still need to be tracked, kept up to date, configured to your corporate standards, and secured.  This is necessary for ongoing health and performance of your systems as well as to make sure you are in compliance with applicable regulations and are getting the most from your IT investment.

For example, a number of industry-specific regulatory requirements, such as HIPAA for healthcare and PCI DSS for retail, mandate organizations to keep up to date inventory of their hardware and software and also require that software be kept current with patches and fixes.  Failed audits can lead to the suspension of certifications, fines, and public notification of non-compliance.  In addition, understanding and rationalizing your existing environment can continue to deliver long-term value by improving decision making – when to upgrade versus refresh hardware, deciding on on-premise versus software as a service in buying new software, renewing software license agreements, etc.

Ideally, you want to prepare for ongoing maintenance and support before migrating your systems to their new environment. You should select tools as part of your migration project that will, not only help you migrate off of Windows XP, but will also enable you to efficiently manage the entire lifecycle of your systems in their new OS – from deployment to inventory and asset management to security and support.  With automated tools that continue to track and manage systems, all of the effort that went into understanding and rationalizing the original environment can continue to deliver value in the new environment.

The Dell KACE K1000 Management Appliance can help you greatly with ongoing management and support of your systems in their new OS.  The K1000 makes tracking, updating, securing and managing systems a snap – for Windows, as well as MAC OSX and Linux systems. For IT administrators, the K1000 appliance provides extensive hardware and software inventory, patch management and software distribution, security audit and enforcement, and policy and configuration management functionality.

In addition, K1000 can help you support end users after they migrate.  Users moving from Windows XP to Windows 7 or Windows 8 must learn a new user interface. Participants in a recent Dell survey indicated they underestimated the amount of time needed for end-user training and support after their migrations. To help end users, the K1000 user portal that implements an IT service desk. Users can submit requests through email, through the web portal and on their mobile devices through a free app for iOS and Android devices. In addition, a knowledgebase is also available for self-help.

Complementing the K1000, the K2000 deployment appliance can help you image and deploy new systems and also reimage systems as necessary – change hands due to someone leaving or starting up, fix a problem with the system, etc.

To find out more about how the KACE Appliances can help you with your Windows migration and ongoing maintenance, please see:

A Dell webcast on end of XP support by Microsoft

A joint IDC and Dell KACE webinar on Systems Imaging

A Dell Whitepaper on Windows Migration


[i] www.netmarketshare.com , May 2014 data

Posted in Featured, New Posts | Tagged , , , , , , , | Leave a comment
Jun
10
2014

Dell KACE K2000 Series Deployment Appliance Architecture

Organizations, regardless of size or industry, roll out business applications to the workforce. These applications and their supporting operating systems are regularly updated and managed by limited teams of IT professionals. These same limited teams support a wider range of hardware platforms than ever before. In response to these challenges, some organizations turned to traditional, Desktop and Monitorenterprise software IT deployment and management solutions. However, the cost and complexity of deploying and maintaining these solutions often puts them out of reach. Traditional enterprise software solutions require hardware procurement and configuration, as well as software installation, integration and customization. In fact, they are so complex that most traditional software vendors recommend weeks or months of expensive professional services to deploy their solutions. Additionally, hidden software and hardware prerequisites can drive up the true ownership cost of traditional solutions.

Due to this cost and complexity, many organizations turn to point imaging solutions that offer lower price points at the expense of functionality. For instance, they cannot automate the build-out of reference systems (gold masters), nor do they offer remote provisioning. While point disk imaging tools offer improved efficiency, they do not fully automate deployment or save organizations the time and effort that full systems deployment tools can provide.

The Dell™ KACE™ K2000 Deployment Appliance (K2000) breaks down these cost and complexity barriers and brings affordable, end-to-end systems provisioning to organizations of all sizes by utilizing an appliance-based architecture. Appliances deliver a complete, pre-integrated bundle of operating environment and application software via a dedicated server appliance. They can be plugged into an existing network and immediately begin functioning. Appliance-based architectures eliminate many of the complexities and costs of traditional software solutions such as hardware procurement, and software installation and integration. At the same time, systemsappliances provide exceptional performance, reliability, and control through a purpose built solution that is pre-tuned, hardened and self-healing.

This paper describes how the K2000 appliance-based architecture provides a centralized, network-centric deployment solution that is both extremely robust and highly affordable. Download the Dell KACE K2000 Series Deployment Appliance Architecture whitepaper and learn how the K2000 appliance can help you eliminate many of the complexities and costs of traditional enterprise software solutions.

Posted in Featured, New Posts, Tech Talk | Tagged , , | Leave a comment
Jun
3
2014

Dr. K’s Korner – Customer Q&A

Every month we take questions for Dr. K. and answer the best one in front of the world!

Have a question for Dr. K? Send an e-mail to kketeam@kace.com

Question:

We occasionally do get new computers that are ahead of the KBE curve. The KBE doesn’t have a driver to enable the new computer to work in the KBE environment so we have to resort to manually installation of these machines. How do we bring KBE up-to-date?

Answer:

There may come a time when you need to update your KBE in order to support new hardware. First you need to determine which drivers your KBE is lacking: network or storage. If your KBE is not getting an IP address it is most likely network drivers. If you go to capture an image and do not see the local drives, then you may be missing storage controller drivers. Once you have determined which driver you need you will want to head out to the hardware vendor’s site to download the newest driver. After downloading and extracting out the driver, you may want to test to see if the driver you have downloaded is indeed the driver you need. Follow the instructions in this Knowledge Base article to manually inject the driver into a running KBE

Once you have determined that the driver is proper, you will want to build that driver into a new KBE.

  1. Browse out to the Samba share of your K2000 (\\K2\drivers) and place the extracted driver into either the kbe_windows_x86 or kbe_windows_x64 folder (to support the KBE you are working with).
  2. Once you have added drivers into your K2000 Drivers Share, you will then want to Recache the Drivers Share to make the K2000 aware of your new driver.  This can be done from Library module -> Drivers tab -> Choose Action dropdown -> Recache Drivers. Select Recache All Drivers to catch any other changes you may have made.
  3. Once completed, you are now ready to create your new KBE. We have an excellent Knowledgebase article detailing all of the steps to upload your brand new KBE.
  4. Once completed, test your new KBE to check the driver support.
  5. If everything turns out successful, you may then want to go set that new KBE as your default under General Settings.

Hope that helps!

BONUS Question:

Do we need certain versions of the KBE to support Win 7 as opposed to Win 8/8.1? Can we use one KBE to rule them all?

BONUS Answer

K2000 version 3.6 supports three different versions of the WinPE environment: 3, 4, and 5.  WinPE is a slim version of Windows created for deployment purposes and is used as the core for the K2000 Boot Environment (KBE).  With so many currently supported Windows OSes and PE versions there may be some confusion as to which WinPE you should be using.

These recommendations will allow you to deploy your Windows OSes without running into any OS related errors, but what about an environment that has Windows 7 and Windows 8?  The WinPE 5 environment can deploy Windows 7/8/8.1 System Images without any issues, but will run into an error when attempting to do a Windows 7 Scripted Installation.  This error is harmless and can be clicked through, but does interrupt an otherwise unattended process. Read more about the error here: http://www.kace.com/support/resources/kb/solutiondetail?sol=115333

Thanks for the questions – I’ll get you a prize soon for picking your question!
—Dr. K

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