RBAC: grant rights to update distribution point

Hi,
I have created a specific group which has all rights to manage specific items within SCCM 2012 console.
Everything works fine BUT the distribution of packages to the distribution point, this is empty when distributing the packge.
Rights on Distribution point are: Read, Copy to Distribution Point.
Please advise.
J.
Jan Hoedt

"Site: Read" is most likely missing.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

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

SCCM 2012 R2 Pull DP fails, works on Update Distribution Points

I'm seeing some odd behavior out of a DP, in particular around driver packages. The system is running SCCM 2012 R2. When I create the driver package I deploy it to the DP on the Primary Site Server. That usually happens in a couple of minutes or less.
I then deploy to a remote DP configured for Pull. This generates the log entries below in the PullDP.log. Even waiting hours doesn't seem to help. If I do a Update Distribution Points for the package, it runs successfully. I know
there was something similar fixed in SP1 CU3.
Intializing DP Monitoring Manager... PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting site code PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting DP Cert Type PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting this DP NALPath PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report state message 0x00000004 to MP PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report Body: <ReportBody><StateMessage MessageTime="20140322004854.000000+000" SerialNumber="1"><Topic ID="ACC0006D" Type="902" IDType="0"/><State ID="4" Criticality="0"/><UserParameters
Flags="0" Count="3"><Param>ACC0006D</Param><Param>["Display=\\DP.xxxxx.xxx\"]MSWNET:["SMS_SITE=ACC"]\\DP.xxxxx.xxx\</Param><Param>{B187E44B-4BF3-4748-B437-AFF29D679AA3}</Param></UserParameters></StateMessage></ReportBody>
PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 3/21/2014 8:48:55 PM 3564 (0x0DEC)
Start Download package ACC0006D version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
Start Download package ACC00070 version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
ExecuteJob (1-NotStarted) 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Cannot find FileInfo (\\?\E:\SMS_DP$\ACC00070\9A25E477-3C0C-499E-A0C1-65243BDBCBF0.tar), content download failed PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
CPullDPPkgContJob::ExecuteJob() failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
State at failure: NotStarted PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Content job 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Package job has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Bob

We ended up changing the DP back to a standard distribution point. That allowed the driver package to distribute successfully. so as a result I can't access the logs any longer.
I should note for anyone who goes searching for this that we had problems with every one of our driver packages. As I dug into it I found the contents, it looked like for some reason that it wasn't being transferred from the download location into
the final DP distribution location. It almost looked like SCCM was ignoring driver package types. I don't know if its a bug or just something quirky about this environment.
We were hoping to use Pull DP to handle our distributions more effectively, but we've backed off on that because of all the issues we've had with it. I hate say it, but it appears to be another SCCM 2012 feature that sounds like a good idea, but the
implementation leaves a lot to be desired.
Bob

Failed to Update Distribution Point

I have an interesting issue with distribution point updating a deployment package. I have ADRs that run for AV definition updates. The rules run, add to an existing deployment package and update distribution points. This works great for
about a month at a time. After that, I have to delete the package and recreate it. I can try to update DPs, use Powershell to update, remove all DPs and add them again as if it were a new distribution, but none of those work. Does anyone
else experience this or have seen it in the past? The error I'm getting is the 80070003 in Package Transfer Manager. Note, this happens every 4-5 weeks and I've experienced it now for the 3rd time. Thanks in advance.
Best, Jacob I'm a PC.

0x80070003 = "The system cannot find the path specified."
Make sure your deployment package where you download definitions is configured properly and accessible.
Is the source folder of the package on shared storage or saved locally on SCCM server?
What release of CM12 are you on?
I would also recommend looking at A/V exclusions for SCCM server:
http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx
http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012

Difference between "Distribute Content" and "Update Distribution Points"

Hi,
Can someone clarify this for me, I need to redistribute a package to all my distributions points. Should select distribute content and then select the DP's or should I just use the option "Update Distribution Points" to redistribute? TIA

Yes. Once content has been distributed you can not "Distribute Content" again to the same DP. However, you do have another option, go to the properties of the DP, "Content" tab, find the package in question and conduct a re-distribute.
This approach does not increase the versioning of the content whereas "Update Distribution Points" does.
P.S. If you have not read it yet, here is a great
article about content monitoring and validation.
-Tony

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

Update Distribution Points & Install pending

Hello All,
I created several Packages and tried to deploy them and they sit with install pending in the state field. I also tried updating a Operating System Image and that is also install pending. I have rebooted the server several times with no change.
The distmgr.log keeps freezing, when I restart the log will run for a while but show nothing useful. The sender.log shows no packages. I have tried a lot of the install pending suggestions but no help.
Any ideas? Thanks

Here is Part of what I am seeing:
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISWebSiteName in the SCF is "". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLState in the SCF is 0. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Virtual Directory SMS_DP_SMSPKGE$ for the physical path E:\SMSPKGE$ already exists.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.574 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~As this is an upgrade Virtual Directory SMS_DP_SMSPKGE$ will be updated with new properties.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.636 2014 Eastern Daylight Time><thread=9760 (0x2620)>
target processor architecture is x86~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.995 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Enabling Anonymous access for virtual directory SMS_DP_SMSPKGE$. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:15.869 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Successfully created the virtual directory SMS_DP_SMSPKGE$ for the physical path E:\SMSPKGE$.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:16.789 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Successfully added file extension C:\WINDOWS\system32\inetsrv\smsfileisapi.dll. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:17.772 2014 Eastern Daylight Time><thread=9760 (0x2620)>
for ["Display=\\dcs-nhamptn-01\"]MSWNET:["SMS_SITE=BOS"]\\dcs-nhamptn-01\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.064 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISWebSiteName in the SCF is "". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLState in the SCF is 0. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
CWmi::GetObject(): GetObject() failed. - 0x80070003~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.499 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Setting HTTPUrl to xxxxx/SMS_DP_SMSPKGE$/BOS0003B/ for package BOS0003B on DP
for ["Display=\\dcs-nhamptn-01\"]MSWNET:["SMS_SITE=BOS"]\\dcs-nhamptn-01\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.687 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.843 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.843 2014 Eastern Daylight Time><thread=9760 (0x2620)>

Report showing which updates are in which Distribution Point folders

SCCM 2007 SP2 R3. We're working on Software Updates distribution issues, and are trying to find a way to tell in which Distribution Point folder and subfolder names a certain patch is (or get a list of all patches under a certain distribution folder).
As an example, on the DP in the SMSPKGG$ folder , I have a folder named RD100492, in that I have a folder named fec8fc58-7ccd-48fe-a16f-ec5eddafef8f, and in that I have the patch named ie8-windowsxp-kb2964358-x86-custom-enu.exe. I'd like to be
able to run a report to find where that patch is in the folder structure and also to be able to list everything under a certain folder.
I've searched through the Views and Tables, but, can't seem to find the right columns.
Any ideas?
Thanks.

We keep having issues with some SU packages getting corrupt and either one or more patches hang, and dont' let the others install, or they seem to go missing (in once case we had a Patch List with 422 patches in it, and only 11 physically distributed and
created folders). MS Premier Support gave us a script to run that clears out the hung patches in WMI on affected computers for the former issue, but, for the latter issues, we have to run a manual comparison of folders find the ones with missing folders,
and recreate the Patch List. PITA trying to find things, why we are trying to create a report.
NOT just idle curiosity...<G>
I am presuming this info might only be in a Table, but, searching for column names hasn't found it, yet...
Thanks, Garth!

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

Troubleshoot Distribution Point Updates Failing

What are the best logs to look at for determining problems with
distribution points? We have 5 DPs. 2 of the DPs are failing to get
distributed content. Both of these systems are remote sites so it could
be due to network latency, but I need some logs to help narrow this
down.
I am watching the distmgr.log. I see the following entry showing its
retrying. The only other red messages are related to a DP that is
currently offline at the moment. Two of my DPs updated successfully.
The other two keep showing as Failed to distribute content.
Failed to process package BR100013 after 12 retries, will retry 88
more times SMS_DISTRIBUTION_MANAGER 5/14/2014 2:23:08 PM 2904
(0x0B58)

distmgr.log + pkgxfermgr.log
Torsten Meringer | http://www.mssccmfaq.de

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.

Remote Distribution Points for Software Update Point Site

Hi,
I have deployed Primary Site MP (SCCM 2012 R2) in the Main Office. In our environment, we have many remote offices with limited internet connection.
Is it best to setup Secondary Site in those remote offices or setup Distribution Points? What are the considerations?
Thanks.
~Andre

You only install one SUP. You can't install a SUP on DP's, and you don't need to install WSUS on DP's either, just IIS.
The clients will need to connect to the SUP (port 8530) to get the windows update catalogue. If they can't connect to your MP and SUP directly, then you will need to check your proxy configuration on the clients
Once the client has performed a scan, it will then match what it determines are "required updates" against what you have deployed in its client policy.
The client then connects to the local DP to download the updates and install them.
The client only downloads policy from an MP. If you have a DP on the same server as the MP then clients may try to download updates if you don't have your content boundaries configured correctly, and have also allowed them to use a fallback location.
To prevent clients going over the WAN to download the updates, check your update deployment under the "Download Settings" tab and choose "Do not install software updates" on both the options, and make sure you have your content location
boundaries configured correctly with the DP at each remote site assigned to the correct boundary.

Distribution Point creation failed. possible cause : distribution manager does not have the sufficient access right to the computer

Hi All,
I had this really disturbing experience with
SCCM 2012 SP1.
OD : 2008r2 Enterprise 64bit
Possible cause: Distribution Manager does not have sufficient rights to the computer.
Solution: Verify that the site server computer account is administrator of the computer.
in Distmgr.log says :
DPConnection::Disconnect: Revert to self
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.xxx\, logged-on as ssm\sccmadmin
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.x\, logged-on as ssm\sccmadmin
SMS_DISTRIBUxxx ON_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
Failed to find a valid drive on the distribution point ["Display=\\PNGBRANCHSERVER.xxx"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.myx
DPConnection::Disconnect: Revert to selfxxx
MS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
GetContentLibLocation() failed SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to get the content library path on server PNGBRANCHSERVER. SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to install DP files on the remote DP. Error code = 16389
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
STATMSG: ID=2370 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMSVR. SITE=SSM PID=2660 TID=16280 GMTDATE=Sun May 25 23:34:30.428 2014 ISTR0="["Display=\\PNGBRANCHSERVER.ssm.com.my\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.\"
ISTR1="PNGBRANCHSERVER.S" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\PNGBRANCHSERVER.\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.my\"
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
I have tried many of the solution provided unfortunately nothing positive happened.
Appreciate your input before engaging premier support.
Thank you

Hi，
NO_SMS_ON_DRIVE.SMS
This file is used to prevent Configuration Manager from installing binaries to a volume. By default, when you install System Center 2012 Configuration Manager on a remote Site System, the SMS Site Component Manager Service installs the binaries (files and
folders) for the Site System on the NTFS-formatted volume that contains the most free space. You may want to use an NTFS volume other than the default volume for your remote Site Systems by preventing ConfigMgr from enumerating certain NTFS volumes.
In order to prevent CM from enumerating an NTFS volume, on the remote server you can create a text file that is named NO_SMS_ON_DRIVE.SMS and put the this file on the root folder of all NTFS volumes where you do not want to install the binaries (SMS folder)
for the ConfigMgr components.
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.

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 :)

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

RBAC: grant rights to update distribution point

Similar Messages

Maybe you are looking for