<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows Server on justinverstijnen.nl</title><link>https://projectkaasplank.justinverstijnen.nl/blog/windows-server/</link><description>Recent content in Windows Server on justinverstijnen.nl</description><generator>Hugo</generator><language>en</language><atom:link href="https://projectkaasplank.justinverstijnen.nl/blog/windows-server/index.xml" rel="self" type="application/rss+xml"/><item><title>Active Directory FSMO roles</title><link>https://projectkaasplank.justinverstijnen.nl/active-directory-fsmo-roles/</link><pubDate>Tue, 04 Feb 2025 00:00:00 +0000</pubDate><guid>https://projectkaasplank.justinverstijnen.nl/active-directory-fsmo-roles/</guid><description>&lt;p&gt;Active Directory Domain Controllers are assigned 5 different FSMO roles, which all have their own function. We can separate them over multiple servers to create more redundancy, but make sure to handle those all as servers. All roles neeed a 24/7 uptime for your environment to work properly.&lt;/p&gt;
&lt;p&gt;In this guide, I will give a brief explaination of the roles, what their function is and how to move them to different servers to enhance availability and redundancy.&lt;/p&gt;</description></item><item><title>Managing Hyper-V server without Active Directory</title><link>https://projectkaasplank.justinverstijnen.nl/managing-hyper-v-server-without-active-directory/</link><pubDate>Tue, 17 Dec 2024 00:00:00 +0000</pubDate><guid>https://projectkaasplank.justinverstijnen.nl/managing-hyper-v-server-without-active-directory/</guid><description>&lt;p&gt;When you use Hyper-V server, you want to manage this with the management tools. However, by default Hyper-V only allows connections from domain-joined machines by design because of security and trust reasons.&lt;/p&gt;
&lt;p&gt;We can bypass this requirement by building these trust ourselves and so managing the server from a machine that isnt even in a domain but Entra ID Joined or in a workgroup.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="installing-hyper-v-management-tools"&gt;Installing Hyper-V management tools&lt;a class="td-heading-self-link" href="#installing-hyper-v-management-tools" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When you use Windows 11 Pro/Education/Enterprise, you have the option to install Hyper-V on your machine. This can be done through the features on demand window:&lt;/p&gt;</description></item><item><title>Solved: August 2024 updates breaks GPO Item level targeting - user in group</title><link>https://projectkaasplank.justinverstijnen.nl/solved-august-2024-updates-breaks-gpo-item-level-targeting-user-in-group/</link><pubDate>Mon, 09 Sep 2024 00:00:00 +0000</pubDate><guid>https://projectkaasplank.justinverstijnen.nl/solved-august-2024-updates-breaks-gpo-item-level-targeting-user-in-group/</guid><description>&lt;p&gt;If you are managing Windows Servers, Group Policies are a great way to distribute settings to your endpoints. However, a recent update of August 2024 in Windows Server 2022 and 2019 breaks user filtering in Group Policy (GPO) Item Level Targeting&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-problem-itself"&gt;The problem itself&lt;a class="td-heading-self-link" href="#the-problem-itself" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When applying printers, registery settings or drive maps to users, we use Group Policy Item level targeting to filter users so only users with a group membership gets the policy applied.&lt;/p&gt;</description></item><item><title>Migrate Group Policies to a new server or domain like a pro</title><link>https://projectkaasplank.justinverstijnen.nl/migrate-group-policy-objects-to-a-new-server-or-domain-like-a-pro/</link><pubDate>Wed, 07 Aug 2024 00:00:00 +0000</pubDate><guid>https://projectkaasplank.justinverstijnen.nl/migrate-group-policy-objects-to-a-new-server-or-domain-like-a-pro/</guid><description>&lt;p&gt;Once in a while, we as IT administrators need to export and import our Group Policies of Windows Server to another server. Sometimes to copy a great policy you&amp;rsquo;ve built, or to migrate a customer to a new server.&lt;/p&gt;
&lt;p&gt;By default, the only option Microsoft has built in into Group Policy Management (gpmc.msc) is the backup option. This creates some administrative tasks.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-export-and-import-scripts"&gt;The Export and Import scripts&lt;a class="td-heading-self-link" href="#the-export-and-import-scripts" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;I have created two scripts with Powershell that fully exports and imports all Group Policy Objects (GPOs). This with 2 seperate scripts. These can be found and downloaded from my Github page:&lt;/p&gt;</description></item><item><title>Change Evaluation version to Standard/Datacenter version</title><link>https://projectkaasplank.justinverstijnen.nl/windows-server-evaluation-to-standard/</link><pubDate>Wed, 03 May 2023 00:00:00 +0000</pubDate><guid>https://projectkaasplank.justinverstijnen.nl/windows-server-evaluation-to-standard/</guid><description>&lt;p&gt;&lt;img src="https://sajvwebsiteblobstorage.blob.core.windows.net/blog/windows-server-evaluation-to-standard-71/jv-media-71-30eb3963ce1a.jpg" alt="Powershell script"&gt;&lt;/p&gt;
&lt;p&gt;When you install a fresh Windows Server installation from a .iso file, it will be installing the OS as a Evaluation version. When you want to activate the installation with a key you need to rebuild the OS and set the edition to Standard.&lt;/p&gt;
&lt;p&gt;Microsoft considers Standard and Standard Evaluation as different editions of Windows, because of this we have to change the edition before you can activate the installation. When you want to use the edition Datacenter, you can change the command to Datacenter which also works.&lt;/p&gt;</description></item></channel></rss>