Forum Widgets
Latest Discussions
Force a specific default lock screen and logon image
Dear, I currently have a DC deployed on Windows Server 2019. i want to configure a specific default image on lock screens on Windows 10 pro clients via group policy. Is this possible or is it only compatible with Enterprise or Education editions? Thanks in advance,
GUID reuse deleted accounts
I had a meeting today and they talked about using the user GUID to identify users, the question came up if a user account is deleted for say 6 months and then I create an account with the same name and organization as well as username will the GUID be the same. I found information on how the GUID is built that says yes but it just seems like the answer should be no. An account that is recreated will not get the same GUID since they are somewhat randomly generated. This is a Server 2016/19 Win10 environment with no Internet connectivity and no Office 365 or teams. Does anyone have a link to how Windows generates a user GUID it seems that SQL server uses that and if in account is deleted and recreated they will not have access to the old data? This is all new to me as my thought is why would you not use usernames, and for me you assign permissions in Windows using groups. Not an SQL expert so any help would be appreciated.
RDP is locked to 30FPS for MacOS clients
I have found that even after going through the guide below, RDP connection remains locked to 30FPS if I connect to my Windows machine from my Mac. Frame rate is limited to 30 FPS in remote sessions - Windows Server | Microsoft Learn Is there any way to set the frame rate to 60FPS while using the Mac client for RDP? Thank you.
Rds famr 2019 and microsoft remote desktop android
Hi all. In my rds farm 2019 i use microsoft remote desktop for android vers. 8 to connect in my Remote Resource Feed with specific url. In new client version 10.0 no ther isn't Remote Resource Feed but there is Workspace. How can connect my rds farm in workspace? Or is there another app can connect in myRemote Resource Feed inviroment? Thanks.User CAL or RDS CAL for this kind of access?
My client need a VM with Windows Server 2022 installed. I've tell him to provide a Windows Server 2022 Standard 16 core installation but i'm confused with CAL license. The VM will start with an autologon on a user and then my customer will connect via RDP to that session (same user that starts in autologon) to manage the installed application (a SCADA automation software). Do I require a RDP CAL or a simple USER CAL? ThanksWindows Server 2016 on ESXi, two servers solution in case of failure
Hi, I'm facing a problem I still can't find a solution to. Short description below. ESXi virtualization environment has a Windows Server 2016 Datacenter installed. The Server has AD switched on, for the sake of our discussion I'm naming it "contoso.local". There are shared resources on the virtualized server such as shared folders and files, also there is MS SQL server which receives incoming connections from Windows clients (Win10/11). What do I need to achieve? I need to create another virtualized Windows Server 2016 Datacenter or Standard which will be an alternative server that will start offering its services immediately in case of the another server failure. What do I mean by "immediately" here? I mean, the switching procedure/time must be immediate and all the resources such as shared folders or SQL databases must be up-to-date. So, if at 1:00 PM the first server has a failure (disconnected, shut down by mistake etc), the other server must take control of the client machines at 1:05 PM. And as I mention all shared resources and SQL connections must stay the same but on the second server. The users on client machines can't have their work disrupted (any open Word documents in shared foilders intact or financial software connections kept on). I'm aware of the fact that the second server must be a sort of replica that works all the time and receives data from the server so it must be a 1-1 copy of all data that it constantly updates itself with new data coming from the first server. The question is - how can this be done ? I tried Cluster failover, storage replica already but this mechanism didn't work out. I created two disks (logs, data) according to step-by-step instructions but it is still not a solution to the problem. I'll appreciate any advice to my issueBLOG: Windows Server Installation guidance / M365 Support on Windows Server
Windows Server 2025 will probablybe released later this year. At least signs / stars seem to align.🙂 Starting with this Windows Server release, Microsoft 365 Apps for Enterprise are supported within the mainstream support of the OS. That means 5 years peace of mind, after the release of the next Windows Server OS. For more information review the official matrix. Windows Server 2025, should be included after release. The latest Office Support Matrix can be obtained here Windows Server 2025 will be released this year with load ofsignificant improvements over 2022 or earlier versions. Please check thisannouncement + comments, and find morehere in the Windows Server 2025 AMA. Feel invited to join the Windows Server Summit and if you cannot attend, learn what's new watching the recorded sessions. This announcement and rich improvments, will make any migration plans worthwhile, noted Windows Server 2016 is already in Extended Support. Will outline later why this isn't a good thing for most. Windows Server 2019 just entered Extended Support this month. Obtaining and maintain Software Assurance for Windows Server through Volume Licensing or CSP Subscription (SA equivalency) makes sense for you this year in several ways for the adoption of the new Windows Server 2025 release Significant cost reduction through Azure Hybrid Benefits, among others for all licensed cores under SA or SA equivalency. This is not a licensing advice post, rather presents you common examples. For details hold on to Product Terms, as conditions may change. free Windows Server Datacenter OS licenses (even if on-prem only Standard licensed) in Azure. For Details hold on to Product Terms, conditions may change. free Azure Stack HCI usage for licensed cores free of charge access to the Windows Server Datacenter Azure Edition VM or ISO within Azure and when running on Azure Stack HCI, granting you exclusive features, but will also appear with Windows Server 2025. Hotpatching SMB over QUIC(fast and VPN-free access to on-prem authorized SMB shares / file server shares). per VM licensing on-premises on Azure Stack HCI and in Azure (currently with a minimum 8 cores per VM (vOSE)) dynamic licensing with Windows Server 2025* *SA or equivalent not required Use Microsoft (server) products, within mainstream support wherever possible especially, when production critical. Some (german) software manufacturers also specify that the Windows Server OS must be in mainstream support in order for their software to be supported. Microsoft 365 joins this chorus now. Caveat: Microsoft Exchange Server on-premises is currently only available in Extended Support (MS Exchange Server 2016 / 2019). So only the OS (WS 2022) can be kept in Mainstream support at the moment. Reasons against operating products in Microsoft Extended Support: support comes at extra costs hard to obtain / not immediately available, especially in emergencies there is no guarantee of solution or workaround Microsoft sometimes removes or replaces documentation of products outside of mainstream support Extended Security Updates are costly (free on Azure Stack HCI on-prem / and when running in Azure) Install Windows Server always in english language (en-us), if necessary use Language Packs (LP) / LIPs Reasons and pain points from the field: Microsoft’s / own PowerShell scripts or modules may be language dependent, e.g. Windows Features, local security groups etc. mass evaluation in Server Manager or PowerShell are hindered, as Eventlogs, Roles & Features and Windows services descriptions are language dependent. For example this renders full text search in Server Manager unhelpful. some roles are language dependent and therefore cannot be (easily) migrated (e.g. DHCP, AD CS) Documentation and error messages are easier to find and understand in English (crude translation) + operational bonus for Microsoft CoPilot in Edge, possibly replacing Dr. Google (Mechanical Doctor) when searching for solutions 🙂 way easier collaboration with Microsoft Support proven fewer problems with Windows Admin Center GPO Search Engine only exists in English. The translation of GPOs is very arbitrary. Direct in-place upgrade to Windows Server Azure Edition possible, when switching to Azure Stack HCI Windows Server 2022 and 2025 Support dynamic user based language packs (LIPs). Internet connection is required for download and updates. Bonus: You can leverage group policy to assign OS language, keyboard and regional settings based on user, or AD group membership. Choose / prefer to install Windows Server as Core option where possible This will enhance your "need" to adopt RBAC and Remote Management without RDP. Possible usecases: Domain Controller, Exchange, SQL (GUI Setup exists), FileServer etc. Remote Management via Privileged Admin Workstation (PAWS :paw_prints:) / Windows Server VM (RDSH) + Tools Windows Admin Center Server Manager DSAC and other RSAT tools sconfig Install Windows Server only as UEFI / GPT Windows Server 2022 and 2025 support VBS and Secured Coresettings. GPT / UEFI is a prerequisite for this. Windows Server 2022 / 2025 can use vTPM for Bitlocker and other things like Windows 11. GPT / UEFI is a prerequisite for this. easier migration paths VMware <> Hyper-V / Azure Stack HCI. These VMs are deployed as Gen 2 Hyper-V. Gen 1 VMs or VMware BIOS VMs are no longer preferred, see above. Keep the WinRE partition behind the OS partition easier maintenance of the OS in an emergency Uninstall of defective Windows Updates before the boot process (starting with Windows 2022) Re-Partitioning / Resizing using 3rd party tools possible via VHD(X) / VMDK mounting in another VM if required. You can find more information on WinRE and WinRE patching considerationsin this guidance. As you've made it to the end of this lengthy and hopefully helpful post, here's your bonus material / extended edition: Windows Server Upgrade guidance. Thanks for reading and adopting changes to your environment and strategy!
