mdedeboer

Including the software key is going to completely dependent on the installer you are using. For example, for Microsoft Office you would need to create an MSP file. Largely, you will need to rely on installation documentation or reverse engineering to silently include license key information. With regards to the exe installer for treesize professional, the online installation manual covers this scenario: https://www.jam-software.com/treesize/manual.php I hope this helps!

For anyone looking for documentation on this, please see: Are there any prerequisites for update 3087985? Yes. Customers running Internet Explorer 7, Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, or Internet Explorer 11 on Windows 7, Windows Server 2008 R2, Windows 8.1, Windows Server 2012 R2, or Windows RT 8.1 must first install the 3078071 update released on August 11, 2015 before installing the 3087985 update. Note For Download Center customers: If you download and install updates manually, you must first install update 3078071 before installing update 3087985. Failure to follow the install order can lead to degraded functionality. https://technet.microsoft.com/library/security/MS15-093

Thanks ebrix I'll look into this. What is odd though is I can successfully install it if I download and install it manually from the update catalog. -Matthew

As you are all well aware, late today Microsoft released KB3087985 as part of MS15-093. I am wondering if anyone else is having issues getting their computers to report that this patch is required. So far I have 65% of my 2000 desktops reporting that it is not required to the SUP. Yet when I download it from catalog.microsoft.com I can install it (although it shows up as a hotfix). I am guessing that this is a detection rule issue in the update although I can't find anyone else having this issue yet... Thanks! Matthew

Ah makes sense... Totally different issue

I don't think this is the entire smsts.log. Keep in mind that once the client is installed, this gets moved to C:\Windows\ccm\logs\smstslog\smsts.log You should have multiple copies in this directory since your log will likely roll over once. In your rolled over version of the log (looks like smsts-DateSTamp-TimeStamp.log), check for any errors during the client install. (such as "Timed out waiting for ccmexec service to be fully operational") Also check the c:\windows\ccm\logs folder for statusagent.log (again, likely the rolled over version of the log). During the time the client got installed (or after a reboot), you may have this error: This currently is mainly speculation, and no one will be able to tell for sure without more log files provided. However, I currently have a call open with MS when my Win 7 base build (from ISO) started failing on Software Updates and Software Packages (command lines that used packages were fine). This started after we upgraded R2 to SP1. We've found that the client actually never successfully registers, but that is it so far. If you can provide these two log files, we can verify if this is a reproducible issue. If these errors aren't in your logs, it is still beneficial to provide them