Is it possible to retry Distribution Point role removal if failed initially?

During my lab testing I came across a scenario where if you select to remove a distribution point role while the remote server hosting the distribution point isn't contactable, SMS_DISTRIBUTION_MANAGER won't retry the removal. Is there a (clean) way to manually
remove the distribution point role from the remote server or trigger SMS_DISTRIBUTION_MANAGER to attempt the removal again? In this case I will be rebuilding the server anyway, but I'm curious if there is a way to do this in case I encounter it in a production
scenario

may be you can try this solution http://blogs.msdn.com/b/rslaten/archive/2006/03/01/removing-a-retired-dp-from-all-your-packages.aspx
http://eskonr.com/2009/11/report-that-gives-bad-distribution-points/
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

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

  • Is the distribution point role required on an SCCM 2012 site server?

    I am wondering if the distribution point role is required on an SCCM 2012 site server. 
    We have an installation of SCCM 2012 SP1 with a site server, and two remote DPs. 
    I would like to remove the DP role from the site server, and stand up another server (2012) at the same location, making it a DP and also have it hold the WSUS content.
    I was successful in creating the DP on the new server.  I distributed all of our packages to the new server. 
    I then removed the packages from the DP on the site server, and removed the DP role from the site server. 
    After making these changes, we lost the ability to deploy packages, either from the new DP server, or from the previously existing DPs that were at other locations. 
    Deployment status in the SCCM console showed that clients were “waiting for content”.
    I found that adding the DP role back to the site server, and distributing packages to it corrected the problem. 
    Deployment resumed after doing that.  Is it necessary to have packages on a DP on the site server? 
    We want to virtualize the server, and would like to make it as small as possible to facility restores.

    Hi,
    Have you checked the log file distmgr.log? Maybe it can give us some clues.
    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.

  • Package content on Primary Site Server (no Distribution Point Role)

    Hey,
    I have the situation that there are 3 Servers with following roles installed:
     1.File Server
     2.SCCM 2012 R2 CU3 Primary Site Server / Database Server (Was a distribution Point previously to update to CU3)
     3.Distribution Point
    Our packages are all stored as "source" on the File Server.
    Now some SCCM Applications / packages are created and distributed to the distribution point.
    Unfortunately on the Primary Site Server the folder "SCCMContendLib" extends as it does on the distribution point (so this means that all packages are distributed to the primary site server, too.
    My question is now- why? :)
    Is this really needed (I see no reason for it) or is it a problem in the infrastructure (if yes - how can I resolve it)?
    Thank you for help
    Kind Regards

    Not a problem with your infrastructure. What you're describing it the default behavior for ConfigMgr, in terms of storing content on the primary.
    -Nick O.

  • Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

    Hi,
    Some of our DP's have a warning (Shown with a yellow exclamation mark) that never goes away. I have run a script on the DP's that could check for inconsistency in WMI, but it found nothing. Everything seems to work fine, but it is annoying that everything
    is not green when it should be!
    The warning is:
    Failed to retrieve package list on the distribution point. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.

    Hi Peter,
    Yes I have tried to validate all content to no avail. ;(
    No help to find in smsdpmon.log, I really think it is a bug...
    Here is a small part of it:
    ]LOG]!><time="03:50:29.934-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:29.943-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package 'C010003E' version 0 ...]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:586">
    <![LOG[Report status message 0x4000094C to MP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.996-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package share for package 'C010003E' version 0 ...]LOG]!><time="03:50:32.510-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:629">
    <![LOG[Package C010003E is verified successfully]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:649">
    <![LOG[Report state message 0x40000950 to MP]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:889">
    <![LOG[Report Body: <ReportBody><StateMessage MessageTime="20141129025032.000000+000" SerialNumber="0"><Topic ID="C010003E" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>C010003E</Param><Param>["Display=\\dk01dc1sscm01.local.avk.dk\"]MSWNET:["SMS_SITE=C01"]\\dk01dc1sscm01.local.avk.dk\</Param></UserParameters></StateMessage></ReportBody>
    ]LOG]!><time="03:50:32.520-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:32.528-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000959 to MP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000952 to MP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[DP monitoring finishes evaluation.]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:500">

  • 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

  • SCCM 2012 Distribution Point without IIS

    Hello. My environment is SCCM 2012 SP1. I need to set up distribution points on several Windows Server 2003 machines. These machines have certain security requirements. One of which is no IIS. In SCCM 2007, I was able to create DPs without installing IIS.
    This prevented the use of BITS extensions but was acceptable. I cannot seemed to do the same with SCCM 2012.
    As a test, I performed three steps to test a DP without IIS on a Windows Server 2003 machine 1) Made the primary server a local administrator on the Windows Server 2003 machine, 2) Installed RDC using the msrdcoob_x86.exe file, 3) in the admin console, I
    created a new site system server with the distribution point role. I did not check allow it to install IIS to install/configure during the setup. The distribution point reports a successful installation status but I get three errors when I try to distribute
    a package. The first error message is Failed to create virtual directory on the defined share or volume of the distribution point. The second error is Distribution Manager failed to connect the the distribution point. The third error is Distribution Manager
    failed to process package "Package Name". I know that installing IIS with BITS extensions and WebDav support would fix this problem. However, I would like to use the DP without IIS like I did in SCCM 2007.
    Looking at the supported configurations, I see the below. This leads me to below that it is possible. Does anyone know if this is possible? If so, what I am missing in my steps.
    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

    BITS is a client side technology and has nothing to do with the server side of a DP or IIS and thus is irrelevant.
    WebDAV was built into the relevant components of ConfigMgr obviating the need for the Windows Server WebDAV component so that's not needed for 2012 at all and thus N/A.
    Ultimately, no, this is not possible. IIS is required on a DP in ConfigMgr 2012. This is clearly listed at http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs.
    Jason | http://blog.configmgrftw.com

  • SCCM 2012 Distribution Point server in a workgroup as well as the clients

    HI, 
    It is possible to have a distribution point set up by SCCM 2012 R2 which resides in a workgroup to manage workgroup users.
    Basically, SCCM 2012 R2 is setup within a domain and a forest, The clients in the workgroup resides in a DMZ. The server in the DMZ is also within the workgroup. 
    For some reasons, at this time, it is not possible to add the server to the Active Directory to push it the distribution point role and therefore managing thoses clients within the workgroup. 
    Is there a way to set up the distribution point role to a server in a workgroup?
    Thank you
    E

    https://technet.microsoft.com/en-us/library/gg682077.aspx?f=255&MSPPError=-2147217396#BKMK_SupConfigWorkgroups
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Recovery Distribution Point

    Hi All
    I am busy with creating a recovery plan for our SCCM 2012 related servers
    I have a question according to the recovery of a Distribution Point
    Is it possible to do a full server recovery in case of a mayor issue (failed) of a server with the role distribution point (and is it supported).
    If it is not supported (or possible) what is the best way of removing de failed distribution point from the SCCM environment
    Step 1 : Remove failed Distribution Point from Boundary Group
    Step 2 : Remove failed Distribution Point from Distribution Point Group
    Step 3: How to remove the entries of the failed Distribution Point from the SCCM Console (SCCM environment) , I think the failed Distribution Point cannot be removed from the Console (Remove Rol Distribution Point will not work anymore I think).
    I hope someone can help me with completing the steps
    Regards,
    Johan

    A full server backup and restore of a DP site system would be OK, but you would need to ensure that you either have content validation enabled or you re-distribute any changed content to that restored DP.
    You can simply delete a failed (server down) distribution point site system, rather than trying to remove the distribution point role.  You would need to re-provision that site system and re-send all of the content.
    My Personal Blog: http://madluka.wordpress.com

  • Setup additional distribution point

    Hi all,
    Currently i have one SCCM server setup and it already has distribution point role installed. We have several branches with limited network bandwidth and file server for each of them.
    My question is, is it possible to add more than one distribution point to one SCCM server and assign them to related branch? I am considering to set the file server on each branch as additional distribution point on the master "SCCM" server. How
    can i achieve this?
    Thanks.

    It is not possible to add particular site system role in this case DP to multiple time for single server.
    However it is possible to setup upto 100 distribution point & 2000 branch distribution point per site. you may use your branch file servers as distribution point/branch distribution point. please refer below link for more information.
    http://technet.microsoft.com/en-us/library/bb680869.aspx
    you may set these new distribution points/branch distribution point as protected one, so only client from particular branch/remote office can access it.
    refer below link for more information about installation & configuration process:
    http://technet.microsoft.com/en-in/library/hh272770.aspx#BKMK_Distribution_Point
    http://technet.microsoft.com/en-us/library/bb932133.aspx
    http://technet.microsoft.com/en-us/library/bb932176.aspx
    Prashant Patil

  • Server 2012 Distribution Point - Is BITS Required ?

    Hi All,
    I have deployed a Distribution Point on Server 2012, i went through the documentation and there was no mention of BITS being a prerequsite...
    So my Question is - Do we still need to install BITS as a prereq for the Distribution Point Role on a Server 2012 box.
    Cheers

    There still seems to be some contradictions on whether you are supposed to install BITS or not when setting up a Distribution Point.
    http://technet.microsoft.com/en-us/library/gg712264.aspx under the section
    "To install Internet Information Services (IIS) on Windows Server 2008 and Windows Server 2008 R2 computers"
    clearly shows for Windows Server 2008 R2, select the
    Background Intelligent Transfer Services (BITS) check box. 
    If you look at http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs under the Distribution Point prerequisites, there
    is no mention of installing BITS unless we are to assume the statement "You can use the default IIS configuration" means to select BITS as described above?
    Plus the following note under Additional prerequisites is as clear as mud.
    Note
    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.
    Most of us understand the client facilitates the BITS downloads but is there still a need for the
    BITS Server Extensions and the only way to get those on a Server 2008 R2 box is to select the
    Background Intelligent Transfer Services (BITS) check box?    

  • ConfigMgr Distribution Point

    Hi all,
    We had to move a distribution point (Server XY) to another site.
    First we uinstalled the distribution point role and the site system role from this server (Server XY).
    Then we installed the distribution point again on the same server (server XY).
    We modified the the boundaries and boundary groups, double checked everthing but the client can still not discover the distribution:
    CAS.log: the number of discovered DPs (including Branch DP and Multicast) is 0
    Any ideas?

    When you say "site" do you mean a ConfigMgr site or do you simply mean geographic location?
    If location, then you really didn't have to do any of the above at all except modify the boundaries.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • R2 - Distribution Point not working properly

    From my main SCCM R2 server, I went to add an additional server with multiple roles. 
    I can't tell if it's working properly, however. 
    For example, the Distribution Point role. I've set it as PXE boot, and our Cisco admin has setup an IP helper accordingly, but when I go to boot a client to PXE, it gets an error "Windows failed to start". 
    File: \Tmp\x86x64{13902C6F-DD5F-4467-88C9-1BAC44DF8287}.bcd
    status: 0xc0000098
    Info: The windows boot configuration data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. 
    From Boot Images on the main SCCM server, I had pushed them to the distribution point. Or so I thought? I mean, the "In Progress" tab says the distribution point server name I'm trying to push it to under the "Device" column. Then
    Description reads "Distribution Manager Successfully processed package "Boot Image (x64)" (package ID = STL00005)". 
    But it's been sitting like that for over an hour...
    WDS role is also installed on the DP I'm trying to PXE boot from. 
    Should I disable WDS and then what do I do in SCCM to get it to PXE boot and make sure the boot file for SCCM is on there? 

    Nvm I got it up
    I removed the WDS server but not the role of the DP in question
    I then removed the roles from the server within SCCM console
    Then added back only Distribution Point, then I was able to distribute the boot ups to it again, no errors in logs
    PXE boot working fine with task sequences 
    This is what I ran into after getting PXE to not throw DHCP error
    http://www.windows-noob.com/forums/index.php?/topic/8836-problems-with-pxe-and-nothing-in-smspxelog/

  • Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point

    We currently in the process of the doing a site server refresh at all our remote sites. Each remote site currently has a physical 2012 SP1 DP, and will be replaced with  a new DP at each location, and will eventually decommission the current one.
    What's the best way to introduce a new DP and remove the old one?
    Thanks
    Bern

    You can use this method if distributing through the WAN is not an option.
    http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx
    If you don't care, just add it to SCCM and replicate your content. Modify your boundary once done.
    I hope you have a DP Group, if so, just make it member of the group and all your content will be copied. If not, you'll have to go through all your content and add it manually or script the process using PowerShell.
    To remove your existing it's simply a matter of removing the "Distribution Point" role on your Server using the SCCM Console. (Administration / Site Configuration /Site Server, select your distribution point, right click Remove)
    Benoit Lecours | Blog: System Center Dudes

  • New Site Server with Distribution Point & Software Update Point Roles not pulling SUGs

    I just set up a new server & installed the DP & SUP roles on it.  I am getting the following in the log this is just a small sample as its kind of repetative:
    Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
     SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Retry 10 times SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Start to evaluate all packages ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Start to evaluate package 'FPP00002' version 0 ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x4000094C to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Failed to evaluate package FPP00002, Error code 0x80070002 SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
     SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x40000952 to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    DP monitoring finishes evaluation. SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Failed to evaluate some packages after 10 retry SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    The Console shows for the DP that it's waiting for content and I don't see where I can create a Prestage Package
    # When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

    D:\SMS_DP$\sms\logs\smsdpmon.log
    This is the 2nd server in our SCCM 2012 Sp1 Hierarchy.  It is set up with the following Site System Roles:
    Component Server
    Distribution Point
    Site System
    Software Update Point
    It is Prestaged Enabled.  My intent is that the client systems @ the location where this DP is located will use it to pull their Microsoft Updates from as well as content for any Applications we push to them rather than going over the WAN to the Primary
    Site Server.
    IN Distribution Point Configuration Status. the console shows "Failed to update package" & "Packaget Transfer Manager failed to update the package "yxz00040". Version 3 on Distribution Point server.my.domain.com review pkgxfermgr.log for more information
    about this failure."
    It also goes on toe list 2 possible causes and solutions
    Site servers does not have sufficient rights to the source directory.
    (Site server account is a member of local Administrators on Primary)
    Not enough disk space available
    (I have over 1TB of available space and primary site server has only 150GB available for entire content repository, both applications and sofware updates.)
    # When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

Maybe you are looking for