Why is the SCCM client so careful about not installing on DC's?

[AJWhite1970]

Numpty question but I've yet to find a good answer.

 

Rolling out SCCM client to the whole school at the moment and I'm just wondering why you wouldn't install the client on DCs? Is there some technical reason I've overlooked or is it just not good practice if you accidentally send out settings and software to a DC?

 

Thanks

Andrew

[Steve21]

Why wouldn't you? (or what makes you say that as if you shouldn't) I know it's best practice not to install the server on a DC, but never seen any issues with the client?

 

Steve

[Steve21]

 

If you mean that option that's just if you want to manage DCs totally seperate to the SCCM installation, e.g. different teams managing parts of network

 

But just tick the first option and it'll install as normal

 

Steve

[AJWhite1970]

Thanks Steve

 

I was just being ultra cautious as any software that makes you click on something extra in my mind reads as "not good practice but we'll allow it if you are daft enough to tick this box..."

 

I'll roll-out to the DC's as planned

 

Cheers

Andrew

[Steve21]

I mean end of day there's no harm if you want to leave it off, all we use the client for on servers is to deploy updates/AV. No software to the server group (clients separate deployment group to stop any issues as you mentioned)

 

Steve

[sparkeh]

I have the client on DCs to manage AV as well.

 

I think the caution is that with SCCM its very easy to stuff your whole network up if something is not configured correctly. Its not such an issue if you mess up a workstation but breaking a DC could be a big problem. An extra check is probably a good idea

[jertsy]

I have had the SCCM client on my DC's from day one without any issues.