locked
SCCM 2012 SP1 - Remote DP install issue. RRS feed

  • Question

  • Hi all,

    We have our SCCM Primary site setup and distributing content without any issues, I am now trying to add a second remote DP on one of our other AD sites.

    The remote DP server is a dedicated Server 2012 box with the firewall disabled.

    I have added the primary sites computer account to the remote DP local Admin group so it has permissions to install, and disabled UAC.

    I have installed the following perquisites on the remote DP Server before attempting to install the DP:

    Distribution point

    Features1:

        
    • Remote Differential Compression

    IIS Configuration:

        
    • Application Development:  
           
      • ISAPI Extensions  
        
    • Security:  
           
      • Windows Authentication  
        
    • IIS 6 Management Compatibility:  
           
      • IIS 6 Metabase Compatibility   
      • IIS 6 WMI Compatibility  

    To support PXE or multicast, install and   configure the following Windows role:

        
    • Windows Deployment Services (WDS)
                    
       

        

       
       

    WDS installs and configures automatically when     you configure a distribution point to support PXE or Multicast on     Windows Server 2012.

       

    For Configuration Manager with SP1, to support   PXE on a distribution point that is on a computer remote from the site   server, install the following:

        
    • Microsoft Visual C++ 2008 Redistributable.
                    
       

       
       

    For Windows Server 2012, the     vcredist_x64.exe is installed automatically when you configure a     distribution point to support PXE.

       

                    
       

       
       

    With System Center 2012     Configuration Manager, the distribution point site system role does     not require Background Intelligent Transfer Service (BITS). When BITS is     configured on the distribution point computer, BITS on the distribution     point computer is not used to facilitate the download of content by clients     that use BITS

       

    The remote DP has a D: drive for the SCCM data with 800GB of free space and I have created the NO_SMS_ON_DRIVE.SMS file on the C: drive so it should select D: drive.

    When I try to create the site system Server and select to install DP role on the remote DP Server I get the following errors in the Distmgr.log:

    DPServerFQDNSMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    Failed to connect to DP WMI provider SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    CDistributionManager::ConfigurePXE failed; 0x800706ba SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    CWmi::Connect() failed to connect to \\DPServerFQDN\root\SCCMDP. Error = 0x800706BA SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    GetWMIObject - Failed to connect to root\SCCMDP on ["Display=\\DPServerFQDN\"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN\. Error code: 0x800706BA SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    Failed to find a valid drive on the distribution point ["Display=\\DPServerFQDN\"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN\ SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)
     

    Failed to install DP files on the remote DP. Error code = 15 SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)
     

    Could not find a valid drive. Error = 15 SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)

    ===================================================================================

    In the Distribution point configuration status I get the following errors:

     8/08/2013 4:50:00 PM Failed to connect to remote distribution point Distribution manager failed to connect to the distribution point ["Display=\\DPServerFQDN\"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN\. Check your network and firewall settings. Error SYD00003 

    8/08/2013 3:28:00 PM    Failed to find an available disk drive on the distribution point      Distribution Manager failed to find a drive on distribution point "["Display=\\DPServerFQDN \"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN \" on system " DPServerFQDN" which has characteristics appropriate for storing shared folders used by distribution point.    Possible cause: Windows NT distribution points might not have at least one available NTFS drive.  Solution: Verify that there is at least one NTFS drive with enough free disk space to store the packages.  Error      SYD00004

    The last thing I would like to add is that the sites are connected with Riverbed Steelhead WAN accelerator devices, I have read there is an issue with the CISCO CIFS Accelerator feature when installing remote DP's could this be related?

    Has anyone experienced these errors before and found a fix? I cant seem to find much online on how to resolve this.

    Cheers

    Sean


    • Edited by Sintesiii Thursday, August 8, 2013 6:54 AM update
    Thursday, August 8, 2013 6:01 AM

Answers

  • Thanks for the reply I have found the issue, this was the first Server 2012 machine at a remote site so I didn't realise straight away that I could not access any shares on the site server, the problem is related to the Riverbed Steelhead devices needing the latest version of the Rios that supports SMB3.0.

    Once you update your head office Riverbed and the site office Riverbed the problem was resolved.

    Cheers

    Sean

    • Marked as answer by Sintesiii Friday, August 9, 2013 1:18 AM
    Friday, August 9, 2013 1:18 AM

All replies

  • When I try to create the site system Server and select to install DP role on the remote DP Server I get the following errors in the Distmgr.log:

    DPServerFQDNSMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    Failed to connect to DP WMI provider SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    CDistributionManager::ConfigurePXE failed; 0x800706ba SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    CWmi::Connect() failed to connect to \\DPServerFQDN\root\SCCMDP. Error = 0x800706BA SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    GetWMIObject - Failed to connect to root\SCCMDP on ["Display=\\DPServerFQDN\"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN\. Error code: 0x800706BA SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:09 PM 3204 (0x0C84)
     

    Failed to find a valid drive on the distribution point ["Display=\\DPServerFQDN\"]MSWNET:["SMS_SITE=SYD"]\\DPServerFQDN\ SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)
     

    Failed to install DP files on the remote DP. Error code = 15 SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)
     

    Could not find a valid drive. Error = 15 SMS_DISTRIBUTION_MANAGER 8/08/2013 1:12:18 PM 2636 (0x0A4C)

    ===================================================================================

    I've seen those "errors" (except the last 3) during DP installations that worked fine and I think that they are expected (because the WMI namespace will be created later in the process etc).
    I've heard that Steelheads are causing issues, but I don't know if that's applicable in this case. Can you upload the entire distmgr.log? There's too much information missing. There should be a part where distmgr is enumerating drives of the remote server.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by EMS-edgemo Tuesday, June 24, 2014 11:19 AM
    Thursday, August 8, 2013 6:58 AM
  • Thanks for the reply I have found the issue, this was the first Server 2012 machine at a remote site so I didn't realise straight away that I could not access any shares on the site server, the problem is related to the Riverbed Steelhead devices needing the latest version of the Rios that supports SMB3.0.

    Once you update your head office Riverbed and the site office Riverbed the problem was resolved.

    Cheers

    Sean

    • Marked as answer by Sintesiii Friday, August 9, 2013 1:18 AM
    Friday, August 9, 2013 1:18 AM
  • Hi, had the same error and in my case it was caused by Network.

    Once we added a PassThrough rule on the Juniper device it ran just fine.

    Wednesday, January 29, 2014 10:48 AM