Blog Posts tagged with K2000

Ask a question

K2000 3.5 is out

Kace K2000 3.5 is out:

https://www.kace.com/en/support/Customer/downloads/K2000-archive

3.5.76460 is the Update for virtual and physical box.

3.5.73831 is the new RSA.

View comments (1)

Backup corrupted, what can be done

As everybody knows, the backup of the K1000 (and K2000 too) consists of two files:

kbox_dbdata.gz which holds the database itself and is simply a zipped dump of the database in one file

kbox_files.tgz which holds all stuff which was uploaded to the box (kbots, MI, Scripts etc) which is a zipped tar-archive, which consists all files unzipped

Both files are needed to restore the box to a older version.

Normally you test the backup to be shure that all is fine.

But what to do, if you have only a corrupted backup?

There are some tools for fixing (if possible) the backup files.

Please be aware: as the backup is corrupted you will never be able to restore all files!

http://filerepair.sourceforge.net/ is freeware, runs for a long time, and is able to repair the tgz, the gz file could be repaired too but I wouldn't bet much money on that.

Got reports http://www.sysinfotools.com/recovery/archive-recovery.html would also help, but never tested it, as it costs money. If the demo is working correctly, may be tested.

http://www.datanumen.com/atr/ will help in full version. In the Demo it only shows if the archive can be repaired.

The best chances you may have if you have a Linux box.

A simple tar xifvz FILE will ignore most errors (usually the EOF error)

Also zcat would work great:

At first you should rename it to .tar.gz

then run zcat kbox_files.tar.gz > kbox.tar If it breaks here, you are _REALLY_ doomed.

untar the kbox.tat using tar xif kbox.tar

If you have results (each way) repack the archive and upload it to the box.

Hopefully you will have most of the files remaining.

View comments (3)

K2000 Deployment Workbench

K2 Advisor

  • An .html overview of your K2000 (version 3.6 and higher) that can identify issues and like to appropriate KB articles.

KBE Manipulator

  • Allows for manipulation of KBE that is uploaded to your K2000, including assigning static IP, adding ADSI, ODBC, DCCTK, Command | Configure, .Net4, Powershell, adding custom DOS commands, or uploading custom .wim/.iso's.

Sysprep Creator Wizard

  • Walks user through creating an unattend file for Windows 7/8/10

Driver Feed Builder

  • Harvest or extract executible drivers and upload to the K2000.

Get/Set ComputerName

  • Allows saving of computername from workstations or apply new names.
Kace Streaming WIM Toolkit
  • Toolkit that allows deployment of K2000 captured wims to be streamed
Default Deploy
  • Script that allows deployment of a default image/scripted install to machines
Export Wi-Fi Profiles
  • Script that will export profiles and .zip them up with a script to deploy them with a K1 or K2
Driver Feed Advisor
  • Script to show the driver feed path of a workstation, via the K1000 or K2000
Upgrading to Windows 10
  • Tasks that provide a solution to upgrading a workstation to Windows 10 using the K2000
USMT 10 loadstate fails when deploying Windows 7
  • A script that will copy the files necessary into USMT so that a Windows 7 deployment is successful with loadstate

Set Autologon Count

  • Change the autologon count in an unattend file of a sysprepped image

Task Timeout Modification Script

  • Modify the task timeout period of each task on version 3.6 or higher.
Using the K2000 UltraVNC during Windows Post Install Tasks - See more at: http://www.itninja.com/blog/view/using-the-k2000-ultravnc-during-windows-post-install-tasks#sthash.ZdF4KBXW.dpuf

Using the K2000 UltraVNC during Windows Post Install Tasks

  • Be able to remote into Windows during Windows PO Tasks
Dismiss Windows 7 Scripted Install Error in WinPE4 and WinPE5
  • Pre Installation task that will dismiss the errors when deploying a Windows 7 SI with WinPE4/5

Disable the DPInst Reboot for Windows 7 or higher Images that use driverfeed

  • disables the reboot for dpinst since it is not needed for Windows 7 or higher
Using the K2000 UltraVNC during Windows Post Install Tasks - See more at: http://www.itninja.com/blog/view/using-the-k2000-ultravnc-during-windows-post-install-tasks#sthash.ZdF4KBXW.dpuf

Kace Appliance Package Export Report

  • Creates an .html report of exported packages.

Linux Deployment Toolkit for 3.5 SP1 and 3.6

  • Allows for the deployment of linux kickstart

Automatically Naming a Macintosh Computer using the K2000

  • A script that behaves similarly to wsname for Windows.

