Forum Widgets
Latest Discussions
Windows Server 2016/2019 AD LDS installation with a specific configuration set level
With the release of Windows Server 2025, AD LDS configuration sets are required to have a functional level of Windows Server 2016 or greater. Unfortunately, there is no documentation on how to create a configuration set on Server 2016/2019 with a specific level or how to raise the level of an existing set. The only article with relevant information says that manually updating the msDS-Behavior-Versionattribute of the Partitions container to7 will not work.LDS service startup fails - Windows Server | Microsoft Learn. If I execute the C:\windows\adam\adaminstall.exe /?:answer command, I see that a parameter named /ConfigurationSetLevel exists and its default value is 7, However, when I create a new AD LDS configuration set via the wizard, it is created at the level of 2 by default. If I specify ConfigurationSetLevel=7in the /answer: file and pass it to adaminstall.exe, the installation fails without any errors. Notably, any ConfigurationSetLevelfrom 2 to 5 works fine using this method. It seems that it is impossible to create an AD LDS configuration set on Server 2016/2019 and add a replica from Server 2025 to it. Is this correct?
New user and roaming profile
Hi I added a new user to domain controller and I also added a profile path (roaming profile). I went to client computer and tried to login the new user, after logging in it is saysing that the profile was not successful and need to logout amd try again. It is doing this over and over again until I delete the path from the user in domain controller then I can login the user to the machine. After successful login I can put back the profile path in domain controller and when I try to login the user again it is working fine. How to solve this issue?
Upgrading a Server 2012 R2 to 2025
Hi everyone, sadly I was unable to locate any kind of search feature so I apologize in advance for potentially repeating this question. I have an old VM with Server 2012 R2 with a self contained AD, DNS and a connected OneIdentity Manager. I want to upgrade that system to something modern. Since Server 2025 advertises a migration path from 2012 R2 I thought that would be easy to do, but I can't even find any place to get an ISO to upgrade. Naturally I'd like to verify if Ican upgrade before shelling out a couple hundred euros on a license. Any suggestions what to do? Regards, Justus Wingert
Unable tocast COM object to interface type 'System.EnterpriseServices.IRemoteDispatcher
When moving a Cluster Role, I get the error: System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'System.EnterpriseServices.IRemoteDispatch' I have a Windows Failover Cluster on two nodes with Windows Server 2019: I have the Windows Service "FTS MasterConsole Online CY" as a Cluster Resource. This service, calls upon start the COM+ method FTS.DataAccess.CORE.UserAccess.LogonU.Logon: oUA = New DataAccess.CORE.UserAccess.LogonU WriteLog("Form1_Load Logon begin") dsUserInfo = oUA.Logon(UserName, curIPAdd.ToString, False, True) The LogonU class is in the COM+ application FTS and implements the IRemoteDispatch interface: When I move the Cluster Role to the other node and the COM+ process (dllhost.exe) of the FTS Application is not running on the other node, the move succeeds. It correctly starts the COM+ process on the other node. However when the COM+ process (dllhost.exe) of the FTS Application is running on the other node, the move fails with the following error in the EventViewer: WinServiceOnline System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'System.EnterpriseServices.IRemoteDispatch'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6619A740-8154-43BE-A186-0319578E02DB}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). at System.EnterpriseServices.RemoteServicedComponentProxy.Invoke(IMessage reqMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at FTS.DataAccess.CORE.UserAccess.LogonU.Logon(String Username, String IPAddress, Boolean chckAlreadyLoggedOn, Boolean blnUpdateUserLoginInfo) at FTS.Services.WindowsServices.CORE.MasterConsoleServer.WCFService.LogOn() at FTS.Services.WindowsServices.CORE.MasterConsoleServer.WCFService.Init() at FTS.Services.WindowsServices.CORE.MasterConsoleServer.WinService.StartMC() Additional Info: MachineName: ABCYFTS201T TimeStamp: 21/10/2024 3:13:12 μ.μ. FullName: FTS.Common.Libraries.CORE.ExceptionHandling, Version=2.0.0.0, Culture=neutral, PublicKeyToken=951855d69736a7a2 WindowsIdentity: ALPHABANK\zzbmastercom Do you have an idea, why this happens? The Windows Service, as well as the COM+ component are written in VB.NET 4.7.Trouble Setting Up Windows Server on My New Aura Edition AI PC
Hey everyone, I recently got an Aura Edition AI PC, and I’m super excited about the AI features. However, I’m running into issues trying to set up Windows Server on it. The installation isn’t going as smoothly as I expected. Also, I’m wondering if the AI hardware or features could be causing conflicts with the setup. Has anyone else set up Windows Server on a similar AI-powered PC? I’d appreciate any tips or advice on what to look out for or how to optimize the configuration. Regards, CharlieWindows 2022 Server RDS - TaskBar Laggy/Slow/Freeze frequently
Windows 2022 Remote desktop servers taskbar freezing in RDP users We are finding the task bar in all sessions (including admin/local) suffer from a delay of 30-45 seconds (varies) when trying to click on the taskbar i.e. to change applications or right click for task manager.issues with the task bar/random task bar freezing on Windows Server 2022 RDS Once the taskbar has focus its responsive as usual, but once it loses focus i.e. you click back into your application, when you try to click on the task bar its delayed to respond again. This is happening on both our 2022 RDS servers - clean boot doesn't resolve the issue, they are fully patched to date. Troubleshotting steps: -Restart the “Explorer” process -recreate user profile in RDP -update the latest windows patch -Run sfc/scannow -Disable programs on the Startup tab If you know anyone please give a solution/feedback.
How to downgrade Windows Server 2019 Datacenter Evaluation to Windows Server 2019 Standard
I have a Windows Server 2019 standard license. However, I accidentally installed Windows Server 2019 Datacenter Evaluation, so I want to downgrade back to Windows Server 2019 Standard. Please help me. Thank you.
Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long.
I am moving a web site from Windows Server 2012 to Windows Server 2022. When I open my web site, I receive the error message:Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. When I inspected the headers, they were only 640 characters long. I have cleared my cache and flushed DNS to no avail. This error doesn't happen all the time, just sporadically. How do I fix this so that it doesn't happen.
StrictTimeWaitSeqCheck setting on Windows Server 2016
I would like to know if StrictTimeWaitSeqCheck needs to be set to 1 for TcpTimedWaitDelay value as mentioned in https://support.solarwinds.com/SuccessCenter/s/article/Tweaking-Windows-Server-performance-to-prevent-port-exhaustion-when-using-Orion-modules?language=en_US
