Windows 11

5 Topics

Windows 11 ADMX and mixed enviorement (win 10 and win 11)
Dear, I hope you are well, I still have the doubt if the windows 11 ADMX are already compatible with windows 10. I noticed that my power GPOs, administrator permissions and remote desktop enablement were not being applied on windows 11 computers but were on windows 10. I started reading and found that there were new ADMX for windows 11 but they were not backward compatible with windows 10 and this makes administration a nightmare. Finally this was solved? I can quietly apply the new templates for windows 11 without them not working for windows 10? I am afraid to make the change and generate chaos. I remain attentive, Greetings to all!
Solved
AptoSx4
Jun 03, 2024 Place Windows Server for IT Pro
2.6KViews
0likes
5Comments
Color Management is broken (GetICMProfile always returns WCS Default Device Profile)
Hi, It looks that color management logic is changed and many many graphics apps are not compatible with color management logic of Windows 11, Windows Server 2022, Windows Server vNext. There are quite a few references in internet: https://techcommunity.microsoft.com/t5/windows-11/windows-11-color-management-not-working-chrome-on-secondary/m-p/2869159 https://www.reddit.com/r/Windows11/comments/qg8dcg/for_those_of_you_going_crazy_over_icc_profiles/ https://community.adobe.com/t5/photoshop-ecosystem-discussions/color-management-not-working-with-photoshop-and-windows-11/m-p/12469301 https://www.eizoglobal.com/support/compatibility/software/win/windows11/ In shortGetICMProfile Win32 API method doesn't return the expected value anymore on mentioned systems. I'm quite surprised to see no comment from Microsoft as the color management is very important aspect of OS Functionality. It might be that Microsoft is deprecatingGetICMProfile in favor ofWcsGetDefaultColorProfile, but there are so many apps in the wild that already use old method, so I don't think it a wise decision and so far looks more like an issue that has not been noticed by Microsoft yet.
SergejKiller
Apr 14, 2024 Place Windows Server for IT Pro
937Views
0likes
1Comment
Windows 11 clients cannot authenticate to NPS server using computer authentication
We have a Windows server 2019 datacenter server running NPS. Our WiFi Office clients authenticate to this server for access to the corporate WiFi network. We use computer authentication, so members of the "domain computers" group are allowed access in the policy (we only want domain computers on this network and we don't want users to need to enter their user credentials). We use GPO to provision a WiFi profile to the domain computers, in which we configure that computer authentication is needed. Our Windows 10 clients (literally all of them) are connecting nicely (I have anonimized the event log for security purposes: Network Policy Server granted access to a user. User: Security ID: DOMAIN\COMPUTER$ Account Name: host/COMPUTER.domain.nl Account Domain: DOMAIN Fully Qualified Account Name: DOMAIN\COMPUTER$ Client Machine: Security ID: NULL SID Account Name: - Fully Qualified Account Name: - Called Station Identifier: xx-xx-xx-xx-xx-xx:SSID Calling Station Identifier: XX-XX-XX-XX-XX-XX NAS: NAS IPv4 Address: x.x.x.x NAS IPv6 Address: - NAS Identifier: AP01 NAS Port-Type: Wireless - IEEE 802.11 NAS Port: 1 RADIUS Client: Client Friendly Name: SonicPoint HQ 1 Client IP Address: x.x.x.x Authentication Details: Connection Request Policy Name: NAP 802.1X (Wireless) Network Policy Name: NAP 802.1X (Wireless) Non NAP-Capable Authentication Provider: Windows Authentication Server: NPS.DOMAIN.nl Authentication Type: PEAP EAP Type: Microsoft: Secured password (EAP-MSCHAP v2) Account Session Identifier: "edited" Logging Results: Accounting information was written to the local log file. When a Windows 11 client (all of them actually) tries to connect, we see the following logged (again, anonimized): Network Policy Server denied access to a user. Contact the Network Policy Server administrator for more information. User: Security ID: NULL SID Account Name: host/COMPUTER.domain.nl Account Domain: DOMAIN Fully Qualified Account Name: DOMAIN\COMPUTER$ Client Machine: Security ID: NULL SID Account Name: - Fully Qualified Account Name: - Called Station Identifier: XX-XX-XX-XX-XX-XX:SSID Calling Station Identifier: XX-XX-XX-XX-XX-XX NAS: NAS IPv4 Address: x.x.x.x NAS IPv6 Address: - NAS Identifier: AP01 NAS Port-Type: Wireless - IEEE 802.11 NAS Port: 1 RADIUS Client: Client Friendly Name: SonicPoint HQ 1 Client IP Address: x.x.x.x Authentication Details: Connection Request Policy Name: NAP 802.1X (Wireless) Network Policy Name: - Authentication Provider: Windows Authentication Server: NPS.domain.nl Authentication Type: PEAP EAP Type: - Account Session Identifier: "edited" Logging Results: Accounting information was written to the local log file. Reason Code: 16 Reason: Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect. The only real difference I see is that for the Windows 11 client, NULL SID is provided as "Security ID". Could it be that this is causing NPS to not be able to verify that the machine that is attempting to connect is a member of the security group which is allowed to connect (the default group "Domain Computers")? Looking forward to either a quick bug fix or a configuration change I need to make. Maybe other Windows Server admins are also experiencing this issue?
Solved
PaulvDam
Nov 13, 2023 Place Windows Server for IT Pro
151KViews
2likes
18Comments
Remote desktop users do not allow reconnection
Hello everyone, Last week we started having problems with our user's sessions to the remote desktop, investigating we found the issue was "supposedly" an error from Microsoft with an update, then we found some patches that supposedly fixed it, however we still have cases of users despite having the patch installed are able to connect to the remote desktop but if for some reason they disconnect, they can not reconnect, they simply receive an error message regarding the password. If they wait a few minutes (more than 15 minutes) and try again, then possibly they can connect again.Another option is rebooting the workstations they are connected to and when they reconnect they do so without any problems. We have followed up on the whole process and our DNS is fine, our Gateway is fine, so we have no idea where else to look. By the way for our login validation process we use DUO Two Factor Authentication. Any ideas? Patches: KB5020387: Windows 11 21H2 KB5020435: Windows 10 22H2 KB5020435: Windows 10 20H2 – 21H2 Thank you in advance,
ADumith
Oct 27, 2022 Place Windows Server for IT Pro
995Views
0likes
0Comments
Windows Server Essentials 2016 Client Backup on Windows 11 Pro unusably slow
I have just upgraded one machine to Windows 11 and everything appears to be working fine (a few tweaks needed for networking printing and some software updates). For WSE2016, I had to uninstall/reinstall the Windows Server Essentials 2016 Client Connector for it to connect correctly to the server - but everything seem OK with the ability to configure the backup working fine (a useful test of proper connectivity of the client to the server). HOWEVER, now I have started a client backup it has currently taken around 16 hours to backup to currently get to less than 40% complete. Previously the (incremental) client backups take minutes and they continue to work fine on my other machines, running Windows 10 Pro 21H2. All machines connected via Gbit wired network. Has anyone else tested WSE2016 Client Backup on Windows 11? Have you seen the same issue? How do we report this to Microsoft - I am reporting through Insider Feedback, but suspect the WSE2016 client may need updates, so want to make sure that the "bug" gets to the WSE2016 team as well, whilst it is still formally supported (End of Life being 11 January 2022). The PC is an Asus ROG Maximus XI Hero (WiFi) with Intel Ethernet adapter running Intel's latest driver (26.4) so I am also waiting for Intel to release updates with specific Windows 11 support, and for the first round for updates for WIndows 11 expected on 12 October.
TheAndyMac
Oct 06, 2021 Place Windows Server for IT Pro
2.1KViews
0likes
0Comments