/build/static/layout/Breadcrumb_cap_w.png

Blog Posts by cserrins

Ask a question

BIOS/UEFI Combined Tasks

We consider this the new way to deploy an image.  Capture a BIOS configured single partition image.  Then for deployment, is using 6.1.251 or higher, apply the task group named "[DISK] BIOS/UEFI Tasks". If using version 6.0.425 or lower create the following 2 bat script tasks.

Preinstall bat task

@echo off
wpeutil UpdateBootInfo
for /f "tokens=2* delims= " %%A in ('reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType') DO SET FIRMWARE=%%B
echo Firmware Type: %FIRMWARE%
echo Explanation of Firmware Type: (0x1 is BIOS, 0x2 is UEFI)
if %FIRMWARE%==0x1 goto BIOS
if %FIRMWARE%==0x2 goto UEFI
goto END

:UEFI
(
ECHO select disk 0
ECHO clean
ECHO convert gpt noerr
ECHO create partition efi size=200
ECHO assign letter=s
ECHO format quick fs=FAT32
ECHO Create partition msr size=128
ECHO create partition primary
ECHO assign letter=c
ECHO format quick fs=NTFS
ECHO exit
)>X:\Windows\System32\UEFI.txt
diskpart /s X:\Windows\System32\UEFI.txt
goto END

:BIOS
(
ECHO select disk 0
ECHO clean
ECHO create partition primary
ECHO select partition 1
ECHO assign letter=c
ECHO active
ECHO format quick fs=NTFS
ECHO exit
)>X:\Windows\System32\BIOS.txt
diskpart /s X:\Windows\System32\BIOS.txt
goto END

:END

Make sure there is a tab and a space between 'delims=' and " %%A"

Then create a midlevel bat task

@echo off
for %%I in (Z W V U S R Q P O N M L K J I H G F E D C) do (
if exist %%I:\BOOT if not exist %%I:\SOURCES\BOOT.WIM set BOOTSYS_DRIVE=%%I:
if exist %%I:\WINDOWS if not exist %%I:\SOURCES\BOOT.WIM set WINDOWS_DRIVE=%%I:
)
wpeutil UpdateBootInfo
for /f "tokens=2* delims= " %%A in ('reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType') DO SET FIRMWARE=%%B

@echo on
echo Boot Drive: %BOOTSYS_DRIVE%
echo Windows Drive: %WINDOWS_DRIVE%
echo Firmware Type: %FIRMWARE% (0x1 is BIOS, 0x2 is UEFI)
echo Explanation of Firmware Type: (0x1 is BIOS, 0x2 is UEFI)

if %FIRMWARE%==0x1 goto BIOS
if %FIRMWARE%==0x2 goto UEFI
goto END

:UEFI
bcdboot %WINDOWS_DRIVE%\windows /s s: /f UEFI
bcdedit /store S:\efi\microsoft\boot\bcd /set {bootmgr} device partition=s:
bcdedit /store S:\efi\microsoft\boot\bcd /set {memdiag} device partition=s:
bcdedit /store S:\efi\microsoft\boot\bcd /set {default} device partition=%WINDOWS_DRIVE%
bcdedit /store S:\efi\microsoft\boot\bcd /set {default} osdevice partition=%WINDOWS_DRIVE%
Bcdedit /store S:\efi\microsoft\boot\bcd /set {FWbootmgr} displayorder {Bootmgr} /addfirst
bootsect /nt60 s:
goto END

:BIOS
if not defined BOOTSYS_DRIVE (
bcdboot %WINDOWS_DRIVE%\windows /s %WINDOWS_DRIVE%
)
goto END

:END

Make sure there is a tab and a space between 'delims=' and " %%A"

Attach these 2 tasks to your BIOS captured single partition image and go at it!!!

These 2 tasks will automatically determine if you are running BIOS or UEFI and applly the appropriate partitioning.
***Warning, issues can arise if using these on images that are not single partition or were captured from a UEFI system.

These tasks will be included as a task group when upgrading to SDA version 6.1, later this year.




View comments (5)

KACE SDA USMT Advisor

This utility is designed to check permissions and configurations required for the
KACE Systems Deployment Appliance's (SDA) Online USMT Scan to complete successfully.

Download (requires support maintenance credentials)

Instructions for use:

1) Log into the target device with the same credentials specified in the online USMT scan

2) Run the USMT Advisor utility and it will run it's tests

3) If there are issues found, click on the Fix it button.
    If a reboot is required to make changes, a Reboot button will show up.
    The device will need to be rebooted before you can continue.

4) Once the issues are addressed, the utility will display a message stating 'Device scanning can now be tested'.
    Stay logged into the target device and initiate the User State Scan from the SDA web interface.

5) When the online scan from the SDA finishes and the user states are uploaded,
    you can check the box to delete the USMT Advisor application (if desired) and press Quit.

6) USMT Advisor creates an undo_fixes.exe file after completetion that will reset the machine back
    to the way it was before USMT Advisor was first run.
    This file should only be run on the machine from which it was created.
Be the first to comment

Custom Deployments

Custom Deployments is a new feature in version 6.0 of the KACE Systems Deployment Appliance (SDA) that allow users to deploy a set of tasks to a Windows workstation without deploying an image or scripted install. 

