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.

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

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

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

All DPs read "Failed to retrieve the package list on the distribution point"...

About 2 weeks ago all 10 of my DPs started reporting the following warning (roughly 2 weeks after upgrading to R2):
"Failed to retrieve the package list on the distribution point ["Display=\\<server.FQDN>\"]MSWNET:["SMS_SITE=<code>"]\\<server.FQDN>\. Or the package list in content library doesn't match the one in WMI. Review
smsdpmon.log for more information about this failure.
This warning has appeared in my environment once before and I've read a number of posts regarding it. In the previous situation I found the problematic package ID recorded in smsdpmon.log and followed the standard procedure of redistributing and then proceeded
with a validation check on the affected DP. These steps resolved the issue originally.
This time around the package ID is not referenced in smsdpmon.log. It had the same error but the ID was not listed. Unfortunately the logs have already rolled over and I forgot to save a copy so I don't have anything to reference. I'm curious if anyone else
has seen this behavior and what the recommended fix is.
As always, appreciate the help!

I used the following process to clean up these warnings on my DPs:
Setup content validation checks for each of my affected DPs to run every morning (previously only set to weekends). I did this so when I made a change I could validate whether or not it worked the following day. It would be great if there was a way to force
these checks manually but I haven't found a method yet.
After the content validation check completed I filtered through the smsdpmon.log on each affected DP. This revealed the package ID that was causing the issue.
In my environment the package in question was not needed so I deleted it. If it is required I suspect re-distributing it would work as well.
At this stage the problem was still not fully resolved for me. Even though I had deleted the package WMI was still inaccurate. I used this script to scrub WMI on all affected DPs and it picked up the problematic package ID:
http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69
My content validation checks are now passing and the warnings are being cleared. YEAH!
As a final note - After running the PS script Nickolaj posted I ran started seeing dozens of error checks on my packages (Distribution Manager failed to process package "Laptop Drivers" (package ID = XYZ00123).) After doing some research
I found I was prone to this issue:
Failed to start DP health monitoring task. In my case the suspect file was called "Microsoft". I moved it to another location and the errors cleared immediately.
Hope this info is helpful to others!

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.

Error 0x80070002 when Task Apply OS has "Access content directly from the distribution point" checked

When I check "Access content directly from the distribution point" for the "Apply Operating System" task in my OSD Task Sequence, I get the failed error 0x80070002 at the step when running the sequence from WinPE.
If I uncheck it, I don't get that error or have any problems.
I've ensured that in the properties of my OS Image in the Data Access that "Copy the content in this package to a package share on distribution points" is checked, and that I Updated DPs.
Am I missing any other settings?
The reason I'm trying to do this is because the "Download" speed of the WIM is incredibly slow. I already installed a hotfix (KB2905002) that fixed this for my Dell systems, but it's not speeding it up for another computer model I'm imaging in
the same way. The Dell computers, after I installed the server hotfix, will downloading the .wim file at 1% per second. However the HP thin clients I'm imaging download at about 1% every 15 seconds, and I'm not sure if that's due to their hardware or what.

Hi,
The error means file not found. So you need to check the smsts.log to see which DP it is accessing, then go to that DP to check the Shared Folder smspkg to make sure the file is there.
For the download performance issue, there are various reasons. You need to check your Switch bandiwidth and if the NIC driver is up to date. If downloading locally is slow, Accessing directly could be slow too.
Juke Chou
TechNet Community Support

How to re-distribute a Task Sequence to the Distribution Point.

Hi, All
I am new to Administering SCCM 2012. I have followed the instructions on this forum carefully and it has
helped me.
I created a TS and for some reason I delete it. But when I created the New Task Sequence it will not allowed
me to re-distribute the content to the old DP where the previous one was.
I went to the Technet site and it says that.
Important
If the task sequence that you selected references content that is already distributed to a specific distribution point, that distribution
point is not listed by the wizard.
http://technet.microsoft.com/en-us/library/hh273490.aspx
This is because when I resend or deploy the job to the laptop I keep getting this error " The Task Sequence
cannot be run because the program files associated with "CHM00008"cannot be found on the distribution Point". But I know is on the DP. I have updated it and redistribute it. I can browse to it.
And help to show me how to re-distribute the TS to the DP will be highly appreciated.
Thanks
KKA

