Can't use as backup tool - Windows Client | Microsoft Docs

Looking for:

- Is there a ImageX version for Windows 10 - Microsoft Community 

Click here to DOWNLOAD

     

Imagex windows 10

 

Although it mentions Windows 10, the same steps will work for Windows 7, 8 and 8. For help with capturing the image, refer to the following Community article:. The file is in the ProvImageX. Click Tools at the top of the window then click Install Scripts. In the Install scripts window, click the Browse button and browse to the folder where the Winx64Unattend. In the Script name box, enter a name for this unattend file to uniquely identify it. In the Description box, enter a description if desired.

Select Windows for the Target operating system. Click the Import button to import the unattend file into the database. The Script name will appear in the Install scripts list if it is successful. Copy the provisioning template DeployWin10ImageX. The template is in the ProvImageX. Click the Import templates icon along the top of the Operating sytem provisioning tool. Click the Browse button in the Import templates window and browse to the location where the template was copied in step 1 and select it.

Click the Close button in the Import templates window. The template name can be changed after it is imported. In the Operating system provisioning tool, double-click the provisioning template that was imported in the Provisioning templates My templates All my templates folder. Expand the OS-installation section of the template and click on the Deploy Image action.

Make sure that ImageX is selected for the image type. Enter the UNC path including the filename to the Windows 10 image to be deployed. The file will have a. WIM extension. Click the Validate button which updates the Command-line then click Apply.

Click on the Inject unattend file action under the Post-OS installation section of the template. Select the unattend. If the OS being deployed already has the drivers for the computer to be imaged or you are not planning on using LANDESK Hardware independent imaging, the Hardware independent imaging action can be deleted from the template in the Post-OS installation and System configuration sections.

Add additional actions to the template if desired. Do this by right-clicking the section of the template and select the Add Action option.

There is an action to join the domain and an action to run software distribution packages as well as many others. After adding any actions, be sure to click the Apply button. Click OK to save the changes to the template.

In the Operating system provisioning tool, click on Provisioning templates in the left pane. Click Tools and click Public Variables. The public variables shown in the screenshot above are there by default. The Replace value for the variables corename and coreIP can be changed if needed but do not change the Search value variable name for them or it will break provisioning.

The Search values are case-sensitive. Enter AdminPass in the Search value box. This variable is used in the unattend. Select Sensitive data from the Type drop-down list. In the Replacement value and Confirm replacement value boxes, enter the password which will be assigned to the local Administrator account on the computer when the image is deployed.

AdminPass now shows up in the Public variables window. Enter WinProdKey in the Search value box. Select String from the Type drop-down list. Enter the Windows 10 product key in the Replacement value box.

Enter Company in the Search value box. Enter your Company name in the Replacement value box. Click OK to close the Public variables window.

This step can be skipped if the HII actions were deleted from the template. In the Add bare metal device window, select MAC address for the Identifier type from the drop-down list. Click the Add button. In the Bare Metal Device window, enter a name for the device in the Name box.

The name entered will be the computers name after it is imaged. The MAC address will show up in Server identifiers. Click OK. The computer added will show up in the Add a bare metal device window. Setup a preferred server for the computer where the image share is located if it has not already been done.

This is reflected in the example below. In the example below we will switch to the drive containing our WindowsPE disc and then to the directory containing ImageX.

We then use net use to connect to a network share to store the image on. Alternatively you could use an external hard drive to capture the image. We then run ImageX to capture the image of the reference computer. Dependent on your situation you may need to prep the hard drive of the target computer. Boot the target computer using your WindowsPE disc and follow the commands below.

This will erase the drive and format it to receive the image. If your target drive is already formatted appropriately you can skip this step. We then use net use to connect to a network share where the image is stored. We then run ImageX to deploy the image to the target computer.

If you experience this, reboot back into you WindowsPE environment and run the command below. Your target PC should now work fine. If you would like to experiment more and further customize your ImageX uses, I recommend the book below. It is a great resource for all the various switches, commands, and proper syntax structures. Windows 7 Portable Command Guide. Tags: cmd Guide image unattend. Thank you for the guide. Even though RAID 10 is in use, it is still one logical drive.

When I go to diskpart and type list disk or list volume, only my UFD shows up. Another question, where do I put the unattend. On the desktop? Diskpart should be able to see it when using the list disk command if the RAID is configured correctly.

What drive letter are you running Diskpart from in your setup? Thanks for the steps…. Can you clarify some things for me please? Is it possible to use imagex without sysprep? Was hoping to avoid using an instance of sysprep due to its 3 limit feature, and call sysprep once the generic image was actually on the physical PC. Windows typically has two partitions these days; Windows itself typically drive C and the hidden mb recovery partition. The very end of my article discusses how to regenerate and repair when this causes problems.

Basic install of Windows with all updates installed and our POS software installed as well. Thank you for this guide. Unfortunately, this does not allow Bitlocker to encrypt the hard drive with a captured image. It wants the partition used to boot and recover to be separate from the OS. How do I format it to allow bitlocker encryption to simply work? Your email address will not be published.