security
57 TopicsUnable to download Windows 11 Client Arm64 Insider Preview Dev Channel Edition
Error We are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists you may contact page for assistance. Refer to message code 715-123130 and c21934f3-66c0-43e3-9e88-c5869adeae48. I am in the US and simply want to download this. Please provide a usable link without restrictions.9Views0likes0CommentsAAD join Server 2025
Hi, Wondering if Server 2025 can be AAD joined. this would help some businesses that have their laptops joined as well as would also like to have the option to join their Server for their line of business apps etc. Seems really strange you can have win11 AAD joined but not server 2025. Or am i just missing something here. Having to use Azure Arc comes with extra headaches and costs.Solved9.9KViews2likes15CommentsServer 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?4.1KViews2likes9CommentsProactive private share #microsoft
Many comapanies is part of my job last two year. I desade to implement and create new public communty group at microsoft, with public share. Like universal patch insade giant org and partner companes ,microsoft deside lead postiton. Proacticve and future plan is constructed to grow on world network with client and our partners109Views0likes2CommentsSMB over QUIC Roadmap
Hello everyone! I had seen somewhere back in October(?) 2022 that Microsoft plans to implement SMB over QUIC for Azure File Shares (without needing Windows Server 2022 (Azure edition). Is this part of the roadmap? I've also seen somewhere that there are plans to eventually make SMB over QUIC available for non-Azure editions of Windows Server 2022. Is this true as well? and if so, is there a roadmap to when this will be available in a Windows Server insiders build? Thank you!Solved4KViews1like4CommentsExtending 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.917Views2likes1CommentWindows Boot Manager not updated
KB5025885 outlines how to update Windows Boot Manager, but build 26257 still has a Windows Boot Manager that is signed with the old "PCA 2011" certificate. The manual processes in KB5025885 are a real pain (and don't scale) so it would be very annoying if this is not fixed before RTM. https://support.microsoft.com/en-us/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d1.4KViews1like10CommentsIs Enforcing LDAP Signing enabled by default starting with Windows Server 2025?
When connecting to Windows Server 2025 (Preview) using LDAP simple bind, the server rejected the bind. 「The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection」was displayed as an error message. If you change the LDAP server signing requirement from the default value to disabled according to the page below, LDAP simple bind will succeed. https://learn.microsoft.com/ja-jp/troubleshoot/windows-server/active-directory/enable-ldap-signing-in-windows-server Is Enforcing LDAP Signing enabled by default starting with Windows Server 2025? If so, where is the announcement about enabling LDAP server signing requirements?5.5KViews0likes2CommentsDocumentation on "Microsoft.OSConfig" PowerShell Module
Hi Server Insiders, is there any documentation available on the PowerShell Module "Microsoft.OSConfig"? https://learn.microsoft.com/en-us/powershell/module/osconfiguration/?view=windowsserver2025-ps does not help that much and also "Get-Help" is not that helpfull on most of the Commands. 🙂 Thanks! Best regards, Jan626Views2likes2Comments