Anybody Have Two SCCM/MECM Servers/Distribution Points on the Same Site?

[Fazza]

At some point we will be relocating our offices/workshop to the other side of our Academy (the server room is not moving).

 

I'd like to create another SCCM/MECM server to live in the same comms room as the switches we'll be connecting to in our new location so that when we're running task sequences and installing operating system images via PXE booting we wont be hopping all over the network to the other side of the school eating up bandwidth - what's the best way to go about this?

 

Do I just install Configuration Manager on a new server and then distribute the task sequences etc. that we will be using in our new location on it or do I need to configure a secondary configuration server?

[Tys]

Someone with more SCCM knowledge may be able to chime in better and I may be wrong here, but I think you can simply use the Create Site System Server wizard within the console and install a distribution point on the new server. That way you can continue to manage everything in one console, but the content is local to the clients. I suspect you will need to setup a boundary group too.

[Fazza]

Someone with more SCCM knowledge may be able to chime in better and I may be wrong here, but I think you can simply use the Create Site System Server wizard within the console and install a distribution point on the new server. That way you can continue to manage everything in one console, but the content is local to the clients. I suspect you will need to setup a boundary group too.

 

I wasnt sure if I was going to set up a boundary group to a range of IP addresses we can use at our new location or if we were to just create bootable media ISO that has the site of the new SCCM server in it would suffice.

[Fazza]

One step forward, 14 steps back!

 

[Fazza]

14 steps forward and 1 step back!

 

It said it had completed with all green ticks and then I noticed this: