Sccm 2007 Cleanup Pck Files
Hi, We've been running SMS/SCCM for a while now and have just completed an upgrade to SCCM R2. We've got 3 primary servers and a bunch of secondaries in our branch offices. Over time we've used and abused the system and now it needs a bit of a tidy up. We're a small shop (about 2500 clients) so don't have a primary SCCM resource.
I'm looking for any tools or tips for recovering disk space and redundant objects (collections/adverts/packages - the whole shebang). I've noticed that when we've removed a package from a DP it will remove the package, but not the PCK files. We're not going to need to redeploy (older versions etc) so how best to clean these up. I'm a lazy person by nature so I'd really rather not do this manually. I figure everyone else has this problem so someone must have invented a magic black box by now. Can I buy one? I've spent a few hours searching for the answer, but I'm either asking the wrong questions or looking in the wrong places. So in summary - I need to clean up my SCCM environment and put in place tasks to keep it clean, tidy and up to date.
System Center Configuration Manager. Is it possible cleanup data from a sccm. Installation files will be reset and downloaded again. Deleted file C: WINDOWS system32.
How best to do this? Any tips, hints or pointers would be helpful.
Microsoft Office 2007 Cleanup Utility
Packages - Delete them from the site they were created at, then the compressed copies (PCK) will go from the hierarchy. No need to manually go deleting these from every DP. I wonder if all you are asking is how to script the removal of the packages from the DP's?
And then remove the Package definition itself so the PCK gets deleted? Well if this is the case then the ConfigMgr SDK is your first stop: The Bing Google for script examples Although this is for SMS2003 a lot of the code examples are still applicable: (Chapter 4, with 4.4 being about the deletions) Keep in mind you should ALWAYS back stuff up before you get the busy with scripts that you are not familiar with, well really you should learn and grow stuff like this in a test lab. Anyway, ConfigMgr has a backup task, this is the only supported way to backup the product so use that method.
Did you ever get into disk Space Issues while copying,Decompressing PCK files in Configuration Manager 2007? Packages are failed due to not enough disk space? Couple of options to get out of it are 1 ) Add Extra Drives or Increase the Disk on the Drive if you are into VM 2) manage with the existing disk by doing some alteration to it like files or Delete them. OR Move to Configuration manager 2012 which no longer use PCK storage and uses Single Instance Storage,More about why should move from CM07 to CM12 and Single Instance Storage If you want to move the PCK files to different drive rather deleting them,Please refer this post, For Deletion,continue reading. As We all Know,The PCK files are stored on the drive letter that you specify in the hierarchy settings—software Distribution. If you found,the PCK drive do not have enough disk,try to change the Drive letter to different drive which has more disk space and creating NOSMSONDRIVE.SMS on the root of the drive to not use for decompressing of the packages,and moving forward,You will no longer have PCK file issues.
Open Pck File
But if you are having Many Packages that are not updated since years,probably it is good Idea delete the PCK for these packages. Note:If you later update these packages,Entire PCK files will get copied over the network to the site server,Please pay attention on it. I Wrote a Script that checks all the drives if smspkg share exists or not,If so check the PCK modifiedDate and then Delete if older than 2 Years.