I’m using the SCUP catalog which is just an msp file. From: [email protected] [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Tuesday, August 16, 2016 7:31 AM To: [email protected] Subject: Re: [mssms] Adobe Updates Always Fail
Hi John, When I worked with Adobe in the past regarding the MSP stuff they recommended and said they only support the Bootstrapper method, which means utilizing the EXE with the proper switch, and modifying the INI file within there to specify your MST. May be the most reliable way forward. On Tue, Aug 16, 2016 at 6:47 AM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: I finally got around to opening case with CSS on my Adobe updates issue. I thought I’d share the resolution here just in case anyone else ever sees the problem. I may get around to blogging that later today. * PROBLEM SCOPE When installing an MSP patch file, MSIExec cannot locate the original MSI file on the DP as stored in Windows Install Source management by ConfigMgr * ENVIRONMENT ConfigMgr Current Branch 1602 * ROOT CAUSE The ConfigMgr client would normally use the computer account and/or the network access acount to accces the content on the DP. However it was not the ConfigMgr client but the MSIExec itself that was trying to access the original MSI file on the DP. When doing so it was trying to use anonymous access instead of either the computer account or the network access account * RESOLUTION Set the registry key value HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\WinHttpAutoLogonLevel to Low. Instead of trying annonymous access, this allows MSIExec to pass credentials to the DP based on the user who launched, which in this case is SYSTEM or the computer account. Since the computer account has access to the DP, it allowed it to access the file Additional Resources WinHttpAutoLogonLevel https://msdn.microsoft.com/en-us/library/windows/desktop/hh706787(v=vs.85).aspx Authentication in WinHTTP https://msdn.microsoft.com/en-us/library/windows/desktop/aa383144(v=vs.85).aspx ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
