Blog Posts tagged with K2000

Ask a question

Upgrading to Windows 10

*NOTE - If these tasks were downloaded and imported into your K2000 prior to September 4, 2015 please contact support.  We found an issue with the import of the task which we will need to fix on the backend.  The download available now does not have this issue.  We apologize for the inconvenience.

Many users will want to upgrade their current operating system to Windows 10, retaining all their user data and applications.  In order to upgrade to Windows 10, one must utilize the same edition of Windows 10 as the older version of Windows.  For example, if running Windows 7 Professional or Ultimate, Windows 10 Professional must be used.  If running Windows 8 Enterprise then Windows 10 Enterprise must be used to upgrade the system.

 

An upgrade to Windows 10 must take place within the operating system itself and cannot take place in KBE.  There are two methods to upgrading to Windows 10 using KACE appliances. The first method would be to create a K1000 script as outlined on an ITNinja blog post. The second method, which is detailed below, can be done from the K2000 with the provided tasks.
*Note, to download the tasks, it is necessary to be a member of the K2000 community.

 

First, use the current version of Media Manager to upload your Windows 10 source media, 3.7 SP2 supports Windows 10 so make sure you are using that version of Media Manager for the upload..  Once this is completed, the source media ID must be obtained from Library | Source Media.

 

Upload the attached .PKG files, which will create a Windows 10 K-Image for each architecture along with a few tasks.  Preinstall tasks such as partitioning and formatting should not be added to the image (or it will no longer be an upgrade).  The image that is being applied to the machine has no files, so nothing is overwritten.  The midlevel task is a template that should be duplicated and edited.  This midlevel task copies down the Windows 10 source media, enables autologon to the workstation and writes a setupcomplete.cmd file that gets applied at the end of the upgrade process.

 

The first few lines of the midlevel task contain variables that need to be changed by the user.

strUser should be an admin username

strPassword is the password of the above user

strDomain is the name of the domain, or leave as localhost if leveraging a local user

win10_source_cd_id is the ID number of the uploaded Windows 10 source media

 

The post install task, “Upgrade Windows 10” does not have to be modified by default.  However, the last command line switch is ‘/dynamicupdates disable’.

When Windows 10 setup begins, it will attempt to download available updates by default.  The command line switch above disables this behavior.  If you prefer for the updates to be downloaded immediately, just delete this switch from the command line.  For more commandline switches see http://winaero.com/blog/windows-10-setup-exe-command-line-switches/


Back to K2000 Deployment Workbench

View comments (37)

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 SDA (version 3.6 and higher) that can identify issues and link 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)
Showing 1 - 5 of 47 results

Top Contributors

Talk About K1000 Smart Labels