Large Software Update Package size.

Not sure if this is normal or not, but I noticed that our Software Update Packages are HUGE. I've noticed a few things.
Office 2010 Updates are being downloaded for ALL Languages - even though I've only selected English.
I see multiple updates being duplicated. For example:
ie11-windows6.1-kb3021952-x64 - I have two of these files, that are same exact size
(50mb) but they are in two different folders.
One is in D:\Source - Updates\February Updates 2015\c2b0814b-b278-4826-b44d-5054771f93d8 the other is in
D:\Source - Updates\February Updates 2015\4178f1cf-204e-4969-aba8-79a537c9ba45
Is this normal? I typically have one SUG/deployment pkg for each month for both Server/Workstation and office packages, and this month my package is about 3.5 gigs..
Is this normal?? Thanks to anyone that can set me straight!

Hi,
In System Center 2012 Configuration Manager, we’ve added the capability to automatically remove software update content from distribution points when that content is related to expired updates. This process helps manage drive space on your distribution points
by removing any content you no longer need.
Also, please refer to the thread below:
https://social.technet.microsoft.com/Forums/en-US/1cdca30e-8b71-41ab-b2f5-7414623da922/ms-office-2013-sp1?forum=configmanagersecurity
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Similar Messages

Software Update Packages and binary differential replication

Do Software Update packages have any differential replication built in, or do the update packages just re-deploy the full package when updates are added or removed from it?

All ConfigMgr content replication always uses file differential replication so no to your question, only the changed files are sent. BDR wouldn't help unless and actual file is changed at the binary level which, to my knowledge, never happens with software
update files, and typically only happens (and is of value) with large files like OS images (aka WIMs).
Jason | http://blog.configmgrftw.com

Why distribute Software Update Packages to DP's?

I recently integrated WSUS with SCCM 2012 and deployed my first update package, I distributed it to our DP's at each of our facilities and then deployed the package. I am seeing results but it looks like all my clients are going directly to the Active
SUP for the updates instead of grabbing them from their DP's (which is causing my admins to flip over bandwidth usage). If the clients can only grab the updates from the SUP itself what is the point of distributing the software update package to them?
Is this things running as intended or should they be looking to their DP's for this? I have already investigated the option of setting up secondary sites and creating downstream SUP's but I am seeing conflicting forum posts mentioning that the DP's should
handle to update downloads so I don't want to commit to reorganizing our SCCM infrastructure when there is a simpler solution to this.

