Hello,I created a new image today for deployment. I used the old image fully updated it and captured it. Now I tried to deploy it but got a message when the task sequence was running at the action "Install Operating System" that there is no access tot the specific file. I added the new image in MDT and made a new task sequence.On the WDSServer I receive the following error:EventID 1032: A request was received by the RPC server on {6F13A317-3687-4B54-81A5-504DAA9062FA} endpoint from 192.168.202.107 but there is no provider registered for {6F13A317-3687-4B54-81A5-504DAA9062FA} endpoint. This can happen if the provider failed to initialize but was not marked as critical or if a malicious code is trying to probe for available services. The binary data contains the first 32 bytes of the request. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Anyone know an answer or experienced the same issue and solved it?yours sincerly, Robin E. Turpijn Microsoft Manageabilty Specialist @ Wortell, Lijnden NL.

Hi, I have exactly the same problem with my WDS server. My server is a Windows 2003 STD SP2 English. The image I'm trying to deploy is Windows XP SP3 French. Event ID : 1032 Source : WDSServer A request was received by the RPC server on {6F13A317-3687-4B54-81A5-504DAA9062FA} endpoint from 192.168.101.45 but there is no provider registered for {6F13A317-3687-4B54-81A5-504DAA9062FA} endpoint. This can happen if the provider failed to initialize but was not marked as critical or if a malicious code is trying to probe for available services. The binary data contains the first 32 bytes of the request. Pour plus d'informations, consultez le centre Aide et support l'adresse http://go.microsoft.com/fwlink/events.asp. Donnes: 0000: 80 01 00 00 00 01 01 00 €....... 0008: 06 00 00 00 03 00 00 00 ........ 0010: 43 00 6c 00 69 00 65 00 C.l.i.e. 0018: 6e 00 74 00 00 00 00 00 n.t..... Thanks for helping us !

Hi, I solved my problem ! I found that the error above (eventid 1032) is not causing the deployment failure (in my case). This error is due by scripts trying to use multicast. But multicast is only available for Windows server 2008. The problem was from a bug in the script c:\Distribution\Scripts\LTIApply.wsf at line 666, character 118. the original version : /ref """ & sRWMPath & "" & The modified version (it works for me) : /ref """ & sRWMPath & """" & I hope this will help you solve your problem.