We started deploying 7-Zip v18.01 but quickly had to stop the deployment due to Windows Explorer crashing and leaving the end user without a taskbar. We tweaked our deployment and added this parameter to our PowerShell App Deployment Toolkit install string:
Upgrading Windows 10 (e.g. v1511 to v1607) is easy using the upgrade task sequence in SCCM. Unfortunately it is not as user friendly as we would like, most notably there is no warning to the user that an upgrade is about to take place (when you set the upgrade task sequence to required). To fix this issue we use PowerShell App Deployment Toolkit to warn the user and allow them to delay the upgrade task sequence.
We had a lot of problems getting Citrix Receiver to install correctly in our task sequence. During imaging it would hang until you moved the mouse or it timed out. Apparently this is a semi-common problem due to how Citrix Receiver installs USB support.
We had an issue in our environment where when a user first logged onto a Windows 10 workstation their Internet Explorer home page wasn’t set to our intranet. This issue occurred even though the home page was being set via GPO. We determined this was due to how Windows 10 provisions profiles on first logon.
For whatever reason the TPM chip was being set to disabled during our imaging process/checklist. This became an issue when we started rolling out MBAM (BitLocker). In order to remediate this we deployed a package using SCCM and PowerShell App Deployment Toolkit that would enable the TPM chip.
Thankfully Lenovo makes it easy to modify the BIOS settings from inside Microsoft Windows. There is a gotcha when enabling the TPM chip though, that gotcha is that the WMI call is different depending on if it is a desktop or a laptop.