Microsoft Windows 10

How stop virtual box vms from command line before computer shutdown?

Suggestion: (this may not work)

Create text files in a c:\scripts folder with the command you need to start and stop vms.
Important: that case of the vms name matched the name you have given them inside Virtualbox.

Create a CMD file with following command:

rem stop one virtualbox image
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list runningvms

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "win2012big" acpipowerbutton
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "Win2016 CAPA" acpipowerbutton

Add the file to group policy on the computer:

  1. In a command window, open the Group Policy Editor (GPE) by running gpedit.msc.
  2. Expand Computer Configuration and select Windows Settings.
  3. Double-click Scripts (Startup/Shutdown).
  4. Click Add and add c:/scripts/vboxshutdown.cmd.

Add the start script (c:/scripts/vboxstart.cmd) to the Start properties.

Create a CMD file with following command to start:

rem start one virtualbox image
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" startvm "Win2016 CAPA"
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" startvm "Win2019"


You may need to use the Task Scheduler instead, to make it work.

Or try placing a shortcut of the script as a startup program in %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup.

Or place a shortcut to your start script in folder C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp – that make the script run when user login.


More Information:

Vboxmanage command not found in Windows CMD or PowerShell

Managing VirtualBox with PowerShell

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

User name Admindonald
Full Name Donald Duck admin
User's comment
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
Logon script
User profile
Home directory
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.

More Information:

Microsoft Windows Server
How configure the agent-config.yaml file to work?

The new windows agent for Grafana Cloud should make it easy to collect some metrics from your  computers to the dashboard in the cloud.

Sign up for a account at

Download the agent and install the agent from here

If you click “Get Started with Grafana”, from your 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:
      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 page, and select “integration – Windows Exporter” dashboard.

Monitoring Windows Services with Grafana, InfluxDB ‎and Telegraf

You will soon fill up your free account, so you must limit the services that is reported up to the cloud.

Add last to your agent-config.yaml file this lines, to limit the information collected:

 # List of collectors to enable
 enabled_collectors: "cpu,system,os,cs,time"

You can copy your text to a YAML checker:

Here is some information of possible values in the file:

cpu CPU usage
cpu_info CPU Information
cs “Computer System” metrics (system properties, num cpus/total memory)
net Network interface I/O
os OS metrics (memory, processes, users)
process Per-process metrics
remote_fx RemoteFX protocol (RDP) metrics
service Service state metrics
smtp IIS SMTP Server
system System calls

More Information:

For a full description of configuration options, see windows_exporter_config in the Grafana Agent documentation.

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:

sc stop "Grafana Agent" 
sc start "Grafana Agent" 

Windows Server Monitoring using Prometheus and WMI Exporter

Microsoft Windows 2019 server

Problem to connect to Remote Desktop from old laptop.


Newer Microsoft Windows server has the possible to harden the communication, to not use old security protocols, then it will not allow connections from Windows 2012 or Windows 7 computers.

Try to connect from a Windows 10 computer with the latest service packs.


More information:

Microsoft Windows 2019

Message when you try to add a schedule


On the local server use Local Security Policy manager:

  1. Click START and type secpol.msc then press Enter
  2. Expand Security Settings > Local Policies > User Rights Assignment node
  3. Double click Log on as a batch job
  4. Click the Add User or Group button and add your service account user
  5. Click OK

You should use a service account that is part of the administrator group, to ensure it have rights to do the task you have in your cmd script file.

More Information:

BigFix Client
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.

Then create a CMD file with following content:

msiexec.exe /i “BigFixAgent.msi” TRANSFORMS=”1033.mst” REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn

Start a DOS prompt as administrator and go to the \install\bigfix folder

Run your installagent.cmd file, to install.

If you run the BIGFIXAGENT.MSI it can look like this

You will have a new “BES Client” windows service on your computer after the installation.

You must copy the actionsite.afxm file to the folder C:\Program Files (x86)\BigFix Enterprise\BES Client to make the client start.

Client/Agent can be downloaded from

More information:


Microsoft Powershell

You are low on disk space, or the Cognos BI have created some large file (dump files or log files) and you want to know where they are.

Enter below text in notepad++ and save as checksize.ps1 in your c:\temp folder

$folder = “C:\Program Files\ibm\cognos”
Get-ChildItem $folder -recurse -ErrorAction SilentlyContinue |Sort-Object length -descending| Select-Object -first 27 @{Name=”MegaBytes”;Expression={“{0:F2}” -f ($_.length/1MB)}} , Fullname | Export-Csv c:\temp\LargeFiles_Report.csv

Start Powershell from Start menu
Go to temp folder with command cd /temp
Enter ./checksize.ps1 to run the script

Open the Largefile_report.csv in notepad++

You need to change the first line to your folder for Cognos products e.g. $folder = “D:\Program Files\ibm\cognos\analytics”

Then you check the list to find the files that you do not need, and can remove them, to get more space.

More Information: