Link to home
Start Free TrialLog in
Avatar of BeallsDesktopTeam
BeallsDesktopTeam

asked on

Deploying Windows Embedded POSReady2009 with WDS and WDT

Hello,

I am currently working on a deployment solution using Windows Server 2012 R2 WDS with MDT 2013.

I can successfully capture the image on our registers but the issue I am having is capturing an additional "apps" partition labelled D:\

For a PC with Windows 7, I created a task sequence in MDT for Lite Touch to use imagex and capture the OS drive with the additional partition. This works without error and successfully captures and deploys the OS (C:\) and the extra partition (D:\) -- (I had to change c: to d: and d: to e: in the run command TS for this to work as WinPE changes the drive letters). This process of capturing the extra partition works fine in this scenario.

On our POSReady2009 machines, the task sequence fails at the "Capture 2nd Partition" sequence. WinPE does not seem to change the drive letters like on the Win 7 boxes. My task sequence is the same (changing back the drive letters of course). I first run FBReseal and it shuts down. I then boot to NIC and run the capture process. It successfully captures the C:\ drive but when it gets to the second partition capture, it fails with the error "LiteTouch deployment failed, return code = - 2147467259 0x80004005"
Failed to run the action: Capture D
This version of  is not compatible with the version of Windows your running. Check computer sys info (error: 8007008D; Source: Windows

My boot disk for this was created using the POSReady2009 install.wim and was converted to boot.wim for use with WDS. After successfully capturing the C: drive in POSReady2009, I am not understanding why it doesn't capture the D drive like its supposed to (obviously works fine on the OS because it captures C:). Again, this TS works fine elsewhere..

Any insight or help here will be greatly appreciated
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

you need an earlier version of MDT as MDT 2013 only supports Windows 7 and newer operating systems. FYI Mainstream support for this product has ended (it is based on Windows XP Pro)
Avatar of BeallsDesktopTeam
BeallsDesktopTeam

ASKER

OK.. So why does it successfully capture the OS C:\ drive if its not supported? Is it only the task sequence "run command" that I created that is not supported?
ASKER CERTIFIED SOLUTION
Avatar of BeallsDesktopTeam
BeallsDesktopTeam

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The simplest things often get overlooked..