Windows Server 2016: Settings -> Accounts crashes
On a Windows server 2016 we recently installed, whenever ANY user goes to Settings -> Accounts, it starts loading and crashes. The event log shows an error every time (see below). All users are local and the system is not in a domain. We have tried several things to resolve it, but the issue persists. Some things we have tried: creating a new user and testing it on there system file check (sfc /scannow) Windows trouble shooter (as well as the downloadable Windows update troubleshooter) reinstalling the Settings app (Get-AppXPackage | foreach {Add-AppxPackage -DisableDevelopmentMode - Register "$($_.InstallLocation) \AppXManifest.xml"}) Event viewer error log: Faulting application name: SystemSettings.exe, version: 10.0.14393.82, time stamp: 0x57a55dc6 Faulting module name: usercpl.dll, version: 10.0.14393.2608, time stamp: 0x5bd1347f Exception code: 0xc0000005 Fault offset: 0x000000000000d297 Faulting process id: 0xb80 Faulting application start time: 0x01d5a36c63ad0ee2 Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe Faulting module path: C:\Windows\System32\usercpl.dll Report Id: dbe77bad-e235-499e-b0c2-13956fa9c637 Faulting package full name: windows.immersivecontrolpanel_6.2.0.0_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: microsoft.windows.immersivecontrolpanelWindows Server 2022 as Domain and DHCP Server
Hi, Windows Server 2022 announced. There are many IT Executives or Organizations who use Windows Server only for DNS Server, DHCP Server, managing network resources and implementing group policies. For this purpose, if we compare Windows Server 2012R2, Windows Server 2016, Windows Server 2019 and Windows Server 2022; can we find any differences? Moreover, for those executives or organizations, does it matter Windows Server 2022 announced? Please let us know differences in Windows Server from above perspectives. With Regards NndnG
Cannot configure RD Licensing
I've got a Windows Server 2016 at my office. I've got around 10 workers who need to access my server through a RDP access. I have no domain : got just the server and my workers respective computers at their place. After much research, I understood that Microsoft only allows 2 users to connect through RDP simulataneously and thus, I'll need to buy CAL licences. I then bought 10 CAL licences per user. I called Microsoft and they activated it by telephone. Now, it seems that there is something need to be configured and I can't get it š Let me say what I've understood so far : 1. I'll have to configure "RD Licencing". 2. I did install the concerned roles but when I open Server Manager > Remote Desktop Services > Overview, it says the following : What should I do ? Do I have to add the Server on a domain ? If yes, what does that change for me? What will happen to the current admin account on my server ? It is a local account. Will that change ? Please help me š
Remote App strange behavior with saved credentials
This problem has confused me for awhile now, and I haven't been able to find any solution. I'm not sure if this is an issue with the mstsc.exe on the client, or if it's an issues server side at this point. The bottom line issue, is that the "Remember me" checkbox for the remote app credentials will stop showing up, preventing the user from saving his or her credentials for the remote app connection. So, here's the scenario. I have a Windows Server 2016 environment, with it's own domain that provides access to applications to remote clients via Remote App services. Joining the clients to the domain isn't an option. We have a publicly trusted certificate deployed in our Remote App servers. When we setup a client machine, we do so through the Remote App and Desktop Connections control panel app, and enter the RDweb url. The client machines are a mix of Windows 7 machines to Windows 10. When we give the users their credentials, it's always in the format of <username>@<domain name> not <domain name>\<username> When we initially setup the client machine, usually the user will save his credentials. Which is fine. However, when their password expires, or when they want to change it through the web interface, things get weird. When everything is working fine, in the windows credential manager there are two entries, both in the Windows Credentials section. 1) <public FQDN of remote app collection> with the username in the format of <username>@domainname> 2) TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> When the users change their passwords via the RDWeb portal page, obviously it doesn't update their saved credentials. The expectation would be that the remote desktop client would prompt them for their new password, with the option to save it, as how it was when it was originally setup. And this is what happens, some times. They get prompted for their password, with a screen that shows them their username in the <domain>\<username> format, with the remember me box. Eventually though, it will break. And this is 100% repeatable by changing the password on the AD side, and trying to conenct again from the client. At some point, one of those times they change their password, they will be prompted for their new password with a credential screen with no remember me box. When it does this. if you look in the credential manager, there will be 3 entries. Windows Credentials: TERMSRV/<RDSessionHost FQDN> with username in <domain name>\<username> format TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> Generic Credentials: TERMSRV/<public FQDN of remote app collection> with username in <domain name>\<username> format After this happens, the users will never get the remember me box again, unless they completely delete the session from their control panel, and re-add it. Manually fixing the credentials in the credential manager to make them match how they were when it was working fine works temporarily, but will break again next time they reboot their computer, or the session disconnects from the servers. Iām not sure what to do with this next. If anyone has any ideas, it'd be greatly appriciated.
