Unable to deploy packages post upgrade

[FixitDave]

Since we have upgraded we are unable to fully deploy a package.

We are able to deploy a package that does not rely on access a network share, eg local disk to the PC (ie gpupdate) but when we try to deploy to a remote share inc DefaultPackageShare, it fails.

All system checks that we have in place all work (OS type, file existence, etc), it always fails trying to access the network share.

We have reconfigured the share, moved to another file server, changed credentials...but still fails.

When we run the command from a command prompt on the PC, it runs fine.

We are due to deploy an upgrade to an application this week so I would appreciate a quick response.

Full error message is;

Result: Deployment ended: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Stop(Failure). Credential: (.\administrator). ShareCredential: (lansweeper\installer).
Command: msiexec.exe /i "\\fs1\WRK1\mir32.msi" /norestart /qn SERVERIP=mirage USESSLTRANSPORT=TRUE /quiet


Thanks
Dave

[Susan_A · Accepted solution]

FYI for everyone: an updated installer with bug fixes is now publicly available. If you haven't already, update to the latest Lansweeper release by following these instructions.

[Susan_A]

There are some known deployment bugs in 6.0.0.19. If you haven't already, please contact support@lansweeper.com to receive an updated installer with bug fixes. An installer with fixes was already created and is being tested internally, but is not listed on our download page yet. Just future reference: the quickest way to get support is to contact support@lansweeper.com, as emails are prioritized.