A task sequence itself cannot be distributed to a DP, but the associated content can.
Have you configured a network access account? Double check if CHM00008 is deployed with 100% success.
Torsten Meringer | http://www.mssccmfaq.de

Once an OS image has been distributed to the distribution point, do I keep the source wim as well?

Just curious what do all you SCCM masters do?,
I really don't know if I explain can this right, but here goes.
If I capture a pre-installed/pre-configured imaged to my sccm server to a folder called OSIMAGES, lets call the image myosimage.wim, once I have distributed content of myosimage.wim to the distribution point, do I really need to keep the source copy of myosimage.wim
in the folder OSIMAGES?

Well how does the ConfigMgr know if the content is correct and intact, if it cannot compare it to the one in the source? Do not remove the sources.
http://blogs.technet.com/b/configmgrdogs/archive/2012/04/16/configmgr-2012-content-library-overview.aspx

DP's have Warning "Failed to retrieve the package list on the distribution point" - How to Clear it?

All but one of my DP's (A new one I just created) have this Warning Message: "Failed to retrieve the package list on the distribution point". They all seem to be working, I can update and push new content to them.
When I go to the smsdpmon.log, it has an error for a package, but I've since redistributed it, and it is working fine. (Items below are snips from the smsdpmon.log)
CContentDefinition::LibraryPackagesWmi: The package data in WMI is not consistent to PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
CContentDefinition::LibraryPackagesWmi: Package PS10011B can't be found in PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
CContentDefinition::LibraryPackagesWmi failed; 0x80004005 SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
Failed to evaluate package PS10011B, Error code 0x80070002 SMS_Distribution_Point_Monitoring 11/16/2013 6:29:50 PM 3920 (0x0F50)
Since then, after redistributing the package, it clears up the logs... but not the warning in Monitoring:
Start to evaluate package share for package 'PS10011B' version 0 ... SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
Package PS10011B is verified successfully SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
So since everything appears to be working fine, how do I clear out that Warning, so I have nice Green Check Mark Icons in my Monitoring Tab, so when something actually does go wrong, I won't just ignore it since it's always been set to Warning?

