Updated Final Report:
*Data1.cab inside a MSI is a problem if you use orca to repack the msi file, attempting to do so will result in the data1.cab file being deleted and the package not being installed.
*With the default msi file being provided, during GPO deploy the transform file is being ignored. (We edited the msi file with installashield and manually edited the properties, bypassing that problem so that the package installs with the properties populated.) (verified via local install)
*Even being repackaged the properties values are being ignored. (when pushed out via GPO software deploy) The msi is being run without invoker rights. So the property values are being dropped.
*Entering this: PROXYSERVER (default value="none") into the transform file will also stop the new installer from installing. Use PROXYSERVER (default value="null") instead and it will complete. I verified that the old method works with the version 8.5 msi file.
All testing was performed locally, then retested via GPO software deployment to a clean test environment with UAC off.
The final test was a clean installation via GPO software deployment onto a windows 7 SP1 machine with UAC on.
Required actions by SysAid development:
The run as invoker property needs to be set while creating the MSI file. Here are some of the more common mistakes made: https://blogs.msdn.com/b/rflaming/archive/2006/10/01/uac-in-msi-notes-answers-to-questions-in-comments-from-earlier-blog-posts.aspx
Dump the contents of data1.cab into the msi. Do not use cab files inside msi's. It is a bad practice and in this case is causing issues.
Instruct users that default is: PROXYSERVER (default value="null") instead of PROXYSERVER (default value="none") when using the new installer.