Thank you, this is wonderful. I had considered trying to write something similar myself. I don't think my Powershell skills are up to this level, but what would be good in this would be: 1. To make it work across a multi-server environment (we have a metadata server, a mid-tier, a compute server and a LASR compute server) 2. To ensure webapp servers don't start until any upon which they are dependent have completely started (eg. 2_1 and 12_1 don't start until 1_1 is fully running).   I do rather love Powershell. And this is from someone who was dragged kicking and screaming from a Unix environment to Windows, about ten years ago! ... View more

On Windows machines, usually "C:\Program Files\SASHome\InstallMisc\InstallLogs". The main log is IT_yyyy-mm-dd-hh.mm.ss.log but DeploymentSummary.html should give you a high-level summary ... View more

Thanks Kurt. We do use the standalone installers for EG and AMO, and the standard install for SMC, Personal Login Manager and XML Mapper. The issue isn't with installation as such, which is working, it's about adding hot fixes to the Depot so they can be included in new installations and applied to existing installations. We can't do that directly from the server hosting the Depot so we have to copy the Depot over to a machine which does. This has quite limited storage and is shared with other folk who need to download software updates, so I would prefer not to copy over the full 29Gb of the Depot. Hence my question. ... View more

Welcome to my World, @SASKiwi, our Cyber Security folk are very risk-averse! Which I suppose is as it should be. I might try pinging TS with my question. ... View more

Thanks to both @SASKiwi and @angian for your responses. The reason I need to get the hotfixes this way is so that they can be added to the Depot for applying to existing and new client software deployments - mainly EG and AMO, but also Management Console, and we have several hundred existing ones. Installations of client software takes place using SCCM, as does the application of hotfixes, but only if I can add them to the Depot. Once that happens, any new installations should automatically pick up the hotfixes, and we have an SCCM deployment for applying new hotfixes to existing installations.   Our environment is quite heavily locked down. I use the Deployment Registry on our servers because I have administrator rights on them, but I don't have that on workstations, and our firewalls and proxies block us from downloading executables directly to workstations. The only place I can do this is a specific machine in our extranet (DMZ), so I need to copy the Depot there. But, as I said, it has quite limited space so I'd rather not copy the whole Depot onto it. Hence, wanting to know if there is a subset of the Depot which would suffice. The "Retrieve Hotfixes" option in Deployment Wizard does more than just download the hotfixes, it maintains a couple of XML index files as far as I can see. But I don't know exactly what it requires from the Depot to work properly, presumably not everything. ... View more