NCR Imaging Suite / User Guide

NCR Imaging Suite

User Guide
V 2.05

NCR ©2017 All rights reserved. 1

NCR Imaging Suite / User Guide

Table of Contents
Document Revision History.............................................................................................................................................. 3
Introduction............................................................................................................................................................................ 4
Assumptions.........................................................................................................................................................4
NCR Imaging Suite Overview............................................................................................................................................ 5
Hardware and Software Requirements................................................................................................................5
Imaging Suite Package Components.....................................................................................................................6
Imaging Use Cases................................................................................................................................................................ 8
Local USB boot to capture or apply an image.......................................................................................................8
Network boot Client and connect to Server to capture or apply an image..........................................................8
Creating a Bootable USB drive......................................................................................................................................... 9
Applying an image from a USB flash drive............................................................................................................... 13
Using an Auto-Imaging USB flash drive..............................................................................................................13
Using a generic Imaging Client USB flash drive..................................................................................................13
Capturing an image to a USB flash drive................................................................................................................... 17
Configuring the Imaging Server.................................................................................................................................... 20
Capturing an image over the Network...............................................................................................................24
Applying an image over the Network.................................................................................................................30
Command Line Options.................................................................................................................................................... 35
Imaging Server Options......................................................................................................................................35
Imaging Client Options.......................................................................................................................................36
Modifying an image file.................................................................................................................................................... 37
Mounting an image using DISM GUI..................................................................................................................37
Customizing the PE Boot Image.................................................................................................................................... 43
Mount the Windows PE boot.wim file.............................................................................................................43
Updating Recovery Tool................................................................................................................................................... 47
Requirements.....................................................................................................................................................47
From within the Recovery Tool...........................................................................................................................47
From Windows...................................................................................................................................................47
RadsImageX.......................................................................................................................................................................... 48
Overview............................................................................................................................................................48
Major Differences from ImageX.........................................................................................................................48
Capture/Append Operations..............................................................................................................................49
Apply Operation.................................................................................................................................................50
UEFI / Secure Boot Operation....................................................................................................................................... 51
Legacy Images Are Compatible...........................................................................................................................51
Changes to MakeBootablePeDisk.......................................................................................................................52
Changes to TFTPD32 (PXE BOOT).......................................................................................................................53
Changes to Recovery Update.............................................................................................................................54

NCR ©2017 All rights reserved. 2

NCR Imaging Suite / User Guide

Document Revision History

User Date Revision Comments
C.Davis/CD185093 6/6/2012 1.00 Initial Creation
C.Davis/CD185093 7/3/2012 1.01 Added new sections and revised existing content.
C.Davis/CD185093 2/21/2013 1.02 Added the new ImagePartialSigner tool.
M.Szramel/MS185443 4/17/2013 1.03 Added UDP firewall port; updated internal location link
C.Davis/CD185093 4/29/2013 1.04 Updated TFTP settings, screenshots and added Option
Negotiation
M.Szramel/MS185443 6/19/2013 1.05 Updated TFTPD to include WINS/DNS for Imaging Client
host name resolution. Updated images for Imaging Suite
D. Mayo/DM185169 10/06/2014 2.01 Added/modified sections for auto-imaging USB drives,
RadsImageX, Server and Client command line options
and Recovery Update procedures. Document format
changes.
D. Mayo/DM185169 08/10/2015 2.02 Adding page numbers. Rewording several sections with
updated information.
D.Mayo/DM185169 06/07/2016 2.03 Added UEFI information. Updated screenshots.
Updated package contents descriptions.
D.Mayo/DM185169 06/17/2016 2.04 Updated screenshots of MakeBootablePeDisk with UEFI
selection.
B.Rogers/BR185069 04/12/2017 2.05 Changed to reflect deprecation of ImagePartialSigner.
Fixed formatting, updated with new icons and
screenshots.

NCR ©2017 All rights reserved. 3

NCR Imaging Suite / User Guide

Introduction
NCR has transitioned most of our imaging infrastructure to Microsoft’s Windows Imaging technology (often
referred to as ImageX). To facilitate this transition, we created a package of applications based on Windows
Imaging technology called the “NCR Imaging Suite” that will enable users to capture and apply system images in
the Microsoft Windows Imaging (.WIM) format.

The Imaging Suite application is GUI based, and provides support for the typical imaging activities previously
available with Symantec Ghost to make the transition as easy as possible.

This document should provide the user with a general overview of the Imaging Suite package, how to configure
the system to run it, and how to use the applications to capture and apply system images.

Assumptions
The target audience for this document is primarily those in image creation roles both within NCR and within
customer organizations. Some knowledge of the Microsoft Windows 7, Windows 10 and Server Operating
Systems is assumed. Prior experience performing system imaging using Symantec Ghost and PXE network
booting may be helpful to the reader for some of the more advanced user scenarios, but is not required.

NCR ©2017 All rights reserved. 4