I'll have to review this. The script
here, alone did not solve the my issue. Interesting that it say I do not have any inconsistencies on any my DP's now, but I run the other one on a single DP, it states I have inconsistencies still.
$WMIPkgList = Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib | Select -ExpandProperty PackageID | Sort-Object
$ContentLib = (Get-ItemProperty HKLM:SOFTWARE\Microsoft\SMS\DP).ContentLibraryPath
$PkgLibPath = ($ContentLib) + "\PkgLib"
$PkgLibList = (Get-ChildItem $PkgLibPath | Select -ExpandProperty Name | Sort-Object)
$PkgLibList = ($PKgLibList | ForEach-Object {$_.replace(".INI","")})
$PksinWMIButNotContentLib = Compare-Object -ReferenceObject $WMIPkgList -DifferenceObject $PKgLibList -PassThru
##### section 1 #######################
Write-Host Items in WMI but not the Content Library
Write-Host ========================================
$PksinWMIButNotContentLib
Foreach ($Pkg in $PksinWMIButNotContentLib){
Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib -Filter "PackageID = '$Pkg'" | Remove-WmiObject -Confirm
I wonder if the first script is not looking for INI's whereas the second one is. I verified that the INI's do exist...
I'll run the second on all of my DP's, remove the left over INI's, and report back again next week on status.
-Tony

Content is being distributed to the distribution point - stuck at "In Progress"

I have Windows Updates due to be installed on all international machines tonight at 12 AM, and our main distribution point gets the files just fine. Our international sccm server, however, is not.
I'm get the "In progress" on the Content View under Monitoring, but it has been sitting like that for over 8 hours. I know there are a ton of logs in the C:\Program Files\SMS_CCM\Logs location that are constantly updating.
Is there a log in there I can attach or show to help determine what's going on? There are so many logs. However, this is a very serious issue, and I don't know what's going on. It worked just fine, then last months worked, except for the fact that after
about a week, it would say that the content "Failed" on the second sccm distribution point. And now, this month's updates are stuck on "In Progress" on copying it over.
Please let me know what I can look into, as soon as possible.
Thank you!

Alright, so this is what it's looking like:
PkgXferMgr.log has a ton of these:
======== Finished Processing Cycle ( 12/13/2014 6:20:56 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
Checking for sending capacity. Used 0 out of 15.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.696+420><thread=3632 (0xE30)>
COutbox::TakeNextToSend(pszSiteCode) $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
No (more) send requests found to process.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.698+420><thread=3632 (0xE30)>
======== Starting Processing Cycle ( 12/13/2014 7:20:56 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
======== Processing Jobs ======== $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
Job count is 0. $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.588+420><thread=3628 (0xE2C)>
======== Finished Processing Cycle ( 12/13/2014 7:21:06 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
Checking for sending capacity. Used 0 out of 15.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
COutbox::TakeNextToSend(pszSiteCode) $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
No (more) send requests found to process.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
======== Starting Processing Cycle ( 12/13/2014 8:21:06 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
======== Processing Jobs ======== $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
Job count is 0. $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.774+420><thread=3628 (0xE2C)>
======== Finished Processing Cycle ( 12/13/2014 8:21:16 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
distmgr.log:
Start adding package to server ["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.455+420><thread=2464 (0x9A0)>
Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
Thread Handle = 00000000000010C0 $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=4932 (0x1344)>
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.484+420><thread=4932 (0x1344)>
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.485 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="US10008A" AID1=404 AVAL1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
$$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.485+420><thread=4932 (0x1344)>
~The contents for the package US10008A hasn't arrived from site US1 yet, will retry later. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932 (0x1344)>
STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.486 2014 ISTR0="US10008A" ISTR1="US1" ISTR2="JP1"
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A" $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932
(0x1344)>
DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
DP thread with thread handle 00000000000010C0 and thread ID 4932 ended. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
~Package US10008A does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.999+420><thread=2464 (0x9A0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=US10008A, Version=3, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.000+420><thread=2464 (0x9A0)>
~StoredPkgVersion (0) of package US10008A. StoredPkgVersion in database is 0. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
~SourceVersion (3) of package US10008A. SourceVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=2464 GMTDATE=Sat Dec 13 06:23:09.096 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="US10008A"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A" $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.096+420><thread=2464
(0x9A0)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.097+420><thread=2464 (0x9A0)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:12.865+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.394+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.395+420><thread=3348 (0xD14)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.409+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.410+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:53:17.953+420><thread=3992 (0xF98)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:00:08.191+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:14:38.368+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:23:23.041+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:53:28.130+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.375+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.376+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:14:38.544+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:23:33.227+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:53:38.332+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.577+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.579+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:14:38.734+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:23:43.428+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:53:48.526+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.783+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.785+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:14:38.926+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:23:53.624+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:53:58.722+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.985+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.986+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:14:39.116+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:24:03.820+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:54:09.080+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.393+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.394+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:14:39.521+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:24:14.228+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:54:19.325+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.612+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.613+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:14:39.713+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:24:24.423+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:54:29.521+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.817+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.819+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:14:39.905+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:24:34.623+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:54:39.721+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.021+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.023+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:35.600+420><thread=3992 (0xF98)>
Found package properties updated notification for package 'US10008A' $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.602+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.604+420><thread=3992 (0xF98)>
Found notification for package 'US10008A' $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.606+420><thread=3348 (0xD14)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.624+420><thread=3348 (0xD14)>

Distribution Point Offline - how long before SCCM client connects to alternative DP?

Hi, I'm doing some testing on my SCCM 2012 setup and have been attempting to test distribution point resiliency and fall-back.
I have a single primary site with two distribution points. One is in the main datacentre and is in the same boundary group as the clients and tagged as fast connection. The 2nd DP is in the DR datacentre, in a separate boundary group (no client subnets are
in this group) and the distribution point has the allow failback checked. Both DP's have the same content.
After shutting down/taking offline the main distribution point, I've then kicked of an install of a package on a W7 client. It attempts to download and stays in that state for as long as I leave it. Looking in the logs I can see both DP's returned to
the client (the DR tagged as REMOTE), it then attempts to connect to the main DP and just keeps retrying over and over.
I thought if it couldn't connect to the main DP it would then failback to the DR DP, but it doesn't appear to do this. Is there a timeout on this before it would fail back?
I'm also currently trying adding the DR DP to the main boundary group and tagging the connection as slow so the main DP would still be used first. Again both DP's are returned to the client when installing software and the client attempts to connect
to the main DP over and over without using the DR DP which is online.
Is this normal behaviour or do I have a configuration issue?
Appreciate your help.
Carl

Hi, just to update on this thread, I raised a support call with Microsoft and the end result is that SCCM2012 clients wont fall back to an alternative DP where a DP is offline. The fall back is only for when content isn't on a DP. The 8hr timeout doesn't
appear to be in affect anymore.
What I have managed to get to work and test out is removing our production DP (also primary site server) from the production content boundary group, then clients will fall back to the DR DP as this is the only other DP available with content.
I've managed to perform the update to remove the site server from the boundary group while the primary site server is offline, by using a PowerShell script to connect to the SCCM provider on the DR site server (DP/MP/SUP) to perform the update as our site
database is off-box. This works well and the changes replicate to the SQL replica in DR that the DR MP uses and when clients failover to the DR MP they then begin using the DR DP and packages can be installed etc.
How funny, I just fixed this at a Client this week.
This is default client behavior as MS CSS probably told you, the client thinks the Distribution Point is coming back online soon so it waits, for good reasons. For some reason I keep thinking "7 days" not 8 hours, but maybe wrong.
I have a work around for this, it just requires a change to the Distribution Points DNS record. Head to the DNS server, find the record for the Distribution Point that is down, change the IP address to a different member server IP address, this will cause
the client, when it flushes it's DNS cache, to get an updated DNS record for the Distribution Point and it will try to connect to the Distribution Point using the changed IP address, which then induces what the client thinks is a severe error which makes it
go to the next Distribution Point in the list it got from the Management Point. Once you've recovered the Distribution Point and it is back online, change it's IP address back in DNS or just let the Distribution Point update its own DNS record when it boots
up (if configured to do so) and viola, you are back in business.
Test, test and test again before ever putting something from "the web" into your production environment. I just implemented this at a client to solve their issues with their DR procedure.
Rob Marshall | UK | My Blog |
WMUG |
File CM12 Feedback |
CM12 Docs |
CM12 Release Notes

Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

Hi,
The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
Below are the patches.
MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
all the 2008 server updates are set and marked to download.
Please help me out on fixing this.

So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Failed to retreive the pacakge list on the distribution point...

I am slowly cleaning up some content mismatches among my distribution points after an R2 upgrade. I am down to my final 2 DPs, both of which are my only standalone DPs. Both servers report the same errors in smsdpmon.log:
Failed to evaluate package XYZ0013A, Error code 0x80070002
Failed to evaluate package XYZ0013B, Error code 0x80070002
I checked the following locations and these Package IDs are nowhere to be seen:
DP\SCCMContentLib\PkgLib - no matching INI files.
WMI - no matching records (gwmi -Namespace root\sccmdp -Query "select * from SMS_PackagesInContLib where PackageID = 'XYZ0013A")
SCCM Console - nothing listed.
Where else could these packages be recorded? They're obviously not in use anywhere.

Hi,
Do you have any errors in the distmgr.log and pkgxfermgr.log file on the site server?
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.

Change "Update distribution points on a schedule" in SCCM 2007 via powershell script

Hi
I would like to change the Custom Schedule start time in the "Update distribution points on a schedule" on a package in SCCM 2007 with out logging into the SCCM console.
I have following line code to query the package.
Get-WmiObject
-Namespace
"Root\SMS\Site_$sitecode"
-Query
"SELECT * FROM SMS_PackageBaseclass WHERE PackageID='$PackageID'"
-ComputerName $ServerName
The problem is I only get the "SourceDate" and "LastRefreshedTime" from the query. I am not sure if I change the "LastRefreshTime" that it would change the start time in the Custom Schedule

Hi Jason
I progressed a little bit with you help. I now have the following bit of code.
$Package = Get-WmiObject -class SMS_Package -Namespace "Root\SMS\Site_$sitecode" -Filter "PackageID='$PackageID'" -ComputerName $ServerName
$RefreshPkg = $Package.RefreshSchedule()
$RefreshPkg.RefreshSchedule
I get the following error:
Method invocation failed because [System.Management.ManagementObject] doesn't contain a method named 'RefreshSchedule'.
At line:7 char:1
+ $RefreshPkg = $Package.RefreshSchedule()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (RefreshSchedule:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

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

Similar Messages

Maybe you are looking for