Yes the SUP was previously the Upstream server for our stand alone WSUS environment, when we integrated WSUS with SCCM we cleared the GPO directing PC's where to get updates from so that it would not interfere with the default client policies I have set.
Interesting point about the DP on the SUP, it does have a DP role assigned as it was the DP for our corporate office. I know the boundaries are configured correctly because my software packages are downloaded by the clients from their local DP's, I even double
checked this to make sure they were not assigned to this DP for some reason. We have the CAS set as the fallback point as well so I don't think that is why either. Our CAS has a DP role and could serve as this for our corporate office, would it be worth a
shot to clear the DP role from the SUP server and see if this reassigns the WUA managed server for the clients?
<![LOG[Enabling WUA Managed server policy to use server: http://NAME OF SUP.DOMAIN.LOCAL:8530]LOG]!><time="08:36:20.522+360" date="02-26-2014" component="WUAHandler" context="" type="1" thread="3924" file="sourcemanager.cpp:938">
That is an excerpt from the WUAHandler.log on one of the clients at a one of our facilities, would this be the correct place to see where it is downloading the update from? My network admin originally tipped me off to this when he was noticing high bandwidth
utilization from our facilities and traced the packets out to our SUP. I edited out the name of the SUP but I know this is the assigned SUP for my Primary site.

Disable Spotlight before installing a large software update?

Is it a good idea to "disable" both Time Machine and especially Spotlight before downloading any large software update? And then enable again after the install?
This question is based on what I have read on various threads. Would like to know both the "pros" and "cons".
Thanks

Not sure where you read that but it is false. There is no need to disable anything before doing any "Updates".
It is always a good idea to do a Time Machine backup before you do any major updates and Especially when doing UpGrades so you can Roll back to that TM backup if the "UPGRADE" fails or causes problems.

Source version of software update package is getting modified

Hi
In what condition does the source version of package get updated.
I have a software update package created, suddenly saw its source version got updated.
Regards Sushain KApoor

There are only two ways the version (of a software update package) is incremented: you manually trigger a package update or you add updates to the package (which in turn triggers a package update).
Jason | http://blog.configmgrftw.com

Recreate Software update packages

Hi,
I am working on a new environment where I would like to reorganize the software update packages. Currently, they are organized in 3 types:
- Workstation update packages (W7,8,8.1)
- Server update packages (2003,2008...)
- Application updates (Office...)
For each type there is one package per year (ex: Workstation update packages - 2014...)
Since (per year) I have one package for servers and another one for computers, I end up having the same update twice in 2 different packages (IE update in that case).
I don't think it's a big deal but I would like to "clean" it and regroup it under only one package per year ideally that would contain computer, server and office packages.
Is it possible to reorganize the packages or should I re-download all the updates ?
Also, since I have 3 ADR (Server, computer, Office), I was wondering if it could cause an issue if the three of them point to the same package and are launched around the same time after Patch Tuesday.
Thanks.

Hi,
>>Is it possible to reorganize the packages or should I re-download all the updates ?
If the updates need to be downloaded do not exist in the package, they will be redownloaded.
>>Also, since I have 3 ADR (Server, computer, Office), I was wondering if it could cause an issue if the three of them point to the same package and are launched around the same time after Patch Tuesday.
I think this is OK.
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Software updates package at install pending for a secondary site

Hello all,
For the last 2 weeks I have been fighting ore secondary server that will not download a software updates package. It continues to say "install pending" I keep seeing the same message in the Distmgr.log on the secondary server. I
have checked the despoil.log, sender.log and replmgr.log and do not see anything that sticks out as being a error. I have other packages that can be sent to this distribution point without any problems so I know the permissions are ok.
I have removed the packaged and added it back a few times and waiting day between removing it and adding it back.
This all started when the drive ran low on space and this was the package that ran the drive out of space. My best clue is in the distmgr.log file I see it says package JFG0001ED requires a newer version (5) and the current version is 4. The
problem is the distmgr.log file on the primary server is trying to push version 8 and that is the current version going to the other distribution points. It appears that the secondary server is trying to get an different version than the primary
server is serving up.
I have also removed the distribution point role from the secondary server and added it back. I'm pretty sure recreating the package will fix the issue but since it is an update package it is almost 5GB that I would have to resend
to 40 other DPs.
~Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\ZMJO6LPC.PKG. $$<SMS_DISTRIBUTION_MANAGER><Fri May 30 08:43:28.556 2014 Central Daylight Time><thread=2204 (0x89C)>
~Adding package JFG001ED to the active package array. $$<SMS_DISTRIBUTION_MANAGER><Fri May 30 08:43:28.587 2014 Central Daylight Time><thread=2204 (0x89C)>
~Package JFG001ED requires a newer version (5) of source files and the new compressed files haven't arrived yet, current version is 4, skip C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\ZMJO6LPC.PKG $$<SMS_DISTRIBUTION_MANAGER><Fri
May 30 08:43:28.587 2014 Central Daylight Time><thread=2204 (0x89C)>
~Removing package JFG001ED from the active package array. $$<SMS_DISTRIBUTION_MANAGER><Fri May 30 08:43:28.587 2014 Central Daylight Time><thread=2204 (0x89C)>

I would remove the package from that distribution point. Once that is done, and it's not waiting for a new version, you can try sending again. Assuming you now have the space for it.

Creating Software Update Packages - Best Practice?

I am setting up our SCCM 2012 R2 environment to begin using it for Windows Updates, however I'm not sure 100% the best method of setting it up.
Currently my plan is to break out the deployment packages by OS, but I read\told that I should avoid creating to many dynamic deployment packages, as every time it changes all the computers will re-scan that package. So What I want to do is create
various packages for OS and years, so I would have a package that contains all updates for Windows 7, older then January 31, 2013 (assuming the package doesn't have 1000+ updates), and are not superseded\Expired. Then I would create Packages for the 2014
monthly updates each month, then at the end 2014, combine them all in 1 package, and restart the process for 2015. Is this a sound plan or is there a better course of action?
If this the best practice method, is there any way to automatically create these packages? I tried the Automatic Deployment Rules, but I can not set a Year of release, only the a time frame of the release,(older then 9 Months), unless I am missing
something. The only way I can see doing this is going into All Software Updates, and filtering on my requirements, and then manually creating the package, but this would less desirable, as after each year I would like to remove the superseded and expired
without having to recreate the package.
Mark.

First, please learn what the different objects are -- not trying to be rude, just stating that if you don't do this, you will have fundamental issues. Packages are effectively meaningless when it comes to deploying updates. Packages are simply a way of grouping
the binary files so they can be distributed to DPs and in-turn made available to clients. The package an update is in is irrelevant. Also, you do not "deploy" update packages and packages are not scanned by clients. The terminology is very important because
there are implications that go along with it).
What you are actually talking about above are software update groups. These are separate and distinct objects from update packages. Software Update groups group updates (not the update binaries) into logical groups that can be in-turn deployed or used for
compliance reporting.
Thus, you have two different containers that you need to be concerned about, update packages and update groups. As mentioned, the update package an update is in is pretty meaningless as long as the update is in a package that is also available to the clients
that need it. Thus, the best way (IMO) to organize packages is by calendar period. Yearly or semi-annually usually works well. This is done more less to avoid putting all the updates into a single package that could get corrupted or will be difficult to deploy
to new DPs.
As for update groups, IMO, the best way is to create a new group every month for each class of products. This typically equates to one for servers, one for workstations, and one for Office every month. Then at the end of every year (or some other timeframe),
rolling these monthly updates into a larger update group. Keep in mind that a single update group can have no more than 1,000 updates in it though. (There is no explicit limit on packages at all except see my comments above about not wanting one huge package
for all updates.)
Initially populating packages (like 2009, 2010, 2011, etc) is a manual process as is populating the update groups. From then on, you can use an ADR (or really three: one for workstations, one for servers, and one for Office) that runs every month, scans
for updates released in the past month, and creates a new update group.
Depending upon your update process, you may have to go back and add additional deployments to each update group also, but that won't take too long. Also, always QC your update groups created by an ADR. You don't want IE11 slipping through if it will break
your main LOB application.
Jason | http://blog.configmgrftw.com

Software Update File Size Different than Apple Downloads File Size

Background:
I am running software update and it retrieves the update for "MacBook, MacBook Pro Software update 1.1" File size is listed as 768K. When I go to the Apple Downloads page for this update, the file size is 979K.
Download ID is 16618 and URl is http://www.apple.com/downloads/macosx/apple/macosx_updates/macbookmacbookprosoft wareupdate11.html
Question:
Is this discrepancy normal based on the way that Software Update calculates file size or should I be concerned? There is no hash to confirm integrity of the file.

File size, and the volume of space it takes up are 2 different things. Space will very from computer to computer. Chances are, the larger the drive the more space it takes up. Reason? The file system (HSF + on macs with Leopard). The file sytem divides the drive into specific number of sections. That number may be 10 M, say. So, even if you have a thumbnail that is 4 kb, it will still require the minimum size of the file system. Make sense? There is a lot of wasted space on very large drives.
Note: Leopard is set up to use a new file system that apple may soon adopt. It will not use the division method HFS + uses, and so will save a lot of space, if adopted.

Nokia C7 (059D0B0) software update package problem...

Hi,
I was helping my aunt to update her C7 (RM-675) model. I tried to help her by installing the PR1.2 update first through SW Update as it showed up there. I managed to download the file with size of almost 7000kb through Wi-Fi on the phone.
When the phone requested for a restart, the screen went white and a word "Updating" showed up. However, within ten seconds, there's a message showing "Restarting the phone" on the white screen.
Phone booted into the homescreen and a message popped out saying "Phone not updated. The software package is not compatible with your phone. Please check with your local service provider".
That didn't make me give up. I went to try again using USB connection to Nokia OVI Suite. The system checked there's an update of PR1.2 and I chose to update it. At first, the system requested for a phone backup and so I waited for it to finish backing up the phone. Later, I downloaded the PR1.2 software update with the file size of 175mb. When finished downloading, there's an error message showing up "Something went wrong". The system suggested me to restart the Nokia OVI Suite and then after several attempts, I couldn't detect the updates anymore. The result returned with "No updates available".
I went to try my luck on *#0000# and check for updates. I could detect v22.014 update was available for download with the file size of 25000kb+. Again, I finished downloaded it and phone requested for a restart and it took me to the white screen and the same word "Updating" appeared on the screen again. I thought this time finally I could update to Symbian Anna. Within ten seconds, the phone got rebooted and went to the homescreen again showing up with the same message of "Phone not updated. The software package is not compatible with your phone. Please check with your local service provider".
The phone product code was 059D0B0. She bought this phone in Malaysia from a local dealer.
I checked the product code variant and this variant is from Spain, I wondered? The latest update for this variant is only 014.002 which I checked on the Nokia official website and still I could detect Symbian Anna update on OTA on the phone. Can the person in charge please check what is wrong with the situation that I'm having? BTW, we're from Malaysia.
Thank you very much.
Bernard

I also had problems with the upgrade to Symbian Anna.
My carkit didn't work, telephone went off and on frequently, etc.
Nokia helpcenter told me that my carkit should be upgraded with
new firmware and that had to try to reinstall Symbian Anna.
I tried to reinstall Symbian Anna a few times but nothing worked.
Now I solved the problem!!!!!
- Make a backup of your files, pics, video's, etc.
- Put your phone back in the factory settings
- sofware update via Wifi or LAN
- Installs Symbian Anna 1/2 en 2/2
EVERYTHING WORKS FINE NOW!!!! also my carkit......
applause for Nokia helpcenter.............NOT!!!!
It will only take about 10 minutes to configure your telephone
and maybe some stuff from your backup.
Tip: put as much as you can on the extra memory card,
I think most you have it in your phone.

Software update package for SnowLeopard on April 1st?

Hi. Am new to this forum. This is my first post.
I got a message about software updates while connected in an aiport lounge on April 1st. I made the mistake of accepting without checking what was in the package. It turned out to be a rather big package, and though the WiFi connection was fast it took about 10 min to download. When shutting down to restart after download, the blue screen with the little spinning wheel just stayed on for 15-20 minutes - so finally I shut down the computer and restarted.
The problem is that this update does not display in System Settings where all previously installed updates are listed.
Any idea what this update was and why it doesn't show?
Should I roll my system back to before I got this update using Time Machine?
Thanks in advance for you help!

Welcome to Apple Discussions.
It sounds like you shut down too quickly, while it was installing. Fortunately the 10.6.3 update can be rerun and it should pick up where it left off. But under the circumstances I think you'd be better off with The standalone 10.6.3 Combo Update
Let us know. And yes, it is a large download.
-mj

Unknown errors during manual software update package installation

Hi,
I'm new to the forum.
Recently I've got a serious trouble while installing standalone update packages from disk image files.
After typing my username and password to update my OS manually my computer suddenly fails to install the software packages saying that "the installer has encountered an unknown error which caused the installation to fail."
I've an early 2009 Mac Mini which I bought during the first half of that year. The problem affects all versions of Mac OS X (10.5 and later). It's normal? I've tried everything (permissions repair, SMART check) to fix the problem with no luck. Now I suspect the issue has something else with bad memory or a faulty hard disk.
How curious, System Graph had put a new Super Drive on it because the original had its laser head damaged due to extensive use.
Cheers,
John

FIXED!
Many DMG executables failed to install because their certificates were outdated.
To resolve the problem: uncheck the automatic time setting box and set the clock to an early date.

Are Software Update Packages Stored On Computer?

I prefer to download updates to install manually at leisure. It also means that they don't need downloading again.
SU used to have a "Download Only" option but that disappeared a while back.
I know that one can go to the Apple Download page but frequently I am unable to find the download even though I type in its name.
I would have thought that when you use SU, the update has to be downloaded to the computer before it can be installed, so where is it stored . . . . . or is it just deleted?

From what I can tell from install.log, the downloads go to /Library/Updates/ but they are deleted after a successful install, leaving only an updated "ProductMetadata.plist" file in that folder.
If you can't find an update at http://support.apple.com/downloads/ by name, try the "Browse Downloads by Product" option to narrow the list of available ones down to your Mac model or software product. If you still can't find it, it may be available only through the Software Update app.
See Mac OS X: Software update sizes can vary for related info about "smaller-sized Delta" updates available only through the Software Update app.

Software Update Packages - the Package Source files are gone

I am running SCCM 2012 SP1. Something or someone deleted all my deployment package source files and folders for my software updates. Once I noticed they were gone, I was expecting there to be a simple way to have SCCM reload them from WSUS, since they should
still be there. However, I see no obvious way to do this in the GUI or from PowerShell. Is there a repair command for deployment packages that have lost their files?

Indeed, I just tested it in my environment and the real download won't start as long as it thinks that the updates are already downloaded.
The easiest way download them again is (if they are not all member of the same Software Update Group) temporarily add them to a SUP, delete them all from the deployment package and start the download again for all the updates in the (temporary) SUP.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Software update package not repilcating to 5 of my 12 branch distribution points

Hello all
As I do every mont for patch Tuesady I attempted to push my Decembers updates package to all 12 of our DP's but 5 of the DP's will not take the take the package. I removed the DPs then readded them still not good. The status show below is what
has stuck on for 3 days. The package status shows Install Pending
Any assistance would be greatly appreciated
Thanks, Phil
Phil Balderos

Also I just checked the Componenet status under Site Status and this is what I am seeing. There is actually a lot of disk space on this DP there is one partition with a 11.3 GB free and one with 29.8 free. Really scratching my head
Content download for the package "UPP00141" - "8" failed. The download failed because either there was not enough disk space to host the content or a disk was not found that satisfied the required properties.
Phil Balderos

Large Software Update Package size.

Similar Messages

Maybe you are looking for