GPOs - Account Policies - How to?
Hello everyone, I'm addressing some Microsoft 365 Defender recommendations for Endpoints. Some of these are related with Password Policy. The recommendation is to configure some GPOs like this one: Set 'Minimum password length' to '14 or more characters' Set the following Group Policy: Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy: Minimum password length To the following value: 14 or more characters I'm trying to achieve this with "Intune only" but can't figure out how. Already used Device Restrictions but it seems to take no effect in the recommendation (already waited 24h to refresh). Any...help? 🙂 Best regards, Diogo SousaWindows 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 NndnGConverting copied Library ID from Unicode to ASCII
Last August, the OneDrive Group Policy documentation has been updated to include a Unicode to ASCII conversion to manage synced library (see https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commit/f0e63a2a667a41e514f24b1bfd76f5654c22cca8#diff-b2e9feac11fcf00c73901527a94c69e8). Several users, including myself, reported that it adding synced libraries works well even without replacing Unicode with ASCII (see https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/323#issuecomment-555513345, https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/323#issuecomment-589993484 and https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/1941). Nevertheless, the need to manually replace Unicode with ASCII would make the procedure a little bit cumbersome, no longer that straightforward. Does anyone have some clarifications on this?
