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.

Similar Messages

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]

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

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.

HT201342 how can I tell if my contacts are being updated and stored in my cloud?

how can I tell if my contacts are being updated and stored in my cloud?

Log into icloud.com with a computer's browser and look at the contacts page. This lists the contacts currently stored on the icloud servers.

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]

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

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

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.

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

Where are Software Updates stored in OS X Server 10.9?

I am trying to find out where the software update folder is in OS X Server, Mavericks and if it is safe to delete unwanted software updates to reduce the size of the cache when it is turned on. This is for a school environemnt and any information or help in this regard would be greatly appreciated. [email protected]

IMHO, it's definitely not safe to delete random updates underneath Software Update Server. SUS has had a history of flakies, and while I haven't seen any untoward behavior on Mavericks (yet?), I'd prefer to avoid encouraging intransigence.
Scrounge a bigger or external disk for the system or as an add-on, use the server settings (select the server in the left navigation in Server.app, select Settings, select a different location for Service Data) and if you're stuck on a budget then load and run Reposado on some bigger-capacity Linux box.
As for your question, look around with this command:
ls -R /library/server/software\ update
But I wouldn't. Disk hardware upgrades are cheap, and the fallout from potentially derailing software is expensive.

To where are Software Updater file downloaded?

I have a software package to update on two computers. The computers are the same and I need to update software on both computers. However, where I live we pay for each megabyte downloaded so I would like to update the first computer then copy the update file to the other. Where does the Software updater store the downloaded files so I can get the file after the first computer is updated?

Whew, took me an hour of searching Apple Downloads to +not find it+ via dial-up!
Then via Google through 4 other sites with clues & back to Apple for 4 more 5 minute steps at pages with links loading leads me to this...
http://www.apple.com/finalcutexpress/index.html
The Resources link on that page leads e to...
http://www.apple.com/finalcutstudio/download/
Where it doesn't mention "Express", but who knows since I don't have a Serial# to sign in with!
Back to *Software Update*, if you choose to "Download only" or possibly "Install & keep Package", the file should be at Library>Packages, but I'm not certain that some of Apple's SWUPDs allow even keeping the PKG.
PS. Even this AD BBS is the absolute slowest loading BBS on the whole internet!

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

I would like to update my computer but when i go into the software updates it says your computer is updated. I would like at least the 10.6.8 update.

I have been trying to update my computer ( mac book Pro ) to at least the 10.6.8 Version but it says that i need a least a 10.6 first. When i go into the software update it says that my computer is updated. Its not help me.

Upgrade Paths to Snow Leopard, Lion, and/or Mountain Lion
You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
Upgrading to Snow Leopard
You must purchase Snow Leopard through the Apple Store: Mac OS X 10.6 Snow Leopard - Apple Store (U.S.). The price is $19.99 plus tax. You will be sent physical media by mail after placing your order.
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
     Snow Leopard General Requirements
       1. Mac computer with an Intel processor
       2. 1GB of memory
       3. 5GB of available disk space
       4. DVD drive for installation
       5. Some features require a compatible Internet service provider;
           fees may apply.
       6. Some features require Apple’s MobileMe service; fees and
           terms apply.
Upgrading to Lion
If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
You can purchase Lion by contacting Customer Service: Contacting Apple for support and service - this includes international calling numbers. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
     Lion System Requirements
       1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
           or Xeon processor
       2. 2GB of memory
       3. OS X v10.6.6 or later (v10.6.8 recommended)
       4. 7GB of available space
       5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
     OS X Mountain Lion - System Requirements
       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer)
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer)
         3. MacBook Pro (Mid/Late 2007 or newer)
         4. MacBook Air (Late 2008 or newer)
         5. Mac mini (Early 2009 or newer)
         6. Mac Pro (Early 2008 or newer)
         7. Xserve (Early 2009)
     Are my applications compatible?
         See App Compatibility Table - RoaringApps.
     Am I eligible for the free upgrade?
         See Apple - Free OS X Mountain Lion upgrade Program.
     For a complete How-To introduction from Apple see Upgrade to OS X Mountain Lion.

Software Update - Files Stored locally

Hi Peeps. I am now down to 20gb on my 100gb MacBook Pro HD. I need to find some more space! I have gone through and removed all the old iPhone and iPod firmware updates I no longer need and lots of the additional files from Applications I no longer use.
Here is my question - do the software updates (Downloaded via the automated Software Update App) get stored locally on my drive? If so where are they and is it safe to bin them? I really need to free up some space.
I know this is an Apple forum but are there another Apps that leave large lingering files behind following an update. (MS Office 08, Quark 7.31, CS3, Final Cut Xpress, iLife 08 etc)?
Look forward to your help

Nothing you download through Software Update should leave any installers on your Mac. If you download outside of Software Installer, it's up to you to eject and delete the .dmg file. If you have any, you would see them in the sidebar of Finder or in your Downloads folder.
Have you gone to /Library/Printers and deleted all but print driver(s) you use? That will free up some space. Since your data is not about to begin shrinking, I also strongly suggest you get another disk for backup
EDIT: What Size can help you find what's hogging your disk space.
-mj
Message was edited by: macjack

Are Software Update Packages Stored On Computer?

Similar Messages

Maybe you are looking for