SOLVED SCCM Development instance

[Brtvngl]

We want to start using a Dev instance next to our production instance of SCCM.
However, looking at the best options where to create a dev instance.
We have a dev domain and a prod domain, but both are child domains of the root, so I'm afraid that installation of the SCCM dev instance will cause issues in the prod environment.

We also have an Azure Dev and Azure Prod instance, but again, they are interconnected.

Is it possible to work out this kind of separate environments, and what is best practice to have them split up that the 2 SCCM Primary site servers don't see each other and start mixing up in AD / boundaries / Azure ...

A second approach would be creating a complete split instance in Azure, without any connection to our current environment, but then everything has to be installed from scratch, causing a lot of extra work for all the different teams involved.

how do you run different Prod & Dev?

Thanks for all the info and suggestions.

Bert

 

[Garth]

A second CM Environment within the same forest/domain will NOT cause problems. I have over 12 CM labs within one domain.

Just don't have overlapping boundaries or better yet have not boundaries within the lab.

 

[Brtvngl]

A second CM Environment within the same forest/domain will NOT cause problems. I have over 12 CM labs within one domain.

Just don't have overlapping boundaries or better yet have not boundaries within the lab.

Thanks Garth, great to hear that.
So if you have no boundaries in the lab, all your dev clients are internet only?
As no boundaries means no boundary groups, and dev clients will not find a way to the dev instance for deployments, policies ...

 

[Garth]

So if you have no boundaries in the lab, all your dev clients are internet only?
As no boundaries means no boundary groups, and dev clients will not find a way to the dev instance for deployments, policies ...

No, no boundaries mean not automatic site assignment. It also mean that clients are considered roaming.

I would still register the site within the system container to make you life a bit easier but other than that, there is nothing to it. Just push the client from the CM console to assign it to that site OR manually assign the site via the control panel applet.