If you are using an internal web server for the kickstart script you simply have to modify the line ps1 file or provide it by a network share or local drive. For this you will have to download the script file manually once and place it either on an internal web server from which the kickstart script can fetch the.
Of course you can also use the kickstart script file for offline installation in case you have no access to the internet. Once completed, the kickstart will ask if you want to continue with the Icinga Agent installation wizard.
It will ask a bunch of questions on where the Icinga PowerShell Framework should be downloaded from and where it should be installed. The Script file from will be downloaded and executed within your current PowerShell instance. Last but not least we will set the progress preference to Silentl圜ontinue, ensuring the PowerShell progress bar will not slow down our installation. The ServicePointManager part will ensure communication is possible to GitHub for example, as by default PowerShell will be unable to open a secure connection otherwise. What this block will do is to download the PowerShell Script from the repository, add it into a ScriptBlock to allow execution and finally execute it. Content $Script += " `r`n`r`n Start-IcingaFrameworkWizard " Invoke-Command -ScriptBlock ( :: Create ( $Script )) :: SecurityProtocol = "tls12, tls11" $ProgressPreference = "Silentl圜ontinue" $global:IcingaFrameworkKickstartSource = '' $Script = ( Invoke-WebRequest -UseBasicParsing -Uri $global:IcingaFrameworkKickstartSource ). Note on Start-IcingaFrameworkWizard and automationĪutomation Example 1: Use local web server for Framework downloadĪutomation Example 2: Use local/network path for Framework "download"Įxecute the Icinga Agent installation wizard
0 kommentar(er)
