Quick background.  I have Windows 7 working as a deployed OS.  I can also tell it to Capture and Save the User State, Deploy Windows 7 then put back the User Settings.  Which turned out waaaay easier than I expected.  My next challenge was to see if we could back up the User Settings on a Win XP machine.  Then deploy Windows 7 to a separate machine, and put those XP User settings back on.  This would be ideal as we have people moving from an old XP machine to a new Windows 7 machine. New Machine. New OS.  The catch now is, I can't get MDT to back up settings to the network.  I followed the directions to set the Network and path in the CS.ini file, and even tried creating the separate task sequence for "capture only", but no file end up in the specified network folder.  If I run a normal deployment and tell it to capture to the network, the progress bar says it's doing it.  But no files :(  If I run the "Capture only" sequence, it doesn't run and all and immediately pops up saying it's done.  Also no files.  Is what I'm wanting possible? And what did I miss to send the capture User State to the network? Below is my cs.ini if it helps.  I edited out the server and passwords.

I am getting the below error when trying to replicate to a linked deployment share

Starting MDT Linked Deployment Share Update

The deployment share at "'\\%servername%\deploy$' cannot be opened because it needs to be upgraded. the version of the deployment share is 0.0.0.0 while the required version is 5.0.1641.0.

The specified Drive Path does not exist.

Any ideas?

Hi,

Does anyone know any registry settings that will make Microsoft lync 2013 load faster on windows 8 x64?

Thanks,

Bobby

Hello All,

I already use MDT 2012 for OSD via SCCM 2007 with a little bit of RND and would like to explore the scripts that is already present in MDT. I got some help from the Documentation library that we get when we install MDT but I am looking for a granular level help, where I can see where I should include this script in a TS and what configs should I have already done before executing a script. so, if there is a scripts roadmap or flow graph for the inbuilt MDT scripts that I can refer to, it would be of great help.

Arun

What credentails does UDShare use in the customsettings.ini file for MDT 2012?  USMT backup works and stores on the network if I use a share located on the deployment server but if i set the location to a different server and am logged in as a network user i can backup to the selected path but upon image refresh it obviously doesnt have the path mapped and therefore it never restores user data from my custom location.

Example my deployment share is located on wds.contoso.com.  If i have UDShare=\\wds.contoso.com\backups\userdata it creates the USMT backup just fine.  If i change the UDShare to be \\fs.OTHERDOM.com\userdata.  When I login to the client with a domain user it will backup fine and create usmt data on \\fs.otherdom.com\userdata but when it does its refresh of the image and gets back into windows under the build in administrator account automaticly it tries to restore user data but it never works. I dont seem to get an error but it never restores any data.

How can I have a custom path with perhaps a different set of credentails to connect to for the UDShare location?

Thanks.

Hi All,

Environment : Windows Server 2008, MDT 2012, Windows XP WIM image (Sysprepped and captured)

I'm have captured Windows XP image using WDS and customized image in in MDT ie, partition details, license keys etc.

But, when I'm deploying the Lite touch image (x86) that's created by MDT 2012 using WDS. I'm not getting the required settings that I have selected ie :

-After the setup the product key is asked,

-After the setup is complete, computer name is asked even though I have created a DB entry in MDT DB for Computer Name vs its MAC address

- EULA page

-Domain Addition.

Also, other things works well like formatting of partitions and application added to MDT.

Is it not possible that I can deploy Windows XP SP3 using MDT and WDS? Or I'm making some mistake here??

I have modified bootstrap.ini and customsetting.ini in the MDT2012 and added the product key. But still its not working.

Any suggestions will be appreciated.

--Arnav Sharma

Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Here is the problem, I have created a Sysprep and Capture Task Sequence in MDT with all the correct parameters, however when I try to run this Task with the GUI or by the command line (running as Admin) the task sequence starts but never ask me the questions it is supposed to ask such as do you want to image this machine and what name do you want to name the file etc. All it ask me what Task do you want to run and then the next window is to begin the sequence so I click begin and it runs the Sysprep and about 15 seconds later it says that the OS deployed successfully which obviously it did not. So I deleted that sequence I made, made another Sysprep sequence and completely regenerated the share and the same thing happened again. I then tried to run an older Sysprep/capture sequence I know that works and the same thing happened. The only thing that is different is that in WDS there is a 64bit boot image that I am not sure if that image works, I am not sure if that even makes a difference because the image I am trying to capture with MDT is a 64 bit one. Do you think I should try to make a 32 bit capture?

Hello all,

is it possible to deploy linux distributions with mdt?

For example the newest Ubuntu Server 13.04?

Regards

Hi,                                                        

I’m seeking advice in regards to using an unattend file and a sysprep wim of win8 that contains a pre-configured user account with admin rights. I have come across multiple forums asking similar questions about skipping the user account setup during the oobe on a workgroup pc. I have tried several methods found throughout forums but would really like to keep the preconfigured user account without creating another user or enabling the default administrator account. Is it possible to add these pre-configured user account details to the unattend?

I have tried adding it to the windows shell setup / user accounts / local accounts but it still prompts me for a new user account during setup. I’m using the same user name and logon password in the unattend that was used in the sysprep OS.

Thanks

So i have a Windows 7 64 Bit Boot image which works perfectly fine on a 2008 Server 64 bit but when I copy it to a 2003 32bit server it does not work. I also have an older Vista 32bit Boot Image which works fine on the 2003 Server so my question is does the image not work because of it being 64 bit or because it is Windows 7 also is there a trick to get it to work? 

I have a VM which I used to syprep and capture a Win 7 image. I left the bs.ini credentials blank and entred them manualy. I had to return to the snapshoted VM to make some changes but when I atttempt to resume it, it cant not make a connection to the DS because my password has changed since I snapshoted it. How can I change the password back so it can make its connection? Where is this information stored.

thanks

For the past 3 years with MDT I have been using customsettings.ini and am finding it's getting pretty complex to do so.  I feel I could make better use of the Database feature but can find little to no instruction on how to accomplish the same things I do with customsettings.ini. I also have several different task sequences with application bundles and such to do specific images and apps...

Here's my customsettings.ini to give you an example...  from a best practices scenario what do you folks here think?

Priority=TaskSequenceID, Architecture, Default, MMApps, ByDesktopType, ByLaptopType, ByMake
Properties=MyCustomProperty

[Default]
OSInstall=YES
Workgroup=<Left blank on Forum>
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipUserData=YES
SkipComputerBackup=YES
SkipApplications=NO
SkipBDDWelcome=YES
SkipDomainMembership=YES
SkipLocaleSelection=YES
UILanguage=en-US
UserLocal=en-US
keyboardLocale=0409:00000409
SkipTimeZone=YES
TimeZoneName=Central Standard Time
Administrators1=<Left blank on forum>
SkipBitLocker=YES
'Policy And Consent
MandatoryApplications001={45a66616-a8c0-4371-b092-3fb6870ee1e6}
'LANDesk Client
MandatoryApplications002={04ba23b7-1518-41d8-aeef-0b729648fded}
'Office 2007
MandatoryApplications003={d8348694-2efa-4e46-9ba8-d546579bc158}
'Office Communicator
MandatoryApplications004={393c5ef3-ee36-4e9a-a091-5ff9af9be475}
'.Net Framework 4.5
MandatoryApplications005={79d3abd9-f863-4291-82d3-5394bd8d2ee4}
'Adobe ReaderX 11.0.03
MandatoryApplications006={a9a480bf-8275-4172-a681-1bb0030349d2}
'Java 1.7.0_09x86
MandatoryApplications007={9c174775-9d81-4b05-b039-7c9c66b874de}
'BG Info
MandatoryApplications008={77b7e96d-0338-4535-be51-a9ac4933def2}
'Adobe Flash 11.7.700.202
MandatoryApplications009={a11b76fc-d5dc-4d74-8749-e01d2096863d}

[05]
SkipComputerName=YES

[WIN8X64]
SkipComputerName=YES



[x86]
'Trend x86
MandatoryApplications001={6286739d-7ce6-4c31-9acc-e17cc015d5c2}

[x64]
'Java 1.7.0_09x64
MandatoryApplications001={11474762-da3a-48b9-bcab-2429b38d163f}
'Trend x64
MandatoryApplications002={212b658c-ad2a-4eb8-9d7c-35225ccdb52d}

[ByDesktopType]
Subsection=Desktop-%IsDesktop%

[ByLaptopType]
Subsection=Laptop-%IsLaptop%

[ByMake]
Subsection=Make-%MaKe%

[ByModel]
Subsection=Model-%Model%

[Desktop-True]
ComputerName=W7D%SerialNumber%
'IE9
MandatoryApplications001={d8fc4f7a-dc11-480b-88ac-b4dd792aade7}

[Laptop-True]
ComputerName=W7L%SerialNumber%
'DataArmor x64
MandatoryApplications001={7752e63e-9dc4-4651-903c-a2ae85f9219c}
'IE9
MandatoryApplications002={d8fc4f7a-dc11-480b-88ac-b4dd792aade7}
BitsPerPel=32
VRefresh=60
XResolution=1280
YResolution=800

'Commenting out this section for now
'[Model-Latitude E6410]
'BitsPerPel=32
'VRefresh=60
'XResolution=1280
'YResolution=800

Help please.

I have built a new production environment with three 2012 servers:

DC1 - ADDS, DNS, DHCP
DATA1 - File Services & Shares, MDT Deploymentshare, MDT2012 Update 1, WDS, ADK
UTIL1 - Software Installs, WSUS, IIS

I have ESXi Update 1 installed and each server is aVM on the RAID5 Datastore.

I have tried all day to deploy anything (tried multiple WIMs) without success and recievederror 5624.

I have tried (without luck)
1. Create a new deploymentshare (importing the same WIMs)
2. Created new task sequence
3. Take out all drivers from task sequence incase a driver is corrupt
4. Eliminated all CAT5 cables/Switches involved in the imaging process
5. Removed and reinstalled ADK (to re-install ImageX)
6. Tried different NIC Cards on the (Brand New!) HP Proliant ML350e Gen8
7. We have tried several WIMs (some from disk some personal), they all fail with same error

What we know:
Well, apart from nothing, it seems we know it isnt phsyical hardware.
We have seen the images fail to apply and fail at any point between 1% and 98% complete

Anybody out there with any fresh ideas?  Johan?  This has me stumped.  If you want anything please ask.

EDIT:
The deploymentshare has been used in multiple 2008/R2 environments without problems.
I have a 'master' deployment share I continually work on and it has been updated with new revisions of MDT

<![LOG[  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Volume 2     C   OSDisk       NTFS   Partition     99 GB  Healthy            ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Partition ###  Type              Size     Offset]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   -------------  ----------------  -------  -------]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Partition 1    Primary            499 MB  1024 KB]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Partition 2    Primary             99 GB   500 MB]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 0     E                       DVD-ROM         0 B  No Media           ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 1     V   System       NTFS   Partition    499 MB  Healthy            ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Volume 2     C   OSDisk       NTFS   Partition     99 GB  Healthy            ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Leaving DiskPart...]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Return code from command = 0]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found: DestinationOSVariable: C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Set the Tag variable: TargetPartitionIdentifier]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property TargetPartitionIdentifier is now = ]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property TargetPartitionIdentifier is now = SELECT * FROM Win32_LogicalDisk WHERE Size = '106848841728' and VolumeName = 'OSDisk' and VolumeSerialNumber = '60AB9B48']LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-1ECRV1F\root\cimv2:Win32_LogicalDisk.DeviceID="C:"   \\MININT-1ECRV1F\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property DestinationDisk is now = 0]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property DestinationPartition is now = 2]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[DestinationDisk: 0]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '106848841728' and VolumeName = 'OSDisk' and VolumeSerialNumber = '60AB9B48']LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '106848841728' and VolumeName = 'OSDisk' and VolumeSerialNumber = '60AB9B48']LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found Drive: C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Target Drive Letter Found: C:]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found OS Drive: C   0]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-1ECRV1F\root\cimv2:Win32_LogicalDisk.DeviceID="C:"   \\MININT-1ECRV1F\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[####### NOTE:  If this is one of the  last lines in your BDD.log file, check C: for the most up to date bdd.log!!!]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="05:33:58.000+000" date="12-14-2012" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">

Regards JH

Quick question:

I am employing the 'Total Control' driver management practice and will be telling my task sequences to use "Windows 7 x64\%model%"... Question:  How do I handle models with special characters in the model name?  I have a model number (when queried using a script) which has three "/" in (e.g XXXXX / XXXXX / XXXXX)

Do I just use the first set of characters leading up to the special character?  or is there some other method?  I cannot create a folder using special characters inside Out-of-Box Drivers.

Regards JH

I have been getting the error "ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: Object doesn't support this property or method (438)" when I use any task sequence with the Windows Update step enabled. This occurs when deploying any image, Windows XP, Server 2008(R2), Windows 7, or Windows 8.

I have updated to MDT 2012 Update 1 (6.1.2373.0). I have updated the WAIK to version 2.0(?) (not sure of the version number but, it is using the Windows 8 PE).

The troubleshooting information I have found to date states that this issue is related to the WSUS server not having the hotfix (KB2734608) installed to provide support for Windows 8/Server 2012. All WSUS 3.0 servers in the update environment have had this hotfix applied, restarted, and resync'd.

Even after all this has been done, I still am getting the same 438 error message when the task sequence gets to the Windows Update steps. The machine properly detects that it needs updates, downloads them to the target computer, then errors out when they try to install. Without fail, every machine that fails during the task sequence, will check in with the update server, download and install their required updates just like any other machine on the network. They just will not do this during the task sequence.

All of these issues did not occur until the current update of MDT 2012 was applied. Any ideas of what is happening here and what I might do to fix it?

I am experiencing issues with multicast transfers in MDT 2012, and for something that is essentially as simple as clicking a checkbox, I am baffled at what else could be going on to cause this.

We are running MDT 2012 on a 2008 R2 server, which is also the home of WDS. Now, multicasting straight from within WDS works fine, but for obvious reasons we need to have this functionality in MDT. The MDT Deployment Shares are established with custom images, setup files, driver support, applications, etc and all of the task sequences work flawlessly. When I enabled multicasting on the DS, I verified that the namespace was in fact created in WDS, however the session never gets created and no clients are able to join. During deployment, "Attempting multicast transfer" appears for a split second before falling back to unicast and completing the rest of the task sequence. Below is what I am seeing in both the BDD.log and LTIApply.log files:

------  Applying Windows image using Setup.exe ------ LTIApply 8/8/2012 2:10:56 PM 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\Win7x64_CI_8-7-12 LTIApply 8/8/2012 2:10:56 PM 0 (0x0000)
<Message containing password has been suppressed> LTIApply 8/8/2012 2:10:56 PM 0 (0x0000)
Command has been started (process ID 1412) LTIApply 8/8/2012 2:10:56 PM 0 (0x0000)
  Console >
 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
  Console > Transfer Failed. [0x80070523]. LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Return code from command = -2147023581 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Multicast transfer could not be completed, rc = -2147023581, falling back to using %DEPLOYROOT%\Operating Systems\Win7x64_CI_8-7-12\Win7x64_CI_8-7-12.wim LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
LTI applying image %DEPLOYROOT%\Operating Systems\Win7x64_CI_8-7-12\Win7x64_CI_8-7-12.wim using SETUP.EXE LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Unable to find SETUP, use imagex.exe as a backup. LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
------  Applying Windows image using ImageX.exe ------ LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
LTI applying image %DEPLOYROOT%\Operating Systems\Win7x64_CI_8-7-12\Win7x64_CI_8-7-12.wim using ImageX LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Property SourcePath is now = %DEPLOYROOT%\Operating Systems\Win7x64_CI_8-7-12 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\Win7x64_CI_8-7-12 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
<Message containing password has been suppressed> LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Command has been started (process ID 1468) LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
  Console >
 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
  Console > Transfer Failed. [0x80070523]. LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Return code from command = -2147023581 LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)
Multicast transfer could not be completed, rc = -2147023581, falling back to using %DEPLOYROOT%\Operating Systems\Win7x64_CI_8-7-12\Win7x64_CI_8-7-12.wim LTIApply 8/8/2012 2:10:57 PM 0 (0x0000)

I've replaced the server name and share path with %DEPLOYROOT% in the log excerpt above, but in the actual log it has the correct path listed. This same error is being returned for each task sequence, on each Deployment Share. I have tried recreating a Deployment Share and enabling multicast transfer, but this yielded the same results, and I never see any clients in the WDS console.

What's strange is that we had this working when we temporarily tested it last year with MDT 2010, but we had decided not to implement it yet to due network restrictions. We are utilizing 802.1x port level authentication, however the systems are on forced auth ports and IGMP snooping is permitting on all devices between the clients and the MDT server. Like I said, multicasting works fine when deploying an image from WDS so this leads me to believe the issue is not network related.

I've searched countless hours on the issue, error codes, or similar symptoms and haven't found anything that solves my problem. We are gearing up for our large deployment of 1500+ systems and we really need to get this working. Any help is appreciated!!