NCR Imaging Suite / User Guide

NCR Imaging Suite Overview

The Imaging Suite package consists of three primary parts:
- A Server application which is designed to be used for local area network imaging.
- A Client application that runs on the target device to either capture or apply a device image.
- A customized version of the Windows PE boot OS environment from which the client application will run

The Imaging Client application is typically run from within the Windows PE environment on the target device.
The Imaging Suite provides tools and instructions for booting to this environment from your network or from a
bootable USB device.

Any existing imaging infrastructure used for Ghost can also be used for the Imaging Suite applications with some
minor changes to existing TFTPD32 configurations for PXE booting. It is recommended that Windows 7 and
Server 2008 R2 be used as the imaging server OS but XP Pro will also work.

Hardware and Software Requirements

Servers used for imaging
 Windows 7 Professional SP1 32 and 64bit | 1GB RAM
 Windows 2008 Server 32 bit SP2 and 64bit R2 | 1GB RAM
 Available Network Interface for static IP and LAN PXE booting
 Gigabit LAN networks are recommended.

Server software prerequisites

 .NET 4.0 Full Version
 Visual C++ 2010 redistributables X86 and 64bit.

Clients
 At least 512MB RAM Installed.
 Supports PXE or USB Drive booting.

Network Ports and Protocols used for imaging

 SMB, Netbios.
 TCP port range: 38400-38408
 UDP port 2671 is used for broadcast.

NCR ©2017 All rights reserved. 5

NCR Imaging Suite / User Guide

Imaging Suite Package Components

The Imaging Suite is delivered as a set of folders containing all the tools and supporting utilities needed for
operation. Below is an explanation of the major components contained in each folder.

Utilities

ImageSigner
Use this application after using DISM to manually modify the contents of an image. This can reapply
the NCR proprietary image hash to the WIM file.

This can also check the signature of an image file. The signature controls the type and size of
recovery partition (if applicable) the Client will create when applying the image to a terminal.

Only NCR can sign images to create a recovery partition, but a signature is not necessary to capture
and apply images.

ImagingServer
Server application which can create network imaging “sessions”. Clients can connect over a network
to capture and apply images.

MakeBootablePeDisk
Utility used to create a bootable Windows PE USB drive that contains the Imaging Client. An option
allows the drive to “auto-image” a terminal with a provided image.

RadsImageX
This utility is typically consumed by other software applications (e.g. Command Center). This is a
compact, command line driven version of the Imaging Client with a graphical progress bar used in
automated imaging tasks. The command line is intended match a subset of the stock ImageX.exe to
allow easy drop in replacement of the NCR Imaging Client and WIM format in existing utilities calling
ImageX.exe. Most users will instead use the main Imaging Client to capture and apply images.

RecoveryToolLogExtractor
The Recovery Tool logs its activity in the normally hidden recovery partition, which can make this
information difficult to access. Running this command-line tool from Windows will retrieve the logs
for reading or submission to support.

DISM GUI
This tool is distributed by Microsoft. A copy is included with Imaging Suite for convenience. This tool
will mount a WIM image captured by the Imaging Suite for offline editing. Be sure to run
ImageSigner (above) to complete image changes made using this method.

PXEBOOT-WINPE
This folder contains all the application and support files necessary for PXE network client booting.

NCR ©2017 All rights reserved. 6

NCR Imaging Suite / User Guide

Legacy / UEFI folders

There are two copies of the PXE network package. If you’re system is configured for Legacy boot
(normal case), use the tftpd32 program in the Legacy folder. The UEFI subtree should only be
used for systems that have been converted to UEFI boot. This is not typical. New terminals ship
configured for Legacy boot. For more information, see Imaging Suite UEFI operation.

Recovery_Update

RecoveryUpdate
This application can be run from Windows to replace the current version of Recovery_Tool on the
terminal with the latest version.

Legacy / UEFI folders

There are two copies of the Recovery Update package. If you’re system is configured for Legacy boot
(normal case), use RecoveryUpdate.exe to browse to the Recovery.wim in the Legacy folder. The
UEFI subtree should only be used for systems that have been converted to UEFI boot. This is not
typical. New terminals ship configured for Legacy boot. For more information, see Imaging Suite
UEFI operation.

Prerequisites
NCR Imaging Suite dependency packages.
 TFTPD32 4.0
 .NET 4.0
 VC++ 2010 Redistributable X86 and X64

NCR ©2017 All rights reserved. 7

NCR Imaging Suite / User Guide

Imaging Use Cases

Local USB boot to capture or apply an image.

Bootable USB Flash
Client Terminal
Drive

Network boot Client and connect to Server to

capture or apply an image.
PXE Server and
Imaging
Client Server
Terminal

NCR ©2017 All rights reserved. 8

NCR Imaging Suite / User Guide

Creating a Bootable USB drive

1. Insert USB drive to be made bootable.

