The Office of the State Comptroller does not warrant, promise, assure or guarantee the accuracy of the translations provided. If you rely on information obtained from Google Translate™, you do so at your own risk. Google Translate™ cannot translate all types of documents, and it may not give you an exact translation all the time. However, the "Google Translate" option may help you to read it in other languages. The New York State Office of the State Comptroller's website is provided in English. If ($InvalidPkgLibPackages.This Google™ translation feature is provided for informational purposes only. Write-Host "All packages in PkgLib on $Env:COMPUTERNAME are valid" -ForegroundColor Green $x = ::Show("$message","Script Execution Paused",$Buttons)Ģ ) # function for pausing the script and prompting the user for confirmationĪdd-Type -AssemblyName # UPDATE THESE VARIABLES FOR YOUR ENVIRONMENT If you want to see how many orphaned packages you have in your production environment without deleting anything, just leave the threshold at 0 and respond 'No' each time you're prompted. If you want things to move along more quickly, you can increase that threshold and you will only be prompted for confirmation if the number of deletions exceeds your input value. Also, by default I have set the warning threshold to 0, which means it will always pause and ask for confirmation before any deletions. You'll need to edit the first 2 variables to match your SCCM environment. I then ran it against all my DPs, triggered one more round of content validation, and jackpot. ![]() Add a mechanism to optionally prompt the script user for confirmation before deleting records, thereby making this script a little safer to run in a production environment.Īfter a couple hours of scripting and testing, I managed to accomplish all 3.Detect package IDs that are present in WMI but missing from PkgLib and prompt the script user to manually redistribute that content to the DP, and.Automate comparing PkgLib to WMI and removing orphaned records from PkgLib,.I set out to build on Bart's script and expand it to automate the full maintenance operation. At that point, here's what I was seeing in smsdpmon.log: The package data in WMI is not consistent to PkgLibīart's script might be enough to repair your distribution point in certain cases, but in my case, I still had a lot of work to do. As it turned out, and as explained by CSE505 (I really wish I knew his/her name so I could give proper credit), I still needed to reconcile the PkgLib folder with WMI on each distribution point. The next morning, I came back expecting to see all green checkmarks, but nope. So, I triggered content validation on all my DPs and let it run through the night. So, I started by giving that a try, and it did exactly what it was designed to do and purged a bunch of orphaned records from WMI on all my DPs. Bart's script automates the process of comparing WMI on the distribution point to the master list on the primary site server. The comments on that technet forum led me to this script from Bart Serneels. Or, if a package ID exists on your DP, but no longer exists in the master list on your primary site server (probably because you deleted the application/package that created it), then you've got some orphaned package IDs on the DP that need to be cleaned up. If the two lists on the DP don't match, you'll get a warning status. Also, any packages listed on the distribution point need to also be listed in the master content package list on your primary site server. One is in WMI, and the other is the list of file objects in the PkgLib folder of the DP's content library. There are essentially 2 different content package lists on a distribution point (DP), and they need to match each other. I'll recap his/her findings here for your convenience. ![]() In particular, this post from user CSE505 in the Technet forums explains the nuts and bolts. But I recently set out to better understand why this was happening and fix it, if possible. Since I usually have 100 other things on my to-do list, I ignored these warning statuses for a long time. You might have even looked for a way to manually reset the warning flag and discovered that there's no obvious way to do that. Like this: Warning statusesĪnd when you comb through the detail records, you find a warning message like this: Detail warning messageĪnd if you're like me, you probably did some testing and discovered that your DPs were still working just fine. If you're a young SCCM administrator, you may have noticed that many of your distribution points have a warning status in the Distribution Point Configuration Status pane of the ConfigMgr console. At the time of this update, I'm running 2006 in my org, so I have not tested yet. Update : As of Current Branch 2010, the ContentLibrar圜leanup.exe tool now also removes orphaned WMI records on the Distribution Point. An improved maintenance script that builds on ideas from the community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |