Running portainer agent on Synology NAS.

If you want to manage Docker on your Synology NAS, from a Portainer instance running somewhere else, you need to deploy the Portainer agent on your Synology NAS.

The installation guideline for running the agent on a standalone Docker host, can be found at portainer.io.

A small correction is needed, as at the Synology DSM, Docker directories are not located at /var/lib/docker, but at /volumeX/@docker.

Continue reading “Running portainer agent on Synology NAS.”

Exchange 2010 – Modify a Database Size Limit

To change the database size limit for a specific database, do the following:

  1. Dismount the database
  2. Run regedit and go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\\Private-Database-GUID
  3. If the Database Size Limit in GB DWORD exists for the subkey, change its value to the desired size in gigabytes.
  4. If the Database Size Limit in GB DWORD doesn’t exist for the subkey, create a new DWORD with that name, and then set its value to the desired size in gigabytes.
  5. Mount the database.

Continue reading “Exchange 2010 – Modify a Database Size Limit”

Citrix Licensing Service crasher

If your Citrix Licensing Service keeps crash every time you try to start it and something like this is in your application eventlog:

Faulting application name: lmadmin.exe, version: 11.9.0.0, time stamp: 0x4d6bbff6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x5d8
Faulting application start time: 0x01ce1b1c6f2579d4
Faulting application path: C:\program files (x86)\citrix\Licensing\LS\lmadmin.exe
Faulting module path: unknown
Report Id: bb0c086a-870f-11e2-a0c7-001cc47ba50e

Go to the folder:

C:\Program Files (x86)\Citrix\Licensing\LS\conf

And delete or rename the files ”activation_state.xml” og ”concurrent_state.xml”. Then restart the Citrix Licensing Service and the files will be recreated automatically.

Eventid 1116 – Printer auto-creation failure. Reason: AddPrinter() failed with status 0x706

If you get errors  in the application eventlog with ID 1116 — Printer auto-creation failure. Reason: AddPrinter() failed with status 0x706, it’s because the print processor is missing for some reason, in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Print Processors\

In my case it was the “Citrix Print Processor” that was missing. The key has to be created manually and has to contain a string named “Driver” and the value has to be the name of the .dll, in this case “cpproc.dll“, as you can see in my example below

Citrix Print ProcessorIf it’s HP, Minolta or anything else, the name and value can be different. Compare it with a working server, to get the correct result. After creating the registry-key, the Print Spooler Service has to be restarted.

Selecting a SSL certificate in a Server 2012 RDS-Farm

In Server 2012, you could select the SSL sertificate for the RDS server in the RDP-TCP properties. These have been removed in Server 2012.

Run the following command in an elevated cmd on every server in your RDS-farm:

wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TSGeneralSetting Set SSLCertificateSHA1Hash="Thumbprint"

Where “Thumbprint” is the thumbprint of your SSL certificate, without the spaces. If you’re using a self-signed certificate, remember it must be imported on each server first.