****WARNING****: Drive will be formatted and all data on USB drive will be lost. Back-
up any important data located on drive before proceeding.

2. Launch MakeBootablePeDisk.exe located within .\ImagingSuite_X.X.X.X\Utilities\.

NCR ©2017 All rights reserved. 9

NCR Imaging Suite / User Guide

3. Click on the drive that will become a bootable USB disk.

4. We supply a WinPE Pre-installation environment boot.wim and select it by default. This will
automatically launch the Imaging Client when WinPE boots. Advanced users, if required, can browse
to an alternate bootable WinPE boot.wim.

NCR ©2017 All rights reserved. 10

NCR Imaging Suite / User Guide

5. The USB drive can optionally be made to automatically apply a specific image. To do this, click the
“Auto Apply” check box and browse to the image (.WIM) that will be applied upon boot of the USB
drive.

NCR ©2017 All rights reserved. 11

NCR Imaging Suite / User Guide

6. Click the “Make Bootable” button.

7. If the “Verify image integrity before creation” checkbox is clicked, the image’s proprietary hash is
verified prior to confirming disk creation. This can be useful in detecting corruption that can be
caused by file transfer operations.

8. Confirm the disk creation by clicking OK.

NCR ©2017 All rights reserved. 12

NCR Imaging Suite / User Guide

Applying an image from a USB flash drive

Using an Auto-Imaging USB flash drive
1. Attach the bootable, auto-imaging USB flash drive created by MakeBootablePeDisk to the target
client PC or terminal you wish to image.

2. Attach a keyboard to the terminal.

3. Power on the system and boot to the USB drive.

Note: On most systems, this can be done by pressing F8 during the boot, and choosing the USB
option, or entering BIOS setup and modifying the boot order.

4. The system will boot into the Windows PE OS environment and start a script that will request
confirmation to completely re-image the terminal, destroying all existing user data.

5. When imaging is complete, remove the USB drive and keyboard.

6. Reboot the system by either closing the Command Prompt, invoking the command wpeutil
reboot, or pressing and holding the power button for 5 seconds to power off, then pressing once
more to power on.

Using a generic Imaging Client USB flash drive

1. Copy the image file to be used onto your bootable USB drive created with MakeBootablePeDisk.

2. Attach the USB Flash boot drive to the target client PC or terminal you wish to image.

3. Attach a keyboard to the terminal.

4. Power on the system and boot to the USB drive.

Note: On most systems, this can be done by pressing F8 during the boot, and choosing the USB
option, or entering BIOS setup and modifying the boot order.

5. The system will boot into the Windows PE OS environment and start the Imaging Client application
automatically.

NCR ©2017 All rights reserved. 13

NCR Imaging Suite / User Guide

6. To apply an image from the USB drive, select the “Apply Image” button.

NCR ©2017 All rights reserved. 14

NCR Imaging Suite / User Guide

7. Select the Removable Drive and the image in the list, then click Next.

NCR ©2017 All rights reserved. 15

NCR Imaging Suite / User Guide

8. Select the destination drive listed, and click Next.

9. After confirmation, the unit will be re-imaged, destroying all existing user data.

NCR ©2017 All rights reserved. 16

NCR Imaging Suite / User Guide

Capturing an image to a USB flash drive

1. Attach the bootable USB flash drive created by MakeBootablePeDisk to the target client PC or
terminal you wish to capture.

2. Attach a keyboard to the terminal.

3. Power on the system and boot to the USB drive.

Note: On most systems, this can be done by pressing F8 during the boot, and choosing the USB
option, or entering BIOS setup and modifying the boot order.

4. The system will boot into the Windows PE OS environment and start the Imaging Client application
automatically.

5. To capture an image from the USB drive, click the “Capture Drive” button.

NCR ©2017 All rights reserved. 17

NCR Imaging Suite / User Guide

6. Select the Source Drive you wish to capture, then click the Next button.

NCR ©2017 All rights reserved. 18

NCR Imaging Suite / User Guide

7. Select the destination drive and input the image filename into the bottom-most text field, then click
the Next button.

8. After confirmation, the new image will be captured to the destination drive, provided there is
sufficient free space available.

NCR ©2017 All rights reserved. 19

NCR Imaging Suite / User Guide

Configuring the Imaging Server

1. Install software prerequisites on Server (if not already present):

a. All dependencies and pre-requisites can be found in the Prerequisites folder in the Imaging
Suite package.

b. Install .NET 4.0 (full version).

c. Install Visual C++ 2010 SP1 Redistributable.

2. Create Windows Firewall Exception:

a. Create Program exception in the Windows Firewall for ImagingServer.exe

i. Open Control Panel then Windows Firewall and select “Add a feature or program
through Windows Firewall”.
ii. Click the “Change Settings” button.
iii. Click on “Allow another program”.
iv. Next, click the Browse button and navigate to
C:\ImagingSuite_X.X.X.X\ImagingServer.exe (where X = the version
number)
v. Click on “Add” and then OK.
vi. Click in the check boxes for the Domain, Work/Private, and Public columns to enable
the program exception for all network locations.

