Delete distribution point in specific package

I need to delete already assign distribution points for specific package. Basically need to remove distribution point and add different distribution point to selected package . since sms_distributionPoint status property read only I cant change it to 3 (delete)
. How can I do using C#.

I already tried this. But it want allow me to delete. that explain under  (http://msdn.microsoft.com/en-us/library/cc144580.aspx) "When your application deletes an instance of
SMS_DistributionPoint, the instance is not totally deleted until its related components are deleted. Instead, Configuration Manager sets the
Status property to 3 (delete) to inform the application that the distribution point is marked for deletion". I cant update it to status 3 since status property is read only.
I tried to do this several ways but didn't get true it. If you have any experience with this please send me the sample code.

Similar Messages

  • Failed to Validate Package on Distribution Point - Straight After Successful Distribution

    Hello,
    I have an updates deployment package which I have sent out to a distribution point and the status reports that the distribution was successful. If however I then do a validation of the same package, or wait for SCCM to do a validation, I get the status that
    it Failed to Validate Package on Distribution Point - the package is either missing or corrupted, please redeploy. If I then redeploy the package it once again goes fine and everything seems good but when another validation takes place I get the
    same error message again.
    The same package is fine on other distribution points and other packages are fine on the distribution point that has the issue.
    Are there are logs that will help me see why SCCM thinks the package is missing or corrupted?
    Thank you for any help.
    Kind Regards,
    Stephen

    Hello,
    Having done a bit more work on this issue I seemed to have managed to get it fixed. It turned out that the issue was due to an incorrect package ini file.
    On the distribution point there is an ini file in the SCCMContentLib/PkgLib directory that has the same name as the distribution package. That ini file is supposed to refernce all the packages that are part of the distribution package but in my
    case the ini file was no longer correct. Since the distribution package had been created and first sent out a number of the updates had expired and so should no longer be sent out to distribution points but for some reason the ini file still contained a reference
    to them so when a validation took place it was complaining that there were package files missing. Deleting the ini file and redistributing the package sorted the problem as the ini file was created once again and this time it only contains references to the
    packages that were actually sent to the distribution point.
    Many thanks for your help.

  • 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

  • Problems streaming specific App-V applications from specific distribution point. Cannot find any KB article on the error?

    Hi there,
    Some clients are having trouble streaming specific app-v packages from a specific distribution point.
    sftlog.txt shows the following on the client:
    [05/14/2014 10:39:25:442 AMGR WRN] {tid=E7C}
    Attempting Transport Connection
    URL:
    https://APPVSERVER:443/NOCERT_SMS_DP_SMSPKGE$/VirtualAppStreaming/AGR00215/{85738DDB-F118-48F3-9459-47354509E464}/AGR00215.sft
    Error: 2460410A-40002EFD
    [05/14/2014 10:39:25:458 JGSW ERR] {hap=34:app=APPNAME 2.0 2.0.0.0:tid=1334:usr=*****}
    The Application Virtualization Client could not connect to stream URL 'https://APPVSERVER:443/NOCERT_SMS_DP_SMSPKGE$/VirtualAppStreaming/AGR00215/{85738DDB-F118-48F3-9459-47354509E464}/AGR00215.sft' (rc 2460410A-40002EFD, original rc 2460410A-40002EFD).
    [05/14/2014 10:39:25:458 SWAP ERR] {hap=34:app=APPNAME 2.0 2.0.0.0:tid=1334:usr=****}
    The client was unable to connect to an Application Virtualization Server (rc 2460410A-40002EFD)
    I have recreated the DP based on the best practice for removing the DP and re-adding, as we've had other app issues which needed tidying up, but that has not fixed this issue.
    I have searched for the above error (The client was unable to connect to an Application Virtualization Server (rc 2460410A-40002EFD) but I get no results.
    Please help me with this, I've deleted the DP content and re distributed the content to the DP with no change.. If I remove the DP, the content is able to be streamed from other DP's no problem.
    Cheers
    Max
    Max Christopher

    It looks as though this may have been sorted out  - A re bind of the computer cert on the DP to the default website https binding seems to have resolved this for me.
    Max Christopher

  • 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

  • SCCM 2007 Failed to run task sequence, inaccessible distribution point package files

    I am trying to deploy an OSD task sequence using a boot disk. After I boot up, select the task sequence it runs a test of dependencies. It then errors out saying program files are inaccessible on the DP. The file is the OS wim file.
    Ive checked the log file and it is trying to connect to the share to download but it never can. In a command window i can map to the share fine. i also checked that the client network access account is set up and its also in AD. Not sure what else to check.
    I assume i do not need to do any thing to give client network access account access to the share right?

    Have you tried accessing the location listed in SMSTS.log from the client?
    Is there an error message?
    Can you post the relevant snippet of the SMSTS.log
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Yes, I can map the drive and copy files to it from the client (boot disk)
    Here's some of the log
    ![LOG[ Adding \\sccm.test.com\SMSPKGC$\BC100005\ to Matched Subnet DP list.]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="resolvesource.cpp:1918">
    <![LOG[Found 1 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="resolvesource.cpp:1974">
    <![LOG[Shuffling HTTP matched subnet DP list.]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="resolvesource.cpp:1990">
    <![LOG[Shuffling Matched Subnet DP list.]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="resolvesource.cpp:2062">
    <![LOG[Skipping remote content locations.]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="resolvesource.cpp:2132">
    <![LOG[Attempting to connect to \\sccm.test.com\SMSPKGC$\BC100005\]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="resolvesource.cpp:2151">
    <![LOG[Deleting any existing network connections to "\\sccm.test.com\*".]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:407">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:32.729+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:33.041+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:36.052+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:36.067+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:39.078+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:39.094+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:42.105+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:42.120+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:45.131+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:45.147+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:48.157+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:48.173+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:51.184+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:51.199+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:54.210+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:54.226+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:30:57.237+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:30:57.252+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\sccm.test.com\SMSPKGC$\BC100005".]LOG]!><time="10:31:00.263+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="10:31:00.279+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1532" file="tsconnection.cpp:508">
    <![LOG[dwErr, HRESULT=80070775 (e:\nts_sms_fre\sms\framework\tscore\tsconnection.cpp,517)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsconnection.cpp:517">
    <![LOG[Failed to connect to "\\sccm.test.com\SMSPKGC$\BC100005" (1909)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="3" thread="1532" file="tsconnection.cpp:517">
    <![LOG[!slistSMBPaths.empty(), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2163)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="resolvesource.cpp:2163">
    <![LOG[FALSE, HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tspolicy.cpp:1635">
    <![LOG[Content location request for BC100005:3 failed. (Code 0x80040103)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="3" thread="1532" file="tspolicy.cpp:1635">
    <![LOG[pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tspolicy.cpp:2330">
    <![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tspolicy.cpp:2862">
    <![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1208)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsmediawizardcontrol.cpp:1208">
    <![LOG[Failed to resolve selected task sequence dependencies. Code(0x80040103)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="3" thread="1532" file="tsmediawizardcontrol.cpp:1208">
    <![LOG[hrReturn, HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1532" file="tsmediaresolveprogresspage.cpp:408">
    <![LOG[ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040103)]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="3" thread="1532" file="tsmediaresolveprogresspage.cpp:408">
    <![LOG[ThreadToResolveAndExecuteTaskSequence returned code 0x80040103]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="1" thread="1368" file="tsmediaresolveprogresspage.cpp:221">
    <![LOG[Setting wizard error: This task sequence cannot be run because the program files for BC100005 are inaccessible on the distribution point. Please make sure that the packages are available, and the distribution points are accessible, and the appropriate network access account is configured if needed. For more information, please contact your system administrator or helpdesk operator.]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1368" file="tsmediawizardcontrol.cpp:1233">
    <![LOG[ResolveProgressPage::OnWizardNext()]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1368" file="tsmediaresolveprogresspage.cpp:113">
    <![LOG[Activating Finish Page.]LOG]!><time="10:31:03.289+300" date="12-02-2010" component="TSMBootstrap" context="" type="0" thread="1368" file="tsmediafinishpage.cpp:106">

  • How long until Deleted Content from Distribution Point frees disk space?

    Hopefully this is an easy question for you guys with more experience with the product.
    Yesterday, I created a new software distribution group for Office 2013 SP1, both 32 and 64bit.   I didn't really understand at the time that it was going to download nearly 8GB into my /sources folder...which is where I save my package contents.  I
    would have not expected this download to exceed approx 2GB.
    Since I indicated that it should also be distributed to my Distribution point, which is the same server, it also increased the disk usage in the /sccmcontentlib folder, as well as increasing the amount of space used in my SQLDatabase which is on the same
    drive.  It was never deployed to anything.
    Since I'm not yet ready to deploy this update to clients, but have a few others things to do instead, I wanted to delete the content from the distribution point to free up some disk space.
    I went into Software Library, Deployment Packages, went to properties of my Office2012_SP1 deployment, went to Content Locations, picked my single distribution point from the list, and chose Remove.
    However, no disk space was cleared on my drive.   I've still got 6GB free on my 120GB volume, so I'm not out of space.    
    Is this something where a scheduled job will come through and process this removal and free up the disk space?   Or is there a way to kick of the process manually?    

    It was never setup as an application. 
    It was a Windows Update, which was added to a software update group.  Then, I went to the software update group and right clicked and chose Download.  I created a new deployment package, and then distributed the content to one of my distribution
    point.
    By doing that, I understood that it would create the D:\sources\WindowsUpdates\Office2013_SP1 folder and put the deployment files there.  And I also see that because that content was set to a distribution point, it copied it there into the ContentLib.
    So, I wanted to remove the data from ContentLib, so I went to the Deployment Package, went to Content locations and removed my Distribution Point.   
    So, are you saying that in order to remove the ContentLib, that I have to remove the entire Deployment Package?   
    I thought by removing the Content Location it would remove it from the DP, and if I later wanted to add it back ,I could go back to the Deployment Package, go into Properties and add a DP back to the content location.

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

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

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

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

  • 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

  • OSD: howto force package to take sources from distribution point (not download it)?

    Hi,
    We have this package which installs correctly, but not in a task sequence. A network drive is mounted during install but we see the install fails due to the fact the package is downloaded (and share is made to c:\).
    You can enforce this behaviour in a deployment (to a collection) but howto do this in a task sequence?
    Please advise.
    Please advise.
    J.
    Jan Hoedt

    What a waste of time. So I should change every single package, application, script, bootimage of task sequence then also make a specific package for sccm 2012 client configmr just for the purpose a package installs from a distribution share instead of copying
    the files locally?!
    You're kidding right?
    Jan Hoedt

  • Can we deploy a software from specific Distribution Point

    we have 12 DPs and a Primary Site SCCM 2012. can we deploy a software or Updates from
    specific Distribution Point?
    Thanks

    DP use by clients is all about your boundaries. Simply adjust your boundary groups so that the good "DP" is referenced in the boundary group defining the boundaries for the alternate location.
    Jason | http://blog.configmgrftw.com

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

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

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

  • Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

    Hi,
    Some of our DP's have a warning (Shown with a yellow exclamation mark) that never goes away. I have run a script on the DP's that could check for inconsistency in WMI, but it found nothing. Everything seems to work fine, but it is annoying that everything
    is not green when it should be!
    The warning is:
    Failed to retrieve package list on the distribution point. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.

    Hi Peter,
    Yes I have tried to validate all content to no avail. ;(
    No help to find in smsdpmon.log, I really think it is a bug...
    Here is a small part of it:
    ]LOG]!><time="03:50:29.934-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:29.943-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package 'C010003E' version 0 ...]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:586">
    <![LOG[Report status message 0x4000094C to MP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.996-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package share for package 'C010003E' version 0 ...]LOG]!><time="03:50:32.510-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:629">
    <![LOG[Package C010003E is verified successfully]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:649">
    <![LOG[Report state message 0x40000950 to MP]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:889">
    <![LOG[Report Body: <ReportBody><StateMessage MessageTime="20141129025032.000000+000" SerialNumber="0"><Topic ID="C010003E" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>C010003E</Param><Param>["Display=\\dk01dc1sscm01.local.avk.dk\"]MSWNET:["SMS_SITE=C01"]\\dk01dc1sscm01.local.avk.dk\</Param></UserParameters></StateMessage></ReportBody>
    ]LOG]!><time="03:50:32.520-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:32.528-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000959 to MP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000952 to MP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[DP monitoring finishes evaluation.]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:500">

  • Package content on Primary Site Server (no Distribution Point Role)

    Hey,
    I have the situation that there are 3 Servers with following roles installed:
     1.File Server
     2.SCCM 2012 R2 CU3 Primary Site Server / Database Server (Was a distribution Point previously to update to CU3)
     3.Distribution Point
    Our packages are all stored as "source" on the File Server.
    Now some SCCM Applications / packages are created and distributed to the distribution point.
    Unfortunately on the Primary Site Server the folder "SCCMContendLib" extends as it does on the distribution point (so this means that all packages are distributed to the primary site server, too.
    My question is now- why? :)
    Is this really needed (I see no reason for it) or is it a problem in the infrastructure (if yes - how can I resolve it)?
    Thank you for help
    Kind Regards

    Not a problem with your infrastructure. What you're describing it the default behavior for ConfigMgr, in terms of storing content on the primary.
    -Nick O.

Maybe you are looking for

  • Compaq F764CA & Windows 7 Upgrade = bad battery performanc​e

    Hi I was wondering if anyone else has come across this problem.  I upgraded my wife's laptop to Windows 7 Ultimate and while there were some drivers from Vista required to work things out, I have noticed that her laptop battery performance has gone f

  • Windows XP/Vista on a Macbook

    Hi... I am very new to Mac. I have always used a PC. Finding OSX hard to get use to. Im just wondering if there is an XP/Vista version for Mac's? I cant seem to find it anywhere to buy. Also it is easy to use? Just install as you would anything? Than

  • Response time too slow when there is competition in the same connector PCo

    Dear all, I'm having a problem with using PCo 2.1. I created all the conections in PCo with OSIsoft PI and when I create a TagQuery on MII to get the values of a tag is not occur problem in response time. But when I have another TagQuery or Transacti

  • HELP ME- ipod mini wont play songs!

    i have rescently moved houses and had to load my ipod mini on to a new computer and new i tunes list. I re loaded all my music on to the new list and transfered my ipod to factory settings to wipe all my old music. But when i went transfer all of my

  • Twisting a Layer, Vector Layer and/or Text Layer?

    Hello everyone, I'm stuck and could use a hand. Here at work, I have the entire CS5 Master Suite at my disposal. Although I'm familiar with the Adobe Suite, I'm having a hard time figuring out the best/most efficient way to do this effect: Now, my bo