I am running Windows Server 2012 R2 with MDT 2012, I installed the Windows 8 ADK before installing MDT 2012. I have created my Deployment Share and set everything up, but when I try to run the build it fails. I have included the error log bellow; FindFile: The file imagex.exe could not be found in any standard locations. LTIApply 09:54:30 0 (0x0000) FAILURE ( 5441 ): 1: FindFile: imagex.exe LTIApply 09:54:30 0 (0x0000) Command completed, return code = - LiteTouch 09:54:30 0 (0x0000) Litetouch deployment failed, Return Code = - 0x80004005 LiteTouch 09:54:30 0 (0x0000) For more information, consult the task sequencer log. LiteTouch 09:54:30 0 (0x0000) I see that it is unable to find the 'imagex.exe' file, where should this be located, and can I copy the file to the directory? Kind Regards.
Copy imagex.exe and wimgapi.dll (this may be optional, but I would still copy it) from the installation of ADK to the Tools x86 and Tools x64 directories in your deployment share. For example (using 8.1 ADK instead of 8 ADK, folder names may be slightly different) the default installation on Server 2012 R2 would be 'C: Program Files (x86) Windows Kit 8.1 Assessment and Deployment Kit Deployment Tools amd64 DISM' for the 64-bit imagex.exe and wimgapi.dll files.
And 'C: Program Files (x86) Windows Kit 8.1 Assessment and Deployment Kit Deployment Tools x86 DISM' for the 32-bit imagex.exe and wimgapi.dll files. These files would be copied to the appropriate folders in C: DeploymentShare Tools x64 and C: DeploymentShare Tools x86. This should resolve your problem. For whatever reason, MDT sometimes does not place all the needed files into the Tools folder when you create a deployment share.
Copy imagex.exe and wimgapi.dll (this may be optional, but I would still copy it) from the installation of ADK to the Tools x86 and Tools x64 directories in your deployment share. For example (using 8.1 ADK instead of 8 ADK, folder names may be slightly different) the default installation on Server 2012 R2 would be 'C: Program Files (x86) Windows Kit 8.1 Assessment and Deployment Kit Deployment Tools amd64 DISM' for the 64-bit imagex.exe and wimgapi.dll files. And 'C: Program Files (x86) Windows Kit 8.1 Assessment and Deployment Kit Deployment Tools x86 DISM' for the 32-bit imagex.exe and wimgapi.dll files. These files would be copied to the appropriate folders in C: DeploymentShare Tools x64 and C: DeploymentShare Tools x86. This should resolve your problem. For whatever reason, MDT sometimes does not place all the needed files into the Tools folder when you create a deployment share.
From GImageX is a graphical user interface for the ImageX tool from the Windows Automated Installation Kit v2.0 (WAIK). ImageX is used to capture and apply WIM images for Windows desktop deployments. It uses the Microsoft WIMGAPI API for working with WIM files. The ImageX GUI is a native application for the x86 and x64 platforms that will also work in Windows PE (WinPE). There is also a COM component version included that implements some of the basic functionality for direct use in languages such as VBScript.
From GImageX is a graphical user interface for the ImageX tool from the Windows Automated Installation Kit v2.0 (WAIK). ImageX is used to capture and apply WIM images for Windows desktop deployments.
It uses the Microsoft WIMGAPI API for working with WIM files. The ImageX GUI is a native application for the x86 and x64 platforms that will also work in Windows PE (WinPE).
There is also a COM component version included that implements some of the basic functionality for direct use in languages such as VBScript.
A recent email from a former asked, “ Is it possible to have you show me how to capture an image using Imagex?” My first thought was ‘Happy to aim you in the proper direction’. This is easy – wait – imageX is deprecated in Windows 8/8.1. DISM serves as the replacement tool in Windows 8/8.1. Technet documentation may be hard to follow. The entire process requires two or more days of a weeklong or deployment course to teach in detail.
While the overall process is rather simple, each step enables alternatives that can make the process appear far more complex. I describe each piece in my and provide updates in the Introduction subset of my. Microsoft also has a 2 minute overview video.
Lots of details to sort. Despite all the details, one can actually perform the entire capture process in about 30 minutes, if a couple of the steps are conducted simultaneously. For the sake of simplicity, let me set the stage. Let’s eliminate some of the alternatives. You want to capture an image of an installed and functional Windows Operating system.
The OS has current patches, drivers, and desired applications installed. It may also be network and domain attached. One or more user accounts may also be presented and configured. In other words, the system you plan to capture has all of the desired components installed and operational. (Microsoft documentation calls this a reference system.). You don’t plan to modify registry or driver settings during the capture process, or filter any system content.
You could use the System Image Manager (SIM) to create an ‘answer file’(typically named unattend.xml) or modify the.wim File Exclusion list to alter the image content during capture or deployment. You aren’t making any changes to your image during capture, so you avoid this step and use of the related tool(s). You are creating a new, single Windows Image (.wim) file.
You are not adding or appending information to an existing.wim file, or creating a differencing file. You don’t need to be concerned with numbering or naming of existing.wim indexed images, or overwriting, auditing, or confirming changes to an existing image. Since you are creating a single, unique image, you may use default options for numbering and labeling. You are not trying to capture a full image for diagnostic purposes. You could use the following process to capture an entire image, including security identifiers, MAC, host name, user data, temporary files and other unique information by skipping the Sysprep step. The captured image could not be multiply deployed without being modified first, but you could deploy it to a Virtual image for diagnostic purposes.
The capture steps are the same, but the deployment steps would be very different and might influence configuration switches that you use during capture. You have captured the unique identifiers, licenses, host name and other settings on the system before capture, or you are prepared to recreate them manually after you complete the capture process. Once you run Sysprep, the system will be generalized for capture and deployment. Minimally, basic installation and configuration questions will have to be answered once the captured system is rebooted before it can be used again in a production environment. Several manual or automated processes, not included in this blog would be necessary to capture system information, if you want to place it directly back into production after image capture. You have a technician system with either the or the installed.
You need the WAIK or the ADK installed on a system to get current copies of CopyPE, ImageX or DISM for image capture. These need to be installed on a technician’s system, and NOT on the system to be captured. You really don’t want all the WAIK or ADK content taking up space in your captured.wim file. You know the BIOS and OS image for the system being captured.
The WAIK and ADK tools within the suites are often specific to the BIOS platform, for instance Amd64, x86, arm. You need to be sure to use the correct tools or switches for compatibility with your target system(s).
Imagex.exe Download
Getting ready to capture that system image. Gather a set of DVD’s or an NTFS configured USB drive.
Imagex.exe Windows 7
Make sure you have identified a storage repository with 30-60 GB storage minimum for the captured.wim file. The high level process outline looks like the following: 1. Identify or select the system from which you want to capture a Windows Operating System image.
Use SYSPREP to prepare the system for capture. Run C: Windows System32 Sysprep Sysprep.exe and select the generalize and shutdown options. (Detailed information). Turn off the PC. Create Pre-Execution bootable media using the COPYPE command on the technician PC (with WAIK or ADK).
Launch the Deployment Tools Command Prompt with run as administrator. From the Deployment Tools command prompt run CopyPE.
Copype amd64 c: winpe64 ( Note: x86 or alternate switches might be needed if target is not a 64 bit system, and I selected the folder name to easily identify this as a Windows 64 PE image.). Once the PE file structure with boot files is created at c: winpe64, add tools like ImageX and DISM. Copy Imagex.exe from within the WAIK or ADK directory tools amd64 imagex.exe to c: winpe64 iso Copy other tools that you want on your PE media to the same folder. Use OSCDIMG.exe to create bootable PE media.
Oscdimg –n bC: winpe iso etfsboot.com c: winpe64 iso c: winpe64 winpe.iso Burn the winpe.iso image to bootable DVD or USB media using your preferred burning tool. (I wrote a prior blog offering simplified media creation alternatives ). Boot the system with the OS to be captured using the newly created PE media. Insert the PE media into the system to be captured.
(BIOS needs to point to the media location whether DVD or USB in the boot sequence so that it is recognized BEFORE the hard drive). Turn on the system. The system should boot to the Command prompt for PE, identified as X: 4. Prepare the media location to which the image will be captured. Map a Network Drive or. Prepare a CD or DVD or USB device to hold the image or. Select an alternate partition on the host system on which to write the.wim image file.
( NOT the C: drive). Note the letter for the image capture. We will call it “ W” but you may use any letter or path you desire other than X: or C.
Run ImageX with the capture command. Imagex /capture C: W: myimage.wim “My Capture Image” Choose your own.wim file name, and provide an internal index name that you can easily identify later. That’s the simple process. With Windows 8/8.1 and the ADK, you simple substitute DISM for ImageX, and the process works identically. For those who have taken our, the digital copy of the Microsoft Official Curriculum through Skillpipe offers DISM related examples within Module 2, Lesson 3 – Customizing and Preparing a Windows 8.1 image for deployment.
Hope to see you in the,. Staff Instructor.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |