by Roger·Comments Off on user not allowed to log on to this computer
Cognos Controller Client 10.4.2
Microsoft Windows 10
During manual install of ccrlocalclient64.msi on a users laptop they get a error message.
Installing a program on a workstation demand that you are local administrator on that workstation.
In many cases, this is not allowed at companies, but you can get a temporary different user account that is local administrator.
But even when you use this temporary admin account, during installation, you get above error.
First ensure that you account is local admin on the computer.
It should belong to a global Active Directory group that you can find in the list of administrator groups on the laptop.
The command net user adminDonald /DOMAIN will show the groups the account is part of.
Then check that one of these groups is part of the Administrator group on your computer.
Press the Win + R keys on your keyboard to open Run, enter the command compmgmt.msc, and then press Enter or OK.
Go to groups and click on Administrators to see what groups are listed.
If the group is in the list, that account is local admin on the workstation.
If it still does not work, ensure the workstation name is listed as allowed (see below).
If you run the below command for user Donald, you get a result similar to this.
C:\Windows\system32>net user adminDonald /DOMAIN
The request will be processed at a domain controller for domain europe.com.
User name Admindonald
Full Name Donald Duck admin
Country/region code (null)
Account active Yes
Account expires 2022-08-11 00:00:00
Password last set 2021-08-11 14:12:59
Password expires 2022-08-11 14:12:59
Password changeable 2021-08-12 14:12:59
Password required Yes
User may change password Yes
Workstations allowed myWorkstationName
Last logon Never
Logon hours allowed All
Local Group Memberships
Global Group memberships *Computers_local_admins *Domain Users
*other group x
The command completed successfully.
If Workstations allowed is missing, then you get above error.
If you click “Get Started with Grafana”, from your grafana.net page, you will see a list of local agent you can install to collect metrics (data) from your system. Click on Windows exporter and Next.
After you have configure the windows agent, as below, you can go back to this page and click “Test integration and finish installation”.
There is a default agent-config.yaml file created, where you need to add your url and username to make the agent ship data to the grafana cloud.
You get your Password (API key) on your host page – go to your name under grafana cloud, and then click on prometheus details to get the key and urls. Click on grafana details to go to your cloud dashboard.
You need to copy the following values, and place in your yaml file. Remote Write Endpoint (Use this URL to send Prometheus metrics to Grafana Cloud.) Username / Instance ID (Your Grafana Cloud Prometheus username.) Password / API Key (Your Grafana Cloud API Key. Be sure to grant the key a role with metrics push privileges.)
Open C:\Program Files\Grafana Agent\agent-config.yaml in notepad++ on your computer.
You need to add the lines remote_write (very important that every line is indent with two spaces)
- url: https://prometheus-blocks-prod-us-central1.grafana.net/api/prom/push
username: (the user number from your account)
password: (the long password from your account)
In YAML file is important to indent the text correct, and the order of the lines, have a meaning. Above setup worked for me, to send data to the grafana cloud. You may find other configurations, also work well.
Then go to your grafana.net page, and select “integration – Windows Exporter” dashboard.
After installation, the Agent config is stored in C:\Program Files\Grafana Agent\agent-config.yaml. Anytime the config file is modified, run the following to restart the Windows Agent so it can pick up changes:
by Roger·Comments Off on Install BigFix client on Windows
Microsoft Windows 2012
How install the Big Fix client/agent on the Windows server?
On the ILMT linux server you can search for the client files with find . -name ClientMSI*
Copy the files you need over to your Windows server
Copy BigFixAgent.msi setup, its .mst files and the actionsite.afxm masthead file to a folder of your target computer, for instance C:\install\bigfix. Actionsite.afxm file is in the /var/opt/BESInstallers/Client folder of the Linux server.