In some cases when attempting to install vSpace software on Windows 7 or Windows 8, you will get the error: “You need administrative rights to install this software. Installation Failed.” This will happen even when logged on as Domain Admin, you must be the local system administrator to install vSpace.
The following steps will allow you to install via command line.
Installation on Windows 7 or Windows 8:
You
must have administrative rights to install vSpace Server onto Windows 7 or
Windows 8. However, unlike in Windows Server 2008 R2, the actual
“Administrator” account is not enabled by default in Windows 7 and 8. So, even
though you may be logged-in as a user that is a member of the Administrators
group, you still won’t have sufficient “administrative rights” to install
vSpace Server, and the MSI installer will generate an error message saying:
“You need administrative rights to install this software. Installation Failed.”
To
check what user account is the right one for vSpace Server installation open
the Command Prompt and invoke following command:
wmic useraccount get name,sid,status
|
Name
|
SID
|
Status
|
|
Admin
|
S-1-5-21-3686465141-1345607283-3162306831-500
|
OK
|
|
Guest
|
S-1-5-21-3686465141-1345607283-3162306831-501
|
Degraded
|
|
HomeGroupUser$
|
S-1-5-21-3686465141-1345607283-3162306831-1003
|
OK
|
|
John
|
S-1-5-21-3686465141-1345607283-3162306831-1002
|
OK
|
|
Paul
|
S-1-5-21-3686465141-1345607283-3162306831-1005
|
OK
|
For
vSpace Server installation an account whose Security Identifier (SID) ends with
-500 (the ‘Admin’ account in the above example) must be chosen. That account
can’t be locked (degraded). Unlock the account and set up a password for it if
necessary. To start an “Administrative Command Prompt” for the selected
administrative user invoke the following command (the password of the administrative
user must be entered when prompted):
runas /user:Admin cmd.exe
To
make sure the “Administrative Command Prompt” has been started for the right
user invoke this command:
msiexec /i install-filename.msi
Your install should now run without issue.
Article: 1019