Multicasting Issues - MDT 2013 - Server 2012 R2

Hello!
I'm having some issues with multicasting on a large university network. Our setup is like this:
WDS role setup on VM with Server 2012 R2
Deployment shares hosted on the same VM - Using MDT 2013 to manage Deployment Shares
VM is on a different VLAN from client computers. - IP Helpers to connect between the VLANs
Multicast namespace was created successfully.
All switches between server and client are managed, IGMPv3 compatible, and have snooping enabled3
MDT Images are custom WIMs, with no setup files
When I run a deployment on any number of clients, I get the message saying "Attempting multicast transfer". The clients show up listed in the WDS Multicast Transmission. Then the clients drop off the server, and begin unicasting. Unicast speeds
are excellent. Our 10GB images copy in about 10 mins. But we plan to do 30-40 systems at a time, and I believe that could cause some issues with so many individual sessions running...
I've noticed under our network adapter properties that Microsoft Network Adapter Multiplexor Protocol is unchecked. Not sure if that is related?
I have copied multicast information from the BDD.log file on one of the failed clients. That can be found below.
Any help/advice will be greatly appreciated! Thank you!
Edit: I likely posted this to the wrong place. I have reposted this to the MDT forum. Thanks!
<![LOG[LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 504)]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Windows Deployment Services Multicast Client [Version 6.3.9600.17237]
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Copyright (c) Microsoft Corporation. All rights reserved.
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Started.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Complete [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Operation Failed. [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > This operation returned because the timeout period expired.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > ]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -2147023436]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer could not be completed, rc = -2147023436, falling back to using \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Hi Kyle T.Johnson,
Could you try to put a test client to your WDS server VLAN then monitor this issue again.
Best Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

MDT 2013 Server 2012 R2 Core Deployment Fails After Disabling ChecksumOffloads on NICs

