QCS (Quest Collaboration Services) Namespaces logic
The documented QCS logic of how it picks redirection address on the stub objects may use some additional clarification so I am going to share it
“It has been a long slog for the team out there, and they’ve done a tremendous job of shepherding this project through its lifecycle into the home stretch.”
The documented QCS logic of how it picks redirection address on the stub objects may use some additional clarification so I am going to share it
Here is the real-world scenario that I was recently working on: QCS currently runs AD and Legacy F/B Sync. QMM DirSync comes in, QCS AD
I am often coming across migration projects where QCS exists prior to the QMM implementation. These conditions always add extra complexity and need very careful