3. Setup a LAN NIC

a. Configure the LAN NIC to a static IP of 192.168.1.10 or something similar.

b. Set the subnet mask to 255.255.255.0

4. Configure TFTPD32 (TFTP and DHCP Server)

a. Navigate to C:\ImagingSuite_X.X.X.X\PXEBOOT-WINPE\Legacy directory

b. Launch the TFTPD32.exe application

i. The first time the application is run, there may be an error message about binding
DHCP/TFTP ports to an IP address not available for your system. These settings will
be changed later and you can ignore this error.

c. When prompted allow program exception for Windows Firewall or manually create a port
exception for tftpd32 TCP port 69.

NCR ©2017 All rights reserved. 20

NCR Imaging Suite / User Guide

d. Set the Current Directory to C:\ImagingSuite_X.X.X.X\PXEBOOT-WINPE\Legacy

(where x=the imaging suite version number).

e. Click on the Settings Tab.

f. Select the Global Tab and the enable the TFTP Server and DHCP options.

g. Click on the TFTP tab

h. Set the Base Directory to C:\ImagingSuite_X.X.X.X\PXEBOOT-WINPE\Legacy (where

x=the imaging suite version number).

i. Set TFTP Security to Standard

j. In Advanced TFTP Options enable the following items:

i. Option Negotiation.

ii. Show Progress Bar.

iii. Translate Unix file names

iv. Bind TFTP to this address

1. Select the IP address in the drop down menu that will be used for serving
DHCP and TFTP.

v. Allow “\” As virtual root.

NCR ©2017 All rights reserved. 21
NCR Imaging Suite / User Guide

NCR ©2017 All rights reserved. 22

NCR Imaging Suite / User Guide

k. Select the DHCP tab and enter a starting IP pool address one number higher than the NIC
LAN static IP.

l. Set size pool to 10 or higher. This indicates the number of IP addresses the DHCP server will
supply to clients.

m. Enter the Boot File name (pxeboot.n12).

n. Set the WINS/DNS Server to the LAN NIC’s static IP address. (Required for Imaging Client
name resolution)

o. Set the Default router to LAN NIC’s static IP address. (optional)

p. Set (Subnet) Mask to 255.255.255.0.

q. Enable Bind DHCP to this address, and set to the LAN NIC’s Static IP.

r. Click OK.

s. Close and restart TFTPD32.

NCR ©2017 All rights reserved. 23
NCR Imaging Suite / User Guide

Capturing an image over the Network

1. Create a new local folder on the server and share it. This folder will be used as a path to which images
will be captured.

2. Navigate to the .\ImagingSuite_X.X.X.X\Utilities\ folder.

3. Launch the Imaging Server application (ImagingServer.exe). If no other ImagingServer instances are
running, the session name will start automatically with “A”. The session ID will increment accordingly
with each additional ImagingServer instance that is started.

4. Select the Capture Image option.

Indicates
Session
Name

NCR ©2017 All rights reserved. 24

NCR Imaging Suite / User Guide

5. Click on the Choose Share button.

NCR ©2017 All rights reserved. 25

NCR Imaging Suite / User Guide

6. Select the share name created earlier in the drop down list.

7. Enter the user name and password used to access the shared folder, then click OK.

NCR ©2017 All rights reserved. 26

NCR Imaging Suite / User Guide

10. Set the Client Disk Number and Timeout fields to 0.

11. Click the Browse button, then browse to a path within the share. Enter a unique filename for the
captured image, then click Save.

12. (optional, recommended) If you would like for the image to include file integrity metadata, check the
Verify Data checkbox.
Note: This will slow the capture process, but will allow users to optionally verify file integrity while
files are being copied during an apply operation.

13. Click the Start button.

NCR ©2017 All rights reserved. 27

NCR Imaging Suite / User Guide

14. PXE Boot the Client Machine:

a. Connect a keyboard to the client machine.

b. Connect the client machine to LAN, then turn power the machine on.

c. Boot from the network PXE agent (press F12 on most systems). Windows PE will start
loading over the network, which may take some time.

d. Once booted to Windows PE, the Imaging Client application should start automatically.

e. Press the Connect to Server button.

NCR ©2017 All rights reserved. 28

NCR Imaging Suite / User Guide

f. Press the Join button for the server session to be connected to (in this example case, group
“A”).

g. The capture will then begin on the client, and its status will be shown on ImagingServer.

NCR ©2017 All rights reserved. 29

NCR Imaging Suite / User Guide

Applying an image over the Network

1. Create a new local folder on the server and share it. This folder will be used as a path from which images
will be applied to clients.

2. Navigate to the .\ImagingSuite_X.X.X.X\Utilities\ folder.

