Unable to create package shares on distribution points

For any OSD packages in our environment (like images, driver packages, etc) I always check the option "Copy the content in this package to a package share on distribution points", so that we are able to run content directly from the DP's in a task
sequence instead of downloading it first to clients. But I've noticed now that for any new package I create, the package shares aren't being created thus my OSD tasks are failing due to missing content. When I check the copy content option for a new driver
package and monitor the distmgr.log, here is what I see:
Copying package DEV0007F to the package share location \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F on the server ["Display=\\hou-sccmdp03.network.local\"]MSWNET:["SMS_SITE=YYC"]\\hou-sccmdp03.network.local\   SMS_DISTRIBUTION_MANAGER
4/3/2013 11:02:35 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:35 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:40 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:45 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:50 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:55 AM   2156 (0x086C)
Failed to set security on \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F for package DEV0007F   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:03:00 AM   2156 (0x086C)
That same sequence of errors is repeated for every distribution point we have. I checked the sharing permissions on the SMSPGKE$ and SMSSIG$ folders on the DP and everything looks correct. I only started noticing this issue after our SP1 upgrade, but I can't
find anything from Microsoft saying this is a known bug or how to fix it. This is also affecting new distribution points that we created after the SP1 upgrade, so I don't believe going down the remove/reinstall of all the DP's route will work. Any suggestions?

Copying package DEV0007F to the package share location \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F on the server ["Display=\\hou-sccmdp03.network.local\"]MSWNET:["SMS_SITE=YYC"]\\hou-sccmdp03.network.local\   SMS_DISTRIBUTION_MANAGER
4/3/2013 11:02:35 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:35 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:40 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:45 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:50 AM   2156 (0x086C)
SetObjectSecurity failed; 0x80070002   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:02:55 AM   2156 (0x086C)
Failed to set security on \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F for package DEV0007F   SMS_DISTRIBUTION_MANAGER   4/3/2013 11:03:00 AM   2156 (0x086C)
I've seen similar errors after installing SP1:
Failed to set share security on share \\DP.domain.tld\SMSSIG$. Error = 5
Failed to set access security on share SMSSIG$ on server DP.domain.tld
DPConnection::Disconnect: Revert to self
Cannot find or create the signature share.
Solution for that case: Use the computer account instead of a site system installation account:
That might fix it.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

Suspend upload of packages to a distribution point

Imagine this situation:
I've created a new distribution point and added it to a distribution point group with a lot of content (packages) assigned to the group. I discover right after SCCM starts to upload packages to the new DP, that the network usage to that office reaches its
limit, and instead of using Rate limits, I would like to stop the package transfer for a while until the weekend comes. If I want to suspend the upload of packages to a distribution point for a day or two, will it be OK to remove the new DP from the DP group?
Freddy

You can certainly remove the DP from the group, but I doubt that that would stop the flow of content. It may also cause the content to be deployed, then removed, and then redeployed when you add it again.
Why not just temporarily change the rate limits or scheduling window and then change it back later?
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2012r2 - Remove "invisible" packages/applications from Distribution Point

Hello alltogether,
I've encountered the following issue:
Our distribution points are displaying applications/packages as "In Progress - Waiting for Prestage content".
These packages doesn't exist anymore. Neither as prestage file nor in the config manager itself. We never tried to apply this package by using a prestage file because such a file never existed.
Even if I open the "content" tab of one distribution point, I can't find these packages in there.
The exact status of this package is the following:
Message: Distribution Content
Message Detail: Distribution Manager instructed Package Transfer manager to send Package "x" to distribution point "y".
Status Type: In Progress
I want to remove these "ghost" packages from the Distribution Status overview. Anyone has a clue how to accomplish this?
Thanks in advance!
Best Regards
Feyh

Hello,
thanks for your answer!
Unfortunately no, there is no information about these files.
Yesterday we installed a new one, extracted all of our prestage files on it and watched the status. The Packages weren't listed in the "Distribution Point Configuration Status".
After some time we added the new DP to our general DP-group where all of our packages/applications are assigned to. Now the "non-existing" packages are added with the "in Progress" status.
I had a look into "Distribution Point groups -> Our group -> properties -> content" but these packages aren't displayed in the list. Some of the packages are now in the "waiting for prestage content" state, others are staying with the "Detail will
be available after the server finishes proccessing ...".
We managed to remove one of the packages by deleting it from the database.
The following statement removed it from the Distribution status overview. However, we still are able to find the package in the database.
select * from SMSPackageswhere PkgID = 'P100003B'
DELETE from SMSPackages
where PkgID = 'P100003B'
Apparently the delete-statement affected 72 rows. But we are having no clue which. As long as we are not sure we killed anything important we are not going to do this with the other packages because it's the productive system. We can't reproduce this in our
test system...

Package deployment to Distribution points

We have SCCM 2012 SP1 with 5 primaries, 23 secondaries and 80 distribution points around the globe. How does SCCM distribute packages to the DPs? Past practice has us distributing to the primaries first, then the secondaries
and then finally the DPs. The question was raised that the DPs get their content from which server? A team member and I have been unable to locate the information in the Tech-net library, does anyone know the answer or can
we get a link to where we may be able to locate the info ourselves?
Thanks.

I am hoping someone else can fill in some gaps for you, but I will give it a shot. The primary site server grabs the content from the content source and sends it to the DPs. This is one reason to plan out your source folder structure carefully.
There was some recent discussion on this here:
https://social.technet.microsoft.com/Forums/en-US/afa0a018-889a-46dd-866c-ee688899ace6/what-is-the-best-practice-for-package-source-locations?forum=configmanagerapps#ad772921-6f85-44c5-8250-7ca1aff6dc11
Jeff

Unable to create packaging material PO

Hi Expert!
Need your help again..
I can't create packaging material PO.. The error is.."source not include in list despite source list requirement". Why am i having this error? How to fix it? Is it because of vendor has been blocked? How to check? Please anyone help me to solve this problem. Otherwise i can't create any PO for packaging material..
Thanks..

Hi
Please maintain the source list for the material
Or remove the soure-list req tick form the material master.
Regards
Niti Narayan

Unable to create a linked server that points to an availability group listener.

I don't even know if this scenarios is supported or not, I can't find any documentation on it.
I have a couple SQL 2012 servers setup using AlwaysOn Availability Groups. The listener (SQLAG1) is setup and working as expected with applications. The 2 machines are in different subnets, so we are using the MultiSubnetFailover=True on the
connection strings to ensure that failover works.
From an SQL 2014 box I want to create a linked server that points at the Listener. I'm able create the linked server, but it appears like sql server is not using the MultiSubnetFailover=True and it fails to connect. Here is what I used to create
the linked server;
EXEC sp_addlinkedserver
@server = N'SQLAG1',
@srvproduct = N'SQL2012',
@provider = N'SQLNCLI11',
@datasrc = N'SQLAG1',
@provstr = N'Provider=SQLNCLI11.1;Data Source=SQLAG1;MultiSubNetFailover=True',
@catalog = NULL
GO
Do anyone know if this is supported? if so what it proper way to create the linked server?
Thanks!!!

Thank you.
OLE DB in the SQL Server Native Client does
not support the MultiSubnetFailover keyword.

Unable to create a share

When I am trying to create a share I receive the following error message "An error occurred whgilw trying to share C. Incorrect function. The shared resource was not created at this time.". I am signed on as a user with Admin rights and I am using Windows
7 Ultimate Edition 64bit. I am on a network with no domain. If someone could help I will be very greatful.
Rick Herritt [email protected]

Hi,
As this thread has been quiet for a while, I assume the issue has been resolved. At this time, we will mark it as "Answered". If the issue still persists, please feel free to
reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
Niki
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Niki Han
TechNet Community Support

Unable to create a share on file cluster

I am having problems creating a share on a new 2012 file cluster. I keep getting an error message that "The resources must be online on the same node for this operation". The disk is online according to disk management and residing on the node
on which I am trying to set this up. How do I get around this message?

Hi,
Before going further, how did we create the cluster file server? Did we follow the following checklist?
Checklist: Create a Clustered File Server
http://technet.microsoft.com/en-us/library/cc753969.aspx
Besides, regarding creating a shared folder in a clustered file server, the following article can be referred to for more information.
Create a Shared Folder in a Clustered File Server
http://technet.microsoft.com/en-us/library/cc732302.aspx
Best regards,
Frank Shen

WIP: Creating packages for other distributions

Hi,
I didn't find any related articles, so I've decided to start work on one:
https://wiki.archlinux.org/index.php/Us … tributions
Looking for any input (especially about Fedora/RPM). Even telling me such an article would be useless.
Cheers,
Alad
Last edited by Alad (2014-05-30 20:41:08)

Interesting you should post this today. I just started working on 'porting' makepkg to debian (makedeb). My goal as described here is to have a tool that can turn something very much like a PKGBUILD (DEBBUILD, RPMBUILD) into a package for those distros.
My approach will currently run only on the target distro. So perhaps this is a bit of the inverse of your method (me using arch PKGBUILDs in debian to make a .deb rather than you using a tool in archlinux to make a .deb).
I have a bit of a "proof of concept" example that works as intended here and I've now modified the actual makepkg script from pacman to create a full featured (but yet untested) makedeb script.
I'd love to have a tool to make fully compatible .deb or .rpm packages from within archlinux, but I know very little about those packaging standards, and had grown a bit frustrated with their (lack of and/or confusing) documentation while I was trying figure it out.
Last edited by Trilby (2014-05-31 00:46:02)

Unable to create CIFS share in NSS4000 after upgrading firmware

Hi,
Hopefully someone can help.
Today I have upgraded the firmware of an NSS4000 ( i wish i hadn't) to the latest 1.16 version.
As it seems I was not able to connect to this server anymore using SMB share CIFS. When i looked under shares I noticed that CIFS was unselected. Went in an selected it back on and hit update. Went in again and found that again it had disappeared and only leaves FTP as selected.
Anyone any ideas on how i can tackle this issue? Have been browsing the web for answers for hours with no luck!!!
Thanks, Mo

Welcome to Cisco Community, hope we are able to correct this problem with you.
When you updated the FW, did you run the update twice, and follow the on screen instructions after reboot, stating to flush the browser cache? It really seems like we either are seeing bogus information due to cached pages, or we have corrupted the config. If possible, please post the log files from your NSS to see if we are able to see what is failing.

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

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

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

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

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

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

2012 -- 2012 Migration: How to Reassign Distribution Points that Reside on Source Secondary Site Servers to the Target Site

Source hierarchy AAA is at 2012 R2 CU3 and contains a primary site and 14 secondary sites (A01 through A14). The 14 secondary site servers hold the following roles:
Site system
Management Point
State migration point
Site server
Site database server
Component server
Distribution Point
Target hierarchy BBB is also at 2012 R2 CU3 and contains only a primary site. The goal is to "downgrade" the severs at source secondary sites A01 through A14 to distribution points.
AAA was added as a source site. Data gathering was done. A migration job was created an run, and distribution points from the source hierarchy were shared to allow a phased migration of the clients.
We have reach the point where we are ready to reassign distribution points in sites A01 through A14 from AAA to BBB, but none of the shared distribution points are eligible for reassignment. We surmise that since the DP role is not the only role on
these servers (as you can see from the bullet list above), they are ineligible for reassignment. We are unable to remove most of the roles. In fact, the only 2 roles that can be removed are the DP role itself, and the State Migration
Point. If we delete the secondary site, it removes ALL roles...not leaving any behind...including the one we need...DP.
My question is 2-part:
Is our assumption correct? Must a DP role be the only one on the server for a DP to be eligible for reassignment?
Is there any way we can reassign these DPs instead of deleting everything and building them from scratch?
These secondary site servers are in branch offices and host a lot of distributed packages. It would be very inconvenient to have to rebuild the DPs from scratch and redistribute all those packages over the WAN.

Full Disclosure: I have never used this tool myself. I intend to, however the opportunity or time to do so has not yet arisen.
You could use the techniques outlined in CloneDP (https://gallery.technet.microsoft.com/scriptcenter/CloneDP-for-SCCM-2012-SP1-825ce5b1) to create prestage media on each DP and rebuild. That at least would prevent redistributing over the WAN
Ken provides a nice writeup too: http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx

Unable to create package shares on distribution points

Similar Messages

Maybe you are looking for