Install Data Deduplication via PowerShell

In a previous article, I showed you how to install data deduplication using the GUI. In this article, we will install data deduplication remotely via PowerShell.

On a your 2012 server, open Server Manager.

The following assumes that you have added the remote server to the Server Manager that you are working on.

In Server Manager, click All Servers.

Right click the server that you want to install data deduplication on and select Windows PowerShell

Type Add-WindowFeature –Name FS-Data-Deduplication and press Enter.

Wait for the process to complete. No reboot of the remote server is necessary.

Once installed, we use the Enable-DedupVolume –Volume E: cmdlet to enable data deduplication on the E: drive.

Using Get-DedupVolume will let you see all the volumes on this server that has data deduplication enabled on them.

Use the Get-DedupSchedule cmdlet to get the current deduplication.

The current deduplication optimization that is scheduled runs at low priority. If you want to create one that will run at a higher priority:

This will start a new regularly scheduled data deduplication job at normal priority every Saturday at 3:45 AM that will last for 4 hours.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog