Open cameronkollwitz opened 4 years ago
It's working fine here, just installed one....
Try to run cmd.exe with "Run as Administrator" option and then run the MSI package from this console.
Try to run cmd.exe with "Run as Administrator" option and then run the MSI package from this console.
This worked despite still receiving the error on a newly-imaged device (see primary thread reply).
Still experiencing the issue, so here's what I see. This is a freshly-imaged device with the Configuration Manager Console installed on it.
First I "unblocked" the MSI that was downloaded from the Release page.
After running from File Explorer, I receive a UAC prompt for administrative priviledges. I accept.
This is the error that is immediately produced, despite confirmed the account is in the Administrator Security Group.
Running the MSI directly from an elevated Command Prompt as suggested by @Kraktorist did allow the installation immediately (without changing anything on the device after receiving the error).
Edition: Windows 10 Enterprise Version: 20H2 Installed on: 12/1/2020 OS build: 19042.508 Experience: Windows Feature Experience Pack 120.2212.31.0
I too am unable to install 1.0.6.1 from the GUI with a domain account that has administrative privileges (i.e. is a member of the computer's local Administrators group). Yes, installing from an elevated PowerShell session works.
The msi log shows:
Action start 8:00:18: LaunchConditions. MSI (c) (E4:70) [08:00:18:794]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Client Center for Configuration Manager requires installation by an Admin user account. MSI (s) (14:68) [08:00:38:356]: Product: Client Center for Configuration Manager -- Client Center for Configuration Manager requires installation by an Admin user account. Action ended 8:00:38: LaunchConditions. Return value 3. Action ended 8:00:38: INSTALL. Return value 3.
The value 3 in the log is a generic and equates to a 1603 error.
Remember, sometime in Windows 10 even though the user account you are using is in the local admin account, you still have to either 1) right-client on the .msi a select 'Run as Administrator', or 2) set the file to 'run as administrator' on file propertise, so it always initiate it.
Just chiming in to say that I also experienced this issue with "Client.Center.for.Configuration.Manager_v1.0.6.1.msi". Calling the installer from an elevated command prompt as a workaround worked for me.
It appears that there is something wrong with the "Client.Center.for.Configuration.Manager_v1.0.6.1.msi" package. No matter what device (I've tried on about 12 now) it will not install. It claims that it needs administrator permissions - even when being run from LocalHost\Administrator.
The only workaround that I've found is to install the v1.0.5.5 MSI package and then run the self-update function within Client Center.