gwblok As mentioned in Previous Post, we’ve had upgrades fail due to non-standard path variables. I’ve created a CI that captures the path and looks for specific things then reports Compliant, or reports the issue, which we track with reports. We use this in our PreAssessment / PreFlight Rules, so if this is Non-Compliant, it prevents … Read more
I’ll try to keep this post updated as I continue to find problem, and link any new posts back to this one (and vice versa). We’re part way into our 1809 push and we’ve found some problems (edge cases) which others might see. Some issues are completely specific to us (or at least places who … Read more
Windows 10 has some great data in the Registry concerning the Windows OS and it’s previous builds. This can be great for reporting, or troubleshooting. First off reporting, I’m not going to touch that one much, but Hopefully Sherry K. will be posting something about that topic, or CM will build in native functionality. UserVoice:HERE … Read more
Ok, this is more for me to reference than others. Another great post to reference similar issues: https://miketerrill.net/2019/01/07/nomad-software-update-lsz-file-purge-aka-whack-a-mole/ Came across a problem with Nomad not downloading Packages properly, it was downloading the wrong version. (which would fail) Clients were getting LsZ File (PS100044_1.LsZ) when the Server’s content was actually version 3. DP’s were not updating … Read more
We are currently writing several keys & values to the registry for our process to collect metrics, more details HERE: Registry Values used in WaaS Process for reporting So, you have all that awesome data from your upgrades, and you want to collect it into your database for reporting, Registry to MOF is the key. … Read more