When changes are made to the Checksum offloads, the NICs reset themselves and I'm losing connectivity to the deployment share during the deployment process (LiteTouch). It happens during a custom PowerShell script I'm running in the Task Sequence
after "Tattoo".
PowerShell Script:
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
Here are the errors from the BDD.log (sorry couldn't get the _SMSTaskSequence.log)
ZTIPowerShell processing completed successfully. ZTIPowerShell 8/25/2014 2:27:28 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
What I was thinking about trying was adding a few lines to the end of my script:
1. PING 1.1.1.1 -n 1 -w 30000 >NUL
    This would give the server 30 seconds to right itself after resetting the NICs
2. net use command to remap the share.
Two questions regarding re-mapping the share.
   1. I'm assuming this will run as Administrator token. Will this be an issue for continued deployment?
   2. At the beginning of the deployment process the Tech has to enter his/her credentials to access the deployment share to begin the deployment process. Are those the credentials I need to continue using, or does MDT use some other credentials
to access the deployment share that far into the deployment process (during state restore phase)?
Thank you for taking time to read my post.
-Cheers!

Apologies for the delay in responding to this thread.
It turns out that Broadcom NICs are the culprit!
For some reason Broadcom doesn't grant you access to all the feature sets on their NICs when it comes to PowerShell.
Same script runs against Intel NICs with no issues.
I placed a 15 second pause in the script to allow NICs to reset, I then remap MDT network drive to continue the deployment process. Big thanks to Keith for assisting with reconnecting the network drive!
Here is the script I settled on:
# All settings will not take, if target is using Broadcom NICs.
# You will still need to manually set TCP IPv4 and IPv6 to disabled.
# Commands to disable Checksum Offloads.
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
# Pause script for 15 seconds to allow ample time for NICs to reset.
Start-Sleep -s 15
net use %DeployRoot% /u:"%UserDomain%\%UserID%" "%USerPassword%"
# Pause script end for 5 seconds to allow completion of share recreation.
Start-Sleep -s 5

I can not install Waik and mdt on server 2012 so that i can deploy windows 7 please may you help me?

i can not install Waik and mdt on server 2012 so that i can deploy windows 7 on target machine, i have downloaded mdt Waik i got error saying you must install frame 2.0 which needs also adk windows 8. i am using hyper machine.
thank you

Hi Warsame12,
It is worth mentioning that don’t use IPV6 PXE, Windows 7 doesn’t support WDS 2012 deployment over IPv6 PXE. If IPv6 PXE boot is enabled and a
Windows 7 installation is selected, a blank screen will appear and Setup will not run.
The related KB:
Windows 7 client deployment over IPv6 PXE network boot does not work.
http://support.microsoft.com/kb/2803741
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MDT 2013 & SCCM 2012 R2 - Slow MDT Download

MDT Use toolkit package inside of OSD takes a very long time to download.<br>
MDT is only around 40mb total size, so i can't understand why it's taking so long on only this section.
Typically the use toolkit package where MDT downloads locally inside of OSD takes around 5-7 minutes, each of the files are small in size but the download time is ridiculous! I transfer a 6bg .wim file in 2 minutes when it comes to applying the image so
i know the network speed is ok, something is going wrong with the MDT package and downloading it.
Running a normal TS without MDT runs fine, and the image installs ok.
Pulling my hair out with how long MDT takes, it's adding on an extra 15-20 minutes onto my sequence just by downloading toolkit files!
Anyone had similar or know what I may be able to try?
The setup is a lab environment. I have a standalone primary, with local SQL, 1 DP & 3 physical clients.

I too have seen significant slowness downloading the MDT 2013 Toolkit package since upgrading my DEV environment (physical server and clients) to SCCM 2012 R2. It takes almost 20 minutes
to download the package.
Watching SMSTS.LOG I can see that it taking about 2 second to download each file in the package. 617 files multiplied by 2 seconds comes out to right around 20 minutes.
Last night I installed the most recent hotfix (KB2910552) but I just confirmed that it did not improve the speed of the MDT toolkit package download.
I’m planning on opening a case with MS support today.
I'll report back with my findings.
Any update here? Can I ask if anyone is seeing the issue when using HTTPS?
@mgouldthorp1 - Have you raised a case yet and if so any updates?
Thanks.

Issue installing SQL Server 2012(with SP1) on windows 7 Error result: -2067529718

When running the installation, it suddenly stops without any error popup.
I ran the installation from the command prompt and this is what I get:
An error occurred during the SQL Server 2012 Setup operation.
Error result: -2067529718
Result facility code: 1220
Result error code: 10
I recently uninstalled SQL Server 2012 SP1, because the SQL server service was not starting up, it would just hang in there with no response. I tried many things to get that issue fixed, finally I decided to uninstall and start fresh but I couldn't since
I was getting an error stating that I needed Windows 7 SP1(which was already installed). I downloaded the
microsoft fix it tool which fixed the issue.
On the control panel/Programs and features, I still see that SQL Server 2012 is listed if I click to uninstall again it tells me:
An error occurred while trying to uninstall Microsoft SQL Server 2012. it may have already been uninstalled. do you want to remove Microsoft SQL Server 2012 from the Programs and features list?
if I click yes, eventually it will be listed again.
currently I'm not able to install SQL server again and besides the info provided there are not error messages (I also copied the installation files to disk).
UPDATE: it appears that the sql server was not completely removed from the system, I still see listed the SQL server(SQLExpress) and server browser services on the SQL server configuration manager.
Thanks.

1) First Reboot your server and try again for the installation.
2) If first fail again than Take a backup of Registry first for safe side and then delete the entries of SQL server 2012 if found take a reboot again and try to install again.
One more thing if installation created any file then move/Delete that also before installation.

Report Viewer control issue in Windows Server 2012 R2

