Westy182 Posted May 13, 2016 Report post Posted May 13, 2016 Hi all, I have an application is SCCM that runs a vbs to install Office 2016 click to run. The packaging team have used a VBS so they can cover installing Office 2016 on different versions of Windows and also trigger the appropriate Office scrub tool if applicable. Anyway, in my instance I am running the application on a Windows 7 Enterprise X64 machine which has Office 2013 C2R already installed. If I run the script out of SCCM it upgrades O2013 to O2016 in around 15 mins but when installing via the SCCM Application it hangs sometimes for an hour before the actual install occurs. The smsts.log sticks at "Invoking App Management SDK to evaluate app polices" and I can see "officeclicktorun.exe" in the processes not doing anything. If I check ccmcache I can see an empty folder with the same time stamp as the last entry in the smsts.log so the download hasn't happened at this stage either. What is actually happening when the App Management SDK is invoking? Also, if I run the script as a legacy SCCM package it seems to work ok. The problem is just with SCCM Applications. I'm a bit miffed. Any help or advice would be gratefully received. Westy Quote Share this post Link to post Share on other sites More sharing options...
