SCCM Central Site but reporting to another SCCM Site Server (both servers don't have Parent-Child relationship with each other) is this possible?
Hi Everyone,This is the current setup of our SCCM Infrastructure.SCCM Workstations Infra (aka SCCMWS)- SCCM service, setup to only support workstationsSCCM Server Infra (SCCMSVR)- SCCM Service, setup to only support servers.Now my questions is, is it possible for our SCCMWS Central SITE SERVER's SCCM Client to be assigned to our SCCMSVR Central site? Would this produce any conflict? with the current system of SCCMWS infra?Now before anyone says to change the architecture of our setup. We can't that is our management's decision, we need to figure out a way to make this work. Please advise if this setup will have conflicts, and where or what this conflicts might be. Are there any workaround we could use, 3rd party application or techniques.All your advise, help, links to any article would be very much appreciated.Just wanna learn
December 16th, 2009 1:02pm

Hi YgiPossible to setup two SCCM environment ,one to manage server and another to manage workstation.our infra. like this.SCCM for WS with boundary limit and client has auto discovery.SCCM for svr with no boundary and client has auto discovery disabled to avoid conflict with SCCMWS.RegardsKarthick V
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2009 3:40pm

The client on the site server is completely unrelated to the server components installed there and this configuration is supported. As was already mentioned, pay close attention to the boundaries so that theclients on Config Mgr servers are assigned and communicating with the correct site/hierarchy. You may want to manually install the client on the servers or push them in small batches or one at a time to double check your settings. I'm assuming you are doing this because you require different settings and policies for servers than you require for clients.One thing to watch for is when the client is co-located with the management point since they share binaries. The client cannot have a higher major version than the management point and it is recommended to keep them at the same version if possible. This makes upgrade scenarios interesting, if your server management infrastructure (SCCMSVR) is upgraded and your client management infrastructure is not (SCCMWS), the client on your MP in SCCMWS won't upgrade but should continue to function as will the MP on that computer. Once you upgrade the SCCMWS infrastructure to the same version as SCCMSVR then the MP in SCCMWS can be upgraded. Stan
December 16th, 2009 7:49pm

Thank you guys for the response on this. I'll just have to make sure that there are not conflicting boundaries. And when installin the client, make sure the site code is directed to the SCCMSVR.Just wanna learn
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2010 2:55pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics