SHIFT-WIKI - Sjoerd Hooft's InFormation Technology
This WIKI is my personal documentation blog. Please enjoy it and feel free to reach out through blue sky if you have a question, remark, improvement or observation. See below for the latest additions, or use the search or tags to browse for content.
Creating a ScreenSaver Policy with a GPO
Summary: How to disable your screensaver using a gpo.
Date: Around 2008
Refactor: 31 December 2024: Checked links and formatting.
Fix: Windows Terminal Server License Errors
Summary: A fix for Terminal Server error 2056
Date: Around 2014
Refactor: 31 December 2024: Checked links and formatting.
If you receive any of these messages:
RDP Disconnected! Error Code: 2056 Any License error regarding Windows Terminal Server
You can always try to delete the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
You can delete the complete key or just the content of the subkey “Store”.
Afterwards you'll have to start the rdp client as an administrator to recreate these keys.
Fix: Vmware Update Manager Unknown Error
Summary: A possible cause for a failed ESX 4 to ESX 4.1 upgrade.
Date: Around 2011
Refactor: 2 January 2025: Checked links and formatting.
During the upgrade from one of our hosts from 4.0 to 4.1 we experienced that the host would hang during the upgrade process, at exactly 33%. The first time I was impatient and restarted vcenter, the host and tried again. That time I decided to wait. After more than an hour it failed with this error:
VMware vCenter Update Manager had an unknown error. Check the Tasks and Events tab and log files for details.
Also, when looking at the host in the esxupdate log (/var/log/vmware/esxupdate.log) I saw these errors:
[2011-03-03 22:56:14] DEBUG: cos.rpm: error: rpmdbNextIterator: skipping h# 2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038) [2011-03-03 22:56:14] DEBUG: cos.rpm: error: rpmdbNextIterator: skipping h# 2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038) [2011-03-03 22:56:14] DEBUG: cos.rpm: error: rpmdbNextIterator: skipping h# 2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038) [2011-03-03 22:56:14] DEBUG: cos.rpm: error: rpmdbNextIterator: skipping h# 2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038) [2011-03-03 22:56:14] DEBUG: cos.rpm: error: rpmdbNextIterator: skipping h# 2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)
Fix: VM gets Network Disconnected After vMotion
Summary: A possible cause for a disconnected VM after a vMotion
Date: Around 2014
Refactor: 26 January 2025: Checked links and formatting.
Symptom: after a vMotion the network card gets disconnected, and even when the box is checked, still the VM is not getting connected.
Issue: The vSwitch gets created with 120 ports by default, if the number of VMs/NICs goes over this there are no ports left. This is not checked by vMotion/DRS/HA so no warnings will be displayed. To solve it, vMotion the VMs back, change the number of ports of the vSwitch and reboot the host.