In these cases, Process Monitor can help us identify the settings in use so that we can manage them centrally. While there are sometimes Group Policy Objects and Intune settings that can help us with setting up the user interface in this way, these settings can be unsuitable or difficult to find. In end-user computing, we are often asked to make specific parts of the UI look a particular way for our users. It does require administrative rights to run.Īs a quick and straightforward example, I'm going to show how I use Process Monitor to capture the settings that drive certain parts of the Windows user interface. You simply download the executable, then copy it to your target endpoint and run it directly. Any insight or ideas would be appreciated on how to speed up SAM or anything else that may be slowing down the initialization (to note after it boots up, it runs perfectly fine - RDP times out but everything else works).Process Monitor requires no installation. There's something that's slowing up the boot up/login process in 2019/2022 server with 50k+ local users which isn't happening in 2012R2. I've also trying sizing the hardware from 1GB to 16GB and more processors but it's made absolutely no difference. How do I get SAM to behave like 2012R2 in 2019/2022 servers? I tried tweaking the registry to disable the last username, allow for automatic login and the requirement for alt+ctl+del and it's no difference. So my question is how do disable any new features in SAM that's causing it to slow down? Someone suggested that SAM is trying to load all the profiles before login or trying to enumerate the profiles etc. I have no issues what so ever on the 2012R2 server, it complete boot up and login in about 2 minutes or less.
From the event logs I can gleam that SAM is causing the issues, (there's a 3-8 hour gap between the first SAM entry and the next one, which is nearly instantaneous on the 2012R2 server). I need to upgrade the server to 2019 or newer to use of some of the newer IIS features, however when I try to migrate (recreate) all the 50+ users to a 2019 or 2022 server the machine takes over 12 hours to complete boot up and login. It's not the best design but that's how it's been running without any issues on 2021R2.
Over time there are now 50k+ local users created on the machine. It's being used as a IIS web server and for authentication IIS is using windows integrated authentication and the users have been created as local users on the machine (it was the easiest solution at the time). I have 2021R2 server on AWS which has been running for almost a decade now.
0 kommentar(er)
