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.
Driver Feed Advisor (DFA) is a command line tool designed to provide an accurate path for the machine from which it is run for the K2000 Driver Feed. This tool can be run in several different ways through the K2000, K1000, or standalone. Note that when this tool is utilized from the K1000 or standalone it will reach out to service.kace.com and download the newest version of drvstr.cfg. This file is part of the tools used by the K2000’s Driver Feed. However, when utilizing DFA from the K2000, this file is not downloaded as it will use the version of drvstr.cfg currently on the K2000 (which may not be up to date). Learn how to update your Driver Feed tools with the following Knowledge Base article: https://support.software.dell.com/k2000-systems-deployment-appliance/kb/118804.
As a standalone tool, simply open a command prompt in the location of the executable and type driverfeed_advisor.exe. The driver feed path of the current hardware and Operating System will output directly to the console as well as write a log file to %systemdrive%\ProgramData\Dell\KACE.
You can also take advantage of DFA from the K1000. Using a combination File Synchronization or Scripting, Custom Inventory, and Reporting you can produce a concise list of all Driver Feed paths required for the devices and Operating Systems in your environment.
In order to run DFA remotely from the K1000 you will first want to push the executable to all of your Windows devices. Scripting is the quickest method as it does not require a K1000 Agent check-in in order to run. The following instructions will walk you through creating a script:
1. Within your K1000 Admin UI, navigate to Scripting > Scripts
2. From the Choose Action dropdown select New
3. On the Script Detail page enter the following information:
a. Name: Copy Driver Feed Advisor
b. Enabled: Check the box
c. Type: Online K-Script
d. Deploy: None
e. Operating Systems: Uncheck Select Specific Operating Systems and Select Windows
f. (Alternate) Operating Systems: Select specific Windows OSes for deployment
g. Windows Run As: Local System
h. Notify: None
i. Schedule: None
j. Dependencies: Select New Dependency and navigate to driverfeed_advisor.exe
k. Tasks: Select New Task
l. Under On Success, select Run a batch file
m. Script Name: copy_dfa.bat
n. Batch file: xcopy driverfeed_advisor.exe %ALLUSERSPROFILE%\dell\kace /y
o. Wait for Completion: Check the box
p. Click Save Changes under the Batch Script
q. Click Save to complete your Script
4. To run your Script on demand, navigate to Scripting > Run Now
5. Select Copy Driver Feed Advisor from the dropdown
6. Under Labels select a label of Windows devices you wish to deploy to or manually select a group of devices
7. Click Run Now
8. Click Save
Once the Script has completed you may progress to the next step in order to create the Custom Inventory rule necessary to collect the output from DFA. Custom Inventory allows you to gather information about devices that the Agent does not already gather. In this instance, we will be running DFA silently and collecting the console output and displaying that in Device Inventory.
1. Within your K1000 Admin UI, navigate to Inventory > Software
2. From the Choose Action dropdown select New
3. On the Software Detail page enter the following information:
a. Name: K2000 Driver Feed Path – CIF
b. Publisher: CUSTOM
c. Supporting Operating Systems: Select the Windows Operating Systems you wish to have this Custom Inventory running on
d. Custom Inventory Rule:
e. NOTE: After the /k2name: enter the name of your K2000
f. Click Save
4. Click back into your new Custom Inventory record and note the ID# at the end of the URL. You will need this later for reporting.
5. Within your K1000 Admin UI, navigate to Inventory > Devices
6. Select a few devices that you know already have DFA
7. From the Choose Action dropdown select Force Inventory (NOTE: Do not perform this function on large numbers of devices)
8. Once the inventory cycle has completed, navigate into one of your selected devices
9. On the Device Detail page, locate the Software section and expand Custom Inventory Fields
10. Your new Custom Inventory should now show the Driver Feed path for that device
11. Check a few other device/Operating System combinations to make sure that Custom Inventory is working as intended
Now that you have Script and Custom Inventory setup, you will want to make sure that all your desired devices get DFA and then complete a Custom Inventory cycle. This might take a few days to ensure that all devices have completed both actions. Once you are satisfied with the amount of data gathered, it is time to take advantage of your K1000s reporting capabilities! While you can definitely pull the Driver Feed information out of the K1000 using a Wizard based report, we are going to use a custom SQL report to process and filter our information into a useful report.
1. Within your K1000 Admin UI, navigate to Reporting > Reports
2. From the Choose Action dropdown select New (SQL)
3. On the Report Detail page enter the following information:
a. Name: K2000 Driver Feed Paths – Total Devices
b. Description: K2000 Driver Feed Paths gathered by Driver Feed Advisor. Displayed and grouped up by Manufacturer, Model, and Operating System combination. Also displays total # of devices per Driver Feed.
c. Category: Select New Category and type: K2000 (or select K2000 if you already have that category)
d. SQL: Copy the following custom SQL
MACHINE.CS_MANUFACTURER AS Manufacturer,
MACHINE.CS_MODEL AS Model,
MACHINE_CUSTOM_INVENTORY.STR_FIELD_VALUE AS K2000_Driver_Feed_Path,
COUNT(MACHINE_CUSTOM_INVENTORY.STR_FIELD_VALUE) AS Total_Devices
JOIN MACHINE ON MACHINE.ID = MACHINE_CUSTOM_INVENTORY.ID
WHERE MACHINE_CUSTOM_INVENTORY.SOFTWARE_ID = 'XXXX'
GROUP BY MACHINE_CUSTOM_INVENTORY.STR_FIELD_VALUE
ORDER BY MACHINE.CS_MANUFACTURER ASC , MACHINE.CS_MODEL ASC
e. Find the line that ends with SOFTWARE_ID = 'XXXX' and modify the ID# to be the ID# of your Custom Inventory. (Note that your ID# may be more or less total digits).
f. Click Save
4. Find and run your report!
Driver Feed Advisor can be utilized by the K2000 as well inside a K2000 Boot Environment (KBE). To use DFA within a KBE, use KBE Manipulator 184.108.40.206 or later to have driver feed advisor automatically inserted and run. The output will show up in the startnet.cmd command window and output a file to x:\windows\temp.
When DFA is run manually within a KBE, it needs the /kbe switch: driverfeed_advisor.exe /kbe.
This switch tells DFA to load the registry of the operating system on the hard drive and find out what version of Windows is currently installed on the drive, and use that information to determine the path. If no operating system is found then the text ‘OSNotFoundonLocalDrive’ will show in place of the KACE operating system path. If this happens, or if you have an older version of Windows on the drive and want to see the path of a different Windows Operating System, then you can use one of the switches below.
/wxp = Windows XP
/wvista = Windows Vista
/w7 = Windows 7
/w8 = Windows 8
/w81 = Windows 8.1
/w10 = Windows 10
/w2k3 = Windows Server 2003
/w2k8 = Windows Server 2008
/w2k12 = Windows Server 2012
So an example command line for a Windows 10 Driver Feed path would look like:
driverfeed_advisor.exe /kbe /w10.
Note that the architecture used within the Driver Feed Path is gathered based on what KBE you are running DFA within.
Exporting Wi-Fi profiles from a device can be useful to use during the deployment of new notebooks or tablets. This process is outlined in detail from Microsoft https://technet.microsoft.com/en-us/library/cc755301%28v=ws.10%29.aspx
This K2000 Deployment Workbench tool, export_wifi_profiles,' will identify the networks connected on your device and display their names in a list to be selected for export. Use the "Select/Deselect All" checkbox to tick or untick all the boxes. Click the Export Profiles button to begin the process. After a few seconds, a message box will appear with instructions on how to use the file that is produced. The file, 'deploy_wifi_profiles.zip' will automatically be saved to the desktop, unless the file already exists in which case it will ask to browse to a new location. If the same location is chosen, the original will be overwritten. This ZIP file will include all of your exported profiles and the executable needed to deploy the wireless profiles.
To deploy using the K2000:
1. Login to the K2000
2. Click Library | Post-Installation Tasks
3. From the Choose Action… drop-down menu, choose Add Application….
4. Give the task a name such as 'Deploy Wi-Fi Profiles'
5. Select 'Windows' from the Runtime Environment
6. Under upload file, click the Browse… button and select the ZIP file that was produced from the export
7. Give your script a name
8. Use the command line, 'deploy_wifi_profiles.exe' in the parameter field and save the task
9. Add this task to an image or scripted install
To deploy using the K1000:
1. Login to the admin portal of your K1000
2. Click Scripts | Choose Action | New
3. Give your script a name
4. Click Type | Online KScript
5. Uncheck the “Select Specific Operating Systems” checkbox under the Deploy section, then select Microsoft Windows
6. Select either specific devices and/or a label of machines you wish to deploy to
7. Under Windows Run As, choose Local System
8. Under Dependencies, click New Dependency
a. Attach the “deploy_wifi_profiles.zip” file
9. Click New Task
10. Under On Success, click Add
a. Select the Launch a Program… step
b. DIRECTORY: $(KACE_DEPENDENCY_DIR)
c. FILE: deploy_wifi_profiles.exe
d. Click Save Changes
11. Save and run your script
Back to K2000 Deployment Workbench Tools page.
Version 220.127.116.11 [05/31/2016]
-Get names of networks and display them in a list
-User selects profiles to export
-profiles are exported, zipped with an .exe, deploy_wifi_profiles, which will import the profiles in the same directory
****WARNING: Implementing this in an environment could have undesired results if a machine boots to the environment unexpectedly. Please follow the instructions and take proper precautions.
The Default Deploy application is a utility designed by Corey A. Serrins to give users of the Dell | KACE K2000 some additional flexibility in the deployment of new computers into an organization.
This K2000 workbench tool was designed with one thought in mind; to deploy an operating system to a brand new computer using the K2000, without importing MAC addresses into the inventory detail.
Expand the .zip download into a folder of choosing. Move default_deploy.ini to \\k2000\petemp and
use the below instructions to set the preferences for x86 and x64
deployments. Using KBE Manipulator,
choose Configure | Modify KBE Tools. Check
the box for “Add files to KBE” and browse to the location of the extracted
folder. If this is indeed to be used as
a boot environment for deployment to a new computer, then also de-selecting
“KACE Deployment Menu” would be beneficial so that the default menu does not
appear. Select Configure | Add custom
dos command(s) and then enter in the following line:
There are a number of options that must be set in the .ini file that will reside in the petemp directory of any K2000 or RSA.
The instructions in the original .ini file are as follows:
TOGGLE=on will enable the tool
TOGGLE=off disables the tool
TYPE A = Kimage or WIM
TYPE B = Scripted Install
ID refers to the ID number of the image or scripted install
Timeout refers to the number of seconds prior to deployment starting
Timeout=0 means no timeout will be used.
TimeoutDeploy=yes sets the default action of timeout to deploy
TimeoutDeploy=no sets the default action of timeout to cancel
Log File can be found on petemp by default, logs are stored by day.
These settings exist for both x86 and x64 systems, just change the settings per the architecture.
By default, the script looks for the ini file on t:\default_deploy.ini and the log file is written to t:. The .bat file can be called with 2 commandline switches if desired to change these settings
/ini_file allows the user to
define the path and file name of the settings file, but should end with the
/log_file allows the user to
define the path of the log file.
Both switches can be used in combination and in any order.
***Note: This KBE should not be set as a default KBE as it could cause the reimage of machines that pxe to KACE. When automated deployments are complete, the default_deploy.ini should either be renamed or removed or the value of Toggle and/or TimeoutDeploy should be set to ‘No’
The issue was first outlined here http://deploymentresearch.com/Research/Post/497/Fix-for-Windows-7-deployments-failing-after-upgrading-to-Windows-ADK-10 and then acknowledged by Microsoft as an issue [https://support.microsoft.com/en-us/kb/3084782].
The resolution is to copy 7 files for each architecture into the directory that contains USMT 10 loadstate.
These files need to be in place prior to uploading USMT 10 to the K2000. ADK 10 must be installed on the workstation along with the K2000 Media Manager. To make the process easier, I wrote a script that will copy both x64 and x86 files to the correct location for you.
The tool can be downloaded from ITNinja, but you must join the K2000 community first.
Please let me know if there are any issues with the tool itself.
*K2000 3.7 SP3 and SP3 Media Manager are required.