Some problems that may be seen are:
1. An error 1603 is received during the install of USB/Port Security.
2. The client computer attempts to reboot each time Desktop Authority (DA) runs because USB/Port Security's install is stuck in a reboot loop .
3. The installation of USB Port Security cannot be performed unless the logged on user is a member of the Local Administrators Group.
This may be an issue with InstallShield.
The default InstallShield DCOM launch Identity settings may have been changed from the default setting. The setting “The launching user” may have been altered to one of several settings. If the user is a local administrator, then they are allowed to install an MSI in their own security context as the launching user. However, if the user is not a local administrator, then the MSI cannot be installed by the service using impersonation because the default setting which allows impersonation to install has been altered not to allow it.
Run DCOMCNFG on the affected client machine and change the launch permissions on the InstallShield DCOM Identity object(s) back to default. To automate this setting using DA, simply enter the first of the two entries below into the Global Definitions File:
$SetInstallShieldDCOM = 1
$SetInstallShieldDCOMback = 1
(Do not copy these settings directly into the definitions file from this article. Either type them into the definitions file or paste them into notepad and then copy from notepad and paste into the definitions file)
Explanation of variables: The first definitions entry above, instructs the main engine to set the DCOM install setting back to default which allows the MSI to be installed by the DA Run As Admin Service and then the second entry reverts the DCOM setting to how it found it originally but only after the MSI is installed.