Search the Community

I have been tasked to make a change to a currnt SCCM Env', at present they have Primary site - Severs only are managed here and the server support team mange the whole environment we are looking to add secondary site - this will be used to manage the workstations, a team of EUC sepport will manage the devices, but will have no access to the primary site. The SCCM will soo move to Co-Management the comapny does not want to move to CAS will a primary site do what we want, i have heard that in Co-Management the secondary site cannot be managed from its MP but only from the primary site any advice guys?

Hello, I am looking for some design recommendations for my test environment that I would like to apply to one production environment. I am working with 2 domains (2 forests) with no trust relationships. Domain A : internal Domain B : DMZ From a firewall point of view, only the ports from the internal to the DMZ will be opened. From the internet to the DMZ, only HTTPS will be opened. Currently, I only manage the clients connected to the internal domain. I would like to deploy a new management point in DMZ that will allow me to manage my DMZ clients and my Internet clients. Should I use 2 management points : - one for the DMZ clients - one dedicated to my internet clients If I use only one MP, should I allow Intranet and Internet clients ? The only documents I can find on Technet require too many ports to be opened in the firewall (From DMZ to Internal) and can't be applied to my environment. Thanks.

Hey Guys / Niall - I recently started in a new position to help implement and advise on SCCM 2012 (1511) as well as the setup of all features including converting them from using imaging to OSD, Application deployment, Software Updates, etc - at least all the basics except for Forefront. Quite a task, but sounds fun to me. I learned something today which I'm questioning so wanted to post and get opinions. I've implemented SCCM in about 5 production environments before and for each one; have had at least a distribution point at each local site. If a site didn't have one; it was understood that they would only experience limited support. Today, I found out that our multiple point site will only have a total of 3 DPs - and - they were told this would be ok by Microsoft - even for using OSD at each one. Microsoft's Recommended Plan The ~30 locations are spread out around the country. Each of these 30 locations connects to one of 3 datacenters via various speeds of connection like T1, 500k, (some fast, some really slow). I was told that "Microsoft advised" that it would be ok for them to create a distribution site (they are actually doing secondary sites) in each of the 3 datacenters. The primary server (4th site server) is offsite from the corporate office in a datacenter that we have a 100mb connection to. Overall I understand that having a 100mb connection to the primary may not be the worst thing ever for doing something like OSD if only running 1-2 at a time, but cannot imagine supporting OSD at all 30 of these locations with the setup above - even with BranchCache - not to mention all other services. So - what are your thoughts? Am I just crazy to think this or do you believe we have a problem on our hands? Thanks Guys!

Hello guys I need help in design in (AD) and SCCM 2012 my topology is : central site (HQ) and 16 branches each branch have 15 users and connected via IP-VPN to central I cannot make additional domain or even RODC in the branches , I just organized them by create OU for each branch My Question : what's the best practice to organize and manage those branches (in domain controller and in sccm) thank you all