User Profile
Marc__K
Brass Contributor
Joined 8 years ago
User Widgets
Recent Discussions
Re: DFS Replication is Not Compatible with NTS Deduplication
It turns out the March 2023 CU didn't have anything to do with this. Not previously mentioned is that the systems experiencing this problem have Veeam Agent for Windows (VAW) installed. After recently updating VAW to a newer release, the 4406 events returned. The last time the reboot from installing the March 2023 CU must have been what actually fixed things. This time I did a reboot without installing any additional Windows updates and the 4406 events stopped again.1.8KViews0likes0CommentsRe: DFS Replication is Not Compatible with NTS Deduplication
So...This appears to have stopped after installation of the March 2023 CU on the servers. Perhaps development already had a bug logged and happened to fix it. I know I had been troubleshooting this for a while before I posted this.1.7KViews0likes1CommentRe: DFS Replication is Not Compatible with NTS Deduplication
It's occurring with both OSes. This morning a 2012 R2 system generated 2 new 4406 events. Yesterday, I "unoptimized" everything on a 2019 server and then re-enabled deduplication. That server generated a few 4406 events right after the deduplication was re-applied.1.8KViews0likes0CommentsDFS Replication is Not Compatible with NTS Deduplication
The https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/interop claims that data deduplication is compatible with DFS Replication, but that is not correct. I have several systems with both enabled, some Windows Server 2012 R2 and some Windows Server 2019 systems. If a user interacts with a file that has been deduplicated, such as moving it from one folder to another, DFS-R may log a 4406 error (The DFS Replication service encountered an unsupported reparse point in a replicated folder. This reparse point will not be replicated because the replication of this type of reparse point is not supported by the DFS Replication service.) and delete the file from the partner. Data deduplication uses reparse points and DFS Replication doesn't like them. I thought that since the documentation says both technologies are compatible that DFS Replication would have been updated to work correctly with reparse points when they are related to data deduplication.SolvedRe: Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
BrianGrell83I'm no longer able to test this. I completed an upgrade to Exchange 2019 a while back. I asked support if the new SU includes a fix for this issue and they said there is no indication that it does. I also found out that since I opened the case via software assurance, the service level is very poor. This team has no ability to contact the product team to express my dissatisfaction that a fix was coded and is being withheld from customers. They said if I wanted better service, I'd need to open a ticket under premier support. This team considers the case resolved once the issue is confirmed as a known bug.4.1KViews0likes0CommentsRe: Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
Support has now acknowledged that another CU is not coming, and since the fix is marked for the next CU, they can't say that it'll ever be released. They're trying to close the case and telling me to upgrade to Exchange 2019. It's unacceptable for Microsoft to break something that was working when a product entered extended support, then say "sorry, we're not gonna fix that because the product is in extended support."4.4KViews0likes2CommentsRe: Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
No, support has been very clear of CU vs SU. I even mentioned there are no more CUs and they still insist their documentation says it will be included in the next CU. I'm in the middle of a migration to Exchange 2019 and found the issue is not there. This may be a case of the Exchange team just showing disdain for customers that are on an old version.4.7KViews0likes0CommentsRe: Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
Support is telling me the fix has been scheduled for "the next CU". Since there are no more CUs planned for Exchange 2013, I guess that means the fix is scheduled for never. This is really poor of the Exchange team. They have the issue diagnosed and a code fix ready, and are choosing not to release it.4.8KViews0likes2CommentsRe: Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
Support had told me it was fixed in the "February update", but it's March now and no update has been released. I'm now working on a migration to Exchange 2019 and am not seeing the same problem there. I suspect that I'll be done with that before support informs me that the Exchange 2013 update is ready.4.9KViews0likes4Comments
Recent Blog Articles
No content to show