If I can import, how do you deploy them in the same manner that imagex would use the images internal answer file using WDT
The simple answer : Yes, intsall.wim files will be compatable between MDT and WDS.
The honest truth : Build a share for building images, and use a second share for production.
People commonly confuse WDS (Windows Deployment Services) and MDT (Microsoft Deployment Toolkit) The alphabet soup of windows deployment can be confusing, but you probably don't need WDS just yet.
You'd really only need WDS for PXE booting.
I highly recommend using MDT to build, capture, and deploy images. MDT uses task sequences, and boot images in combination with install images. If you use a VM to build your reference, you can build a "hardware independent" image that'll run on everything, laptops, desktops, Dell, HP, Lenovo, whatever.
A quick overview of what you would do in the MDT workbench
Download & Install MDT 2012 Update 1 -
Download Win7 AIK -
Create Deployment Share -
Import Drivers -
You would import the existing .wim file from your old imagex days into the Deployment Workbench under Operating Systems.
Create a task sequence and import your .wim file
You would then launch the Windows System Image Manager from the Task Sequence Properties OS Info Tab.
Update the deployment share
Upload boot image from MDT into WDS -
Theoretically, it'll load the same unattend.xml, if not you should be able to reimport your old answer files in WSIM. If not, you may have some luck copying the answer file over manually into the deployment share control folder, but I wouldn't recommend trying that.
Learning MDT is highly rewarding, and it takes some time, but it really pays off. Once I really understood MDT, my company went from 12 images to 1. Currently we can image, provision, join to the network, and update in less than 30 min.
Deployment Soup Video
Deploying Windows A - Z
Learning to use MDT litetouch