Pull Distribution Point on updates removing

(1)When you distribute packages, you can use Pull Distribution Point. By this way, "SMS_DISTRIBUTION_MANAGER" component can do more Jobs. OK.
(2)My question is about the process of updates removing. SCCM Site takes long time to remove expired updates from DP. Is this action managed by "SMS_DISTRIBUTION_MANAGER" or SCCM Site notifies Pull DP to remove updates like (1)

distmgr is not involved when it comes to pull DPs. So assumption (1) is wrong. All actions are done by the pull DP after it was "notified" by the site.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

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

SCCM 2012 R2 & Pull Distribution Point Casuing 0 Byte amd64 folders

Experiencing an extremely frustrating problem.
ENVIRONMENT:
1 Primary Site Server / DP (Main Office)
40 DP's (Remote School Locations)
- Hosted on a file server VM
- Contains 3 partitions: C: (System), E: (Data), I: (PKG share)
OS: Server 2008 R2 (Primary Site Server and File Servers / DP's)
SCCM Version: SCCM 2012 R2
We recently upgrade to SCCM 2012 R2. I have confirmed that this has not caused the problem I am about to describe. The only other change that has occurred recently is that we configured all of our DP's at each of our 40 sites to be pull distribution points.
While this seems to be working fine we are now seeing a whole bunch of 0 Byte alpha numeric folders with a 0 Byte amd64 subfolder. These folders seem to attach to the E: drive on all of our File server distribution points....for the life of me I cannot figure
out why and this occurred as soon as we switched to pull distribution points. While this does not seem to be having an erroneous effect on our environment, it is annoying and somewhat disconcerting as I have not been able to ascertain what is causing it. Any
SCCM admins out their ever encountered this?
Thanks

Yes, I have examined the logs using cmtrace and done a search for the amd64 string to see if any of the logs indicate its creation as part of the pull dp process. I have not found anything as of yet.
Thanks

Pull Distribution Points - Any views?

We are about to embark on a project to upgrade to 2012. We have a lot of branch locations (>250 and rising) and traditionally these locations hosted secondary sites. What is currently being proposed is to have a primary with two secondary sites under
that and an even distribution of DPs underneath the secondaries in place of the old 2007 secondary sites. The purpose of the secondary sites in this instance is to alleviate the 250 DP limit load per site.
With SP1, there are pull DPs that might be an alternative to this approach, allowing us to do away with the secondary sites. If this were the case I'd probably look at having three standard DPs coming off the primary and the pull DPs set to get their content
from these 'randomly'. I put the word in inverted commas, as according to http://technet.microsoft.com/en-gb/library/gg712321.aspx:
If there are multiple source distribution points with the same priority, the pull-distribution point nondeterministically selects one
of the source distribution points that share that priority.
What is meant by nondeterministically?
One assumes this would mean randomly but is this the case? Has anyone got any experience of this and pull DPs in general? Do they work as well as traditional DPs? Any advice is appreciated.
Thanks

Non-deterministically can be equate to random. It effectively means there's no (publically) defined way that they choose.
There is no difference between a PullDP and a normal DP from the client's perspective -- they have no way to know the difference and no reason to know the difference because they are in fact the same as far as making content available to clients.
The only actual difference with Pull DPs is how they acquire their own content. PullDPs use BITS and use the same logic (and code even to my knowledge) that clients themselves do (they don't require the actual client agent though). There have been a lot
of improvements in PullDPs in R2 as well as some of the CUs. There was even a KB for a hotfix released in the past couple of weeks that discussed a registry tweak to help PullDPs along.
PullDPs, in general, work quite well and there is no specific reason to avoid them. They do require a bit of extra care and feeding, but to my knowledge, nearly all of the kinks with them have been worked out.
Have you considered using BranchCache as an alternative (or one of the third-party ACPs) though? Not trying to make your decision harder or recommend one over the other, just making sure you knew about other options that could address your challenge.
Jason | http://blog.configmgrftw.com | @jasonsandys

Pull Distribution Point Requirements (BITS?)

We have recently migrated to all SCCM 2012 infrastructure. All of our recent deployments are Server 2012 but we have a lot of Server 2008 R2 64bit. There is a lot of documentation online and some say BITS is required for DPs and some say not. Our packages
have been struggling to reach our DPs and Pull DPs. Does anyone have any opinion if BITS should be installed on DPs or Pull DPs. I know I have read that BITS is not required on Server 2012 however it states nothing about Server 2008 R2 64bit. Any opinion or
experience would be helpful.

Nothing specific to Pull DP...
Windows Server 2012 or Windows Server 2012 R2:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_Win2k12SiteSystemPrereqs
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
A pull-distribution point is considered to be a client when it accesses another distribution point to obtain content.

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

SCCM 2012 SP1 Distribution points not updating

The package that holds my MS updates is not updating on my distribution points ever since I upgraded to SP1. If I remove the package from the distribution points and then add it back it will work fine. This is happening to me every I add updates to this
package. Below is part of the smsdpprov.log file from one of my distro points.
[C90][Thu 02/14/2013 11:03:51]:Content 'f16906f8-d1d4-44df-8cf7-35dd7428893a' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:55]:Content '1ebc4751-063f-46dd-a7ae-096cce3545dc' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:56]:Content 'b2903470-59e0-4d89-a1a5-808b58c9fd4e' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:58]:Content 'f058ee07-a66e-4bdf-8a53-7cc30affe333' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:00]:Content '03546ec3-2613-46ce-bf0c-a6064149f2c6' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:03]:Content '7492e432-b69c-478c-8c7b-7c2396302eb4' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:05]:Content '995a1a82-6d7c-4fb6-9e1b-8cfac070b787' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:06]:Content 'a0a2a75d-beab-49ca-96e5-e03afa98dc8f' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:08]:Content '21061204-1d54-4262-bc90-cf5922191940' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:11]:Content 'ce9e07ad-1467-4da5-bf03-8c7013743d34' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:14]:MoveFile failed for \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f.ENS00006.temp to \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f
[C90][Thu 02/14/2013 11:04:14]:FileRename failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:CContentDefinition::Finalize failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:Failed to finalize content '6178f7ae-a640-4e04-a851-abd13239a50f' for package 'ENS00006'. Error code: 0X80070005