3. Launch the Imaging Server application (ImagingServer.exe). If no other ImagingServer instances are
running, the session name will start automatically with “A”. The session ID will increment accordingly
with each additional ImagingServer instance that is started.

4. Select the “Apply Image” option.

Indicates
Session
Name

NCR ©2017 All rights reserved. 30

NCR Imaging Suite / User Guide

5. Click on the Choose Share button.

6. Choose the share name that contains the image to be applied.

NCR ©2017 All rights reserved. 31

NCR Imaging Suite / User Guide

7. Enter the user name and password used to access the shared folder, then click OK.

8. Click the Browse button, then browse to an image within the share. Select a file, then click Open.

9. If imaging multiple clients, change the Clients field value under Start Options.

NCR ©2017 All rights reserved. 32

NCR Imaging Suite / User Guide

10. (optional) If you would like for the apply process to include verification of file integrity metadata, check
the Verify Data checkbox.
Note: This will slow the apply process.

11. Click on the Start button.

12. The image’s proprietary hash should now be validated prior to starting the session.

13. PXE Boot the Client Machine

a. Connect a keyboard to the client machine.

b. Connect the client machine to LAN, then turn power the machine on.

c. Boot from the network PXE agent (press F12 on most systems). Windows PE will start loading
over the network, which may take some time.

d. Once booted to Windows PE, the Imaging Client application should start automatically.

e. Press the Connect to Server button.

NCR ©2017 All rights reserved. 33

NCR Imaging Suite / User Guide

f. Press the Join button for the server session to be connected to (in this example case, group “A”).

g. The apply will then begin on the client, and its status will be shown on ImagingServer.

NCR ©2017 All rights reserved. 34

NCR Imaging Suite / User Guide

Command Line Options

The Imaging Server and Client applications accept command line options to help automate the imaging process.

Imaging Server Options

/mode=<A or C>
A – Apply Image
C – Capture Image

/group=<string>
A unique group ID to identify the server session for clients to connect to (Max length is 10 characters)

/disk=<N>
The disk index on the client to be applied to/captured from.

/file=<path>
The filepath (relative to the root of the share folder) to the file to apply, or the location where the capture will be
saved.

/sharename=<string>
The name and folder path of the share folder to be mapped for the imaging operation.

/username=<string>
The username used to access the network share.

/password=<string>
The password for the account credentials used to access the share folder.

/clients=N
The number of clients that are allowed to connect to sever session.

/wait=N
The maximum time, in minutes, to wait for clients to connect.

/confirm
The client must click confirm before operation will begin

Example:
Assumptions:
Folder Named “Share” is being shared.
Username = TestUser
Password = 12345
Image is located \\Share\Images\

ImagingServer.exe /mode=a /group=ABC /file=ExampleImage.wim /disk=0

/sharename=Share\Images /username=TestUser /password=12345 /clients=1
NCR ©2017 All rights reserved. 35
NCR Imaging Suite / User Guide

Imaging Client Options

/userjoin
Automatically join a server session (use /join to identify the server group to connect to.)

/join=<string>
A string to identify which server session to connect to (this string is case sensitive, and must match the group ID
of the server exactly).

Example:
Assumptions:
A server session has been launched with a group ID as ABC.

ImagingClient.exe /userjoin /join=ABC

NCR ©2017 All rights reserved. 36

NCR Imaging Suite / User Guide

Modifying an image file

It may be necessary at some point to modify your image file after it has been captured. ImageX image files
(.WIM’s) image can be “mounted” to your local drive and the contents browsed with windows explorer.

To mount a WIM file, one can use the DISM tool built into Windows 7 and 2008 R2 server from the command
line, or use a third party application to do the job. In this case, we are using a third party application named
DISM GUI that is available from the Microsoft CodePlex site: http://dismgui.codeplex.com.

Mounting an image using DISM GUI

1. Download and run the DISM GUI application as an administrator.

2. Create a scratch directory for where the image will be mounted to (for example, C:\Mount).

3. Next, select the image file (WIM) you wish to open.

NCR ©2017 All rights reserved. 37

NCR Imaging Suite / User Guide

4. To the right of the WIM File field, you will see an Index drop down. This selects the proper image or
image partition within the WIM file to mount.

 For most XP based images (XPE, WES, WEPOS, POSReady2009), you should select Index 1.
 For most Windows7, POSReady7, Windows 10, Server 2008/2012/2016 images, you should select
Index 2.

5. Click the Mount WIM button.

6. Under Mount Location, click on the Choose Folder button, and browse to the scratch directory you just
created.

The system will work for a few moments, and then display an operation completed message.

7. Click on the Open Mounted Folder button. This will open the scratch directory.

The actual image contents will be displayed. Make any needed changes to the image.
NCR ©2017 All rights reserved. 38
NCR Imaging Suite / User Guide

8. When finished, click on the Dismount WIM button.

9. When prompted to commit changes, select YES if you want to save your changes.

