How do I know if DFS Replication is completed using PowerShell?

You can check the state of DFS-Replication by using the DFSRDiag command. If replication was in progress, you would see these results
dfsrdiag RepliationState
Updates served:

[1] Update name: user32.amx
[2] Update name: gdi32.amx
[3] Update name: report.docx
[4] Update name: Train.pptx

Total number of Outbound updates being served: 4

Summary

Active inbound connections: 0
Updates Received: 0

Active outbound connections: 1
Updates sent out: 4

Operation Succeeded

This must be ran on a server with DFS installed on it. Your exact results will depend on what is being transferred.

To do this in PowerShell, I created a function that sends a value of True into the pipeline if DFS replication is active and False if it is not. Here is the code:

<#
.SYNOPSIS
Test to determine if DFS replication is in progress

.DESCRIPTION
Returns [Boolean]TRUE if replication is in progress.
Returns [Boolean]FALSE if replication is not in progress.

.EXAMPLE
Test-DFSRProgress

True

The example returned True.  That means DFS
replication is in progress.

.NOTES
This function can only be executed on a server
with DFS installed.  It will only test for
DFS replication to and from this executing
server.

.LINK
Invoke-Command
#>

Function Test-DFSRProgress
{
# Execute the MS Dos command "DFSRDiag ReplicatoinState"
    # and store the output in the variable $DFSRInfo.
    $DFSRInfo = Invoke-Command -ScriptBlock {DFSRDiag ReplicationState}

# Test to see if the output has the below strings in it.
    # if it does not, then replication is in progress.
    If ($DFSRInfo -like "*Active inbound connections: 0*" -and $DFSRInfo -like "*Active outbound connections: 0*")
{Write-Output $False}
Else {Write-Output $True}
}

Comments

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog