notebook keyboard

There is a great post on Technet on Manually Clearing the ConflictAndDeleted Folder in DFSR, however it was written back in 2008 and it seems things changed slightly, so I thought I better write a quick blog post in case anyone runs in to the same issues I did.

Please refer to the above article first, I had issues running the CleanupConflictDirectory method.

Eg.

WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where “replicatedfolderguid=’70bebd41-d5ae-4524-b7df-4eadb89e511e’” call cleanupconflictdirectory

ERROR:
Description = Invalid query

Look Familiar?

I found simply by switching the quotation marks around so that the single quote (‘) surrounds the ‘replicatedfolderguid=xxx’ value and the double quotes surround just the GUID (“) did the trick.

For example:

WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where ‘replicatedfolderguid=”insert-GUID-here“‘ call cleanupconflictdirectory

See after the GUID there is a double quote followed by a single quote “‘

This should work! (If not, are you using an elevated Command Prompt?)

Crazy, eh?

For more information on how to clear the ConflictAndDeleted folder please refer to the blog post here: https://blogs.technet.microsoft.com/askds/2008/10/06/manually-clearing-the-conflictanddeleted-folder-in-dfsr

4 Comments

  1. Mishman on August 2, 2017 at 10:38 pm

    This didnt work for me, but instead something else worked – do not copy the command from a web page, but write it directly from keyboard to the command line. There must be some mismatch in coding, that prevents it working. Well sometimes you have to do all the work on your own 🙂

  2. Allan on April 24, 2018 at 1:29 am

    Didn’t work for me either but it was the order of the quotes. Single quotes around the query with double around that:

    WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where ‘replicatedfolderguid=”GUID”‘ call cleanupconflictdirectory

  3. LabanM on October 19, 2018 at 7:46 am

    Worked perfectly. Thanks!

  4. Cyril on April 10, 2019 at 12:08 am

    This worked for me on server 2012 r2 thanks

Leave a Comment