Preferred Distribution Point and Fallback

If I have a protected (preferred) distribution point that doesn't have content distributed to it yet and I have fallback enabled will the client then move to another distribution point that has the content even though that one is protected by other boundaries
which the client is not in?
So question is can a client fallback to another protected distribution point which is referenced by boundary groups that don't include any boundaries the client is in?

Basically yes. It's well explained here
http://blogs.technet.com/b/neilp/archive/2013/01/03/on-demand-content-distribution-fallback-distribution-points-a-2012-configuration-manager-micro-depp-dive.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

  • 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.

  • 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

  • Log location for the DP having only "Distribution point" and "site system" installed

    Hi
    I have one SCCM DP 2012 server. that have only "Distribution point" and "site system"  role installed.
    Is the log will be generated on primary server?  I am not able to find the log on this server.
    Please help me in this.
    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

    HI,
    You will have it in a folder called \SMS_DP\sms\logs, you can also see information about package transfers in the primary site server in the distmgr.log and pkgxfermgr.log files .
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM - Branch Distribution point and Management point on the same server

    Hi All,
    Would like to know if any other SCCM roles like management point , distribution can be installed on the same server on which a branch distribution point is installed?
    Rgs,

    Hi,
    Branch Distribution Points no longer exist in Configuration Manager 2012 and above.
    I'm assuming you want to install additional roles on an existing server that is currently only acting as a Distribution Point and the answer is yes, this is possible, but it depends on which other roles you want to install and there will probably be some
    prerequisites needed.
    Can you elaborate on which roles you are considering installing? 
    Steven Hodson | http://www.stevenhodson.com | @_hodders

  • 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 and SSL

    Hi there,
    I am experiencing issues with what appears to be the intermittent downloading of content from distribution points using SSL.
    We have our own internal PKI and are using Windows 2008 Server, Configuration Manager 2012 SP1 with Windows 7 SP1 Workstations.
    Client to management point communications using SSL work no problem and we can see this reflected in the logs located at ‘C:\inetpub\logs\logfiles\W3SVC1\u_exxxxxxx.log’.
    However, when downloading packages, the majority of the time, content seems to fail back to downloading from /NOCERT_SMS_DP_SMSPKG$/ as opposed to /SMS_DP_SMSPKG$/.
    I am at a loss as to what logs to look at in respect to this!?
    Has anyone experienced this or can point me in the right direction?
     Thanks!

    CAS.LOG
    Requesting content WES00120.3, size(KB) 39445, under context System with priority Low    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    User policy requested with no user credentials.    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Invalid user.    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Submitted CTM job {3D028D6A-F955-4FA2-922F-F74E243BB20E} to download Content WES00120.3 under context System    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Successfully created download  request {E6C88496-5C7A-4E09-8128-4DB87DE6C6E0} for content WES00120.3    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Location update from CTM for content WES00120.3 and request {E6C88496-5C7A-4E09-8128-4DB87DE6C6E0}    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Download location found 0 - http://our.server.com/SMS_DP_SMSPKG$/WES00120    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Download location found 1 - http://our.server.com/NOCERT_SMS_DP_SMSPKG$/WES00120    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Download request only, ignoring location update    ContentAccess    6/5/2014 23:54:43    5116 (0x13FC)
    Download started for content WES00120.3    ContentAccess    6/5/2014 23:54:43    4360 (0x1108)
    Download completed for content WES00120.3 under context System    ContentAccess    6/5/2014 23:54:57    4680 (0x1248)
    Hash verification succeeded for content WES00120.3 downloaded under context System    ContentAccess    6/5/2014 23:54:58    4680 (0x1248)
    Saved Content ID Mapping WES00120.3, C:\Windows\ccmcache\k    ContentAccess    6/5/2014 23:54:58    4680 (0x1248)
    Download succeeded for download request {E6C88496-5C7A-4E09-8128-4DB87DE6C6E0}    ContentAccess    6/5/2014 23:54:58    4680 (0x1248)
    Error: DeleteDirectory:- Failed to delete Directory  with Error 0x00000003.    ContentAccess    6/5/2014 23:54:58    4680 (0x1248)
    Error: DeleteDirectory:- Failed to delete Directory C:\Windows\ccmcache\k.BCWork with Error 0x00000002.    ContentAccess    6/5/2014 23:54:58    4680 (0x1248)
    Saved Content ID Mapping WES00120.3, C:\Windows\ccmcache\k    ContentAccess    6/5/2014 23:54:58    3832 (0x0EF8)
    IIS Log
    2014-05-06 13:33:55 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 23
    2014-05-06 13:33:55 x.x.x.x HEAD /SMS_MP/.sms_pol WFD20061-WES0007E-803AE2D1.3_00 443 - 10.5.3.233 Microsoft+BITS/7.5 200 0 0 197
    2014-05-06 13:33:56 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.0.150 Microsoft+BITS/7.5 200 0 0 7
    2014-05-06 13:33:56 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.32.121 ccmhttp 200 0 0 51
    2014-05-06 13:33:56 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.32.121 ccmhttp 200 0 0 39
    2014-05-06 13:33:57 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.32.121 ccmhttp 200 0 0 40
    2014-05-06 13:33:57 x.x.x.x GET /SMS_MP/.sms_aut MPKEYINFORMATIONEX 443 - 10.3.32.121 SMS+CCM+5.0 200 0 0 9
    2014-05-06 13:33:59 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.1.219 ccmhttp 200 0 64 19
    2014-05-06 13:33:59 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.2.90 Microsoft+BITS/7.5 200 0 0 6
    2014-05-06 13:33:59 x.x.x.x GET /SMS_MP/.sms_pol WFD20061-WES0007E-803AE2D1.3_00 443 - 10.5.3.233 Microsoft+BITS/7.5 200 0 0 2
    2014-05-06 13:33:59 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.60 ccmhttp 200 0 64 291
    2014-05-06 13:33:59 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.2.45 Microsoft+BITS/7.5 200 0 0 6
    2014-05-06 13:33:59 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.1.85 ccmhttp 200 0 0 327
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.60 ccmhttp 200 0 0 318
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.1.85 ccmhttp 200 0 0 272
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system_windowsauth/request - 443 - 10.5.1.233 ccmhttp 401 2 5 15
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system_windowsauth/request - 443 LONDON\j.lin 10.5.1.233 ccmhttp 200 0 0 13
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.60 ccmhttp 200 0 0 273
    2014-05-06 13:34:00 x.x.x.x CCM_POST /bgb/handler.ashx RequestType=Continue 443 - 10.5.17.44 ccmhttp 200 0 0 309968
    2014-05-06 13:34:00 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.1.85 ccmhttp 200 0 0 275
    2014-05-06 13:34:02 x.x.x.x GET /SMS_MP/.sms_pol WFD20061-WES0007E-803AE2D1.3_00 443 - 10.5.3.233 Microsoft+BITS/7.5 200 0 0 2
    2014-05-06 13:34:04 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.3.48 Microsoft+BITS/7.5 200 0 0 7
    2014-05-06 13:34:04 x.x.x.x GET /SMS_MP/.sms_pol WFD20061-WES0007E-803AE2D1.3_00 443 - 10.5.3.233 Microsoft+BITS/7.5 200 0 0 3
    2014-05-06 13:34:05 x.x.x.x GET /SMS_MP/.sms_pol WFD20061-WES0007E-803AE2D1.3_00 443 - 10.5.3.233 Microsoft+BITS/7.5 200 0 0 3
    2014-05-06 13:34:05 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 22
    2014-05-06 13:34:05 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 39
    2014-05-06 13:34:05 x.x.x.x PROPFIND /NOCERT_SMS_DP_SMSPKG$/WES0007E - 443 - 10.5.3.233 SMS+CCM+5.0 401 2 5 1
    2014-05-06 13:34:05 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 37
    2014-05-06 13:34:06 x.x.x.x PROPFIND /NOCERT_SMS_DP_SMSPKG$/WES0007E - 443 DOMAIN\DESKTOP06732$ 10.5.3.233 SMS+CCM+5.0 207 0 0 3
    2014-05-06 13:34:06 x.x.x.x HEAD /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeUpdate.cmd 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 2
    2014-05-06 13:34:06 x.x.x.x HEAD /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeUpdate.cmd 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 200 0 64 3
    2014-05-06 13:34:06 x.x.x.x HEAD /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 1
    2014-05-06 13:34:06 x.x.x.x HEAD /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 200 0 64 3
    2014-05-06 13:34:06 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeUpdate.cmd 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:06 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeUpdate.cmd 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 200 0 0 2
    2014-05-06 13:34:06 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 1
    2014-05-06 13:34:06 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 21
    2014-05-06 13:34:07 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.1.148 ccmhttp 200 0 0 14
    2014-05-06 13:34:07 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 1
    2014-05-06 13:34:07 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 2
    2014-05-06 13:34:08 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.117 ccmhttp 200 0 0 274
    2014-05-06 13:34:08 x.x.x.x POST /SMS_FSP/.sms_fsp - 80 - 10.3.16.46 ccmhttp 200 0 0 5
    2014-05-06 13:34:08 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 1
    2014-05-06 13:34:08 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 17
    2014-05-06 13:34:08 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.1.101 ccmhttp 200 0 0 20
    2014-05-06 13:34:08 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.117 ccmhttp 200 0 0 290
    2014-05-06 13:34:08 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.16.46 ccmhttp 200 0 0 31
    2014-05-06 13:34:08 x.x.x.x POST /SMS_FSP/.sms_fsp - 80 - 10.3.16.46 ccmhttp 200 0 0 5
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.16.46 ccmhttp 200 0 0 38
    2014-05-06 13:34:09 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 1
    2014-05-06 13:34:09 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 21
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.16.46 ccmhttp 200 0 0 40
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.117 ccmhttp 200 0 0 278
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.2.113 ccmhttp 200 0 0 30
    2014-05-06 13:34:09 x.x.x.x GET /SMS_MP/.sms_aut MPLIST1&WFD 443 - 10.3.16.46 SMS+CCM+5.0 200 0 0 7
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.2.113 ccmhttp 200 0 0 34
    2014-05-06 13:34:09 x.x.x.x GET /SMS_MP/.sms_aut MPLIST1&WFD 443 - 10.7.2.117 SMS+CCM+5.0 200 0 0 97
    2014-05-06 13:34:09 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.2.246 Microsoft+BITS/7.5 200 0 0 6
    2014-05-06 13:34:09 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.3.2.113 ccmhttp 200 0 0 33
    2014-05-06 13:34:09 x.x.x.x GET /SMS_MP/.sms_aut MPKEYINFORMATIONEX 443 - 10.3.2.113 SMS+CCM+5.0 200 0 0 10
    2014-05-06 13:34:11 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:11 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 33
    2014-05-06 13:34:11 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.3.65 Microsoft+BITS/7.5 200 0 0 6
    2014-05-06 13:34:12 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:12 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 115
    2014-05-06 13:34:12 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.1.196 ccmhttp 200 0 0 17
    2014-05-06 13:34:13 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:13 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.0.247 Microsoft+BITS/7.5 200 0 0 9
    2014-05-06 13:34:13 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 235
    2014-05-06 13:34:14 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:14 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 476
    2014-05-06 13:34:15 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:15 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 660
    2014-05-06 13:34:15 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.2.197 ccmhttp 200 0 0 20
    2014-05-06 13:34:16 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 - 10.5.3.233 Microsoft+BITS/7.5 401 2 5 0
    2014-05-06 13:34:16 x.x.x.x GET /NOCERT_SMS_DP_SMSPKG$/WES0007E/sccm /SkypeSetup.msi 443 DOMAIN\DESKTOP06732$ 10.5.3.233 Microsoft+BITS/7.5 206 0 0 300
    2014-05-06 13:34:16 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 23
    2014-05-06 13:34:18 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.66 ccmhttp 200 0 0 364
    2014-05-06 13:34:18 x.x.x.x POST /SMS_FSP/.sms_fsp - 80 - 10.9.0.48 ccmhttp 200 0 0 87
    2014-05-06 13:34:18 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.66 ccmhttp 200 0 0 290
    2014-05-06 13:34:18 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.0.253 Microsoft+BITS/7.5 200 0 0 8
    2014-05-06 13:34:19 x.x.x.x GET /SMS_MP/.sms_pol %7B7be5bfb6-03e6-4938-adac-1c412e0b1cf0%7D.2_00 443 - 10.5.1.152 Microsoft+BITS/7.5 200 0 0 5
    2014-05-06 13:34:19 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.7.2.66 ccmhttp 200 0 0 303
    2014-05-06 13:34:19 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.9.0.48 ccmhttp 200 0 0 279
    2014-05-06 13:34:19 x.x.x.x POST /SMS_FSP/.sms_fsp - 80 - 10.9.0.48 ccmhttp 200 0 0 88
    2014-05-06 13:34:20 x.x.x.x CCM_POST /ccm_system/request - 443 - 10.5.3.233 ccmhttp 200 0 0 20

  • Distribution point and failed content

    Hi I have SCCM 2012 R2 and 5 Pull DPs now when I distribute Packages to these Pull DPs some times i can see some package didn't distributed and giving me failed content but when I redistribute it i can see the SCCM Start to redistribute the package from
    the failed point which is will resume the distribution and to be honest this very coll specifically for big packages but on some packages starting from 0,
    to be honest I'm Confused when the SCCM will resume and when will not.
    Thanks,
    Ahmed Ali

    Hi,
    There might be many files in a package. I think when one file transfers failed, it starts from the failed file.
    I suggest you use BITSAdmin to monitor BITS jobs in the transfer queue.
    http://msdn.microsoft.com/en-us/library/aa362813(v=vs.85).aspx
    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.

  • Management point and Distribution point behind netscaler for virtual ip/dns name

    Is it supported to place a server behind a netscaler for using a virtual IP/DNS name?
    We are looking into placing our distribution points and management points behind the netscaler to provide firewall functionality.
    We would point our clients to a different DNS name for each individual MP and DP to provide routing through the netscaler.
    As far as I know this is only possible using IBCM.
    Please let me know if this is possible without IBCM internally.

    Using a different DNS name is problematic as there is no way to specify an alternate fqdn for a site system on the intranet. Clients use the actual fqdn of the system hosting the role; this is given out by the MP directly to the client based upon the site
    system's actual name.
    You could manipulate name resolution in a variety ways so ultimately the actual IP used wouldn't matter, but that's useless unless the client is using the proper name.
    If you you could use the same name and IP, then it should work no problem as long as the traffic is properly delivered to the site system. Ultimately, nearly all client agent to site system traffic is nothing more than WebDAV via IIS on the site system so
    just basic web traffic.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Monitoring and troubleshooting in-place distribution point upgrades

    I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
    through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
    the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
    But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
    Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

    Hi all
    I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
    Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
    points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
    12 hours.
    I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
    point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
    local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
    If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
    article. There seems to be a bug which is currently in a solving process.
    For me, there are two solutions for this problem:
    1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
    2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
    I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
    SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
    after 3 days.
    Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
    As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
    during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
    the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
    Kind regards Stefan Somogyi

  • Distribution point Critical

    Hi all,
    How to setup in sccm 2012 r2 not to use some drives for Distribution point , because we have some drives has very low disk space it shows critical in site status .
    Thanks,
    Sengo

    Specify the preferred drive(s) during the configuration of the Distribution Point and place a file called
    NO_SMS_ON_DRIVE.SMS on the other drive(s). This file will prevent ConfigMgr from using it to store any information.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Distribution Point install failure

    Hi all,
    In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers.
    About two days ago I have done an inplace upgrade on one server to 2012 R2.
    The upgrade went mostly without a hitch except for the SCCM DP.
    The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content.
    So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy...
    I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log.
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)>
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)>
    Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)>
    ~Processing 18.INS  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)>
    ~DPID 18 - NAL Path ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ , ServerName = [SERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:20:59.263-600><thread=7708 (0x1E1C)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)>
    ~Created policy provider trigger for ID 18  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)>
    DPConnection::Connect: For [SERVER NAME HERE], logged-on as rondo\sccmpush~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)>
    Found notification for package 'RDO00002'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)>
    Found notification for package 'RDO00003'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)>
    Failed to find a valid drive on the distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x88 (136)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)>
    DPConnection::Disconnect: For [SERVER NAME HERE], reverted to SYSTEM context~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([SITE SERVER NAME HERE]) is submitting SDK changes from site(RDO)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x2B78 (11128)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128
    (0x2B78)>
    ~Retrying package RDO00003  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)>
    No action specified for the package RDO00003.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136
    (0x88)>
    ~Retrying package RDO00002  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)>
    No action specified for the package RDO00002.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)>
    Thread Handle = 00000000000035C0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)>
    ~Failed to install DP files on the remote DP. Error code = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)>
    ~Drive E: is not valid. Error = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)>
    STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER
    NAME HERE]\" ISTR1="[SERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[SERVER
    NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)>
    ~Will try again after 20 mins ...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)>
    Thread Handle = 00000000000029C8  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)>
    DP thread with thread handle 00000000000035C0 and thread ID 9852 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)>
    DP thread with thread handle 00000000000029C8 and thread ID 10028 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)>
    ~Package RDO00002 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)>
    The package and/or program properties for package RDO00002 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)>
    ~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)>
    ~SourceVersion (3) of package RDO00002. SourceVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136
    (0x88)>
    ~Failed to process package RDO00002 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)>
    ~Package RDO00003 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)>
    The package and/or program properties for package RDO00003 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)>
    ~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)>
    ~SourceVersion (1) of package RDO00003. SourceVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:21:06.797-600><thread=11128 (0x2B78)>
    ~Failed to process package RDO00003 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)>
    ~Sleep 1826 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)>
    ~Sleep 1821 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)>
    So I have two questions,
    How can I fix this and how do I prevent it from happening to the remainder?
    Thank you all in advance.
    Daniel.

    The server does not appear at all
    You really need to give more information so we can help you.
    What about the logs, are you getting the same errors after making all the changes? please upload the full log to SkyDrive or any other place. 
    Did you reboot this DP\DC?
    Can you successfully ping from the primary to DP and back?
    Do you have access from primary to C$ on that DP?
    What account did you choose for installation?
    Did you choose to install IIS?
    If IIS was installed, try to remove it and let DP installation install it automatically.
    Confirm that PowerShell 3.0 is installed.
    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
    Hi Idan,
    I will go through and reply to each of the suggestions you have made below;
    1. The log that was attached was the full log. I cleared the log prior to setting up the DP and copied the contents into this forum after it has stopped.
    2. Yes I had rebooted, Many times.
    3. Yes I can successfully ping either way.
    4. Yes I can access the C$ share on the DP from the Primary
    5. I have tried both the PC account and a service account that is part of the domain admins group and also added to the local admins via a net command
    6. Yes I did choose to install IIS and I had already tried uninstalling IIS and running the install again.
    7. as above
    8. Yes Powershell 3.0 is installed
    PS C:\Users\admindg> $PSVersionTable
    Name                           Value
    PSVersion                      4.0
    WSManStackVersion              3.0
    SerializationVersion           1.1.0.1
    CLRVersion                     4.0.30319.34014
    BuildVersion                   6.3.9600.16394
    PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
    PSRemotingProtocolVersion      2.2
    Thank you for all your suggestions and I hope that the information that I have provided is sufficient to draw a better picture of our environment.
    Regards,
    Daniel

  • Redistributing Application to Distribution Point Group

    Hey Guys - 
    Just a quick question for you about something I've never been 100% sure about and wanted to clear up...
    Let's say I have an "Application" in which I've added files to the source folder which is required by the script the application runs.  After adding the file, I need to update it's distribution on all 3 of my distribution points (which all
    happen to be in a DP Group.)  Which of the following methods will accomplish this or is the preferred method?  
    1. Select Application in console, choose "Deployment Types" tab, right click on type I want to update and choose "Update Content"
    2. Open Application's Properties, choose "Content Locations" tab, select the Distribution Group (which contains all 3 DPs) and click "Redistribute"
    3. Open Application's Properties, choose "Content Locations" tab, select each of the 3 distribution points and choose to "Redistribute" to each one of them
    Below is what my Content Locations looks like when distributed to all 3 DPs.  As is was distributed to the group containing all 3, it lists the group and the 3 DPs for a total of 4 objects.  Which of the above methods (or a different one) is the
    best way to go?
    Thanks!
    Ben K.

    Option #1
    http://eskonr.com/2013/09/sccm-configmgr-2012-how-do-i-refresh-the-application-after-change-in-source-files-or-source-location/
    Benoit Lecours | Blog: System Center Dudes

  • Org Unit as Distribution Point for Document Distribution

    Hello Experts,
    I would like to maintain a distribution point for the document distribution. Therefore i still have maintained the distribution point (it is an org unit) in the available communication types (INT, RML,..) in SPRO...->Document Distribution->Define Communication Type.
    But now every time when a distribution package will be started for distribution I get an error message: "Function <senden> not possible". The package should be send via distribution type INT to the distribution point.
    Perhaps the communication type INT is not maintained for the org unit yet?Where can i do this?
    Regards,
    Christian

    Hi Christian
    The distribution point under Type of distribution point and Distribution point is used under the following conditions:
    1. If distribution is initiated manually and the Distribution immediately indicator was set without entering an explicit distribution point.
    2. If distribution is initiated manually and the
    Distribution immediately indicator was not set.
    3. If distribution is initiated by an event.
    If the "Send to distribution point" indicator is set and no distribution point is entered explicitly, the current user becomes the distribution point if distribution is initiated manually. If distribution is initiated by an event, the user that triggered the event becomes the distribution point.
    Follow this Procedure.Also Check all the setting in Define Distributio Types for Distribution type INT
    where you mention distribution Point details.You will have to explore alittle bit.
    With Regards
    Mangesh Pande

  • Configuring Failover Cluster Server Share as a Distribution Point

    Hello and thanks for this helpful forum!
    I am trying to configure a server share as a Distribution Point and am running into problems.  I am running SCCM R2 on Server 2008.  I am trying to use a clustered share coming from 2008 R2 Failover Cluster.
    I have been trying to get this working for the better part of 2 days now, and I have successfully created a Distribution Point to another 2008 Server (non-R2) by simply using the site system (not the server share).
    When I try to use the server share option, I keep receiving an error with Message ID 4701 stating that the SMS Site System Status Summarizer cannot access storage object
    \\servername\sharename$ on site system
    \\servername\sharename$
    The operating system reported error 2147942467: The network name cannot be found.
    The server share is defined as a site system as
    \\servername\sharename$
    I am trying to create a "Packages" directory under it, so I'm using the option "Share the distribution folder" under the Data Access tab of the Package.
    In addition, I have given local admin rights to the site server on both nodes of the cluster.  I have given the site server modify rights to the share and NTFS permissions.  I have given Authenticated Users Read access to the share and NTFS.
    As I mentioned, I can take another server and define a Site System as a DP and everything will work properly.  I am still missing something though regarding using a Server Share.
    Thanks so much in advance for your assistance.

    Hi,
    No DP on NLBs:
    http://technet.microsoft.com/en-us/library/bb735883.aspx
    Yes, but that is NOT a failover file cluster. Is there a workaround? It seems silly to have to stand up an additional server for this. It also seems odd that the forthcoming version of SCCM would not have some support for failover clustering which was a HUGE
    improvement over the previous clustering solutions from MS.Jeffrey S. Patton Assistant Director of IT School of Engineering Computing Services University of Kansas 1520 West 15th Street Lawrence, KS. 66045-7621

