Microsoft Lingering Object Liquidator (LoL) "Failed to create event log subscription to target DC".

I am trying to run the Lignering Object Liquidator (LoL) on my Domain Controllers. But some DC's are Server Core and don't have .Net installed. So I have to run it on a DC with a GUI and connect to the DC with server core.

But then I found this error message: "Failed to create event log subscription to target DC".

win rmquickonfig

reports WinRM is already set up for remote management on this computer.

So I tried turning off the firewall altogether:-

Set-NetFirewallProfile -Profile Domain,Public,Private - Enabled True

And run the LOL again.  That worked!

Of course don't forget to turn the firewall back on again immediately afterwards.


Comments

Post a Comment

Popular posts from this blog

Server Manager will not start, error .NET Framework: "This application requires one of the following versions of the .NET Framework:"

Server Manager will not start on Windows Server 2019 after installing ADConnect. Error ServerManager.exe: This application could not be started. .NET Framework: "This application requires one of the following versions of the .NET Framework:xxxxx Do you want to install .NET framework now?" Of course it's already installed automatically on the server, so if you try and install it again you can't, error "already installed". Try the .NET repair package, can't repair the install. Try dsim.exe to install the package, error "Microsoft .NET Framework is already part of this installation". .NET Runtime version : 4.0.30319.0 - This application could not be started.This application requires one of the following versions of the .NET Framework:  v4.0.30319 The answer is to re-create the registry entries deleted when you installed ADConnect:- [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "AspNetEnforceViewStateMac"=dw...
Read more

Start virtualised domain controller in DSRM (Active Directory Restore Mode).

If you have a totally virtualised Active Directory infrastructure in Hyper-V, you can't boot the VM into  Directory Services Restore Mode  using F8. The keypress is not recognised. To get around this, in a elevated command prompt, type: bcdedit /set {globalsettings} advancedoptions true Now when you reboot the DC, it will ask if you want to boot into restore mode, and you can restore A.D. After rebooting, type the command: bcdedit /set {globalsettings} advancedoptions false and it will boot normally again. Now you have to find the restore mode password....
Read more