Registry Editor Windows Server 2012

  • Expand the following GPO section: Computer (or User) Configuration Preferences Windows Settings Registry. Select in the context menu: New Registry Wizard; Registry Wizard allows you to browse the registry on a local computer. You can connect to the registry on the remote computer, and select the existing registry key and parameter.
  • Windows 2008 R2 and 7 Windows 2012 R2 and 8.1 Windows 2016 and 10 Windows Server 2019: Category. Subcategory: Object Access. Registry: Type Success: Corresponding events in Windows 2003 and before: 567.

For more on the registry and how it works, be sure to read our guide to using the registry editor like a pro. Backing up and Restoring Sections of the Windows Registry For the most part, all you need to know is how to backup and restore sections of the registry, especially those sections that you might be attempting to edit. The registry editor for the 3.1/95 series of operating systems is RegEdit.exe and for Windows NT it is RegEdt32.exe; the functionalities are merged in Windows XP. Optional and/or third-party tools similar to RegEdit.exe are available for many Windows CE versions. Registry Editor allows users to perform the following functions. To configure Windows registry audit settings on Windows Server 2012 and above On your target server, open Registry Editor: navigate to Start → Run and type 'regedit'. In the registry tree, expand the HKEYLOCALMACHINE key, right-click SOFTWARE and select Permissions from the pop-up menu.

One of the most important things in every Windows based domains are updates. You`ll probably want to arrange updating via Domain Group Policy since people often forget/postpone Windows Updates.

This LAB assumes you already have domain configuration in place.

Here is how to do it on Windows Server 2012 R2:

On your domain controller open search (or run) and type in gpmc.msc Click on gpmc

!!!! Little side note– In this case, I don`t want same Windows Update policy for my servers and clients. It would be inappropriate for production servers to update and restart let’s say at Monday 13 hours. But it would be very good time for clients since everybody is at lunch at that time.

Anyway, it is good practice to create different Organizational Units for different types of computers and users in your environment so you can fine tune your group policy and permissions also.

You can create new organization unit in Active Directory Users and Computers right click on domain name New – Organizational Unit

Let’s get on with the LAB

Expand forest Domains right click on your OU (organizational unit) that you want this policy to apply (in my case TestPCs OU) Create a GPO in this domain, and Link it here

We need to name New GPO. I`ll name mine Windows_Update Leave None under Source Starter GPO OK

New Policy is created (in my case) under TestPCs OU and it will apply to all PCs that are part of TestPCs OU.

Select created Windows_Update GPO (group policy object) and click on Settings tab on the right part of the screen

Right click on Computer Configuration Edit

Click on Computer Configuration Policies Administrative Templates Windows Components Windows Update

Double click on Configure Automatic Updates Enabled under Options define how you would like your updates to work. I choose following

Configure automatic updating: 4 – Auto download and schedule the install

Schedule install day: 2 – Every Monday at 13:00h

Apply OK


In order to confirm that this setting is working we need to test on one of the PCs that are affected by this policy.

Log on onto the PC – command prompt with administrative privileges (run as administrator)

After that if we check under Control Panel Windows Update Change settings (right part of the screen) we see that update settings are changed

Other Windows Updates options worth mentioning:

Turn on recommended updates via Automatic Updates

With this enabled you`ll get optional updates for windows components.

No auto-restart with logged on users for scheduled automatic updates installations is also good option.



We did some Group Policy and enabled automatic Windows Update for our domain PCs.

How to get the Windows Version from the System Registry

The Windows version is stored in the registry key: HKLMSOFTWAREMicrosoftWindows NTCurrentVersion


The value CurrentVersion contains the version number as string(!):

Version Number:Operating System:
5.0Windows 2000
5.1Windows XP
5.2Windows XP 64bit
5.2Windows Server 2003 / R2
6.0Windows Vista / Windows Server 2008
6.1Windows 7 / Windows Server 2008 R2
6.2Windows 8 / Windows Server 2012
6.3Windows 8.1 / Windows Server 2012 R2
10.0Windows 10 (Preview)

The value ProductName contains the system name, e.g. 'Windows 8.1'

Helper function to read a string value from the registry:

CString GetStringFromReg(HKEY keyParent, CString keyName, CString keyValName)
CRegKey key;
CString out;
if (key.Open(keyParent, keyName, KEY_READ) ERROR_SUCCESS)
ULONG len=256;
key.QueryStringValue(keyValName, out.GetBuffer(256), &len);
return out;

Get the OS version (e.g. '6.3')

CString osversion = GetStringFromReg(HKEY_LOCAL_MACHINE, L'SOFTWAREMicrosoftWindows NTCurrentVersion', L'CurrentVersion');

Get the OS name (e.g. 'Windows 8.1')

Registry Editor Windows Server 2012 Free

CString osname = GetStringFromReg(HKEY_LOCAL_MACHINE, L'SOFTWAREMicrosoftWindows NTCurrentVersion', L'ProductName');

Open Registry Editor Windows Server 2012

Registry Editor Windows Server 2012

Registry Editor Windows Server 2012 Download

Disclaimer: The information on this page is provided 'as is' without warranty of any kind. Further, Arclab Software does not warrant, guarantee, or make any representations regarding the use, or the results of use, in terms of correctness, accuracy, reliability, currentness, or otherwise. See: License Agreement