MDT & SAMSUNG ATIV Smart PC Tablet Part 1

Last week i was playing with Samsung ATIV Smart PC.

Samsung ATIV Smart PC is a great device. This is one of many Touch laptops from Samsung. This Laptop is also usable as Tablet PC. Because it run Windows 8 x86 you can run al your applications on this device.

De Samsung ATIV Smart PC does not have fast Ethernet nic onboard only a Wifi NIC.

I would like to deploy our company “image” to this device.

1. Download Software Update

2. Install Software

3. Search for XE500T1C-A01NL

4. Download al the Drivers and Software

5. Extract all Packages en sort this in Driver and Applications

6. Import the drivers in MDT

7. You need the a NIC I uses the USB 2.0 to Gigabit Ethernet NIC Network Adapter

8. Download the Driver

9. You find after unpacking in de Windows Folder de driver LAN7500-WDF-v1.2.0.0.exe

10. You can Extract the Driver with “LAN7500-WDF-v1.2.0.0.exe /extract d:\downloads\LAN7500”

11. Import the Drivers in to same Driver Store als descripted in 6.

12. Update Deployment Share Wizard

13. Create A Task Sequence

14. Create a selection Profile descripted here: MDT 2010 Importing automatically the right driver

15. Change import driver on the Task Sequence

16. You need at Least a 4GB USB Stick

17. Format the USB stick with FAT32 How to create a bootable USB drive from an ISO image for UEFI systems

18. Mark the partition als Active
1.Open Command Prompt

2 Type: diskpart

3. At the DISKPART prompt, type: list partition

Make note of the number of the partition that you want to mark as active.

4. At the DISKPART prompt, type:

select partition n

Select the partition, n, you want to mark as active.

5. At the DISKPART prompt, type: active

19. If you’re on Windows 8, double-click your ISO image to mount it. If you’re on earlier versions of Windows, use a 3rd party utility to mount the ISO. Just search the web and you’ll find options. Or, burn the ISO to a DVD and then mount it. Once the ISO is mounted, copy all files and directories over to your newly formatted USB drive by dragging and dropping. You can also do this from the command line using robocopy or xcopy.

20. Delete the install.wim and boot.wim from the sources directory

21. Copy LiteTouchPE_x86.wim from the Boot directory on the MDT server to de Sources Map on the USB Stick

22. Rename LiteTouchPE_x86.wim to boot.wim

23. Disable Secure Boot:

24. Boot From USB

25. You Can deploy now your OS to your Tablet.

Part Two I will write about installing Touch Driver Software/Driver

2012 Blogging

This blog was viewed about 110,000 times in 2012. If it were a concert at the Barclays Center, it would take about 6 sold-out performances for that many people to see it.
In 2012, there were 88 new posts, growing the total archive of this blog to 485 posts.
The busiest day of the year was March 13th with 616 views. The most popular post that day was Exchange 2010 Opening multiple shared calendars & additional mailboxes.

These are the posts that got the most views in 2012. You can see all of the year’s most-viewed posts in your Site Stats.


MDT 2012 Settings Per Task Sequence

I recently converted to MDT 2012 after running MDT 2010 for awhile. 10 December 2010 I blogged about MDT 2010 Automatically Move Computers to the Right OU.

After I upgraded from MDT 2010 to MDT 2012 this did not work anymore.

After a lot of searching a found the following on the Technet Forum at the MDT section: MDT 2012 – Settings Per Task Sequence

I changed DeployWiz_SelectTS.vbs file and it work again Glimlach

1. Edit DeployWiz_SelectTS.vbs
2. Add after "Dim sTemplate"
Dim sCmd
Set Oshell = createObject("")
3. Add before "End Function" (bottom of page)
sCmd = "wscript.exe """ & oUtility.ScriptDir & "\ZTIGather.wsf"""
oItem = oSHell.Run(sCmd, , true)

