Forum Discussion
Hi Mike,
Through Intune (along with other remote shells that execute as SYSTEM) I've always used the following
/qn /norestart ALLUSERS=1
This has typically worked without any issue for the past several years.
Through Intune in particular though, this would have been as an MSI wrapped as a Win32 application simply with those as the install command.
Since being forced to use the .exe version, I've been unsuccessful in any SYSTEM context deployment using a combination of '-silent -allusers' or simply just '-allusers'
In every instance, I can see the process just sit there in the background, failing to proceed.
As this is in SYSTEM context, there is no UI visible to me, even when using PSEXEC to execute as SYSTEM.
Are you able to advise exactly which logs you'd like me to review?
EDIT:
It should be noted that using '-allusers' as a local user, not SYSTEM works perfectly fine, but this is just not a feasible or realistic solution if this is expected to be deployed at scale.
Thank you for the additional info jbiskit , and sorry for the delayed response.
For the logs, can you please check: %localappdata%\SquirrelTemp
I have enabled private messaging for you if you want to share the logs to me via direct message.
- jbiskit18 days agoMember
Hi Mike,
I've checked the %localappdata% path for the SYSTEM account after a failed install attempt and there was no output of a SquirrelTemp folder.
For reference, this is the script I've used previously. When running as SYSTEM it fails, when running as a local administrator, it works fine.
TLDR: Save the below as a .ps1 file, call it using `ScriptName.ps1 -version 2026.6`
It will download the latest version, and attempt to install it.[CmdletBinding()] param( # Version to install; this is passed through to URL and installer args. [Parameter(Mandatory = $true)] [string]$Version, # URL template must contain "{version}" placeholder. [string]$DownloadUrlTemplate = "https://download.myob.com/arl/MYOB_AccountRight_Setup_{version}.exe", # Extra installer arguments passed through as-is. [string[]]$InstallerArguments = @("-allusers") ) $ErrorActionPreference = "Stop" function Get-InstalledMyobVersion { param( [Parameter(Mandatory = $true)] [string]$TargetVersion ) $uninstallPaths = @( "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*", "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" ) $entries = foreach ($path in $uninstallPaths) { Get-ItemProperty -Path $path -ErrorAction SilentlyContinue } $expectedDisplayName = "MYOB AccountRight $TargetVersion" $myobEntry = $entries | Where-Object { $_.DisplayName -eq $expectedDisplayName } | Select-Object -First 1 return $myobEntry.DisplayName } $installedVersion = Get-InstalledMyobVersion -TargetVersion $Version if ($installedVersion) { Write-Output "MYOB version $Version is already installed. Nothing to do." exit 0 } $downloadUrl = $DownloadUrlTemplate.Replace("{version}", $Version) $tempInstaller = Join-Path 'c:\temp' ("MYOB_AccountRight_Setup_{0}.exe" -f $Version) Write-Output "Download URL: $downloadUrl" Write-Output "Temporary installer path: $tempInstaller" if (-Not (Test-Path -Path $tempInstaller)) { Write-Output "Temporary installer not found at $tempInstaller. Will download." Write-Output "Downloading from $downloadUrl" try { Invoke-WebRequest -Uri $downloadUrl -OutFile $tempInstaller } catch { throw "Failed to download MYOB installer from $downloadUrl. $_" } if (-not (Test-Path -Path $tempInstaller)) { throw "Downloaded installer not found at $tempInstaller." } } else { Write-Output "Temporary installer already exists at $tempInstaller. Will re-download." } Write-Output 'Swapping Install Mode...' change user /install ##Tested to see if this would fix the SYSTEM issue on Terminal / Multi-user hosts. It doesn't Write-Output "Running installer..." $process = Start-Process -FilePath $tempInstaller -ArgumentList $InstallerArguments -Wait if ($process.ExitCode -ne 0) { throw "MYOB installer failed with exit code $($process.ExitCode)." } $postInstallVersion = Get-InstalledMyobVersion -TargetVersion $Version if ($postInstallVersion) { Write-Output "MYOB $Version installed successfully." Remove-Item -Path $tempInstaller -Force } else { throw "Install completed but expected app name 'MYOB AccountRight $Version' was not detected." }- Mike_MYOB18 days agoCommunity Manager
Thank you jbiskit - I have passed your email to the team who are looking into this. I think it will be easier to connect with them directly instead of having this thread as the middleman.
Really appreciate you connecting with me via the forum on this though! Hopefully we can publish an update on how this was fixed soon
- The_Doc18 days agoUltimate Cover User
Hi Mike_MYOB
This is now working for me but not on an elevated CMD prompt - this install method failed on my in-house staff server as it has for my client servers.
However, what worked perfectly was an elevated Powershell process.
Download the MYOB_AccountRight_Setup_2026.6.exe to a directory on your desktop eg. MYOB_Installers
Open an elevated Powershell window.
Cd to the desktop directory holding the installer exe.
Then in Powershell type .\MYOB_AccountRight_Setup_2026.6.exe -ALLUSERS and it silently installs PC Edition into
C:\Program Files (x86)\MYOB\MYOB AccountRight 2026.6 and deposits in public desktop a shortcut for 2026.6.
This process does not appear to work under an elevated Cmd.
The Doc
Looking for something else?
Search the Community Forum for answers or find your topic and get the conversation started!
Learn, solve, grow
Level up your skills and find answers across all MYOB products