You will most likely install Software Deployable Packages using LCS, as outlined on the official docs, so why would you need a PowerShell script for this? It so happens that you need to install the package manually if you for example need to upgrade from 7.2 to 7.3 of Operations.
You download the package from LCS. After unblocking the zip-file, and extract it somewhere. I typically extract it on the Temporary Drive, the D-drive. Then you simply need to run this small script to initiate the installation locally.
#Requires -RunAsAdministrator function InstallSDP() { $BinaryPackageLocation = 'D:\Update' $Installer = $('{0}\AXUpdateInstaller.exe' -f $BinaryPackageLocation) if (Test-Path -Path $Installer) { Set-Location $BinaryPackageLocation & $Installer 'quickinstallall' 2>&1 | Out-String } else { Write-Output $("No update found in {0}" -f $BinaryPackageLocation) } } InstallSDP
Now, this will not work unless you have local admin rights. So the yes, that means if you plan to run the 7.2 to 7.3 upgrade, you need to run it on a machine where you have local admin rights. This is pointed out in question 14 on Robert Badawys FAQ on the matter.
Notice I am using the "quickinstallall" command here, and this is only applicable for OneBox Developer VMs.
So what about "devinstall"-command? You cannot use the devinstall for the upgrade package, but you can use it in other scenarios where you install customization packages and hotfixes. It was introduced in Platform Update 12, and is intended for use without the need for local admin privileges.
No comments:
Post a Comment