Hello,
I have a production SMS 2003 environment that's working well. I have recently created a completely seperate SCCM server with a different Site Code and plan to move clients and secondaries over, one boundary at a time.
My question: Should I not create a Server Locator Point role on the new SCCM server to avoid confusing clients?
It's important that while I'm building/testing the SCCM environment I not accidentally disrupt the SMS 2003 environment. I know to avoid overlapping boundaries and naming the primary Site codes the same. Are there any other gotchas?
Thank you,
-Ref
SLP Side by Side
↧
↧
Trending Articles
More Pages to Explore .....