Forum Widgets
Latest Discussions
When is Network Profile Issue for Domain Controllers going to be at least acknowledged?
Since the insider builds from 25398 to the latest 26227 all have the same bug where the domain controller on the builds will show the network category as Public instead of DomainAuthenticated and the only way to fix it is to disable and re-enable the NIC after each reboot. There has been a few bug reports submitted in the feedback hub and in this community many months ago. It would be at least be nice to be acknowledged.CWooldridgeFeb 10, 2025Copper Contributor2.3KViews1like23CommentsServer 2025 Domain Join Error ASN.1
hallo we wanna join an appliance (cisco ISE) to our domain/forest and get an error. Domain Controllers was updated from Server 2022 to Server 2025 preview it was ok with the appliance in ad. With Server 2025 final we get this error: Test Name :Kerberos test obtaining join point TGT Description :Tests TGT Obtaining in joint point Instance :CCLOUD-AD Status :Failed Start Time :10:13:54 22.11.2024 MET End Time :10:13:54 22.11.2024 MET Duration :<1 sec Result and Remedy... Could not obtain TGT : ASN.1 failed call to system time library. Check Kerberos related AD configuration What we done in troubleshooting, yet: DNS Resoluion works. domain is resolvable NTP is ok and correct time from pdc and synced to all other DCs and Clients/Servers domain join user credentials and permission are correct We tested also with an Domain Admin User/Cred Container/OU and Computer Object Permissions/Owner rights are set to the join account. Delete and let the Appliance create a new Object did not work can anyone help with ideas?JoeSchmiCCFeb 10, 2025Copper Contributor647Views2likes6CommentsRAM Memory Leak Issue
Good morning. I am experiencing issues with an updated installation of Windows Server 2016. The task manager reports 8.1GB of memory used (which normally tends to grow indefinitely), and I can't figure out what is using this memory. The growth is about 1GB per day. However, no processes appear that justify the 8GB of RAM used. Even using RAMMAP, I can't find anything significant... On the server, additionally, we have SentinelOne as antivirus and Apache-Tomcat. Thank you for your help.Solvedandrea_rinaldiFeb 09, 2025Copper Contributor40Views0likes2CommentsServer 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
OS: Windows Server 20225 Standard Core (no GUI), build 26085.1 Role: ADDS, DNS ForestMode: Windows2025Forest DomainMode: Windows2025Domain Platform: Hyper-V guest When standing up a clean Windows Server 2025 using server core and configuring it as a domain controller, the network category (profile) always shows as "public." A clean load of Windows Server 2022 with server core as a domain controller has the same behavior. However, in Server 2022, the fix is to add DNS as a required service to the nlasvc (Network Location Awareness) service. Once that is done, the network category reflects "DomainAuthenticed" and persists between reboots. In Server 2025, the nlasvc service does not have the same requiredservices as Windows Server 2022, and it does not start automatically. Even after configuring the nlasvc service the same way it is in Server 2022 and adding DNS as a required service, the network category still reflects "public." The only way to get the network category to properly reflect the "DomainAuthenticated" status is to disable and reenable the network adapter after each reboot.8.3KViews10likes50CommentsWindows Server on ARM (Insider Previews) availability
Last year it appears around 3 preview versions of Windows Server on ARM architecture were released to the insider community - possibly one may have been bundled inside a Windows 10 Insider download. Does anyone retain a copy of those ISOs and would you be willing to share for testing purposes? And what is the current status of this project?giliusFeb 07, 2025Copper Contributor15KViews0likes4CommentsI can't Turn on network discovery
Hi Why in Advanced sharing settinggs the Turn on network discovery can't save the settings in Windows Server 2019 Preview? Although as an admin I turn it on and save settings, it's again off when I open Advanced sharing settinggs. The second problem is that when I click Choose media streaming optons, I get the message The page failed to load.Kari KaipainenFeb 05, 2025Copper Contributor205KViews1like21CommentsExtending AGPM support for Windows Server 2025
Does Microsoft have any plans for extending AGPM to Windows Server 2025 or creating a new GPO management and approval system? GPOs are still the best solution for Windows Server, and now even Linux distributions are adding GPO support.136Views1like1CommentWS2025 Preview (26100.1) fails to boot after joining WS2016 forest
I installed WS2025 Preview (Datacenter, 26100.1) in a virtual machine and after joining the domain, the box is rendered unbootable (boot loops). I can reinstall and do other tasks as a standalone server with no problem but joining the domain immediately bricks the VM, 100% of the time. The forest is running at functional level WS2016. I disabled all GPs and verified with gpresult they are not applied. Safe mode boots if you need me to poke around. Am working to get a kernel debugger attached. No memory dump is generated and disabling reboot on errors yields nothing.WithinRafaelJan 27, 2025Copper Contributor1.2KViews1like10CommentsProblems to join Debian/Ubuntu machines to a domain
Is not posible to join Debian/Ubuntu machines to a domain based on Windows Server 2025 (using realm at least) this is the error: ! Couldn't set password for computer account: XXXX$: Message stream modified adcli: joining domain xxxx.local failed: Couldn't set password for computer account: XXXX$: Message stream modified ! Failed to join the domain realm: Couldn't join realm: Failed to join the domain Domain is discoverable vía realm: root@lnms01:/home/administrator# realm discover xxxx.local xxxx.local type: kerberos realm-name: XXXX.LOCAL domain-name: xxxx.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss Tested on WS2025 build 26227 and Linux 6.1.0-21-amd64 x86_64, Linux 6.6.31+rpt-rpi-v8 aarch64 and Linux 6.8.0-31-generic x86_64. Those 3 versions of Linux joined to another doman based con Windows Server 2022 without issues.ejc2_Jan 26, 2025Copper Contributor2.9KViews0likes6Comments- bruno85Jan 25, 2025Copper Contributor89Views4likes1Comment
Resources
Tags
- General343 Topics
- New Build121 Topics
- management111 Topics
- Hyper-V72 Topics
- Networking60 Topics
- Developer Platform58 Topics
- security54 Topics
- containers45 Topics
- storage43 Topics
- @Windows Server37 Topics