Don't let your AntiVirus software ruin DFS Replication

Windows Server 2008 has some really neat features to help make your users (and your) life easier. One of them is Distributed File System. There is a sure fire way to ruin this feature, having an incompatible antivirus product.

Since a move to Windows Server 2008 and antivirus protection is a big investment in your business, neglecting compatability in your antivirus protection can cause a serious cost over run.

Below is a list of compatible antivirus products from http://support.microsoft.com/kb/815263/en-us.

There is also a hot fix availible for ForeFront client users. If your files take unexpectedly long to replicate, check out this link. 3rd party antivirus vendors may also have this issue as well.
http://support.microsoft.com/?kbid=956123

Antivirus
• Microsoft ForeFront
• Computer Associates eTrust Antivirus build 96 or later with the "NTFS incremental scan" feature disabled •
Computer Associates eTrust 7.0
• Eset Nod32 version 1.199.16
• Grisoft AVG Antivirus 7.0
• McAfee/NAI NetShield 4.50 with the NetShield Hotfix Rollup
• Norton AntiVirus 7.6 or later
• PowerQuest V2i Protector Desktop Edition 2.01
• PowerQuest V2i Protector Server Edition 2.01
• Symantec Antivirus Corporate Edition 8.1
• Trend Micro ServerProtect for Microsoft Windows/Novell Netware
• Trend Micro OfficeScan 7.0
File and system state backup
• Legato Octopus/Replistor 5.2.1
Disk optimization
• PowerQuest Drive Image 7.01

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