Active Directory Recycle Bin was released back in 2012 with the releases of Windows Server 2012. And with the release of Server 2016 the technology Is more mature and easy to use.

Administrators can restore deleted Items with a few easy clicks with Active Directory Recycle Bin. However, for the feature to work the recycle bin need to be enabled first and once enabled you can’t disable it.

If you’ve deleted a user before enabling the AD Recycle Bin, you won’t be able to restore it.

Deleted object will stay in the recycle bin for 180 days.

You will need an Administrator account first.

Log In a Domain Controller or a Server that has the RSAT tools Installed and open Active Directory Administrative Center

In the ADAC right-click on the domain and click on Enable Recycle Bin…

Confirm by clicking OK

Click OK

Once done, Refresh the console and you will see a new Deleted Objects OU. Next time you delete a user and need to restore it you will see In the OU

If you click on a deleted object you will have the option to restore it its original location or a different location

The post How To Enable Active Directory Recycle Bin appeared first on Linux Windows and android Tutorials.

Demoting a Windows Server domain controller Is a very common task In the lifecycle of every Active Directory Infrastructure and it’s something every Systems Administrator or Systems Engineer will have to do some day.

Saying that many admins are still keeping their old Windows Server DCs online because of they afraid they will break Active Directory when removing it, This post will show you how to do the right way and optimize your Infrastructure.

It’s a known that old and unmanaged Domain Controller cause 80% of Active Directory replication and Health Issue.

First, and before demoting your Domain Controller, make sure the items below are fulfilled

• You’ve moved the FSMO roles to another Server
• You have at least two domain controllers in the forest
• Active Directory Replication Is working 100%
• The Domain Controller Is not the last DC In the forest

To complete this process, you will need to use a user account with Domain Admins permissions.

To get started, Logg into the Domain Controller with an admin user account and run the command below.

Dcpromo

This will start the Active Directory Domain Services Installation wizard

“OK” to confirm that the Server will no longer act a global catalog server

Click next

Again, click next and wait, this part can take a few minutes to complete

“Finish” and restart the Server

After restart log Into the Server and you will see that the server is now just a member server.

The post How to Demote a Windows Domain Controller to a member server appeared first on Linux Windows and android Tutorials.

Introduction

“Flexible Single Master Operation” (FSMO) is a Microsoft Active Directory feature that is a specialized domain controller task used when standard data transfer and update methods are inadequate. Tasks that do not suit multi-master replication are only viable as flexible single-master operations.

Multi-master models have a number of operators, which are held by a single master. This problem is solved by applying a number of operations to a single domain controller. A single domain controller holds the role for a particular operation and is the single master for that operation. These operation masters are called flexible single-master operations.

The FSMO roles are logical Server roles that control the management and operation of an Active Directory Domain, the roles are listed below:

• Schema master
• Domain naming master
• RID master
• PDC emulator
• Infrastructure master

In most Active Directory environments the roles are located on the first deployed Domain Controller and In most places, the roles are always kept together for simplicity reasons.

When upgrading a Domain or retiring a Server we must move the roles before decommissioning the old Domain Controller.

FSMO Transfer

The move operation is done using 3 consoles as you will see below.

To get started, Open Active Directory Users and Computer and right-click on the domain and select Change domain Controller to the new Domain Controller

How to Move FSMO Roles on Windows Server 2016

Once connected to the new DC, Right click again on the Domain and select “Operations Masters”.

From here I’ll change 3 roles as you will see below

To move the role, Click change

Next, I’ll change the Domain Naming roles, by opening Active Directory Domains and Trusts and again right click on Operations Master

Once again, Click change

How to Move FSMO Roles on Windows Server 2016

Next, I’ll move the scheme Master Role, for that I’ll need to register Schema master MMC Console for the run task bar: Regsvr32 schmmgmt.dll

Once the MMC registered, Open the MMC and the “Active Directory Schema” snap-in

Once again, right click and select “Change Domain Controller”.

Select the New DC from the menu and click OK

Right Click again select Operations Master

Click Change

Finally, To verify that FSMO roles have moved to the new Server, type the cmdlet:

netdom query fsmo

Felicitation, you have done a great job. Now you can securely remove the old Domain Controller.

The post How to Move FSMO Roles on Windows Server 2016 appeared first on Linux Windows and android Tutorials.

In addition to the immediate benefit of having that data on a file server that is much easier to keep backed up, the user also gets the benefit of being able to go to multiple computers in your organization and still have access to their data. Using the default Windows settings and the default share settings on your file server, this redirection will be even made available offline automatically for your users. Let’s get started.

01 – Create a Shared Folder

On your server, on second Local Disk create New folder.

Right-click the New folder (I rename it to “Redir“), click Share with, and then click Specific people.

In the File Sharing dialog box, click the drop-down arrow, select Everyone, and then click Add.

For the “Everyone group” section, click the Permission Level drop-down arrow, and then click Read/Write. Click Share, and then click Done.

02 – Create a GPO to redirect the Documents folder

Open Server Manager, click Tools and then click Group Policy Management.

In the navigation pane, right-click on the domain name, and then click Create a GPO in this domain and Link it here.

In the New GPO dialog box, in the Name text box, type Folder Redirection, and then click OK.

Now In the navigation pane, right-click Folder Redirection, and then click Edit.

In the Group Policy Management Editor window, under User Configuration, expand Policies, expand Windows Settings, and then expand Folder Redirection.

Right-click Documents, and then click Properties.

In the Document Properties dialog box, on the Target tab, click the Setting drop-down arrow, and then select Basic-Redirect everyone’s folder to the same location.

Ensure that the Target folder location box is set to Create a folder for each user under the root path.

In the Root Path text box, type \\Server\Redir, and then click OK.

In the Warning dialog box, click Yes.

On the Client PC, right-click Documents, and then click Properties.

Verify that on the General tab, the Location field has a value of \\Server\redir\username.

If not type the following command : gpupdate /force, Sign out and Sign in again.

The post How to Configure Folder Redirection in Windows Server 2016 appeared first on Linux Windows and android Tutorials.