Remote Task fails OMSA Upgrade

Yes it has permissions.

Just wondering, looking at these two lines in the error, could there be something going on with the file being named incorrectly or being referred to incorrectly?:

PackageFileName:   C:\Users\QASO_D~1\AppData\Local\Temp\s6eo\SysMgmt_6_5_0.msi

Error 1316.A network error occurred while attempting to read from the file C:\Users\QASO_D~1\AppData\Local\Temp\s6eo\SysMgmt.msi

The original file on the OME is named SysMgmt.msi, does it get renamed temporarily in the process?

For minor version upgrades of OMSA you will have to specify following parameters in the install arguments for the task

REINSTALL=ALL REINSTALLMODE=VOMUS

We are working on a white paper for OMSA deploy which will provide detailed information for deploying/upgrading OMSA for windows/Linux. We'll post it on the forum pretty soon.

From the error it looks like possible permissions issue while accessing the file from the location below

C:\Users\QASO_D~1\AppData\Local\Temp\s6eo\SysMgmt_6_5_0.msi

Can you confirm if the account you have logged in to OME with has permissions to access the file?

These parameters are carried over from the cloned sample task and are included in the task that still fails.

Thanks for your patience.

OME does rename the MSI with a version but that file is kept on Management Station(the server running OME). The same source file is then used and gets sent to multiple target servers. In OME 1.0.1 when the file is sent to the target it is renamed to SysMgmt.MSI.

Is it possible that you may have deployed OMSA 6.5 to the same target using OME 1.0 or ITA? From the error messages it looks like both SysMgmt.MSI and SysMgmt_6_5_0.msi are present in the windows temp folder on the target.

If you can you clean the temp folder on the target node (Type %temp% from Start Menu->run on the target server and delete) and restart OMSA services, the upgrade task may work fine.