MDT

You are currently browsing the archive for the MDT category.

Friend of mine found it, online, somewhere… :) … but here it is, Very useful for me at this moment

For download: MDTAppsSort

Yeah, I found it somewhere out there, but who knows where at this moment.
Anyways, good info so … here it goes:

The Windows Automated Installation Kit (WAIK) includes the Imagex utility, which, in addition to facilitating the capture and deployment of WIM images, can also be used to mount a WIM file so that you can access its content.

But before you can mount a WIM file, you need to install the WIM File System Filter, which is responsible for handling all file system requests to the mounted WIM file, enabling browsing and editing of its contents. To install the WIM File System Filter, navigate to the C:\Program Files\Windows AIK\Tools\x86 folder, right-click wimfltr.inf, and select Install. This will install and activate the wimfltr.sys file system filter.

After you install the WIM File System Filter, you can mount a WIM by following these steps:

1. Create a folder on the file system that will be used to access the WIM file content (e.g., d:\vistamount).

2. Start a command prompt with Administrative credentials (Start, Programs, Accessories; right-click Command Prompt and select “Run as administrator”).

3. Navigate to the C:\Program Files\Windows AIK\Tools\x86 folder on a machine with WAIK installed (assuming you’re running on an x86 architecture box).

4. Run the Imagex command with the /mount switch to open the WIM file in read-only mode or the /mountrw switch to open with full read and write abilities. Use the following command syntax: imagex
For example, to mount the first image of the standard Vista install.wim file to path d:\vistamount, use the following command:

C:\Program Files\Windows AIK\Tools\x86>imagex /mountrw d:\Sources\install.wim 1 d:\vistamount

You can then modify the WIM file via standard file system manipulation tools, such as the command prompt and Windows Explorer.

Once editing is complete, unmount using the Imagex utility with the /unmount switch, and if you wish to keep the changes made also add the /commit switch (if you don’t specify the /commit switch, all changes will be lost, and you won’t be prompted for confirmation). Unmounting without the /commit switch is significantly faster because it doesn’t have to convert file system changes to the relevant area inside the WIM file.

When you deploy your image using WinPE, it creates nice log under:
c:\Windows\temp\DeploymentsLogs

One TIP for whoever will read this, is:
Download “SMS 2003 Toolkit 2″ and check out “SMS Trace”.

If you want to analyze any of the logs, they are presented to you in human-readable form.

You will find out more small little useful applications, once you install the toolkit.

Ok, It took me, 4h to google for answer… but finally I found something what made me happy.

I installed Windows DS on my Win2003 server. Configured. As I have already WinPE .wim, we created it using MDT, I just imported it to WDS.

When I booted my client machine, I got this error:
TFTP
PXE-T01: File not found
PXE-E3B: TFTP Error - File Not Found

Was not sure what is going on, I tried a few things, solution/comments I found googling…

…and then from Microsoft TechNet Forums:

So, what’s probably going on here is that your x64 VM is reporting itself as x86. This is a common problem and can cause this kind of error.

You can work around it as you say by adding a 32-bit WinPE, or by turning on Architecture Discovery using
WDSUTIL /Set-Server /ArchitectureDiscovery:Yes

I turned on Architecture Discovery, and it worked for me, my client machine booted into our WinPE.

Trying to find out “Make and Model” of machines in your enviroment so you could correctly enter those in MDT database?

You can do this two ways:

1) Using Power shell

Get-WmiObject Win32_ComputerSystem

2) Using WMIC.EXE

wmic.exe csproduct get name,vendor

If you use DRIVERPATHS1=\\pathtoshare\%model% variable in your customsettings.ini then you have to create specific Folders with the exact name of the Model for the machine. Then you can copy to the folders the specific drivers for that Model, and later on WinPE will take care of it, its way :)

It’s nice.

Locations of visitors to this page