Important
To filter the blog, please use theses tag:
General news.
Website related post
website.
parental-control about technology.
technology post.
Note
All blog links are archived here.
Hi everyone
I seen an interesting bug yesterday, it was about Windows Server 2019 and a error when you try to rename a new domain controller to the old name of a retiered's one;
The error Windows was giving was:
The account already exists.
The culprit into that case was a left over that was visible in ADSI Edit. The exact location was;
Configuration -> CN=Sites -> CN=Default-First-Site-Name -> CN=Servers -> CN={Old Domain Controller}.
As simple as that, but it need a bit of playing in ADSI Edit :)
Hi everyone
If you stumble into the Windows Update error 80243004 please know there is an easy way to resolve it.

The bug is related to missing icon in the systray, so we go check there, we right-click the systray and click property;

We click personnalize;

On that windows we click to show all icon in the systray.

After that the Windows Update should work correctly :)
Hi sysadmin !
Today I wanted to share a small bug I encountered, and how to solve it.
After all the update, if you lost all your network connection, and in your device manager they are all yellow in error, please check the status of them;
Network Adaptor error: Windows is still setting up the class configuration for this device. (Code 56)

If that happen to you, any new devices you will try to install will fall into the same state.
The Windows update will try to reinstall the driver, but will fail.
The recovery step is easy, check your VPN software installed, one is not Windows Ready for that build.
In my case it was CheckPoint VPN
Uninstall and the bug disappear live, no reboot necessary !
In Windows Server 2019, if you ever find yourself hit by a bug when you try to add the rds-web-access, then please follow these step;
Problem
In the eventlog
Install-WindowsFeature RDS-Web-Access -IncludeAllSubFeature
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
Exception
+ FullyQualifiedErrorId : DISMAPIError\_Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
Step tried
Issue
A previous installation of IIS is the culprit
Solution
Removing IIS:

After that; then you migh have to remove the IIS directory completly;
netsh http show urlacl
netsh http delete urlacl http://+:80/ netsh http delete urlacl https://+:443/
Today I will share a small tip if your Windows VM get an Unknown state in your ESX.

The problem can be easily fixed by first removing the machine from the inventory, without deleting the files.

After that you will have to go back into your datastore to re-add the machine back to the inventory, by right-clicking the .VMX file, and select the Add to Inventory option.

After that the state will be green :)