Hi,
I have a reporting application (web) and it is using the Microsoft.ReportViewer.WebForms.dll (version 11.0.3366). While deploying I have kept all the Reporting Viewer related dll's into the bin directory and things are working fine in the below combinations.
1) Windows Server 2008 R2 , SQL Server 2008 R2 SP2
2) Windows Server 2012 and SQL Server 2012
Today I have installed the same setup into the Windows Server 2012 R2 (with SqlServer 2012) machine and I am facing the some issue. The Print icon and find/next options are not visible in the Report Viewer . I am not sure what was the cause for this.
Then I have installed the Report Viewer 2012 runtime on the Windows Server 2012 R2 machine and things are working fine. So , I am wondering how the same setup worked fine in other two combinations with out installing Report Viewer 2012 runtime.
Did any one have idea/suggestion on this.
Thanks in advance!
Best Regards
Muthuraja

Have you verified that the runtime assemblies are not on those servers? Maybe someone else added them. There are numerous other possibilities such as code refactoring that moved these elements from to other assemblies (unlikely) or that there was some other
difference in your installation that you overlooked. I am glad that you were quickly able to resolve your issue however and may help others if they experience the same problem.
"You will find a fortune, though it will not be the one you seek." -
Blind Seer, O Brother Where Art Thou
Please Mark posts as answers or helpful so that others may find the fortune they seek.

DateTime issue in Windows Server 2012 R2

Hi all,
I have created a web application. Its working fine in Windows server 2008 R2. I have used Report Server 2005 & Report Viewer 2005 SP1 for reporting. Reporting is working fine in Windows Server 2008 R2. But when I try to run reporting in Windows server
2012 R2 system I am getting error "start/end date can not be set to a future date". The screen shot is given below:-
How should I resolve this issue. Any help in this regard would be highly appreciated.
Thanks.

Hi Vishwajeet,
I have tested on my local environment and can't reproduce the issue.
Could you please check another report with the start data and end date in the report of Report Server 2005 in Windows server 2008 R2 and then run the report in Windows server 2012 R2 to see if you will also got the issue.
If you only got the issue when running this report, I suggest you to open and edit the report in designer of the Windows server 2012 R2 to delete and re-create the two parameters to see if the problem will be resolved.
Please also try to run this report in other broswer to have a check.
If you also got the issue in other report.
I recommend you that submit this suggestion at https://connect.microsoft.com/SQLServer/
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Licensing issue with Windows Server 2012 R2 Essential

Hi,
we purchased a server that came with Windows Server 2012 Essentials. and we found out some of the issue regarding the licensing. I would like to verify it with the experts here.
1. This Essential O.S. cannot be deployed as a member server in the domain, only Windows server 2012 r2 Standard and data center is capable as deploy as a member server?
2. does it work with a single domain with multiple domain controllers and one primary domain controller? Example, 10 offices in different states, each location has a domain controller in their office, I'm installing to install this Essential server as another
domain controller in one of the offices for redundancy purpose. I promoted this server into domain controller with success, but it gives me an fsmo error everyday, and warning about shutting down if i don't transfer the fsmo role to this server.
3. which leads to this question, so this Essential OS can only be deploy as a single domain as the primary domain controller? Up to 25 user and 50 device license?
4. Is it possible to deploy it as a domain controller (that office has less than 25 users) in that office while syncing correctly with the other 10 domain controllers in other offices, they are all in the same single domain? I can't make this work, and I
think due to the Essential O.S.'s limitation.
5. we use a vpn connection to connect all the office together, and all the domain controller uses lan ip address to communicate with each other.
Thank you for the help in advance. I have been researching for the past couple days, but I still couldn't get a clear answer. Thank you again.

