Client-driven PST migration post-processing

[charles-k]

In the PST migration policy settings, Post Migration ab, it says that the options to compact the PST, mark it read-only, and mark it hidden are "Actions that do not apply to client-driven migrations."  And yet, when I do client-driven PST migrations, the users' PST files *are* getting marked as read-only and hidden.  Can someone explain why these settings don't apply to client-driven migrations, at least in theory, since, like I said, they are actually being applied to my client-migrated PSTs?  I'm running EV 8.0 SP3.  Thanks.

Charles

[Nick_White · Accepted solution]

The reason the settings don't apply is because client-driven migration is hard-coded to carry out those operations so they will always happen by default

[charles-k]

Nick, thanks for the response!

Charles

[charles-k]

Actually, the client driven PST migration is marking the PST as read-only after migration, but it's not marking it as hidden.  I thought it's supposed to do both.  So now I have to manually hide each PST after migration completes.  Can someone explain this, and also advise on how to make it set both file attributes after migration?  Thanks in advance.

Charles