Westlife’s v0.5.9 strikes an admirable balance between simplicity and power. As one GitHub commenter put it: “It does one thing – makes PowerShell behave the same everywhere – and it does it quietly, quickly, and without drama.” For official documentation, check the README.md and docs/ folder in the AutoSettingsPS distribution. Version 0.5.9 was last updated according to its manifest – always verify compatibility with your PowerShell version before production deployment.
| Feature | Description | |---------|-------------| | | Works on PowerShell 5.1 (Windows) and PowerShell 7+ (Core) | | Granular logging | Separate logs for errors, warnings, and verbose output, with rotation | | Credential-free remoting | Uses WinRM delegated credentials via -AsJob flag | | Group Policy detection | Skips settings that are locked by domain GPO (no conflict) | | Export as DSC resource | Can generate PowerShell DSC configuration snippets | | Idempotency | Running the same command twice makes no unnecessary changes | AutoSettingsPS by westlife v0.5.9
| Limitation | Workaround | |------------|-------------| | – You must use Task Scheduler or a similar mechanism. | Use Register-ASPScheduledTask helper script (provided in /tools ). | | Conflicts with constrained language mode – In JEA or AppLocker environments, some cmdlets fail. | Run in FullLanguage mode or whitelist the module. | | No native Linux support – Even PowerShell 7 on Linux cannot set Windows-specific policies. | Use only on Windows hosts. | | Backup file contains plaintext sensitive data – Registry values (e.g., proxy passwords) are stored as-is. | Encrypt the backup with Protect-CmsMessage or store in an ACL-protected folder. | | Remote remediation requires WinRM – Not usable on workgroups without CredSSP (insecure). | Use Invoke-Command with explicit credentials. | Westlife’s v0