With a custom deployment, no hidden tasks are automatically assigned like in an image or scripted install.  This means that everything needing to run will have to be manually assigned and for this reason, it is considered an advanced feature.  The 6.0 release of the SDA includes 2 custom deployments by default; x86 and x64 variations of "Scan User States Offline and Shutdown".  This is a perfect example of a custom deployment because after the task is complete and the shutdown command is given, the deployment shows as completed.  In the past, you would need to do a batch script to shut down, and because the built in tasks did not run, it would never display as successfully completed and it would stay in the Progress portion of the UI until removed.  This is just one example of a custom deployment, there are other great ways to leverage them.

We are including these downloads to get you started, you must be a member of the K2000 community on ITNinja to gain access.  After extracting the download, the package can be imported into the SDA.  The import is a task group (another new feature of 6.0) that contains all the tasks needed for the custom deployment. Since each custom deployment is assigned a specific architecture, it is easier to provide them as a single package with task groups

To use the imported item, create a new custom deployment, apply the appropriate task group, and save.  All the tasks are named with [CU] as a prefix, as CU is the prefix used when exporting custom deployments. By implementing this naming scheme it is easy to find the tasks commonly used for custom deployments.  I also name my custom deployments with the [CU] prefix.


The title of the Custom Deployments below are links to download a .zip file, you must be a member of the K2000 Community.  Extract the zip once it is downloaded and you will have a .pkg file and an .xml file.  You can import the Task Group one of two ways.  Since these are small packages you can browse to Settings | Package Management | Import Packages on the SDA web UI.  Then from the choose action drop down menu select "Upload Package for Import."  Select the .pkg file and click on the "Import Package" button.  You can also browse to the SDA Restore UNC path (\\sda_ip\restore).  Place both the .pkg and .xml file in the restore share.  Then on the SDA web UI browse to Settings | Package Management | Import Packages. You should see the Task Group on the list page.  Select the checkbox next to the Task Group to import and then from the choose action drop down menu choose "Import Selected."


******NOTE
Do not import these tasks into any version less than 6.0, it will cause issues.

Windows 10 in-place upgrade.  This custom deployment is used when an in-place upgrade of Windows 10 is needed, either from Windows 7/8 or an earlier build of Windows 10.  The same edition must be used when upgrading.  The auto logon and prepare Windows 10 tasks need to be customized for your environment, make sure to read the notes field for those two tasks.

Run tasks in an operating system.  If you have tasks that need to be run within the OS, then this task group is needed for everything to run the way you would expect. Some tasks need to be customized for your environment, make sure to read the notes.

USMT, DoD Wipe and Shutdown.  This task group will scan user states offline, partition/format the drive, perform a 7-pass DoD wipe and then shut the machine down.  We have referenced the SysInternals tool SDelete.  We cannot include the executables as we do not have rights to distribute them, but the task "[CU] Run SDelete (7-pass)" has a link to download SDelete from Microsoft.Once you have downloaded SDelete from Microsoft, extract the executable file. Next using the SDA WebUI download the SDelete.bat file from the usmt_wipe_shutdown task you previously imported and then ZIP the 3 files together. Use the resulting ZIP file to replace the BAT file in the task.  The BAT file will determine which architecture is running and run the appropriate application.  No other changes are needed unless you want to change some of the SDelete parameters, those changes would need to be made in the BAT file before it is added to the ZIP.

How will you use custom deployments?  If you have any interesting ideas that you believe others can use, export your tasks as a task group, making sure to have the tasks named with [CU].  Please review the tasks that are included here first and try to reuse those so we can stay consistent. Email your exported task groups to Corey Serrins [corey dot serrins at quest dot com] and we will add those to this page.



View comments (6)

Unattend LTI

The Unattend LTI application is a utility designed by Corey A. Serrins and Nick Morea to give users of the Quest | KACE K2000 some additional flexibility in the deployment of new computers into an organization by manipulating the unattend.xml file of the deployed device.

Read the included PDF for instructions on how to use these tasks, as they can be run in the most basic form of a user interface with all options available, or the UI can be narrowed down to just the options preferred by the administrator, or can be run silently.

To download, the user must be a member of the K2000 community.

Back to K2000 Deployment Workbench

View comments (2)

Change the KBE keyboard layout

In order to use a keyboard layout for a different language, there are steps that can be taken to make this easy.
First identify the language ID from the this page: For IDs of other languages, see: https://msdn.microsoft.com/en-us/library/cc233982.aspx
According to [https://technet.microsoft.com/en-us/library/cc765969%28v=ws.10%29.aspx] boot into a kbe and go to command prompt

Substitute the language ID found from the step above for your usage, this example looks at French, which had the language ID code of 0x040c
Type 'wpeutil listkeboardlayouts 0x040c’ at the command prompt
The list is long, so you may want to output to a file because the buffer isn’t big enough to let you scroll all the way back to the beginning.
'wpeutil listkeboardlayouts 0x040c > t:\petemp\idcode.txt'

Then scroll through this file and find the name of the keyboard layout you want to use.  For example Belgian French is 040c:0000080c

So then you would type in 'wpeutil setkeyboardlayout 040c:0000080c’

This does not work in the initial command window from which it was run, but does work in other command windows and works in the dialog box for getcomputername.exe!!

So a user could run KBEM and type 'wpeutil setkeyboardlayout 040c:0000080c’ as a command line option, or a preinstall bat task could be used containing the identical information.

*Warning, after the change is made, the keyboard layout does not affect the K2000 Deployment HTA pages.
Be the first to comment
Showing 1 - 5 of 32 results

Top Contributors

Talk About Server Management