none
MDT 2013, WDS, Server 2012 R2 multicasting not working rc = -1073740940

    Question

  • Hi,

    I have been reading all over the internet and not able to find an issue that we are having.  We have setup MDT 2013 and WDS on a Server 2012 R2 server.  Unicast has been working fine for us and we have the PXE boot working great too.  We have recently tried setting up Multicast.  Every time we try and deploy an image we receive the following error when the client tries to run the multicast.  I have pulled this error from the ltiapply.log on the client.  The error is:  Multicast transfer could not be completed, rc = -1073740940, falling back to using \\mdtserver\deploymentshare\operating systems.  We have also made sure we have IGMP enabled on all our switching and VLan's.  We have tested with mcast.exe and Wireshark and the packets are hitting the machine for multicast but we always seem to get this error.  Any help would be great.

    Thanks,

    Monday, July 28, 2014 2:39 PM

Answers

  • Thanks for all the help.  We found what the issue was.  It turns out that the MDT Deploymentshare needs to be shared with the name LTI$  We had it shared as just Deploymentshare.  After making that change multicast is working great.

    Hope this helps anyone else with this problem.

    • Marked as answer by cklein425 Wednesday, July 30, 2014 4:20 PM
    Wednesday, July 30, 2014 4:20 PM

All replies

  • Did you create the correct Namespace?

    What does "wdsutil /get-allNameSpaces" say?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, July 28, 2014 4:43 PM
    Moderator
  • Here is what the report shows:

    Name:  Deployment Share

    Friendly name:  MDT Share Deploymentshare

    Description:

    Content Provider: WDS

    Configuration string: E:\Deploymentshare

    Type: AutoCast

    Status: Active

    Start clients: 0

    Start time:

    Everything looks good.  The namespace is correct.

    Monday, July 28, 2014 4:58 PM
  • IF you still need assistance, can you post the bdd.log file to a public site like OneDrive, and copy the link here?

    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, July 29, 2014 4:41 AM
    Moderator
  • Keith,

    Here is the link to the log file.

    https://msctc-my.sharepoint.com/personal/ck6533fl_msctc_onmicrosoft_com/_layouts/15/guestaccess.aspx?guestaccesstoken=2Mp4%2fr01CoN0RJT5rcyy1xItiaS2LNX9CNSybi5y3RA%3d&docid=0b57cd220d6c94ce7acd4f76d1efc8e59

    Any help on this would be great.  I am at a loss at this point.

    Tuesday, July 29, 2014 2:43 PM
  • MDT logs the output from the wdsmcast.exe command itself within the bdd.log file.

    A quick scan reveals:

    Multicast transfer to directory: C:\MININT\Operating Systems\BaseWin7x64_6_17_2014
    <Message containing password has been suppressed>
    Command has been started (process ID 776)
      Console > 
      Console > Windows Deployment Services Multicast Client [Version 6.3.9600.17029]
      Console > Copyright (c) Microsoft Corporation. All rights reserved.
      Console > 
      Console > 
      Console > Operation Failed. [0x80070523].
      Console > 
      Console > The name provided is not a properly formed account name.
      Console > 
      Console > 
    Return code from command = -1073740940
    


    "Not a properly formed account name"?!?!?  What?

    MDT will pass the user account credentials to the wdsmcast.exe command using the USERID value.

    SO... What is UserID set to?

    Property USERID is now = vdl-mdt\helpdesk	ZTIGather	7/29/2014 8:27:55 AM	0 (0x0000)
    

    Whoops! UserID should not contain the domain name, instead it should just contain the user name.

    USERID=Helpdesk


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, July 29, 2014 8:29 PM
    Moderator
  • Keith,

    That is not a domain account rather a local user account on the server.  Is there another way that the USERID should be set?

    Tuesday, July 29, 2014 8:34 PM
  • Also the Deploymentshare folder is shared out to everyone.  We have removed the userid in the bootstrap.ini and tried using the domain admin account and received the same result and error.  We are imaging the computers to be just on a workgroup and not a domain.  Not sure if that makes a difference or not.  We also just tested WDS with a image and multicast worked fine.  Its just not working when configured with the MDT Namespace and MDT Deploymentshare being set to Multicast.  Both the WDS and MDT are on the same server.  Is there any special setup for that?
    • Edited by cklein425 Tuesday, July 29, 2014 8:41 PM added more info
    Tuesday, July 29, 2014 8:38 PM
  • That's not what I said.

    Your bootstrap.ini file looks like this:

    UserID=Domain\UserName

    Instead is should look like

    UserID=UserName
    UserDomain=DOmain

    Got it?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, July 29, 2014 9:13 PM
    Moderator
  • Keith,

    I got it but we removed that completely from the Bootstrap.ini and used our domain admin creds when prompted by MDT and we still get the same error in our logs and the multicasting does not work.  Do we need to specify those in the Bootstrap.ini or should we be able to get by with entering in the creds when prompted.

    Thanks again for your help, do you have any other thoughts?

    Tuesday, July 29, 2014 9:25 PM
  • I don't follow what you are saying above. Did you update the deployment share after modification of the bootstrap.ini?

    Specifically what is UserID Set to within the BDD.log file? You can easily search within the bdd.log file for this entry.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, July 29, 2014 9:32 PM
    Moderator
  • Thanks for all the help.  We found what the issue was.  It turns out that the MDT Deploymentshare needs to be shared with the name LTI$  We had it shared as just Deploymentshare.  After making that change multicast is working great.

    Hope this helps anyone else with this problem.

    • Marked as answer by cklein425 Wednesday, July 30, 2014 4:20 PM
    Wednesday, July 30, 2014 4:20 PM