Duplicate Distribution Point

Has anyone seen this problem where the distribution point shows up twice? I'm in the process of moving all of our distribution point off a secondary(SS1) site to a second primary site(PS2). I moved one of the distribution point and for some reason it's
showing up twice under Administration --> Distribution Point. Though, if I look under the Server and Site System Role it only shows up once. Any Idea why?

Hi,
Please check Smsprov.log and SmsAdminUI.log when you open Administration --> Distribution Point. Anything useful?
Best Regards,
Joyce
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.

Similar Messages

  • Is there a way to avoid having a content library on a site server when the Distribution Point role is not installed on that server (disk cost issue)?

    Hello,
    I don't think it is possible, but my goal is to start a discussion about content libraries and maybe suggest something for a future release or version of Configuration Manager.
    Actually, based on Configuration Manager Technet documentation, Configuration Manager creates a content library on each site server and on each distribution point.
    Often, when designing the architecture, people will offload the distribution point role from the site server to an external server (and add the role to other servers too for redundancy). They could also do the same for the Management Point role, but this
    is not related to content library. The idea is to save the site server from having to deal with clients for software distribution (applications, software updates, OS, etc.), this is especially true for organizations having a large number of clients and/or
    primary site servers involved in a hierarchy. Doing so will allow more resources on the site server to deal with the database and also replication in the case of a hierarchy.
    When doing that, you still have to maintain a content library on the site server and the thing is this library will usually become huge, especially for organizations having more than 1000 applications (add also OS images to this). Will the content library
    on the site server become as huge as the one for a distribution point having a copy of all content? I guess the answer is yes.
    I know that Pull distribution points will help offloading the task from the site server to distribute content to distribution points, but, correct me if I'm wrong, you still have to maintain a content library on the site server when using them, and they
    will not make the content library smaller on the site server. Also, I don't like the fact that you lose the rate limits feature with Pull DPs, but this is another story.
    Storage cost is high and in this scenario, it hurts to have to pay this cost for a content library not used by the clients, but only to distribute content to DPs.
    Correct me if I'm wrong, but the key component here is Distribution Manager on the site server; this is the one which has to maintain a content library to do its job.
    It would be nice if we could have a way to elect a specific distribution point (not on the site server) as the Distribution Manager for a site, that main DP would hold a copy of all content by default, but would be used to distribute content to other DPs
    and avoid the content library on the site server. Said differently, the Distribution Manager component would become a site system role that could be transferred outside the site server.
    Tnx for comments, answers or suggestions.
    Patrick

    There is no way to avoid that the contentlib will be placed on the site server.
    I don‘t agree that storage cost is high. It might be true for fast storage, but that‘s not needed for it.
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 R2 unable to install Distribution Point on Windows 7

    We have a SCCM 2012 R2 CU 2, single site. We would like to deploy the distribution point at 1 of the branch but hit with issues.
    We tried various workaround. Reinstall IIS, manually install IIS.
    We had repair WMI, and test WBEMTEST to the WMI and proof it able to connect, given security permission to everyone. Problem still persist.
    The distmgr.log shows
    CWmi::Connect() failed to connect to \\["Display=\\dpname\"]MSWNET:["SMS_SITE=sitename"]\\"dpname\\root\default. Error = 0x80070005
    GetWMIObject - Failed to connect to root\default on ["Display=\\dpname\"]MSWNET:["SMS_SITE=sitename"]\\dpname\. Error code: 0x80070005
    CDistributionManager::SetDpRegistry failed; 0x80070005
    Anyone can help?

    Hi,
    Have you tried to disable firewall? Just for test.
    Best Regards,
    Joyce
    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.

  • SCCM 2012 Distribution Point not working properly on a Windows 2012 Server

    I have an SCCM SP1 site running on a Server 2008 R2 machine.  I had a couple of distribution points, also running on 2008 machines.  These served as DPs and PXE boot points.  I had no problems with these.
    I resently added a Server 2012 machine, and set it up as a DP, with a PXE boot point.  The servers is part of a boundary group containing about 1500 clients.  I distributed all of packages that are included in my main task sequence, and am able
    to PXE boot, and image machines successfully.
    However, I am having problems deploying other packages and Windows update packages from this DP.  It seems like I am only able to deploy packages that have the "Copy the content in the package to a package share on distribution points" enabled. 
    If this is not enabled, the client will get the deployment policy, but will never download the package.  The "In Progress" tab for the deployment status will just say "Waiting for content".
    I have checked the rereqs for IIS on the Server 2012 DP, also checked the firewall.  Everything that I see seems to be OK.  Are there other things that I can check to determine why this DP isn't working right?

    Hello,
    According to the following description, this behavior would be normal:
    If you configured the option Run program from distribution point on the
    Distribution Points page of the Deploy Software Wizard, do not clear the option
    Copy the content in this package to a package share on distribution points, because this will make the package unavailable to run from distribution points.
    http://technet.microsoft.com/en-in/library/gg682178.aspx

  • SCCM 2012 R2 - Distribution Point

    Hello,
    I have a SCCM environment configured only one server to handle all the Role MP, DP, etc..
    SQL Server 2012 is Remotely installed.
    I am using Windows server 2012 R2 Standard with installed SCCM 2012 R2.
    I am using VMware vSphere 5.1
    I want to use SCCM 2012 R2 for PXE boot to deploy Windows 7 Enterprise 32 bit and 64 bit.
    But I am unable to install the Windows 7 Enterprise 32 bit and 64 bit through PXE Boot.
    When I am trying to install on VM this error message is:
    Downloaded WDSNBP from 10.100.1.178
    Pending request ID : 31
    Message from Administrator:
    Configuration Manager is looking for Policy.
    Contacting Server 10.100.1.178
    PXE Boot aborted. Booting to next device...
    PXE-MOF: Existing Intel PXE ROM.
    The operating system was not found. Try Disconnecting.......
    And 2nd thing when I am selecting Packages in SCCM 2012 R2 Console and right clicking on User State Migration Tool for Windows 8.1 and Selecting Distribute Content and After clicking next when its asking for Specify the Content destination its now showing
    any Distribution Point.
    Can someone help me please to fix this issue.
    Thanks a lot and help/advise much appreciated.

    Contacting Server 10.100.1.178
    PXE Boot aborted. Booting to next device...
    This indicates that there's no task sequence deployed to the computer that was PXE booted.
    Torsten Meringer | http://www.mssccmfaq.de

  • Critical Errors SCCM 2012 (Distribution Point and Reporting services point)

    Hello,
    We are getting errors under the Site Status for the Distribution Point and Reporting services point. Was running fine and have not really made any changes but all of a sudden we have these critical errors.
    The report server service is not running on Reporting Service Point server "XXXXXXXXXXX"; start the service to enable reporting.
    We have stopped and restarted the SQL 2012 reporting service point with no errors. What else should we look at for this error? And are these related?
    Thanks,
    Bobby

    Hi,
    Have you checked the log file SRSRP.log?
    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.

  • SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)

    Hello!
    Scenario
    Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
    The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
    DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
    errors indicate that this software can'tbe downloaded.
    In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
    Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
    implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
    Problem
    The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
    The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
    A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
    were reinstalled. A fresh install didn't detect the NAA.
    Solution
    After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
    the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
    Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
    domains aren't approved automatically (by default).
    In this case something as simple as an Approving the client fixed these issues. 
    The DataTransferService.log highlights the issue:
    <![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="1" thread="3136" file="dtsjob.cpp:3501">
    <![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
    ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
    <![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="3" thread="3136" file="dtsjob.cpp:3513">
    <![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
    file="dtsjob.h:166">
    <![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
    {38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download.  Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="2" thread="3136" file="dtsjob.cpp:3652">
    <![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
    file="dtsjob.cpp:3205">
    <![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
    thread="3136" file="netaccessaccount.cpp:288">
    <![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
    type="1" thread="3136" file="netaccessaccount.cpp:858">
    <![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
    (0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
    The IIS server logs u_ex150219.log captures the request:
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 2 5 1509 2
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 1 3221225581 1509 4
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 1 3221225581 1509 3
    2 x Domains: DomainA and DomainX
    - Single domain forests
    - No trusts between domains/forests
    DomainA\PRIMARYSERVER
    - Primary Site Server, MP, DP, IIS, all roles
    DomainX\DP1
    - Distribution Point, IIS, etc
    - CCM client installed

    Based on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM 2012 R2 Distribution Point Installs but does not send packet.

    I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
    send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got. 
    The computer account is in the Administrators group and Admin Domains; 
    Already checked the WMI with Wbemtest; 
    I uninstalled and installed the DP again; 
    Below is the log, changed the name to contoso by issues of customer privacy.
    Sleep 928 seconds...      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:00:07       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:12:13       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5264 (0x1490)
    Thread Handle = 0000000000002330       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5264 (0x1490)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41              
    5264 (0x1490)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    DP thread with thread handle 0000000000002330 and thread ID 5264 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5364 (0x14F4)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41                5364 (0x14F4)
    Failed to process package LAA00003 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41      
    5364 (0x14F4)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:46       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    2528 (0x09E0)
    Sleep 1824 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5736 (0x1668)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5736 (0x1668)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    5736 (0x1668)
    Thread Handle = 0000000000002A50      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with thread handle 0000000000002A50 and thread ID 5736 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5328 (0x14D0)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47       5328 (0x14D0)
    Failed to process package LAA00004 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47      
    5328 (0x14D0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:42:18       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:23       5112 (0x13F8)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5112 (0x13F8)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    5112 (0x13F8)
    Thread Handle = 0000000000001CF0      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:23      
    5012 (0x1394)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:24       5012 (0x1394)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24                5012 (0x1394)
    Failed to process package LAA00003 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:24      
    5012 (0x1394)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:24      
    5012 (0x1394)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:29       4576 (0x11E0)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       4576 (0x11E0)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    4576 (0x11E0)
    Thread Handle = 00000000000025F8       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with thread handle 00000000000025F8 and thread ID 4576 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:29      
    5996 (0x176C)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:30       5996 (0x176C)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30       5996 (0x176C)
    Failed to process package LAA00004 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30      
    5996 (0x176C)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:30      
    5996 (0x176C)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA.   SMS_DISTRIBUTION_MANAGER             14/08/2014
    00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       5292 (0x14AC)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32       4008 (0x0FA8)
    Processing status update for package LAA00003              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32               
    4008 (0x0FA8)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Sleep 1048 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA     SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Sleep 1043 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA.  SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39              
    4008 (0x0FA8)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39       4008 (0x0FA8)
    Processing status update for package LAA00004              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39               
    4008 (0x0FA8)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA    SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 1038 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleep 1033 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:28       5292 (0x14AC)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       5292 (0x14AC)
    Found notification for package 'LAA00003'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Found notification for package 'LAA00004'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x388 (904)      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33              
    2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34              
    2528 (0x09E0)
    Sleep 3600 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
    Lucas Simoes MCTS

    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              13/08/2014 23:57:10               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    13/08/2014 23:57:10       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xBE8)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x3B4)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       3048 (0x0BE8)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       948 (0x03B4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45       3048 (0x0BE8)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45      
    3048 (0x0BE8)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52       948 (0x03B4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52      
    948 (0x03B4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:52       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x1680)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:52               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x18A4)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:16       5760 (0x1680)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:17       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43       6308 (0x18A4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43      
    6308 (0x18A4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50       5760 (0x1680)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50      
    5760 (0x1680)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xF28)      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x11D0)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       3880 (0x0F28)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       4560 (0x11D0)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:16       3880 (0x0F28)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       3880 (0x0F28)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27      
    3880 (0x0F28)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34      
    4560 (0x11D0)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 01:19:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 01:19:34       4004 (0x0FA4)
    No (more) send requests found to process.     
    SMS_PACKAGE_TRANSFER_MANAG
    Lucas Simoes Rezende MCP, MCTS , ITIL V3

  • Report showing which updates are in which Distribution Point folders

    SCCM 2007 SP2 R3.  We're working on Software Updates distribution issues, and are trying to find a way to tell in which Distribution Point folder and subfolder names a certain patch is (or get a list of all patches under a certain distribution folder).
    As an example, on the DP in the SMSPKGG$ folder , I have a folder named RD100492, in that I have a folder named fec8fc58-7ccd-48fe-a16f-ec5eddafef8f, and in that I have the patch named ie8-windowsxp-kb2964358-x86-custom-enu.exe.  I'd like to be
    able to run a report to find where that patch is in the folder structure and also to be able to list everything under a certain folder.
    I've searched through the Views and Tables, but, can't seem to find the right columns. 
    Any ideas?
    Thanks.

    We keep having issues with some SU packages getting corrupt and either one or more patches hang, and dont' let the others install, or they seem to go missing (in once case we had a Patch List with 422 patches in it, and only 11 physically distributed and
    created folders).  MS Premier Support gave us a script to run that clears out the hung patches in WMI on affected computers for the former issue, but, for the latter issues, we have to run a manual comparison of folders find the ones with missing folders,
    and recreate the Patch List.  PITA trying to find things, why we are trying to create a report.
    NOT just idle curiosity...<G>
    I am presuming this info might only be in a Table, but, searching for column names hasn't found it, yet...
    Thanks, Garth!

  • Distribution manager failed to connect to the distribution point

    After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
    I see the following error.
    source: SMS Server
    Component: SMS_DISTRIBUTION_MANAGER
    message id 2391
    Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
    The firewall is not enabled. 
    wbemtest is able to connect to the remote server that has the distribution point role installed.
    The network access account is working.
    How do I fix this?

    but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
    I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
    I have the same issue as described above.
    The IT guys from LukOIL

  • Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

    We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
    point and failed to connect to remote distribution point"
    Errors on the package transfer log file.
    CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
    CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
    Failed to connect to the DP WMI namespace on the remote DP

    Thanks Sandys for your suggestions.
    i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
    server is unavailable" from both ends.
    error:0x800706ba - The RPC server is unavailable

  • SCCM 2012 - Pull distribution point and target PKI or HTTPS DPs

    I have spent several days researching this and so far have found only a single page that even takes a stab at offering a solution.
    Problem:
    Trying to target an HTTPS DP when creating a pull distribution point in SCCM 2012 R2. The link that I'm referring to that does offer a workaround is here(guess I can't post a link, but it ends with the following, how-to-set-an-https-distribution-point-as-a-source-dp-for-pull-dps)
    I have several problems with the proposed solution.
    Is a script really the only way to proceed with something that has up till now been a built in feature with the rest of the product.
    You have to provision the DP to use a self signed cert initially for it to even work, then supposedly you can add the private key to the DP later.
    Does that mean I have to unbind the cert from both the pull and target/source push DP in IIS?
    Powershell which would be a logical way to go, doesn't seem to make any head way(Mr. Snover I know you don't oversee configman but please push for more documentation, you've taught me to live and die by get-help. A single example for a command as large
    as set-cmdistributionpoint or add-cmdistributionpoint is a shame. Perhaps my update help just didn't finish properly and I'm talking prematurely. If that is the case then I apologize!)
    Is there no other solution other than build the DP with a self signed cert then run this VB script and then switch the private key later? I have read through a lot of the pull DP documentation and it makes mention of leveraging the SDK but I haven't seen
    anything definitive. I would like to at the very least convert this from VB to powershell(if that script is the only option) and I know how to convert the portions where it's interacting with the site's WMI namespace (smsprovider if I'm not mistaken).
    What I don't know how to do, rather don't have the chops for is what comes after. The site control file piece, I see it's also WMI and I could spend the time stepping through the different piece and just might to learn more about SCCM in the lab anyhow. I've
    spent the last year getting to know powershell and have spent next to no time with VB. I know enough to recognize what a script is doing.
    The environment:
    The reason this is important for me is I'm about to start the production build(been all lab up till now) that is going to have just under 300 DPs in the field connected via T1 lines. They were all 07 secondary sites. I was thinking about migrating them using
    the migration tool but considering the amount of work its going to take if that link is the ONLY path to target a HTTPS DP then I might as well just spend the time and manually uninstall and reinstall the field DPs. The client count in the field is an average
    of 50 machines per site where there are on-prem devices... Total client count is around 25k. The primary site in the datacenter will house the majority of the site roles unless I start running into resource issues, at which time I will begin offloading site
    roles to one of two more servers that I have slated for the project. No CAS, no Secondaries. SQL is co-located on the primary.
    Ramblings:
    I'm sure there are more people out there using PKI, and using pull DPs. How have you managed to target your HTTPS enabled DPs? Security wants this to be a HTTPS only environment, and up until now I have successfully done that. If someone could please point
    me in the direction of some more thorough documentation I would be very grateful. I understand that this is a somewhat new feature, but there has to be an easier way. Perhaps powershell can cleanly do it with the set-cmdistribution point...but when I update
    help and do showwindow for the command I only get one example and so far haven't found any other stories like mine with the exception of the link I posted in the beginning.
    While I'm rambling, Wally there are a lot of us in the community that are going to miss your presence at Microsoft and should you read this I wish you luck with your new position. But that is a whole different topic. Thanks in advance for any links or help
    you can provide. -K.R.

    Yes, this is the only way, from
    http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_PlanPullDps: "However, you can use the Configuration Manager SDK to specify a source distribution point that is configured for HTTPS. To use a source distribution point that is configured
    for HTTPS, the pull-distribution point must be co-located on a computer that runs the Configuration Manager client. "
    Does "why" really matter , who cares? It just is. Whether it was an oversight, a coding bug, or an act of God doesn't change anything. Why does there "have to be" an easier way? And what's wrong with using the VBScripts others have
    written? A script is a script is a script particularly if you've been given it already. Just because the hammer is pink doesn't mean it can't hammer the nail in.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Distribution-Point sharing (SCCM 2007 - SCCM 2012)

    I've some problems by gathering data from a SCCM 2007 Hierarchy, into the SCCM 2012 environment.
    Gathering Data without enable Distribution Point sharing is successful, enabling Distribution Point Sharing the Process always fail.
    In migmctrl.log i recogniced that the process alway stucks on the following Row for about one hour:
     [Worker]:                                 Query against Legacy Site , @SourceSiteCode=KR1,
    @LastID=KR10001B:                       WITH Block AS                     
    (                          SELECT TOP 2500 ID FROM PkgStatus WHERE ID > @LastID ORDER BY ID                     
    )                      SELECT                         
    ps.ID COLLATE SQL_Latin1_General_CP1_CI_AS AS ID,                          ps.Type AS Type,                         
    ps.SiteCode COLLATE SQL_Latin1_General_CP1_CI_AS AS SiteCode,                          ps.PkgServer COLLATE SQL_Latin1_General_CP1_CI_AS
    AS PkgServer,                          ps.Personality AS Personality,                         
    ps.Status AS Status,                          ps.SourceVersion AS SourceVersion,                         
    ps.UpdateTime AS UpdateTime,                          ps.Location COLLATE SQL_Latin1_General_CP1_CI_AS AS Location,                         
    ps.SigLocation COLLATE SQL_Latin1_General_CP1_CI_AS AS SigLocation,                          ps.ShareName COLLATE SQL_Latin1_General_CP1_CI_AS
    AS ShareName,                          ps.HTTPUrl COLLATE SQL_Latin1_General_CP1_CI_AS AS HTTPUrl,                         
    ps.State AS State,                          ps.SigURL COLLATE SQL_Latin1_General_CP1_CI_AS AS SigURL                      
    FROM dbo.PkgStatus ps                      JOIN (                         
    SELECT d.ThisSiteCode COLLATE SQL_Latin1_General_CP1_CI_AS AS SiteCode FROM SMSData d                           UNION ALL                         
    SELECT s.SiteCode FROM Sites s JOIN SMSData d ON s.ReportToSite = d.ThisSiteCode AND s.SiteType = 1) s2                      ON s2.SiteCode = ps.SiteCode                     
    JOIN DistributionPoints dp ON ps.SiteCode = dp.SMSSiteCode                          AND ps.PkgServer = dp.NALPath collate SQL_Latin1_General_CP1_CI_AS                     
    WHERE ps.Type != 1 AND dp.Action != 3                          AND ps.ID > @LastID                         
    AND ps.ID <= (SELECT MAX(ID) FROM Block)
    And after that this Errormessage appear:
    ERROR: [Worker]:                                 Failed to execute:                      
    WHILE (1 = 1)                      BEGIN                         
    MERGE TOP (1000) PkgStatus AS target                          USING   (                             
    SELECT                                ps.ID, ps.Type, SiteCode = @CurrentSiteCode, PkgServer = dps.PkgServerFQDN,
    ps.Personality, ps.Status, ps.SourceVersion, ps.UpdateTime,                                ps.Location,
    ps.SigLocation, ps.ShareName, ps.HTTPUrl, ps.State, ps.SigURL, SiteCode as SourceSiteCode                             
    FROM #MIG_PkgStatus ps                              JOIN #MIG_DistributionPointSource dps ON ps.PkgServer = dps.PkgServer                             
    WHERE ID in (SELECT PkgID collate SQL_Latin1_General_CP1_CI_AS from dbo.SMSPackages_L)                             )
    AS src                          ON                           
    (target.ID = src.ID AND target.Type = src.Type AND target.SiteCode = src.SiteCode AND target.PkgServer = src.PkgServer AND target.Personality = src.Personality) -- TODO: Ensure we match an index                         
    WHEN NOT MATCHED THEN                              INSERT  (ID, Type, SiteCode, PkgServer, Personality, Status,
    SourceVersion, UpdateTime,                                      Location,
    SigLocation, ShareName, HTTPUrl, State, SigURL)                              VALUES (src.ID, src.Type, src.SiteCode,
    src.PkgServer, src.Personality, src.Status, src.SourceVersion, src.UpdateTime,                                     
    src.Location, src.SigLocation, src.ShareName, src.HTTPUrl, src.State, src.SigURL)                          WHEN MATCHED AND (                             
    target.Status != src.Status                              OR target.SourceVersion != src.SourceVersion                             
    OR target.UpdateTime != src.UpdateTime                              OR target.Location != src.Location                             
    OR target.SigLocation != src.SigLocation                              OR target.ShareName != src.ShareName                             
    OR target.HTTPUrl != src.HTTPUrl                              OR target.State != src.State                             
    OR target.SigURL != src.SigURL                              ) THEN                             
    UPDATE SET                                  target.Status = src.Status,                                 
    target.SourceVersion = src.SourceVersion,                                  target.UpdateTime
    = src.UpdateTime,                                  target.Location = src.Location,                                 
    target.SigLocation = src.SigLocation,                                  target.ShareName = src.ShareName,                                 
    target.HTTPUrl = src.HTTPUrl,                                  target.State = src.State,                                 
    target.SigURL = src.SigURL                          WHEN NOT MATCHED BY SOURCE AND EXISTS(                                 
    SELECT * FROM MIG_Entity me WHERE me.Type = 2 AND me.ObjectKey = target.ID)                              AND EXISTS
    (                                  SELECT * FROM MIG_DistributionPointSource dpsrc                                 
    WHERE dpsrc.PkgServerFQDN = target.PkgServer AND dpsrc.SourceSiteCode = @SourceSiteCode                             
    )                              AND NOT EXISTS (                                 
    SELECT * FROM MIG_Job job                                  WHERE Type = 3 AND dbo.fn_GetNALPathFromMIGJobConfiguration(job.AdditionalConfiguration)
    = target.PkgServer                              )                             
    THEN DELETE ;                            IF @@ROWCOUNT = 0 BREAK                     
    END SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]:                 End syncing Distribution Points related tables. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]:         ========== End syncing distribution points ========== SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    ERROR: [Worker]:         System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.     at System.Data.SqlClient.SqlConnection.OnError(SqlException
    exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler,
    SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)    
    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior
    runBehavior, Boolean returnStream, String method, DbAsyncResult result)     at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)     at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()    
    at Microsoft.ConfigurationManagement.MigrationManager.MigrationRepository.BulkCopyData[T](Snapshot snapshot, LegacyRepository legacyRepository, IntlSqlFormatter formatter, Func`2 watermarkFunc, T lastMaxId, Boolean doNotDrop)     at Microsoft.ConfigurationManagement.MigrationManager.MigrationRepository.BulkCopyData[T](Snapshot
    snapshot, LegacyRepository legacyRepository, IntlSqlFormatter formatter, Func`2 watermarkFunc, T lastMaxId)     at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<SyncDPSettings>d__5f.MoveNext()    
    at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    STATMSG: ID=8610 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS="<SourceSITESERVER>" SITE=CA1 PID=2348 TID=4516 GMTDATE=Do Nov 07 11:28:33.390 2013 ISTR0=""<SourceSITESERVER>" (CA1)"
    ISTR1="<DestinationSITESERVER>" ISTR2="-2146232060" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33
    4516 (0x11A4)
    STATMSG: ID=8605 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS="<SourceSITESERVER>" SITE=CA1 PID=2348 TID=4516 GMTDATE=Do Nov 07 11:28:33.416 2013 ISTR0=""<SourceSITESERVER>" (CA1)"
    ISTR1="<DestinationSITESERVER>" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516
    (0x11A4)
    [Worker]: ==================== Sync Agent Job 16 Ended ==================== SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    ERROR: [Worker]: Microsoft.ConfigurationManagement.Migration.MigrationException: 1 exceptions occurred during syncing.     at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<get_ExecutionPlan>d__7.MoveNext()    
    at Microsoft.ConfigurationManagement.MigrationManager.Job`1.ExecuteNext() SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Start processing status changed event for MIG_SiteMapping.ID=16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]:         Set the schedule item 16 end time SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]:         Set the schedule item 16 status to Failed SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: End processing status changed event for MIG_SiteMapping.ID=16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Disposing Job 16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Removing Job 16 from job manager. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Removing the Job with Id 16. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Disposing worker SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    [Worker]: Disposing current site connection SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131500, 80131500 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131500, 80131500 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
    In the StatusMessages of Migration_Manager there are the following Errormessage:
    The Migration Manager on Configuration Manager site server "<SourceSITESERVER>" was unable to complete the SQL operation on the SQL Server "<DestinationSITESERVER>" of Configuration Manager 2007 due to error "-2146232060".
    Thanks in advance

    Hi,
    1.Please examine reports “All active package distributions” on SCCM 2007 to check whether have package is currently being installed or removed. Then refresh all DPs on SCCM 2007.
    After completing these actions above, try to re-gather data.
    2.If fail, please check the transaction log both on SCCM 2012 and SCCM 2007 SQL Server. Then, a SQL engineer should be involved in this case.(This forum do not support database issue)
    Best Regards,
    Joyce Li
    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.

  • "Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

    Hi
    We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
    During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
    as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
    source site" but data gathering process is completing successfully.
    Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
    Thanks in Advance
    srkr

     Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
    site" but data gathering process is completing successfully.
    Earlier all the shared DPs are showing under  Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
    Anoop C Nair (My Blog www.AnoopCNair.com)
    - Twitter @anoopmannur -
    FaceBook Forum For SCCM

  • After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

    I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
    I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
    Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
    IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

    Hi,
    So you have tried to reinstall IIS conponents and DP?
    Have you checked the distmgr.log? Anything helpful?
    Best Regards,
    Joyce
    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]

Maybe you are looking for