Software Deployment

Hi,

try doing the same by using a Local System Account (LSA). Perform the following task:

1. type cmd in the run command line.
2. use the at command to open another console that will run using the LSA.
3. launch the executable that gives you this error.

if this behaves the same was as for the administrator, then you can always run this executable using the LSA or you can also use the RunAs command and embedd it at the end of the MSI to run this executable. However, I would term it as a very bad approach.

What a pity that Cisco has packaged this MSI and such a clause is included in it... [X(]
All the Best to you dear!!

Thanks Matrixtushar, thats a good tip to try. The only problem with this particular scenario is that on first launch the app starts a wizard which requires input from the user to set up the audio properties. It's after this wizard completes the error comes. When run by the LSA it hangs waiting for user input.

Try snapshotting the changes made by the first launch and add those resources to a transform.
If any are located in the userprofile or HKCU make sure that the application repair those on first launch.

a dirty solution would be to write a VBScript that runs in LSA and uses the function SendKey in the shell object to simulate a user click.

I had to do such a workaround in PGP 8.1 Package... [:(]
if you need the script probably i can provide you...

Hi folks,

I have also come across that issue and found it will appear if a user without administrative privileges is logged in at installation time. As we use Altiris (Symantec) Deployment Server for distribution, we perform an auto-log off prior to the install of the package. The same is valid for currently released IPC v7.0.2.x which we currently distribute.
Hope this helps,
Bij

It didn't matter if the user was logged in or not during the install. The problem is if after the install a non-admin logs in, the initial tasks (audio setup, etc) fail. I tried capturing it, procmon, regmon, etc. I even tried manually giving the standard user admin equiv permissions on the registry and file system without adding to local admins. It acted like it was doing a check for membership of local admins.

I haven't tried the 7.x versions, so they may have fixed it.

It acted like it was doing a check for membership of local admins.
In that case; shimming sound like the solution to this.