Adobe Updates via SCUP

I am attempting to push out updates for Adobe products using SCUP but am running into a strange issue when clients attempt to install them.
The clients all see that flash player 11.9.900.170 is available and a required update based on the version currently installed, however when they attempt to install the update, UpdatesDeployment.log reports error 0x80240017 indicating the update is not applicable.
I thought maybe it was due to the version the clients were currently on (11.7.x.x) so I manually updated a couple to another version (11.9.900.117 then 11.9.900.152 when that failed) to see if that would make a difference, but every time it was the same
result.
Has anyone experienced this/found a solution?

I have seen issues with the rules multiple times. Open the Flash Player package in SCUP and verify that the detection rules are correct.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

Similar Messages

Flash Update via SCUP Problem

Hello,
I am deploying Updates via SCUP and SCCM to hundreds of Computers.
Fortunately Adobe provides an SCCM Update Catalog for both Adobe Flash ActiveX and Adobe Flash Plugin.
But now my Problem:
After publishing the Update via SCCM, the client is not supposed to be interfered with the Update Progress (which is working)
I figured the Updater works like this:
First SCCM checks if a Update needs to be deployed, if this is the case, The Flash Updater begins.
First the old Flash Version is beeing uninstalled.
But now: if the Client has a Browser Window (IE, or Firefox) open, the Updater is not able to install the new Flash Version and quits with an Error.
This leaves the Client PC without any Flash (because its being uninstalled before)
How can I prevent Flash being uninstalled due to the Update progress not working while a Browser window is open?
Thank you very much!
Sincerely Martin

You might get better results asking in the Flash Player forum rather than here in the Flash Pro forum. Here's a link:
http://forums.adobe.com/community/flashplayer
If you are hoping for an answer from an Adobe employee, you should be aware that these are primarily user-to-user forums.

Install Adobe updates via WSUS and ignore UAC restrictions

Hi
My company has currently set new UAC security settings but we have an issue where we are not able to update Adobe products because UAC stops it, UAC also does not prompt for elevation it just out right blocks updates.
We really need a way to either allow the updater to run/install past the UAC restrictions OR find a way to distribute adobe updates via WSUS if it's possible
Thanks

I am not sure what you mean, I am able to install all updates from Microsoft through WSUS. I read something about being able to install an Adobe add-on or something like this to enable WSUS to download updates for Adobe and distribute them this way. This would save on network traffic and downloads, considering there are so many Adobe updates, it would be nicer to download them once and distribute. Otherwise how do big networks send out Adobe updates if they update it at all?
I am not sure where the updateshandler.log is stored as searching the entire drive did not display anything. Something that might help is that some PCs use Adobe acrobat 8 and some use acrobat 10.

Adobe Reader 11 Update via SCUP

Hi all,
i'm updating Adobe Reaer via SCCM and SCUP and the published catalogs from Adobe.
When importing the updates i do not see the MUI Update for Version 11.0.5, but the not MUI Version is available.
is this update published later what do i wrong?
Thanks a lot