You can download the changed  file here: DeployWiz_SelectTS.7z

Update 12-09-2012
In beta 1 MDT 2012 Update 1 this was fixed Glimlach. But in de final release MDT 2012 Update 1 this is still a issue….. Bedroefde emoticon but no error anymore at the final page Glimlach.

MDT 2012 Beta 2 Monitoring

Today I upgraded a MDT 2010 installation to MDT 2012 Beta 2.

One of the new features is monitoring Glimlach

To Configure monitoring you find a tab Monitoring on properties of the Deployment Share.
You must set a V Enable monitoring of this deployment share


Under the root of the Deployment Share u see now Monitoring. When you click on Monitoring you can see running deployments.


Optimizing Windows 7 Images for use in VDI

One of our MCS deployment guys in the UK – Jonathan Bennett (you may know Jonathan as the author of the autoit tools and GImageX) has developed a tool for configuring Windows 7/Windows Vista/Server 2008 images for use in a VDI environment. The tool called VDI Optimizer outputs a VBScript (based on the selections you make in the GUI interface), which can then be used to apply performance and configuration settings to images that will be deployed via VDI platforms – this is particularly useful if you are using MDT 2010 for your image engineering process as the VBScript can bolted into the task sequence using a Run Command Line task.


You can make machine based selections for turning off services and functions that may not be required when the operating system is running in a VDI environment such as hibernation, system restore, and background defrag, as well as adjusting some user based settings such as visual effects, font smoothing and off-screen composition for Internet Explorer.

The beta of this tool is available from but please remember The tool is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation.

Source: Optimizing Windows 7 images for use in VDI

MDT 2010 WSUS deployment Error 0x80244019

I added so as always WSUSServer=http://ward-bh01 to customsettings.ini

When the deploying the image I get de following error

The Error



Ad the Port number to de WSUSServer address in customsettings.ini. In my case it was 8530. Because the WSUS site was running on that port number see the pictures



Microsoft Deployment Toolkit (MDT) 2012 Beta 1 Available

Microsoft has just released as a public beta the newest version of Microsoft Deployment Toolkit (MDT) 2012 with a few important updates:

  • Supporting System Center Configuration Manager (SCCM) 2012.
  • Using Lite Touch Installation (LTI), great improvements in the client side look-n-feel.
  • Also for LTI, behind-the-scenes enhancements for partitioning, UEFI (Unified Extensible Firmware Interface), and user state migration.
  • Some minor bugs fixed.

MDT 2012 Requirements

Same as MDT 2010:

  • Windows Automated Installation Kit (WAIK) 2.0. You can download it from here.
    Note: The download page indicates that the WAIK version is “1”; but don’t worry, the actual version is 2.0.
  • MSXML 6.0
  • PowerShell.
  • .Net Framework 3.5 SP1. Available for download here.
    Note: Even though .Net Framework 2.5 SP1 is not a requirement for MDT 2010 installation; one of its features, User-Driven Installation (UDI), does requires the latest Microsoft Framework installed.

MDT 2012 Look-n-Feel

For what I’ve seen so far, the user experience of the Deployment Workbench console is pretty much the same.



MDT 2012 Beta 1 Download

The beta is available in this link from Microsoft Connect,

Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1

With the release of the Windows AIK for Windows 7 SP1 supplement (see Windows AIK for Windows 7 SP1 Released for details), there is a new version 3.1 version of Windows PE available. If you plan to install this update, you need to be aware of an issue when using this with MDT 2010 Update 1.

With MDT 2010, Deployment Workbench will look for a “boot.wim” file from one of the imported operating systems that has the same build number as Windows AIK (e.g. “boot.wim” from a Windows 7 RC, build 7100, operating system to go with the Windows AIK for Windows 7 RC). If it finds a match, it will use that WIM instead. Why do we do this? Because the “boot.wim” contains the Windows Recovery Environment (Windows RE), a component that isn’t available in Windows AIK.