I've got the same issue. When I look at the smsdpprov.log on the distribution point, this is what I see.
[EB0][Thu 10/31/2013 08:39:08]:Content '0a3fe62c-58ce-47c7-b635-e23407515ecb' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:Content '809b4727-78b3-48bd-85ca-f2fdcf668297' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:MoveFile failed for
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93.ONB0007A.temp to
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93
[EB0][Thu 10/31/2013 08:39:08]:FileRename failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:CContentDefinition::Finalize failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:Failed to finalize content '5263454e-e3de-49e5-a077-48dba0eefe93' for package 'ONB0007A'. Error code: 0X800700B7
If I reboot the DP, then the package gets updated. I'd like to figure out how to make this not happen :)

Update distribution point errors updating the boot image....SCCM 2012 r2

Fairly new to SCCM (started on it about a month and a half ago and only been troubleshooting different things). As of this moment I'm attempting to get imaging back up, which it looks as if the drivers did not get injected into the boot image properly
before. This seems to be resolved but when I attempt to update the distro point i end up with this error below. Any help is appreciated.
Error: The wizard detected the following problems when updating the boot image.
• Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4716;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"SMS00005\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;

What version of Configuration Manager are you running, and are you using MDT?
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

Remove package from Distribution Point

I have been fighting with an OS deployment for the last day. The log was showing it was unable to find the package p0100001 which was my boot image. I eventually got it working as I failed to configure my boundary correctly. But it got me wondering...
In SCCM 2007, it was pretty straight forward on how to remove packages from distribution points. But I still can't figure out how to remove a package, specifically a boot image, from a DP. I can view the distribution in the monitoring section and see the
package successfully deployed, but what if I wanted to remove that boot image from the DP? How is this done. I'm sure it's staring me in the face, but I'm missing it. Thanks!

I realize this is an old post, but I am dealing with the same issue regarding the removal of deployment package contents from Distribution Points. After removing a Distribution Point from the Contents Locations tab on one of my Deployment Packages,
how long does it take for the deployment package to be removed from the distribution point. I have removed a large deployment package from a distribution point, but am not seeing any increase in the available free space.
Any help would be appreciated.
Muskie
Muskie

Client update not working due to distribution point

Since upgrading from 2012-SP1-R2 i haven't been able to upgrade the clients, im fairly sure now after a fair amount of research this is down to the distribution point. I would assume that if there was an issue with the distribution point the update wouldn't
be sent to the clients.

Im fairly sure i have the automatic updated all done, via the Hierarchy settings. Its only when i went to distribute content on one of my packages i realised that the issue might be with the MP/DP as i get "failed to distribute content details will
be available after server finishes processing"
In distmgr.log i get "package ****00002 does not have a preferred sender.
Used 0 out of 3 allow processing threads
In smsdpmon.log There is nothing for months which was my next check.

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

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

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

Pull Ditrbuation Point

Hi i have one primary site and One Secondary site and one Pull Distribution point the source of Pull DP is the secondary site now my question is what happened if i need to distribute package to the Pull DP without distribute it to the secondary site DP?
is this package will be pulled or will be distributed from the primary site?
Thanks,
Ahmed Ali

okay good so if i want to distribute packages to the PULL DP only i have to add the primary site DP as source DP for this Pull DP.
now what will happened if i want to distribute package to PULL DP and this package already presented on the primary and secondary site DP which DP will be used as source DP however that Primary and Secondary are considered as source DPs.
Thanks
Ahmed Ali

Deploying operating system and applications to branch distribution points

Dears,
Is there a way to distribute the content of an operating system image or an application package manually to a branch distribution point to overcome network bandwidth limitation and let SCCM know it is distributed there or you still need to distribute
content via SCCM console?
Regards,

You will always need to perform action via the console (or do something similar via PowerShell). I think the options of prestaging content, or a pull distribution point could be beneficial for you. Have a look here for more information:
http://technet.microsoft.com/en-us/library/gg682083.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Pull Distribution Point on updates removing

Similar Messages

Maybe you are looking for