I'm a bit sorry, I've used the non MUI version for deployment, it was the German 11.0.04 Package.
11.0.05 Deployment via SCUP was done without any problems.
I tried "msiexec /update AdbeRdrUpd11006.msp" with Logging Option and this is the output (It's a bit in german I hope its not a problem):
=== Verbose logging started: 24.01.2014 09:53:11 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (CC:14) [09:53:11:008]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (CC:14) [09:53:11:008]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (CC:5C) [09:53:11:018]: Resetting cached policy values
MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'Debug' is 0
MSI (c) (CC:5C) [09:53:11:018]: ******* RunEngine:
           ******* Product: {AC76BA86-7AD7-1031-7B44-AB0000000001}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (CC:5C) [09:53:11:047]: Cloaking enabled.
MSI (c) (CC:5C) [09:53:11:047]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (CC:5C) [09:53:11:050]: End dialog not enabled
MSI (c) (CC:5C) [09:53:11:051]: Original package ==> C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:11:051]: Package we're running from ==> C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall Flags override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall VersionNT override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1031-7B44-AB0000000001}'.
MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (CC:5C) [09:53:11:060]: MSCOREE not loaded loading copy from system32
MSI (c) (CC:5C) [09:53:11:062]: Opening existing patch 'C:\WINDOWS\Installer\1e65cb.msp'.
MSI (c) (CC:5C) [09:53:11:063]: Original patch ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
MSI (c) (CC:5C) [09:53:11:063]: Patch we're running from ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp' against software restriction policy
MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp has a digital signature
MSI (c) (CC:5C) [09:53:15:798]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (CC:5C) [09:53:15:798]: SequencePatches starts. Product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, Product version: 11.0.04, Upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}, Product language 1031
MSI (c) (CC:5C) [09:53:15:798]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} is applicable.
MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
MSI (c) (CC:5C) [09:53:15:800]: PATCH SEQUENCER: minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is not applicable.
MSI (c) (CC:5C) [09:53:15:801]: SequencePatches returns success.
MSI (c) (CC:5C) [09:53:15:801]: Final Patch Application Order:
MSI (c) (CC:5C) [09:53:15:801]: {AC76BA86-7AD7-0000-2550-7A8C40011005} -
MSI (c) (CC:5C) [09:53:15:801]: Other Patches:
MSI (c) (CC:5C) [09:53:15:801]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40011006} - C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
Das Upgrade kann nicht vom Windows-Installationsdienst installiert werden, da das zu aktualisierende Programm nicht vorhanden ist oder eine andere Version des Programms mit dem Upgrade aktualisiert wird. Überprüfen Sie, ob das zu aktualisierende Programm vorhanden ist und das richtige Upgrade verwendet wird.
C:\WINDOWS\Installer\1ba82.msi
MSI (c) (CC:5C) [09:53:15:802]: Produkt: Adobe Reader XI (11.0.04) - Deutsch - Update "{AC76BA86-7AD7-0000-2550-7A8C40011006}" konnte nicht installiert werden. Fehlercode 1642. Weitere Informationen sind in der Protokolldatei C:\temp\msi2.log enthalten.
MSI (c) (CC:5C) [09:53:15:803]: Ein Update wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Updatename: {AC76BA86-7AD7-0000-2550-7A8C40011006}. Erfolg- bzw. Fehlerstatus der Installation: 1642.
MSI (c) (CC:5C) [09:53:15:803]: Note: 1: 1708
MSI (c) (CC:5C) [09:53:15:803]: Produkt: Adobe Reader XI (11.0.04) - Deutsch -- Installation fehlgeschlagen.
MSI (c) (CC:5C) [09:53:15:804]: Das Produkt wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Erfolg- bzw. Fehlerstatus der Installation: 1642.
MSI (c) (CC:5C) [09:53:15:806]: MainEngineThread is returning 1642
=== Verbose logging stopped: 24.01.2014 09:53:15 ===
Do you have any hints what could be the problem?

CU4 Client Update via SCUP

Anyone else seen issues with this update getting stuck on "Installing"? Followed usual procedure, deployed to around 5,000 client but seeing the number of clients reporting in as CU4 growing very slowly and reports of it being stuck in
Software Centre...

I've recently used this to update my lab environment:
http://www.petervanderwoude.nl/post/publish-cumulative-updates-of-configmgr-via-system-center-updates-publisher/
I've not encountered any problems with that. Have you verified the client log files for any issues?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Updating Flash Player ActiveX / Plugin via SCUP / SCCM

Hello,
I am deploying Updates via SCUP and SCCM to hundreds of Computers, mostly with Windows 7 x64.
Fortunately Adobe provides an SCCM Update Catalog for both Adobe Flash ActiveX and Adobe Flash Plugin.
But now my Problem:
After publishing the Update via SCCM, the client is not supposed to be interfered with the Update Progress (which is working)
I figured the Updater works like this:
First SCCM checks if a Update needs to be deployed, if this is the case, The Flash Updater begins.
First the old Flash Version is beeing uninstalled.
But now: if the Client has a Browser Window (IE, or Firefox) open, the Updater is not able to install the new Flash Version and quits with an Error.
This leaves the Client PC without any Flash (because its being uninstalled before)
How can I prevent Flash being uninstalled due to the Update progress not working while a Browser window is open?
Thank you very much!
Sincerely Martin

