Blog Post
OK Mike
Can you explain why 2026.600.10011 stops printing ability? Also email from myob ability, and even print preview. Ive blown close to 6 hours now uninstall/reinstall/setting library location/checking permissions on the relevant folders.
previously prior .400 or .500 we ran Accountright Server Edition on MS Server 2022 TS. Then SE updated and stopped working. so after hours we reverted to PC edition installed on every TS instance. Then had to modify the library folders permissions on every instance because installed. now today another new install, printing stops, email stops.
i found your release post, followed the -allusers install instructions. with now hours of futile effort.
As a matter of urgency, can you advise of at least a workaround, if not a resolution.
It would be fair to say that "frustration" barely passes as decriptrive of mood.
I sincerely look forward to the day that myob stops treating software usability and user experience as collateral damage, and elevates them to crtical to myob's long term survival.
- ITHelper1239 days agoMember
Hey Joe!
So, I battled with this yesterday. The new installers “-allusers” and “-silent” flags are not working as you'd usually expect from a normal installer MSI, EXE or otherwise. I also don’t want uses to install the product in AppData and manage the app themselves aka using the “-silent” parameter.
Long story short, we use PDQ connect currently to manage all app installs and we are ESS8 compliant so no user can install any app themselves. I figured out yesterday EVEN logged in as a LOCAL ADMIN on a workstation I STILL had to elevate a (right click open as admin) CMD/Powershell window to use the -allusers command. Running PDQ as normal “Local System” did not work. So I wrote two packages:
- One uninstalls the old version and copies the “MYOB_AccountRight_Setup_2026.6.exe” to the users’ workstation to “C:\PDQConnect\MYOB”. (This file could be hosted on a share if you like)
- The second runs the following script on a Jumpbox/utility VM with a workstation admin logged in you could do it en masse with many different tools in your org:
$ComputerName = "COMPUTERNAME.domain.doman"
$Session = New-PSSession -ComputerName $ComputerName
Invoke-Command -Session $Session -ScriptBlock {
Set-Location "C:\PDQConnect\MYOB\"
Write-Host "Starting installation"
Start-Process ".\MYOB_AccountRight_Setup_2026.6.exe" `
-ArgumentList "-allusers" `
-Wait `
-PassThru
}
Remove-PSSession $Session
This runs the powershell script on the VM, which in turn ps-session’s into each pc and then runs the installer in an already elevated session. Basically, the EXE is broken or written in a way to not operate as a “True” all user/silent install.
- Mike_MYOB9 days agoCommunity Manager
Thanks for the assist ITHelper123 !
joemj, the team ran some testing on our end and were unable to see any issues with:- Preview sales
- Print sales in bulk or single
- Email sales/purchases
If the advice from ITHelper doesnt solve this for you, can you please provide some more details/screenshots on the reported issues? Is it for any specific transactions?
You can send this to me via private message if you prefer - brunob9 days agoMYOB Product Manager
Hi ITHelper123
Can I confirm my understanding?- Previously, you used the MSI installer with "/qn" for silent deployments.
- With the MSI installer, automatic updates were disabled and updates were managed through your deployment tooling.
- With the new installer, "-silent" performs a silent installation, but automatic updates remain enabled, which doesn't fit your deployment model.
Is that an accurate summary of the challenges you're seeing?
Question from me: Have you also tried using "-allusers" (the equivalent of MSI's "/AllUsers=1")? If so, was the issue that it did not behave as expected in your deployment environment?