Maybe you are looking for

  • Error occurred while converting the file "song name" the required folder cannot be found

    In ITunes 12, while trying to import from CDs I keep getting this message "error occurred while converting the file "song name". The required folder cannot be found". It will import 2 or 3 or 5 songs and then this message. I have tried multiple CDs,

  • List fonts used in a document, search by font.

    Help! I cannot find a way to list, by name, of the fonts used (past tense) in a document. Like in the document properties: where the word and character count is. Example: The author used Arial, Arial Condensed and OCR A in her document. I would like

  • AIR-AP1131AG-A-K9 Reload Reason: FAILED CRYPTO INIT.

    Hi All, I have a standalone AP of model AIR-AP1131AG-A-K9 and have changed the mode to LAP by using mannual archive command. However after changing the mode to LAP it gives below log and keep on booting. Reload requested by LWAPP CLIENT. Reload Reaso

  • Flash Galleries generate multiple image folders

    Can anyone explain why the Flash templates need to generate 3 image folders (Large, Medium, Small) in addition to the Thumbs? I'm pushing my disk space limit on my hosting server, and wonder if I really need to upload all these, as the combined size

  • FORM HELD WHEN RUNNING

    HI EVERY BODY I AM RUNNING DATABASE 9I AND FORM 6I I CREATE A MENU FROM WHICH I CALL DIFFERENT FORMS I USE CALL_FORM TO CALL A FORM ANY WHERE WHEN I CALL A FORM SOME TIME IT WORK PROPERLY AND TAKE NO TIME BUT SOME TIME IT WILL TAKE TIME AND LOOKS LIK