Group Policy
We provide ADM and ADMX templates, to simplify deployment in corporate environment. You can silently deploy application and take advantage of our ADM and AMDX templates to take care of settings for application.
You can find current templates within repository, including ZIP archive with both ADM and ADMX templates.
- Unpack downloaded ZIP archive to location of you choice.
- Open Group Policy console or Local policy (run
gpedit.msc) - Right-click Administrative templates and choose Add or remove templates
- Navigate to .adm file located in the location you specified and add it.
- You can then find settings under Computer Policies/Classic Administrative Templates/Lazy Admin
- Unpack downloaded ZIP archive to location of you choice.
- Assuming you have central store on your DC, copy LazyAdmin.admx and en-US folder to:
\\{DOMAIN}\SYSVOL\{DOMAIN.FQDN}\policies\PolicyDefinitions\
Alternatively if installing on local computer, copy to C:\Windows\PolicyDefinitions - You can then find settings under Computer Policies/Administrative Templates/Lazy Admin
Note: We do not store settings under Policies registry key, so user can modify those values without being overriden by GPO on each update.
Currently you can set two values via GPO.
This settings allows you to specify full path to master definition file. The location can be on local storage, network share or on web server.
Master definition file contains URLs to all scripts definition files, which are used within your company. You can read more about definition files on Definitions wiki page.
This settings allows you to specify full path to custom language file. The location can be on local storage, network share or on web server.
If you want to use Lazy Admin in unsupported language, you can either translate it and share it with us, so we add more languages to Lazy Admin, or you can create JSON file and serve it within your company only. You can read more about how to do it on Custom Translation wiki page.
You are done! Local policies take effect immediately, while settings deployed with GPO take effect on next Group Policy update, which may be forced with gpupdate /force