The pIT

Jackson Hall 011
35 Fifth Field Company Lane

x32442

+1 613-533-2442

Live Chat

Start a live chat with one of our techs

icon_map
The pIT

Jackson Hall 011
35 Fifth Field Company Lane

icon_phone
x32442

+1 613-533-2442

icon_chat
Live Chat

Start a live chat with one of our techs

You are here:
< Back

1

Check if drivers for the target machine already exist on the K2000.

a

Mount the K2000 samba share \\K2000.engineering.queensu.ca\drivers_postinstall\

b

Change into the feed_tools folder and double click the driver_feed_discovery_tool script

c

A window will pop up with the discovered model information for the desktop or laptop.  We are most interested in the Path information.

d

Go up a level to the root folder of the share and proceed to check if the path from 1c exists.

e

If the path does not exist; create it – match case and spacing as displayed; then skip to Step 2

f

If the path does exist but is empty; skip to Step 2

g

If driver files are present skip to Step 3.

2

Capture drivers from target machine.

a

Download the Double Driver package from cloudFiles (TEAMS \ IT Support \ Double Driver \ double_driver+4.1.0_portable.zip).

b

Expand and run Double Driver (dd.exe)

c

Click Backup in the menu bar.

d

Change into the feed_tools folder and double click the driver_feed_discovery_tool script

e

Review the scanned drivers – ensure all non-Microsoft drivers are checked.

f

Click Backup Now.

g

The default save location is fine or you can specify one of your choosing. Select Structured folder (default) as the Output type and click OK.

h

Double Driver will copy and collate the driver files. This can take a few minutes.

i

A success dialog will pop up when complete. You can close the dialog and the program.

j

Copy the captured drivers from the folder specified in Step 1g into the folder from Step 1e/1f.

3

Image the target machine with the K2000.

a

Boot the computer using PXE Boot or a K2000 USB Key

b

Once the K2000 interface is up, select scripted install.

c

Choose the appropriate script based on the machine and end user(s).

d

Let the K2000 image the machine — this step can take a while.

e

Once complete confirm the image was applied correctly.