Hi Cliff,
Thank you for your reply.
1. We will get a new server 2012 r2 standard to deploy as member server.
2 and 3. Only ONE domain controller can hold all FSMO roles in a single domain, correct? Currently an windows 2003 enterprise, this is our first server in our domain, it holds all the FSMO roles currently.
4. Yes, we realized essentials will not work for us, so we are switching to 2012 r2 standard to deploy for the new
domain controller for our new office, still under the same domain.
5. This wasn't a question, just wanted to give out the connection information.
The problem was that We didn't read the Essentials in detail when buying the new server, on dell website, it said it was perfect for small business, we didn't know it has to run as a primary DC. it was great in price, and it doesn't need CALs.
but we quickly realized after deploying it as a DC, it gives us error about Server Licensing compliance, and will shut down automatically. Then we were going to use it as a member server to run application, and realized we couldn't. So we are returning the
server, and getting a new one with standard r2 2012 and CALs license.
It was a costly mistake.
Thank you again.

SQL Server 2008 R2 Standard - Compatibility issues with Windows Server 2012 R2

Hello,
We used as a test a box on which we installed Windows Server 2012 R2 and SQL Server 2008 R2 Standard Edition. No Service pack was installed. It worked perfect.
Now we try to do it on another box and all of the sudden there is compatibility issue when we try to instal SQL Server. We can still install SQL Server by clicking "Continue without getting help".
Where can this come from? If it is hardware related what are the thing I should look at?
Thanks all

Hello,
Adding to Shanky suggestion, you can perform a slipstream installation of SQL Server 2008 R2 + SP3 to make SQL Server
2008 R2 compatible with the newer operating system, as explained on the following post.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
https://support.microsoft.com/en-us/kb/955392/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Shadow copies issues with Windows Server 2012 R2, deduplication and defragmentation

Hello,
I have a virtual Windows Server 2012 R2 with a data volume with deduplication and shadow copies enabled.
During this weekend some Windows process deleted all the shadow copies and I don't know what process has caused this issue.
After taking a look at Internet forums it seems that could be related to defragmentation process and cluster size but if I review the logs it seems that shadow copies deletion is during some deduplication optimization process (Background Optimization, WeeklyGarbageCollection
and WeeklyScrubbing) and 1 hour after defragmentation.
The related events are a lot of volsnap 33 and finishing with volsnap 36.
Any help would be appreciated.
Thank you.

Hi Ricard,
Above all, here is a long discussion about a "losing all volume shadow copy" issue:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/204e8cce-cd1f-4ca2-852e-a5f09a77c04c/volsnap-event-id-25-and-loss-of-previous-backups?forum=windowsbackup
As it mentioned, it could be caused by disk I/O. When you have high input/output traffic on the original volume, the shadow copy storage area cannot grow fast enough to hold all the copy-on-write changes. This causes deletion of all the shadow copies on the
original volume.
Deduplication will cause a high disk I/O for sure so it could be the cause of this issue.
Here are some suggestions for this issue:
a. Put the shadow copy storage on another volume, even if the volume is located on the same hard disk.
b. Make sure that the volume that causes the issue is not the same volume that contains the paging file. If it contains paging file, consider putting the paging file on another volume.
c. Make sure that the volume is not used as the shadow copy storage for any other volume.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Data Warehouse issue after deploaying Server 2012 MP in SCOM 2007R2

Hi all,
I have recently installed Server 2012 MP in SCOM 2007R2. But now I get DataWarehouse warnings that the specified schema name "sdk" either does not exist or I do not have permission to use it.
It's event 31565 with source Operations Manager Health Service Modules
Can anyone help me?
Failed to perform Data Warehouse component deployment operation:Install; Component: Script, Id: '79c157e5-9aa8-7045-d0b8-19e2d713d6c7',Management Pack Version-dependent Id: '01f04523-ee6c-1f3e-08a1-a108dda43507';Target: Database, Server name: 'SQL\SCOM,10100', Database name: 'OperationsManagerDW'. Batch ordinal: 0; Exception: The specified schema name "sdk" either does not exist or you do not have permission to use it.
Best regards,
Oliver
Gruss Oliver Scholl