Maintain KUID of a Macintosh System using the K2000.

  • capture the kuid of a Macintosh system and put it back to the workstation as a midlevel task.

Screen Resolution Changer

  • A script to either maintain screen resolution from each workstation, or assign a new one.
View comments (1)

Linux Deployment Toolkit for 3.5sp1 and 3.6

As a limited release, we are posting this patch for the K2000, 3.5 sp1 and 3.6 to support linux kickstart deployments from the petemp\kickstart directory.
*Note: downloading the items require KACE support credentials to be entered.

Enable SSH root logon and reboot the K2000 before applying the patch.

3.5SP1 linux deployment toolkit patch.

3.6 linux deployment toolkit patch.

Then read the documentation in full for directions on how to implement this process.

The process does not support RSA deployment of linux at this time.

Please make feel free to comment below on ideas, suggestions or issues.

 

Back to the K2000 Deployment Workbench Page

View comments (9)

K2000 best practices

Prerequisites:

  1. NIC need to be able to PXE (fixed or via USB dongle)
    1. BIOS configuration
    2. Dongle needs to support PXE (Startech 7500 USB to Ethernet Dongle is supported)
  1. Not possible via WLAN/Bluetooth
  2. DHCP server needs to be configured correctly
    1. KACE internal DHCP server is suitable
    2. Options 66 (FQDN of the K2000 or RSA), 67(k2000.0)+ 244(IP of the K2000 or RSA) need to be set
    3. Client needs to be in the same subnet like the K2000 or RSA

 Deployment:

  1. Client boots to the  KBE-Boot Environment
    1. Via PXE
    2. KBE from boot media (flash media/USB thumb key)

http://www.itninja.com/blog/view/deploying-images-from-usb-devices-with-the-kace-2000

  1. KBE mounts the K2000
    1. KBE needs only two drivers: network + storage for the questioned system
    2. KBE queries kgetdhcp 66 and kgetdhcp 244 to get the correct IP
    3. KBE mounts the drivers \\k2000\drivers\ as drive Y:
    4. If this fails possibly a driver is missing https://support.software.dell.com/kb/111717
  1. KBE runs the interactive GUI or if started as automated task directly the SI/Image
  2. KBE runs the Pre-Install Tasks
    1. Create partition(s)
    2. Format the partition(s)
    3. Install MBR for questioned OS
    4. Get/Set Computername if needed

http://www.kace.com/support/resources/kb/article/get-set-computername

  1. KBE runs the Installation (SI/Imaging) including Mid-Install Tasks
  2. Reboot, the client boots from HDD
  3. OS runs the Post-Install Tasks
    1. Install Agent
    2. Automatic inject the drivers so no yellow question mark is in device manager anymore

                 i.      For Dell systems: enable the driver feed and download the drivers for that system

                ii.      For systems which are not in that feed: http://www.itninja.com/blog/view/driver-feed-builder

  1. Modify the firewall to allow the agent
  2. Scripts for all stuff you may need
  3. Installing software should be done by the K1 if possible

Typical issues:

Before testing on a client please try always in a virtual environment to be shure that the installation itself works fine

  1. Client don’t boot the KBE
    1. Review this table for Dell systems: http://www.itninja.com/blog/view/bios-pxe-boot-issues
  1. Review the BIOS config of the client (boot from NIC with PXE)
  2. Review the settings of the DHCP server (the settings must not have a space in it (esp. at the end!)
  3. Client boots the KBE but is not able to mount the K2000
    1. Check if the KBE got a correct IP

                i.      Type ipconfig /all

               ii.      If no IP: clean out all drivers for the KBE and download the KBE driver pack and install it   https://support.software.dell.com/kb/111717

              iii.      Recache the drivers and rebuild the KBE

              iv.      If this don’t fix: inject on the same way the needed network + storage drivers

               v.      Recache and rebuild

  1. Post Install Tasks not working correctly
    1. Use the runonceex converter http://www.itninja.com/blog/view/k2000-postinstall-task-converter
    2. If a batch is started, use call call batch.bat
    3. If a vbs is started, use cscript cscript vbscript.vbs
    4. If you use a post install task use start /wait
    5. Attachments must be smaller than 2GB due to a limitation of the box
    6. If you use 3.6 or newer: remove all call, cscript, start /wait and the runonceex-converter, as this was only needed prior to 3.6 since with the 3.6 a new task scheduler is in use which does not need it anymore. You can use the K2 advisor to check your installations. It will show you possible problems: http://www.itninja.com/blog/view/k2-advisor 
View comments (2)
Showing 1 - 5 of 47 results

Top Contributors

Talk About Windows Installer (MSI) Customizations