First know that Windows 7 is not officially supported by PolicyPak and may or may not work for all functions.
Pre-read the following to know what is known to NOT work in Windows 7 before continuing:
https://kb.policypak.com/kb/article/1191-how-does-policypak-support-and-not-support-windows-7/
Then after that, if you still wish to use PolicyPak with Windows 7 and PolicyPak Cloud, you must update Windows 7 to be TLS 1.2 complaint.
Then to adjust on these computers, all pre-Windows 10 machines must be upgraded to use TLS 1.2 on the client. The how-to from Microsoft is here:https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-clientThe quick version goes like this:
Note that PolicyPak Support cannot be engaged for you to update these machines on your behalf. And we cannot automatically validate or report that you have performed the steps correctly.
If you wish to script the installation of the KB3140245 hotfix and the Registry with the “Easy fix” you can do so with two scripts. These scripts will work with PolicyPak Cloud and PolicyPak Scripts Manager (GPO, MDM or Cloud.)
The video explaining how to do this by hand, or by script, or using PolicyPak Scripts can be found at : https://kb.policypak.com/kb/article/1194-05-how-do-i-update-windows-7-machines-to-tls-1-2/
Note for the MSU file, you will need to stage it on Amazon S3 or another publicly readable service like Azure Blob storage. The file cannot automatically be downloaded by Windows 7 in its original home location because that download requires TLS 1.2; and the machine you’re trying to update doesn’t support that yet. Note also that the script references the 64-bit MSU file. You will need a separate script to deliver the MSU to 32-bit Windows 7 machines. Or if you have Windows 8 machines or Server 2008 R2 machines, use the corresponding MSU from the Microsoft Catalog referenced above.
Script 1: Win 7 MSU Update
Script 2: Win 7 Easy Fix