Hi Gruss,
Was there any resent permission change on the SQL server or the Data warehouse ?
Has your Data reader and writer account Sys admin permissions on the SQL application ?
Also is the reporting tab working and are the reports related to this and other management packs working ?
Gautam.75801

Applications not being deployed during task sequence - MDT 2013 + SCCM 2012 R2

Hi everyone,
I have recently integrated MDT2013 with my SCCM 2012 R2 and I am trying to move away from OSD in SCCM and switch to MDT. I managed to get a blank image deployed and now I am trying to tweak CustomSettings.ini to install applications based on the default
gateway and model. For some reason, the apps are getting pulled but not deployed. Here is what I have in the files:
Settings Package - CustomSettings.ini
[Settings]
Priority=DefaultGateway, Model, Default
Properties=MyCustomProperty
[OptiPlex 9020]
Applications001=Mozilla Firefox
[DefaultGateway]
192.168.XXX.254=Poland
192.168.XXX.254=London
[Poland]
Applications001=ESET
[Default]
DoCapture=No
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
Administrators001=myDomain\adminGroup
Applications001=Skype
Applications002=Office Professional Plus 2010
When the TS runs, I can see it's getting all the apps from the list, here is a snippet from ZTIGather.log
Using from [Settings]: Rule Priority = DEFAULTGATEWAY, MODEL, DEFAULT
------ Processing the [DEFAULTGATEWAY] section ------
Match found for default gateway 192.168.XXX.254, retrieving settings.
------ Processing the [Poland] section ------
Property APPLICATIONS001 is now = ESET
Added value from [Poland]: APPLICATIONS = ESET
------ Processing the [OptiPlex 9020] section ------
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Added value from [OptiPlex 9020]: APPLICATIONS = Mozilla Firefox
------ Processing the [DEFAULT] section ------
Property OSINSTALL is now = Y
Using from [DEFAULT]: OSINSTALL = Y
Property DOCAPTURE is now = No
Using from [DEFAULT]: DOCAPTURE = No
Property SKIPCAPTURE is now = YES
Using from [DEFAULT]: SKIPCAPTURE = YES
<Message containing password has been suppressed>
<Message containing password has been suppressed>
Property SKIPPRODUCTKEY is now = YES
Using from [DEFAULT]: SKIPPRODUCTKEY = YES
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Added value from [DEFAULT]: APPLICATIONS = Skype
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Property APPLICATIONS004 is now = Office Professional Plus 2010
Added value from [DEFAULT]: APPLICATIONS = Office Professional Plus 2010
Property ADMINISTRATORS001 is now = myDomain\adminGroup
Added value from [DEFAULT]: ADMINISTRATORS = myDomain\adminGroup
------ Done processing CustomSettings.ini ------
So the settings do get picked up and selected. ZTICoalesce.log also shows the apps picked up:
Coalesce pattern to be used: Applications
Coalesce base variable to use: CoalescedApps
Added value ESET-KRKLON from APPLICATIONS001 to the list
Added value Mozilla Firefox from APPLICATIONS002 to the list
Added value Skype from APPLICATIONS003 to the list
Added value Office Professional Plus 2010 from APPLICATIONS004 to the list
Property CoalescedApps01 is now = ESET
Property CoalescedApps02 is now = Mozilla Firefox
Property CoalescedApps03 is now = Skype
Property CoalescedApps04 is now = Office Professional Plus 2010
ZTICoalesce processing completed successfully.
Now when I go to the smsts.log file, I can see this:
App policy for 'ESET' not received. Make sure the application is marked for dynamic app install
Policy download failed, hr=0x80004005
and later
Failed to run the action: Install Application.
Unspecified error (Error: 80004005; Source: Windows)
After that, no other apps are mentioned and seems like the failure on ESET drops the whole sequence and moves forward. I can see later the default admin being added correctly.
Any ideas what I may be missing here? Especially on the failed policy download?
Thanks
Jakub

