SYSTEM account fails to read configuration file where as other admin account does.(Quick View Plus 12.0)
Hi, can some one help me with a solution on the below issue.
I have a setup.exe and setup.cfg file. setup.cfg has the serial key and some other customization settings in it. If the setup.cfg file is placed in the same folder during the installation, the installation finishes successfully and handles the activation as well. The main purpose of setup.cfg is to handle the auto activation. This works perfectly fine when run using an admin account. But fails when run using SYSTEM account.
This issue is faced with Quickview Plus 12.
Any help is appreciated.
Thanks,
Praveen
Answers (2)
Think about how activation works....
Now think about what access the System account has. Specifically, think about its "full name", i.e. local System...
I'm sure you can work out the rest. As to a solution, if there's no way that the user can silently trigger an activation, perhaps you need to think about creating a special domain account which will have local admin privileges on all your estate's workstations (although most sites will already have such an account) and use that to install.
Comments:
-
Hi VbScab,
Thanks for your inputs. After investigating, found that SYSTEM account does not have internet access to activate the product. This is the reason for the activation to fail.
There is no common admin account as such in my client environment. Looking for an alternate solution.
Cheers,
Praveen - praveenk 10 years ago
The SYSTEM account is used by varous deployment technologies (HPCA\Radia SCCM) to run the installation in an administrative context where ordinary users are not administrators of their own machines (most corporate environments). You cannot specify an alternate account.
We had whitelisted the activation url so that the SYSTEM account could access the URL but still found that the activation failed.
In this situation, the activation process of the product was attemting to use the IE proxy settings for the account running the installation (in this case SYSTEM), it would ignore the system proxy settings (configured via proxycfg on WinXP or NetSh Winhttp set proxy under Win7)
As a solution, we scripted the install to configure a proxy server for the system account by using a REG ADD to push the proxy settings directly into the SYSTEM account registry settings (GUID is S-1-5-18), install the product and let it register, then remove the registry settings.
This allowed us to register the product, but would not leave the SYSTEM account with internet access.
Luckily the product is registered on a per-machine basis so after being registered as SYSTEM, any user could run the software.