Exactly the same issue here (see http://forums.adobe.com/message/6285043#6285043). We have stopped the deployment of that package since nearly every second client is affected by this. It seems that the installation package does uninstall the flash player ocx (both 32-bit and 64-bit), but does not install the new version.
I remember there was a bug at the beginning of this year, where the install package did install the new version, but marked it as "failed" in SCCM software center.. Just a few days later there was a new package in SCUP with the same version number...

Adobe Flash player SCUP catalog cound found update from India

Hi ,
We have 2 sites with SCCM 2007 R3 and SCUP 2011 for each site.
We have Windows 7 x64 SP1 on all client systems
First site is in INDIA .
Second Site is in European country
1. Now when we import flash update from SCUP from India server then it Could not found the Latest flash update
2. But at the same time when we import flash update from SCUP from European country it could found flash update .
We are using url for both sites : http://fpdownload.adobe.com/get/flashplayer/current/licensing/win/AdobeFlashPlayerCatalog_ SCUP.cab
Any idea why Adobe is not publishing updates to INDIA server.
Thanks

Download Flash Player only from the Adobe.com website, not any dubious 3rd-party download site.
Here are the installers for Windows: http://helpx.adobe.com/flash-player/kb/installation-problems-flash-player-windows.html#mai n-pars_header

We are having problems pushing push adobe reader install and updates via Microsoft deployment

We are having problems pushing push adobe reader install and updates via Microsoft deployment. We issue is with our mail server. We cant open PDF within outlook.
Cliff Butler
Coastal Connection
www.coastal-connection.com

Hi ccbutler,
What is the current version of Acrobat/Reader installed and what is the version of Outlook installed.
Was it working before if yes do you have idea when did problem started.
~Ajlan Huda.

How do I install the FM10 licensing fix when Adobe Update Installer won't run?

Adobe Update Installer won't run so can't install FM10 licensing fix
This question is Not Answered.(Mark as assumed answered)
Aug 9, 2013 12:09 PM
Tags (edit): none (add)
Because FM10 began crashing with "fatal" errors whenever I tried to generate a TOC for a small (65 page) book, I researched workarounds and none of them worked. Now that I have delivered a crippled deliverable via Acrobat manipulations, I would like to fix FM. I uninstalled it and reinstalled it, got some updates, and then received the "licensing fix" error that popped up in January. I'm wondering why this fix was included not in the updates. That said, the licensing fix package, first, would not unzip so I downloaded it again. I unzipped it but I got a message that Adobe Updater Installer could not run and after several clicks I found that file. I reinstalled Adoble Update Installer but it still does not run.
I am running Windows XP and have TCS 3.5.I uninstalled FM and RH but not Acrobat, Captivate, or Photoshop.
So, now what? Listen to my supervisor who says never use FM again?
P.S. Why do I have to enter a title for my question and then do it again when this page opens??

Give Adobe Support a call or contact the TCS team at [email protected] - something in your environment is causing the installer to fail (I'd guess).

HOW TO: Your very own Adobe Update Server (Windows)

Well, I thought I'd contribute something after wasting time sifting through info on how to get this done. It's not a hard process at all, once the steps get organized correctly.
If you are reading this post, you most likely have already seen:
http://helpx.adobe.com/creative-cloud/packager/update-server-setup-tool.html
Maybe you’ve seen the dry (read: hard to stay awake and boring) video Adobe has posted as well and yet here we are… I found the materials Adobe provided informative yet riddled with inconsistencies and scatter brained writing. This guide will get you to a working install with minimal pain and effort. I’m sure plenty of you have Mac’s that you’d like to get running as an update server. Good luck, we’re a pc shop and that’s what this guide is going to be on. You can still update Mac’s with a windows based server. Mac users that want to setup an update server on a Mac will have to try and endure that video.
I like complaining about things, so if you want the relevant info, I bolded it. If you need to change the command to fit your system, I highlighted the relevant section in red. You’re welcome.
Requirements:
Windows Operating System 64-bit (just so the file structure makes sense, if you are running 32-bit, that’s fine, but you’ll need to make the necessary changes to my write-up.)
The requirements for CPU, Memory, and hard-drive free space are minimal (My freshly sync’d update directory is only 30.2GB). I’m going to lean on the safe side and say leave a few hundred gigs free on the hard-drive. All you are doing is making a file store that can be accessed via http from your clients. Any modern day computer can be your host. Have hundreds of client computer that will be downloading from your update server? That’s up to you on how you will want to handle it. Do DNS load balancing across multiple update servers, deploy different override files to different groups of clients that point those groups of clients to different servers, or use sas drives and team multiple gigabit Ethernet ports. I’m sure you’ll figure something out to handle your particular situation. I am just going to focus on a simple step-by-step to get you on your way.
Step 1: Install Creative Cloud Packager
This was the first thing that wasn’t clear to me. I’m new to Creative Cloud for Teams. I have 20 computers and knew that updating would be an issue with our internet connection. I intuitively searched for a way to set up an update server and came across the article linked earlier. “Note: AUSST is available in the utilities folder of Adobe® Creative Cloud™ Packager installation.“ Oh, that’s nice. No link. No help on where to get it…
You can grab the download from your “Manage Your Team” control panel. It’s on the right side under “IT Deployment”. Download it, install it. This how-to isn’t about packages and how awesome they are for deployment or how to use them. So close the packager when you are done installing and move on to step 2.
Step 2: Create a root directory to store all of your updates.
I think it’s safe to assume that the root directory will only grow in size over time, so put it somewhere with a few hundred gigs of free space. The cloud is still young but I expect that amount to last you a while. To keep this easy, I created my directory as such: G:/CreativeCloudUpdate
Step 3: Run the AdobeUpdateServerSetupTool for the initial sync
Open up command prompt as an administrator and type the following:
cd "c:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\CCP\utilities\AUSST"
AdobeUpdateServerSetupTool --root="G:/CreativeCloudUpdate" --fresh
When it is done updating, leave the command prompt up, you’ll need it again.
Step 4: Create the client config file
For whatever reason, the AdobeUpdateServerSetupTool can’t create a config folder. So you’ll have to make it yourself if you want this to work.
Go to G:/CreativeCloudUpdate and create a folder called config
Head back over to the command prompt and type the following:
AdobeUpdateServerSetupTool --genclientconf="G:/CreativeCloudUpdate/config/AdobeUpdaterClient" --root="G:/CreativeCloudUpdate/" --url=http://192.168.1.4/
If this worked, you should get something like the following:
“Generate Client Configuration XML chosen.
Files generated at specified path.”
Double check to make sure the files are generated inside the G:/CreativeCloudUpdate/config directory.
Step 5: Setup the Web Server
We’ll use Apache 2.2 for this setup. Yes, I am aware 2.4 is out, and 64-bit is available and that there are different web servers and and and. If you want to set something else up, go for it, be my guest, but you won’t find compile or update directions here. Also, if you want to use IIS, again, go for it. I didn’t find anything wrong with the directions in the very first link in this post. Remember, this guide is simplicity focused. I expect you to know how to keep your own network up to date.
ALLOW PORT 80 THROUGH WINDOWS FIREWALL OR ANY OTHER FIREWALL SOFTWARE YOU ARE RUNNING ON THE SERVER!
Download and install the following:
http://mirror.metrocast.net/apache//httpd/binaries/win32/httpd-2.2.25-win32-x86-no_ssl.msi
You can keep all of the defaults during install.
Once installed, you’ll have a little feather and play button in your system tray. Double click on that to bring up the server monitor. STOP the process.
Navigate to C:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf
Open up httpd in a text editor like notepad, you’ve got a little editing to do. Do a search and replace. You’ll want to find EVERY OCCURANCE of the following sentence:
C:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs
And replace it with the following sentence:
G:/CreativeCloudUpdate
Save the file. Go back to the Apache server monitor and start the process.
Step 6: Setup the Clients
The file is located here: G:\CreativeCloudUpdate\config\AdobeUpdaterClient\win
And here: http://192.168.1.4/config/AdobeUpdaterClient/win
It is called: AdobeUpdater.OVERRIDES
And it needs to end up here on the client computers:
In Windows XP:
\Documents and Settings\All Users\ApplicationData\Adobe\AAMUpdater\1.0\AdobeUpdater.Overrides
In Windows 7/Vista:
\ProgramData\Adobe\AAMUpdater\1.0\AdobeUpdater.Overrides
In Mac OS X:
/Library/Application Support/Adobe/AAMUpdater/1.0/AdobeUpdater.Overrides
It is your choice concerning how to get the overrides file onto the client computer. THE BEST WAY is to include it in the package you deploy from the Creative Cloud Packager(not covered in this guide). If you already have Creative Cloud installed and want to start updating via the server you just setup: You could use group policy to deploy the file. If you only have a handful of computers, you could put it on by hand. You could script it. You could email it to all your users and tell them to place the file. Pick whatever you feel will work best for you in your environment.
IF you are just deploying the Creative Cloud in your environment and were smart enough to think ahead and setup the update server FIRST. Look up (If you have to, it’s really intuitive) how to use the package manager and make sure to change the package configuration to use this overrides file.
Step 7: Check for and download updated files to your update server
To manually do this, open up command prompt as an administrator and type the following:
cd "c:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\CCP\utilities\AUSST"
AdobeUpdateServerSetupTool --root="G:/CreativeCloudUpdate" --incremental
To do this automatically you need to make a scheduled task to run the command above. The only issue I have run into is the task does not seem to run unless you are logged into the server. If no-one is logged in, the task triggers, but an update never happens.
All in all, I am happy that there was a way to do this. I AM NOT HAPPY that Adobe made it an after thought. A system service would have been a very elegant solution or you know, a simple custom server app that does everything in this guide for you AND makes it easy to run the incremental updater on a schedule. But noooooo, they couldn’t be bothered to do that, I mean really, who wants their own update server anyways…

Hi,
in relation to on to the above could you please share some thoughts on using AUSST in an enterprise environment spread over 50 countries i relation how to setup the AUSST, taking WAN Lines into considerations. We are using SCCM for application deployment and patching. Is there a comparising model for AUSST vs. SCCM?
i Get the picture using AUSST in a company with one huge Building using the LAN capacity, but what technologies are used to replicate over WAN etc?
br
Twinkle6862

Unable to install the latest version of Adobe Muse via Adobe Application Manager

I´m a user of Creative Suite applications and all of them have been updated successfully with the exception of the latest version of Adobe Muse.
I´m unable to install it. I get error DW 050
I´m using Windows 7 64 bit.
All previous versions of Adobe Muse have been installed OK.
Following a forum discussion I could read, I uninstalled the previous version, but the installation fails again.
Does any body know how to solve this issue?

Dear Sachin:
Thank you for your help, however I have to get back to you to inform that after downloading the new package based on the link that you´ve provided, I´m still unable to execute the application. I get the message: “block by the administrator” and also another message: “the editor of this program is unknown and unsafe”. Please note that all other programs from Adobe´s Creative Cloud have been downloaded and installed with success. All Adobe Creative programs have been installed on my computer several months ago and all are working fine so far. This morning I installed an update for Photoshop without any problem. It seems that the problem persists only with Muse. I have to highlight that I´m the administrator of my PC and therefore all applications are currently being executed as administrator. I have never had the intention to block any program, including obviously Adobe´s Creative Suite programs.
Could you please let me know how to splve this problem?
Michael.
De: Sachin Hasija [email protected]
Enviado el: lunes, 28 de enero de 2013 18:57
Para: retonxxy
Asunto: Unable to install the latest version of Adobe Muse via Adobe Application Manager
Re: Unable to install the latest version of Adobe Muse via Adobe Application Manager
created by Sachin Hasija <http://forums.adobe.com/people/Sachin+Hasija> in Help with using Adobe Muse - View the full discussion <http://forums.adobe.com/message/5028441#5028441

CU2 Update with SCUP

Hi All
We have an environment of a CAS and a Primary site and approximately 15.000 Windows 7 computers
We implemented 3 months ago SCUP for the updates of Adobe everything works perfectly.
We have upgraded our servers to SCCM 2012 R2 CU2.
We now want our clients to be upgraded from SCCM 2012 R2 to SCCM 2012 R2 CU2.
I've imported the CU updates (cab file) into scup afterwards published these 4 updates in SCUP .
These 4 updates are now visible in SCCM underneath all software updates.
I want to deploy these CU2 updates with the monthly patches of November , can I handle these updates as a normal software update and deploy these updates at the same time as the other software updates for the month November.
Second question will the load of my primary server be a problem with the upgrade of the clients to CU2?
I hope someone can help me with these questions?
Regards
Johan

Just go ahead an deploy it, but I won't upgrade the client at the same time as regular patches (just a feeling, no technical reason).
The load would be the same as on other patchdays.
(Why have you deployed a CAS and a single primary site only?)
Torsten Meringer | http://www.mssccmfaq.de

Adobe updater error: Photoshop CS6 update to 13.0.5

Trying to install Photoshop update to 13.0.5 with Adobe updater/Adobe Application Manager. It's downloading completely, then trying to install. Constant error message: U44M1P7.
How can I proceed? Can not find helpful advice, when clicking on "weitere informationen" (more).
Switzerland, German version
Mac OS X 10.7.5
When clicking on "more information", it says "Error log file location: /Library/Logs/Adobe/Installers"
never had any problems before. Have not changed anything in the library. Each and every update before this one allways worked perfectly.
any hints?
thank you

Sorry, but this does not help
installing via "help>updates" says, photoshop would be up do date. no update.
and I can not find any file link to download a update file manualy.
How to get the Update
In Photoshop, choose Help > Updates…"
does not work

InDesign refuses to update via Creative Cloud - each attempt fails within 30 seconds - no problem with other items - any suggestions?

InDesign refuses to update via Creative Cloud - each attempt fails within 30 seconds - no problem with other items - any suggestions?

What is the error message you receive?
There is a manual way to do updates - All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/

Will camera raw 8.7.1 update via plugin be available to Photoshop Elements 12 or at least Photoshop Elements 13?

Hello
Will the recent camera raw 8.7.1 update via plugin be available to Photoshop Elements 12 or at least Photoshop Elements 13? (Mac)
I understand it likely won't for PSE 12, however what about PSE 13? The official "Adobe Website" info for PSE 13 only refers to Camera Raw module V.8.6. Can someone advise please?
Would customer support email a link to the plugin module for Camera Raw 8.7.1 for a manual download/installation? The official 8.7.1 DNG/CR Download packages available via Adobe.com are only complete packages and won't update the embedded PSE plug-in mentioned above.
Many thanks for your support
Jonny

As far as photoshop elements is concerned, the added camera support for the sony A7II in camera raw 8.7.1 is probably the only thing on this page that affects pse.
(the camera raw version in photoshop elements doesn't have any user setting for camera lens profiles or applying chromatic aberration)
Camera Raw 8.7.1 is now available
Photoshop elements should have camera raw 8.7 available using Help>Updates from within the photoshop elements 13 editor.
(very unlikely that pse 12 will ever get the camera raw 8.7.1 update or any camera raw updates past camera raw 8.5)
Do you need camera raw support for that camera in photoshop elements 13?
If you do, i would post at these two places and see if you get any response from an adobe employee.
http://feedback.photoshop.com/photoshop_family
https://forums.adobe.com/community/cameraraw

Adobe Updates via SCUP

Similar Messages

Maybe you are looking for