Master Definition File
If you want to deploy Lazy Admin in your environment and use you own commands, you have to create master definition file. Don't worry, it is a simple feat.
Below you can find example how master definition should look and explanation for each parameter.
After you create master definition file, you have to serve it to computers where Lazy Admin will be used.
You can either:
- Install Lazy Admin with installation parameter as described on Deployment wiki page.
- Deploy with GPO using our ADM/ADMX templates as described on Group Policy wiki page.
- Set Registry value
HKLM\SOFTWARE\Lazy Admin\MasterDefinitionUrlwith path to your file.
Once Lazy Admin is started and user logs in, master definition file will be downloaded and processed, downloading all listed scripts definitions.
You can view our example master definition file, which serves our example scripts definition in repository.
Version is important parameter, which has to be updated when editing master definition file as Lazy Admin performs simple comparation of its current version and downlaoded master definition version. This version is then displayed on About page in Lazy Admin. You can name it whatever you want it. Just make sure to change it when new version of Master definition file is created.
Note: You do not have to update Master definition file if you only change Scripts definitions contents and retain their location. Scripts definitions are updated separately even if master definition does not change.
Purely information and optional parameter with date of master definition update date.
Required parameter, which is an array containing paths to Scripts definitions, which get downloaded by Lazy Admin.