Adding cloned and syspreped vm to existing dfs replication group - replication not working

Question

Trying to add cloned and syspreped vm to dfs - replication not working - getting "The replicated folder has been offline for too long." in event log.

This is tied to an existing file server replication group, not AD.

We're trying to add another member at a different site, based on a cloned and sysprepped existing member of the same DFS.

How can I clear out DFS settings on this machine so it doesn't think it's the same machine we cloned and sysprepped? (I already deleted the dfs folder off the machine prior to adding it to dfs.)

Getting this error when it attempts to replicate:

--

** c:\windows\debug\dfs*.log

20230222 00:24:39.530 10352 CSMG 8676 [WARN] ContentSetManager::IsOfflineTooLong This replicated folder has not connected with other partners for too long. lastOnlineTime:20221122 00:01:38.907 offlineDays:92 maxOfflineDays:60 csId:{DC7CFA9B-45FD-46E1-9E71-E9A1D654E280} csName:%somefolder% rootPath:C:%somefolder% state:InitialBuilding ptr:000001EFFAA34910 csInfoHistoryGuid:{B3207465-0F8A-42FC-B8C8-3AE33304D23F}

20230222 00:24:39.530 10352 CSMG 8424 [ERROR] ContentSetManager::Initialize Failed to initialize ContentSetManager csId:{DC7CFA9B-45FD-46E1-9E71-E9A1D654E280} csName:%somefolder% rootPath:C:%somefolder% state:InitialBuilding ptr:000001EFFAA34910 csInfoHistoryGuid:{B3207465-0F8A-42FC-B8C8-3AE33304D23F} Error:

• [Error:9061(0x2365) ContentSetManager::CheckContentSetState contentsetmanager.cpp:6265 10352 C The replicated folder has been offline for too long.]
• [Error:9061(0x2365) ContentSetManager::CheckContentSetState contentsetmanager.cpp:6176 10352 C The replicated folder has been offline for too long.]

** 'dfs replication' event log

Log Name:      DFS Replication
Source:        DFSR
Date:          2/22/2023 1:55:39 AM
Event ID:      4012
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      %somecomputer%
Description:
The DFS Replication service stopped replication on the folder with the following local path: C:\%somefolder%. This server has been disconnected from other partners for 92 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. 
 
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. 
 
Additional Information: 
Error: 9061 (The replicated folder has been offline for too long.) 
Replicated Folder Name: %somefolder% 
Replicated Folder ID: DC7CFA9B-45FD-46E1-9E71-E9A1D654E280 
Replication Group Name: %somereplicationgroup% 
Replication Group ID: A0D57EF9-043D-4515-898D-71BD435C1836 
Member ID: 0B4C4F89-EE75-433E-A6EC-796C97909530
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">4012</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-02-22T08:55:39.683697600Z" />
    <EventRecordID>9790</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>%somecomputer%</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DC7CFA9B-45FD-46E1-9E71-E9A1D654E280</Data>
    <Data>92</Data>
    <Data>C:\%somefolder%</Data>
    <Data>9061</Data>
    <Data>The replicated folder has been offline for too long.</Data>
    <Data>%somefolder%</Data>
    <Data>%somereplicationgroup%</Data>
    <Data>A0D57EF9-043D-4515-898D-71BD435C1836</Data>
    <Data>0B4C4F89-EE75-433E-A6EC-796C97909530</Data>
    <Data>60</Data>
  </EventData>
</Event>

Answer 1

I believe this folder holds the underlying data:

D:\System Volume Information\DFSR

I can see that it contains tons of info from the time the machine was cloned.

Logically it seams that I can delete these contents and refresh it. But Know it's not that simple.

Any help is greatly appreciated.