#windowsserver2019

Switching to a new server system or upgrading from one version to another can be tricky. We get so used to our regular pattern of movements that any change in the flow can disrupt work for a few days. But once you learn the new layout and features, you’ll find that they improve your flow overall. Windows Server 2019 is a powerful server system that can help you work better and faster with new improvements and updates. Here’s everything you need to know about Windows Server 2019.

All OUs in this domain should be protected from accidental deletion. All OUs in this domain should be protected from accidental deletion.Severity: WarningProblem: Some organizational units (OUs) in this domain are not protected from accidental deletion.Impact: If all OUs in your Active Directory domains are not protected from accidental deletion, your Active Directory environment can experience disruptions that might be caused by accidental bulk deletion of objects.Resolution:Make sure that all OUs in this domain are protected from accidental deletion.Best Practices Analyzer

With Active Directory Users and Computers console

To "protect an OU from accidental deletion", do the following: Open Active Directory Users and Computers console;Right click the OU that you want to protect from accidental deletion, and click Properties;Go to the tab Object, check "Protect object from accidental deletion" and click OK.

NOTE: If you don't see Object tab you must enable Advanced Features. In the Active Directory Users and Computers console click View and select Advanced Features.

With Windows PowerShell

What are the minimum requirements for a domain controller server? According to TechNet minimum requirements for Windows Server installation is.

Windows Server Installation Requirements

Processor Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements for this product: Minimum: 1.4 GHz 64-bit processorCompatible with x64 instruction setSupports NX and DEPSupports CMPXCHG16b, LAHF/SAHF, and PrefetchWSupports Second Level Address Translation (EPT or NPT) RAM The following are the estimated RAM requirements for this product: Minimum: 512 MB (2 GB for Server with Desktop Experience installation option)ECC (Error Correcting Code) type or similar technology Important: If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail. To avoid this, do one of the following: Allocate more than 800 MB RAM to the virtual machine you intend to install this release on. Once Setup has completed, you can change the allocation to as little as 512 MB RAM, depending on the actual server configuration.Interrupt the boot process of this release on the virtual machine with SHIFT+F10. In the command prompt that opens, use Diskpart.exe to create and format an installation partition. Run Wpeutil createpagefile /path=C:\pf.sys (assuming the installation partition you created was C:). Close the command prompt and proceed with Setup. Storage controller and disk space requirements Computers that run Windows Server must include a storage adapter that is compliant with the PCI Express architecture specification. Persistent storage devices on servers classified as hard disk drives must not be PATA. Windows Server does not allow ATA/PATA/IDE/EIDE for boot, page, or data drives. The following are the estimated minimum disk space requirements for the system partition. Minimum: 32 GB NOTE: Be aware that 32 GB should be considered an absolute minimum value for successful installation. This minimum should allow you to install Windows Server in Server Core mode, with the Web Services (IIS) server role. A server in Server Core mode is about 4 GB smaller than the same server in Server with a GUI mode. The system partition will need extra space for any of the following circumstances: If you install the system over a network.Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files. Network adapter requirements Network adapters used with this release should include these features: Minimum: An Ethernet adapter capable of at least gigabit throughputCompliant with the PCI Express architecture specification.Supports Pre-boot Execution Environment (PXE). A network adapter that supports network debugging (KDNet) is useful, but not a minimum requirement. Other requirements Computers running this release also must have the following: DVD drive (if you intend to install the operating system from DVD media) The following items are not strictly required, but are necessary for certain features: UEFI 2.3.1c-based system and firmware that supports secure boot Trusted Platform Module Graphics device and monitor capable of Super VGA (1024 x 768) or higher-resolution Keyboard and Microsoft® mouse (or other compatible pointing device) Internet access (fees may apply)

Domain Controler installation requirements

Windows Server rebooted due to Reason Code: 0x80020002.

Check that the server was rebooted by User32

1. Log into the affected Windows Server and open up the Event Viewer; 2. Navigate to Windows Logs\System\Filter Current Log and search for the Event ID: 1074; 3. Results will appear as per the screen shot below:

Update the Local Computer Policy to stop the server from rebooting

1. Run the command gpedit.msc. You will need to be an elevated user to manipulate Local Group Policy Editor. 2. Navigate to Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Windows Update; 3. Enable the policy No auto-restart for scheduled Automatic Updates installations;

Windows Domain Controller fix Error 0xc00002e2. This error indicate that the Active Directory database (NTDS.DIT) is being corrupted. NOTE: Error code 0xc00002e2 may occure only on a system with Active Directory role. Resolution

Method 1

Reboot the server into Directory Services Restore Mode by pressing F8 before the OS loading. You will be required to use the local Administrator account password (for domain controller pc this is global Active Directory admin). In Directory Services Restore Mode, you can check if there is a problem with the database by running the following commands: ntdsutil.exe activate instance ntds files If there is a problem with the Active Directory database NTDS.DIT, you will see an error: Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113 To resolve this issue, rename all of the *.log files located in C:\Windows\NTDS\ to *.log.old, so the logs can be recreated after reboot. This should fixed the database after the server is rebooted once more.

Method 2

Reboot the server into Directory Services Restore Mode by pressing F8 before the OS loading. You will be required to use the local Administrator account password (for domain controller pc this is global Active Directory admin). Run the next command: esentutl /p "c:\windows\ntds\ntds.dit" Reboot the server and the issue should be solved.

Method 3

Hyper-V VM stuck in Stopping state. It stuck in the Stopping or Running state in and doesn't give any Turn Off, Shutdown, Save, Pause or Reset options. One way its possible to kill off that stuck virtual machine is to open Task Manger and end the task responsible for that machine. Unfortunately its not quite that simple because the Virtual Machine Worker Process which is responsible for running the virtual machine appears numerous times, once for each running guest machine!

Method 1

If you have small amound of VM's: Open Task Manger and view the Details tab;You will see many vmwp.exe running process with Username column including the machine GUIDs;Browse to the location where the virtual machines are stored and open the folder of the virtual machine which is currently hung. From here we can find the machine configuration file and make note of the GUID for that machine;Now we know which GUID relates to the virtual machine that we are looking to stop. Jump back to Task Manger, right click on the correct process and End Process. NOTE: this process should only be used as a last resort as it could cause corruption of the virtual machine!

Method 2

If you have bunch of running VM's. The fastest way is to find needed VM GUID with powersell command. Get-VM | fl *

Now we know which GUID relates to the virtual machine that we are looking to stop. Jump back to Task Manger, right click on the correct process and End Process. This command pulls a list of virtual machine names and GUIDs then compares that to a list of GUIDs in the Command Line of the processes running and returns virtual machine names with the associated Process ID (not VM GUID). Get-WmiObject Win32_Process -Filter "Name like '%vmwp%'" | %{$vm=get-vm -id $_.CommandLine.split(" ");"$($_.processID)`t$($vm.name)"}

Method 3