The system will save the modified image. This process may take a few minutes or longer depending on your
local hard drive speed.

**** Important Step****

After mounting any NCR WIM image, a new proprietary hash will need to be calculated to avoid a WIM
validity error during an apply operation.

To recalculate the hash, navigate to the .\ImagingSuite_X.X.X.X\Utilities folder and run the
ImageSigner application.

NCR ©2017 All rights reserved. 39

NCR Imaging Suite / User Guide

Browse to the recently mounted image file, and then click the Rehash button.

NCR ©2017 All rights reserved. 40

NCR Imaging Suite / User Guide

Mounting a WIM image file from the command line

1. Create a scratch directory for where the image will be mounted to (for example, C:\Mount).

2. Open an elevated Command Prompt.

3. Mount the desired image using the following command:

DISM.exe /Mount-Wim /WimFile:c:\imagelocation\imagefilename.wim

/Index:1 /MountDir:C:\Mount
/Index:1 is used for most XP Pro, WES, XPE, POSReady 2009 images.
/Index:2 is used for most Windows 7, POSReady 7, Server 2008/2012/2016, and Windows 10
images.

4. Once mounting is complete, navigate to the mount directory and make any needed changes.

5. When changes are complete, unmount the image using the following command:

DISM.exe /Unmount-Wim /MountDir:C:\mount /commit

If you do not wish to save your changes then use the following command:
DISM.exe /Unmount-Wim /MountDir:C:\mount /discard

6. If you received and error unmounting the image, run the following command:

DISM.exe /Cleanup-Wim

**** Important Step****

After mounting any NCR WIM image, a new proprietary hash will need to be calculated to avoid a WIM
validity error during an apply operation.

To recalculate the hash, navigate to the .\ImagingSuite_X.X.X.X\Utilities folder and run the
ImageSigner application.

NCR ©2017 All rights reserved. 41

NCR Imaging Suite / User Guide

Browse to the recently mounted image file, and then click the Rehash button.

NCR ©2017 All rights reserved. 42

NCR Imaging Suite / User Guide

Customizing the PE Boot Image

The PE boot image can be customized to perform various actions when loaded. One can modify the WinPE
startup sequence to execute custom commands, such as automatically map network resources, running
specific programs, or using a program selection script.

The WinPE boot image file (boot.wim) calls a command file named startnet.cmd that is called when
WinPE starts. This file can be edited to add custom startup actions.

Mount the Windows PE boot.wim file

To modify the command file, the WinPE boot.wim file must first be mounted. To do this, use the DISM GUI
application, or use the DISM.exe tool from an elevated command prompt on a system running at least
Windows 7, 2008 Server R2, or later.

DISM GUI Example:

NCR ©2017 All rights reserved. 43

NCR Imaging Suite / User Guide

Elevated Command Prompt Example:

DISM.exe /Mount-Wim /WimFile:C:\ImagingSuite_X.X.X.X\sources\boot.wim

/Index:1 /MountDir:C:\mount

Editing the startnet.cmd file

Once boot.wim is mounted, open the mount directory, and navigate to startnet.cmd. It can be found in
.\Windows\System32.

startnet.cmd can be edited in a text editor of your choice.

The default contents of the file:

Example customizations
 Add lines to map to a network share
wpeinit

@ECHO OFF

set path=%path%;X:\ImagingTools
ImagingClient.exe

REM Automatically map to a single or multiple drive shares on WinPE bootup:

net use H: \\YourServerName\YourSharename /user:username password
net use I: \\YourServerName\YourSharename /user:username password
net use J: \\YourServerName\YourSharename /user:username password

NCR ©2017 All rights reserved. 44

NCR Imaging Suite / User Guide

 Add a customized selection menu

wpeinit

@ECHO OFF
set path=%path%;X:\ImagingTools

REM Automatically map to a drive share on WinPE bootup le:

net use H: \\YourServerName\YourSharename /user:username password

REM Use a custom menu to launch apps, reboot or shutdown client from within WinPE
:MENU
cls
ECHO.
ECHO ===============================================
ECHO.
ECHO Please select the desired program, or press 5 to EXIT Menu.
ECHO.
ECHO.===============================================
ECHO.
ECHO.
ECHO 1 - Run Ghost32
ECHO 2 - Start Imaging Client
ECHO 3 - Reboot System
ECHO 4 - Shutdown System
ECHO 5 - EXIT
ECHO.
ECHO.

SET /P a=Select desired option then press ENTER:

IF %a%==1 GOTO GHOST
IF %a%==2 GOTO IMAGINGCLIENT
IF %a%==3 GOTO REBOOT
IF %a%==4 GOTO SHUTDOWN
IF %a%==5 GOTO EXIT

:GHOST
REM Symantec Ghost32.exe can be run from mapped drive.
cd /d H:\YourDirectoryLocation of Ghost32.exe
ghost32.exe

NCR ©2017 All rights reserved. 45

NCR Imaging Suite / User Guide

