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
“You really put a lot of time and effort into this [project handover document]. It is very clear and concise. Really nice job on the documentation!”
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