So let’s get a little more specific. First, some background details:

  • The build number for the RTM version of Windows 7 is 6.1.7600.16385.
  • The build number for Windows AIK for Windows 7, released with Windows 7 RTM, is also 6.1.7600.16385. This is stored in the registry.
  • The build number for Windows 7 SP1 is 6.1.7601.17514.
  • The build number for the files included in the Windows 7 AIK for Windows 7 SP1 supplement, including Windows PE 3.1 and all the Windows PE feature packs, is also 6.1.7601.17514. But since this supplement is installed by replacing files in the Windows AIK installation directory using XCOPY, the registry isn’t updated so MDT still thinks the Windows 7 RTM version (6.1.7600.16385) of Windows AIK is installed.

Now, let’s assume that you have Windows 7 RTM x86 installation files present in your deployment share, and you haven’t installed the Windows 7 AIK for Windows 7 SP1 supplement. MDT’s processing when creating a boot image will look like this:

  • Is there a boot.wim available with the same version number as Windows AIK (6.1.7600.16385 = 6.1.7600.13685)? Yes, copy it to a temporary folder and mount it.
  • Inject the required Windows PE optional components from the Windows AIK installation directory into this mounted boot image.
  • Inject the needed MDT scripts.
  • Commit the changes to the WIM file and copy it to the deployment share.

Now, install the Windows 7 AIK for Windows 7 SP1 supplement and update the deployment share:

  • Is there a boot.wim available with the same version number as Windows AIK (6.1.7600.16385 = 6.1.7600.13685)? Yes (because MDT doesn’t know that Windows AIK has been updated, the registry still says it is version 6.1.7600.16385), copy it to a temporary folder and mount it.
  • Try to Inject the required Windows PE feature packs from the Windows AIK installation directory into this mounted boot image. All fail, because they are for Windows PE 3.1 and won’t work with the Windows PE 3.0 boot image copied from the Windows 7 RTM files.
  • Stop.

The actual error will look something like this (repeated for each Windows PE feature pack):

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Processing 1 of 1 – Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.1.7601.17514
Error: 0x800f081e
The specified package is not applicable to this image.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = –2146498530
DISM /Add-Package failed for component C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\, rc = -2146498530.


Modify the Settings.xml file in the deployment share’s “Control” folder to tell MDT to never use the boot.wim. The settings look like this:


They should be changed to instead say:


As a result of this change, MDT will no longer use the boot.wim from the Windows 7 RTM installation files. Instead, it will always use the winpe.wim from Windows AIK. And since the Windows PE feature packs in Windows AIK should always match the winpe.wim in Windows AIK, this will always work.

Note that this will never be an issue with MDT-generated boot images used with ConfigMgr 2007, as MDT will always use the winpe.wim from Windows AIK when generating these. (ConfigMgr 2007 doesn’t yet support Windows PE 3.1, so don’t install the Windows AIK for Windows 7 SP1 supplement yet if you are using ConfigMgr.)

More info check: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Deploy office 2010 and a previous office version together on one PC with MDT 2010

Deploy office 2010 and  a previous office version together on one PC with MDT 2010. Then you need to do the following things

– Office 2010 ISO
Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool

1. Make sure you have a working Office 2007 deployment. Check this How to deploy Office 2007 with MDT

2. Extract the Office 2010 ISO to the application folder on de MDT Server

2. Extract AdminTemplates_32.exe or AdminTemplates_64.exe to a folder.

3. Copy the Admin folder that you can find in the extracted folder to the Office 2010 folder that you created at step 1.

4. Run setup.exe /admin

5. Check the Screenshots for the settings

6. Save the file in Updates folder that you find in Office folder. I named the file setup.MSP

7. Create a new application without source files.


Command Line is:
setup.exe /adminfile “\\mdtservername\deploymentshare$\Applications\Microsoft Office 2010 x86\Updates\setup.msp

Translate »