Would this help? I have seen this as a suggested solution as well. Still recieving 136 error code when installing Adobe DC and still cant print anything to PDF through Adobe products.Ī question ahead of time: Is it safe to uninstall CC app without messup other adobe products i have installed on my computer. thinking I was fully removing Adobe DC off my computer in hopes of reinstalling after I restarted the computer. I next did the adobe cleaner tool per Adobe's support recomendation here seen here. Attemped to reinstall Adobe DC but now I have an Error code 136. Restarted computer after the process was done. Issue#2: The next recomendation by Adobe support was to uninstall Adobe DC. I can find AdobePrint.idf in the program files but can not load the driver properly. Step 6 on that support thread is where I go wrong because Adobe is not an option under "manufactures". I have found similar threads on how to solve this issue by manually adding a local printer and downloading the drivers that way (shown here. Issue #1: Print to PDF was not showing up after installing Adobe DC through CC on a fresh new computer. I had my Adobe apps installed and working properly until today. If ($, I have recently upgraded to windows 11. "HPSE" = "Photoshop Elements Home Screen" "FLPR" = "Animate and Mobile Device Packaging" Sap codes obtained from various Internet sources # Define a hash table of all product names for each Sap Code (sorted by Sap Code) # Define the regex pattern to match Sap Codes, version numbers, and platforms $updatesrequired = "Following Updates are applicable on the system" # Define the search pattern to match in the output # Define Latest Version of Adobe RUM executable $ARUMPath = "C:\Program Files (x86)\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager\RemoteUpdateManager.exe" # Set the path to the Adobe Remote Update Manager executable $LogPath = "$env:ProgramData\Microsoft\IntuneManagementExtension\Logs" This makes the assumption your RemoteUpdateManager.exe is located in the default path: "C:\Program Files (x86)\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager\RemoteUpdateManager.exe" In fact, here is the PR scripts I wrote (I’m no Powershell expert, but it works ), I run these daily and are targetted at all users that have Adobe Creative Cloud installed If you have an existing version of an Adobe Creative Cloud App installed, (and have chosen to deploy the Remote update manager with the Creative Cloud App) it is quite easy to call Adobe’s Remote Update Manager (aka RUM) to check for and update existing versions (Note: RUM can not be used to Upgrade to a new full version of a product (2022 to 2023 for example), but can be used to update existing in year updates) - we use this very effectively to fix security issues. I wish Adobe’s larger software packages (Premiere Pro & Photoshop for example) were chunked into smaller components so you could choose what to install, and new versions would only update the changes.Īs a side note it’s worth looking at using a Proactive Remediation (PR) in Intune to keep Adobe applications upto date. Our mitigation is to package each Creative Cloud app (Photoshop, Premiere Pro, InDesign, Media Encoder, Bridge etc… separately) and create the dependencies within the Intune deployments this allows each app to download and install one at a time and stands a much better chance of landing without hitting the timeout issue - Sadly you do end up with a lot of packages in the Adobe Adminconsole. Hi, yes you are correct Intune does have a timeout period, and deploying most of the dobe Creative Cloud applications usually hit this time limitation as the installs are GB’s in size. The intune install seems to done on a machine with a previous version already installed and needs to be removed before re-installed. Last line is: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install sourceDir=. There are 1060 mentions of UnregisterSharedComponentProvider There are 4200 mentions of UNKNOWN\Components CreativeCloud.mst is mentioned 15 times (!?!?!?) creates a local cache? (CacheRTMFile and CacheSizeFlush The Intune DeployAdobe_Creative.log file however. There are more lines after Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install sourceDir=. Certain special characters, like (asterisk) or / (forward slash), arent compatible with all devices. There are NO mentions of UnregisterSharedComponentProvider There are NO mentions of UNKNOWN\Components CreativeCloud.mst only shows up 3 times. The Local圜ommandInstallAdobe_Creative.log file While there is a formal way to strip-out the MSI timestamps to compare MSI log file, I did a visual compare by myself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |