Forum Widgets
Latest Discussions
Getting Prompted for Username and Password on Internal Web Site, HTTP Error 401.2 - Unauthorized.
I have an internal web site that uses Windows Authentication. This works perfectly on my Microsoft Windows Server 2022 Datacenter Azure Edition which is my developer server. When I tried to put this site out on our test Microsoft Windows Server 2022 Datacenter Azure Edition, with the exact same setup, I get prompted for my Username and Password. It does not matter what I have tried to enter for Username and Password, nothing is ever accepted and it I hit cancel, I get the dreaded HTTP Error 401.2 - Unauthorized. I don't understand why this would work on 1 server, but not the other server. HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.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-Version attribute of the Partitions container to 7 will not work. https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/lds-service-startup-fails. 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=7 in the /answer: file and pass it to adaminstall.exe, the installation fails without any errors. Notably, any ConfigurationSetLevel from 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 I can upgrade before shelling out a couple hundred euros on a license. Any suggestions what to do? Regards, Justus WingertTrouble Setting Up Windows Server on My New Aura Edition AI PC
Hey everyone, I recently got an Aura Edition https://www.lenovo.com/ca/en/lenovoauraedition/, 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, CharlieHow 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.
ntel Ethernet controller(3) I 225V issue
Hello, I was having 2019 standard server, running, Added one SSD and Installed fresh new standard 2022 server. After installation, drivers are missing so exported from running 2019 server. All drivers are installed except one Network card. This card is Intel Ethernet controller(3) I 225V.. I tried all possible but did not find any luck. This 2022 server is not yet keyed, but I guess its good for next 180 days. what could be reason ? Any help ?Microsoft RD client Android app url scheme is not working
I've been using a legacy URL scheme in my Android app to open the RD Client app via a deep link and initiate an automatic connection with a remote server. It used to work fine, but now it's no longer functioning. Is there a change in the URL scheme that hasn't been documented, or perhaps an update that affects this functionality? Can someone guide me on this issue?