goto MENU

:IMAGINGCLIENT
X:
ImagingClient
goto MENU

:REBOOT
X:
wpeutil reboot
goto MENU

:SHUTDOWN
X:
wpeutil shutdown
goto MENU

:EXIT
break

Once all customizations have been added, save the startnet.cmd file, and close the mount folder.

Using DISM GUI, unmount boot.wim and choose to commit the changes, or from an elevated
Command Prompt, run:
DISM /Unmount-Wim /MountDir:C:\mount /commit

Boot customization is completed. There is no need to recalculate a proprietary hash for the boot WIM.

NCR ©2017 All rights reserved. 46

NCR Imaging Suite / User Guide

Updating Recovery Tool

The Imaging Suite can update the Recovery Tool on a POS terminal to the latest version. There are two supported
methods of updating the Recovery Tool without reimaging the terminal.

Note: There is no need to update the Recovery Tool to a later version unless a new feature was added that you
wish to use.

Requirements
 USB drive that is 2GB or greater

From within the Recovery Tool

1. Navigate to .\ImagingSuite_X.X.X.X\Recovery_Update\Legacy in the latest Imaging Suite
package.
2. Copy Recovery.wim and Recovery.signature to a USB drive.
3. Attach USB drive to POS.
4. Enter Recovery on POS by pressing the recovery button, or F9 during the boot process.
5. Click the “Settings” button, and enter the configured password.
6. Select the Replace Recovery Image button, then choose the USB drive that contains the files.
7. The Recovery Update operation will prompt for confirmation, then will begin and notify the user when
complete.

From Windows
1. Copy the .\ImagingSuite_X.X.X.X\Recovery_Update folder to a USB drive.
2. While running Windows, attach the USB drive to the POS.
3. Launch .\ImagingSuite_X.X.X.X\Recovery_Update\RecoveryUpdate.exe.
4. Select physical disk 0.
5. Browse to .\ImagingSuite_X.X.X.X\Recovery_Update\Legacy\Recovery.wim.
6. Click the Update Recovery button.
7. The Recovery Update operation will begin and will prompt the user when complete.

NCR ©2017 All rights reserved. 47

NCR Imaging Suite / User Guide

RadsImageX

Overview
RadsImageX.exe is intended for use by application developers that have historically been using Microsoft’s
ImageX.exe.

RadsImageX was created as a simple, graphical replacement for Microsoft’s ImageX. At the time of initial
development, there were a few applications already using ImageX for image management. The intent for
RadsImageX was to be backward compatible with the existing ImageX command line parameters and the WIMs
already created by these supported applications while still providing the additional image features available in
the full NCR Imaging Suite.

The documentation below references use of ImageX command lines with which RadsImageX is backward
compatible; however, it is highly recommended to use the new, enhanced RadsImageX command line which
provides additional features and will always use the enhanced NCR WIM format.

Major Differences from ImageX

Whole Disk Support
ImageX operates on disk partitions, so capturing an image with ImageX typically meant capturing only the OS
partition of any given system. For Windows 7 systems in particular, this was problematic because the System
partition would not be saved or restored. The NCR Imaging Suite captures and applies an entire disk including
the partition table, OS loader, etc.

Incremental Backups: Image Slots

ImageX has support for incremental storage of new images using the Append operation and the concept of
“slots” in the image. Slots are indexed by name or number and are specified on the command line. RadsImageX
wraps this concept with some pre-named slots called Factory, Site and User. This restricts the number of slots
available in the image, but gives a logical association to each as a suggestion to the caller of how each slot could
be used in a Retail or Hospitality environment.
When supporting legacy ImageX command lines, which would never mention an NCR named slot, the User slot is
always chosen. RadsImageX specific command line options allow selection of any slot.

NCR ©2017 All rights reserved. 48

NCR Imaging Suite / User Guide

Capture/Append Operations
RadsImageX Enhanced Command Line
Command Line:
RadsImageX.exe </capture | /append> <disk num> <image filename> <slot name>
[description]

Where:
- <disk num> is the physical disk number whose partitions are to be captured. This number can be seen
from Disk Management or DiskPart.
- <image filename> is the fully qualified path of the WIM file to which to capture/append.
- <slot name> is the name of the slot to which to capture. This can be “Site” or “User”.

Sample usage:
RadsImageX.exe /append 0 F:\backup.wim Site

This operation will capture the contents of physical disk 0 into the “Site” slot of the existing WIM file
F:\backup.wim.

The difference in /capture and /append is that /capture uses the WIM_CREATE_ALWAYS flag instead of the
WIM_OPEN_EXISTING flag. It is important to use the correct flag based on whether the file already exists or
not. If /capture is used on an existing WIM file, its existing contents will be lost. If /append is used on a non-
existent WIM file, the operation will fail because the file does not exist.