HI,
"App policy for 'ESET' not received. Make sure the application is marked for dynamic app install"
Is the ESET application deployed? it sounds like it could be the check box on the application "Allow this application to be installed from install application task sequence action without beeing deployed" that is missing? If the application isn't
deployed this checkbox must be ticked.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

MDT 2013 - Windows 2012 R2 - Need Assistance !!

I have my original question posted here . Below
are my few questions.
i) Do i need to have MDT installed on another server ? I basically want to take entire image of ServerA (including application,settings,regkeys etc) ,create .iso and deploy on other servers.
ii) I have MDT installed on ServerA (same server of which i want to take an image), i followed instructions from "Quick Start Guide for Lite Touch Installation.docx", i do see that my LiteTouch.iso
file is only 300MB, i would expect this file to be around 5gb. I am assuming this is the file i would copy on to other baremetal servers and have it restored?
iii) Also what option should i select for task sequence, should it be "Standard Client Task Sequence"
or "Sysprep"
Any help is highly appreciated.
<o:p></o:p>

You will need to have MDT installed on another server or workstation. Basically, anything that can contain your deployment share, which is where you scripts and files reside and where your captured image will be stored.
The Litetouch ISO is for Windows PE environment, and that's why the size of the file is ~300MB.
Standard Client Task Sequence will install the OS, drivers, apps and, if you selected the option in the wizard, it will also perform a sysprep and capture. The Sysprep and Capture Task Sequence is for syspreping and capturing an OS that may already be deployed;
it just runs the sysprep and capture step.
If you are new to MDT, you may want to visit YouTube and watch a few videos about how the process works in general. I think MDT could work quite well for what you need but it may take a bit to wrap your head around if you aren't familiar with deployment
methodologies.
-Nick O.

Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

Hi All,
After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
with the tests I am using the MDT 2013 Server Task Sequence Template.
Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
\Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
Some background info:
As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
In both Task sequences the Format and Partition step is as follows:
Disk 0
Standard(MBR)
BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
OSDisk (Primary) - 90GB variable OSDisk assigned
In both Task sequences the Apply Operating System step is as follows:
Using Captured Image
Apply operating system from a captured image (Image 2-2)
Apply image to Logical Drive (OSDisk)
In both Task sequences the Apply Data Image step is as follows:
Using Captured Image
Image 1-1 (from the same captured image as shown above)
Apply image to Logical Drive (BDEDrive)
What has been done so far:
Already eliminated driver packs as the problem occurs with and without them
Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
are preserved.
I have disabled an UEFI Partitioning steps just as a precaution.
There is no Bitlocker steps involved yet.
I have trawled through the SMSTS.LOG. So far it looks OK to me:
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\use
The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
Any suggestions would be great.
NSutton

Hi,
If I were you, I would Streamline the MDT Task Sequence to find the root cause.
Moreover, please refer to the link below:
How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Using MDT 2013 for deploying Software from MDT Server to PC Client automatically and silently ?

I have a trouble about deploying software from MDT 2013 server to PC Client , Can we using MDT 2013 for deploying software automatically and silently , that Users/Clients don't have to click "next,next" to install software ?
If you have a solutions to deploying it , please share me about that solutions ?
Thanks.

you can make software silently with boot opción:
with chocolatey opensource.
or make software with switches
here link to help you:
http://blogs.itpro.es/octaviordz/2014/05/29/instalando-aplicaciones-con-chocolatey
http://blogs.itpro.es/octaviordz/2014/06/05/integrando-chocolatey-a-mdt-2013-e-instalando-aplicaciones-de-forma-desatendida-en-windows-8-1/
http://blogs.itpro.es/octaviordz/2014/10/31/probando-chocolatey-en-windows-10
http://blogs.itpro.es/octaviordz/2012/07/10/aplicaciones-desatendidas
MVP Jesús Octavio Rdz http://blogs.itpro.es/octaviordz

Multicasting Issues - MDT 2013 - Server 2012 R2

Similar Messages

Maybe you are looking for