-
Notifications
You must be signed in to change notification settings - Fork 5
Deployment
WARNING
We use NSIS as current installer provider, which works, but carries some caveats:
- Parameters are case sensitive
- Installation path paramater
/D=
must be last parameter when used
Parameter syntax
/S
Example
CMD
".\Lazy-Admin-Setup-X.X.X.exe" /S
PowerShell
Start-Process -FilePath ".\Lazy-Admin-Setup-X.X.X.exe" -ArgumentList '/S'
Installs silently and does not open application after installation. Default behavior is passive install and application opens afterwards.
Parameter syntax
/URL="{CustomURL}"
Example
CMD
".\Lazy-Admin-Setup-X.X.X.exe" /URL="http://share.contoso.local/master-definition.json"
PowerShell
Start-Process -FilePath ".\Lazy-Admin-Setup-X.X.X.exe" -ArgumentList '/URL="http://share.contoso.local/master-definition.json"'
Sets master definition URL in HKLM\SOFTWARE\Lazy Admin\MasterDefinitionUrl
.
If parameter is not supplied and key does not exist, installation sets URL to example definition in this repository. Preferably should be set with GPO.
Parameter syntax
/D={CustomPath}
Example
CMD
".\Lazy-Admin-Setup-X.X.X.exe" /D="C:\CompanyApps\LazyAdmin"
PowerShell
Start-Process -FilePath ".\Lazy-Admin-Setup-X.X.X.exe" -ArgumentList '/D="C:\CompanyApps\LazyAdmin"'
Installs directly to target directory, without any additional subfolders, in example above, main application would end up in:
C:\CompanyApps\LazyAdmin\Lazy Admin.exe
Note: If you use this parameter, you must use it as last parameter, as NSIS will treat anything after
/D=
as installation path.
- How to Use
- Login Page
- Scripts Page
- Settings Page
- About Page
- Workflows
- How to Install CredentialManager Module
- How to Install PowerShell Core
- Setting up Development Environment
- Contributing to Project
- Components
- Login Page Breakdown
- Scripts Page Breakdown
- Settings Page Breakdown
- About Page Breakdown
- Command Execution
- Get SavedCredentials
- Scripts definitions update workflow