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
“We all know how stellar the Coherence migration teams are, and it is hard to believe, but they have upped it a notch. This team not only has delivered high quality, consistent work in a political nightmare environment, but they have uncovered new business. This is the synergy we have been speaking to for years – how these guys as technical experts can bring in additional products and services because they are so highly technically-skilled.”
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