Note: RadsImageX will not capture or append to the Factory slot of a WIM file. This is disallowed to prevent
interference with the Factory slot that exists in WIMs directly from NCR manufacturing. Applying from the
Factory slot is, of course, allowed and is described in a later section.

ImageX Style Command Line

Command Line:
RadsImageX.exe </capture | /append> <source path> <dest filename> <slot name>
[description]

Sample usage:
RadsImageX.exe /append C: F:\backup.wim backup

This operation will append the contents of the C: volume in the WIM file F:\backup.wim and name the image
“backup”.
Note: If capturing to a new WIM file, or appending to a WIM that already contains an image that was captured
using the NCR Imaging Suite (e.g. a WIM that has a manufacturing factory image in it), the <slot name> field is
ignored, and is instead captured into our “User” slot.

NCR ©2017 All rights reserved. 49

NCR Imaging Suite / User Guide

Apply Operation
RadsImageX Enhanced Command Line

RadsImageX.exe /apply <image filename> <slot name> <disk num>

Where:
- <image filename> is the fully qualified path of the WIM file to apply
- <slot name> is the name of the slot to apply. This can be the following: Site, User or Factory
- <disk num> is the physical disk number to which to apply the image. This number can be seen from
Disk Management or DiskPart.

Sample usage:
RadsImageX.exe /apply F:\backup.wim Factory 0

This operation applies the Factory slot from WIM F:\backup.wim onto disk 0. In the case of a signed WIM, the
Recovery Partition type specified in the metadata of the WIM will be created.

ImageX Style Command Line

Command Line:
RadsImageX.exe /apply <image filename> <index number> <destination path>

Sample usage:
RadsImageX.exe /apply F:\backup.wim 1 C:

The behavior of this operation will vary depending on whether <image filename> points to a generic WIM or
one that was captured using the NCR Imaging Suite.

If <image filename> refers to a generic WIM captured with ImageX, this operation applies the contents of the
first index contained in F:\backup.wim onto the C: partition.

If <image filename> refers to a WIM created with the NCR Imaging Suite or with RadsImageX using
/capture (instead of /append), multiple, named image slots may be available. Because the original ImageX
command line does not specify this slot name, a priority scheme will determine which slot to apply. From
highest to lowest priority, the first slot that exists in the WIM will be applied: User, Site, Factory.

NCR ©2017 All rights reserved. 50

NCR Imaging Suite / User Guide

UEFI / Secure Boot Operation

Imaging Suite and Recovery version 4.0.0.0 and later support UEFI and Secure Boot operations on NCR POS
terminals with these options. There are some minor changes to the way these tools are configured when the
POS is booting in UEFI or Secure Boot mode.

***Important***
These steps only apply on a terminal that has been reconfigured for UEFI or Secure Boot. NCR Terminals ship
configured in Legacy boot mode.

Legacy Images Are Compatible

There are no changes needed for existing images to be applied to UEFI or Legacy boot mode systems. An image
captured on a terminal configured in either boot mode can be applied to a terminal configured in the other boot
mode.

Once an image is applied, the boot mode on that terminal cannot be changed without reapplying the original
image. Without reimaging, neither the Windows image nor Recovery Tool will boot properly.

NCR ©2017 All rights reserved. 51

NCR Imaging Suite / User Guide

Changes to MakeBootablePeDisk
When creating a bootable USB drive for a POS that has been configured for UEFI boot, check the UEFI 64-bit
checkbox above the boot.wim path.

If your POS is configured for Secure Boot, you must temporarily disable Secure Boot to boot to the Imaging Suite
bootable USB drive. All other UEFI and Compatibility Support Mode settings can remain the same. Secure Boot
can be re-enabled after your imaging operation is complete.

NCR ©2017 All rights reserved. 52

NCR Imaging Suite / User Guide

Changes to TFTPD32 (PXE BOOT)

When PXE/Network booting a terminal in UEFI mode, the boot image must be changed to the 64-bit, UEFI
compatible boot image.

To make this easier, two separate configurations of TFTPD32 are included with Imaging Suite.

1. Navigate to .\ImagingSuite_X.X.X.X\PXEBOOT-WINPE\UEFI.
2. Run tftpd32.exe.
3. Change Current Directory to .\ImagingSuite_X.X.X.X\PXEBOOT-WINPE\UEFI

4. Press the Settings button, then browse to the DHCP tab.

NCR ©2017 All rights reserved. 53

NCR Imaging Suite / User Guide

5. Change Boot File to bootx64.0.

Changes to Recovery Update

When updating Recovery from within the Recovery Tool, copy Recovery.wim and Recovery.signature
from .\ImagingSuite_X.X.X.X\Recovery_Update\UEFI instead of the Legacy subfolder.

When updating Recovery from Windows, launch RecoveryUpdate.exe and browse to

.\ImagingSuite_X.X.X.X\Recovery_Update\UEFI\Recovery.wim instead of
.\Legacy\Recovery.wim.

NCR ©2017 All rights reserved. 54