Of course, this is just my opinion only; but for what you describe, if they want to pick up and move the whole thing elsewhere, you'll want to have completely independent ConfigMgr infrastructures; one for company1.com, one for company2.com, etc. etc. Naturally I'm just guessing; it may be more complex (or less complex) than I'm thinking it needs to be. I for one would avoid like the proverbial plague any kind of CAS. Just... don't. Also, seriously, carefully consider all of the arguments about having SQL off-box for ConfigMgr... and then dismiss all that and keep it local. If you need ammunition for why local is better, just ask this list. but hopefully you don't have people fighting you on that. ... and there's CM design in a nutshell. KISS.
Sherry Kissinger ________________________________ From: "Orlebeck, Geoffrey" <[email protected]> To: "[email protected]" <[email protected]> Sent: Friday, May 9, 2014 3:43 PM Subject: RE: [mssms] RE: Brand New to SCCM Thank you all for the responses. I’ll definitely be referencing the windows-noob.com site as well as the suggested books on the subject. Not sure I’ll dive into training just yet, but I’ll keep in mind the suggesting on looking to potential “unofficial” training sources. As to Sherry’s post, I’ll just give a bit of detail which may give more clarity. (All this was decided prior to my hiring, my role is to build out and maintain the sister companies networks). We (the parent org) will be hosting the sister companies’ servers, with everything on dedicated VLANs/subnets. We will host/maintain AD/Exchange/SQL/SCCM in their own domains (company1.com, company2.com, etc.) with trusts between any/all that require shared resources. Due to the separate domain(s) and segmentation of the network aspect, in a perfect scenario we would forklift their infrastructure and allow them to place it wherever they want to take it. I’m not naïve enough to think it’s that simple, but once we give them their network as a whole, the onus is on them to make it work wherever they move it. So we’re looking at how we want to implement SCCM. While in the present day we’d love to manage the sister companies from our existing SCCM console (CAS setup, right?), if we need to maintain ability to breakaway, then do we need to build out completely independent SCCM servers for each domain? I’m trying to gather as much information and see how all this works so we don’t start down a path we can’t back out of. But again, to everyone that has responded, thank you for taking the time, I do appreciate it. I’m sure I’ll be lurking on this list to pick up helpful things as they’re discussed. And I’ll likely be asking a lot of questions going forward J Thanks again! -Geoff From:[email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Friday, May 09, 2014 1:26 PM To: [email protected] Subject: [mssms] Brand New to SCCM Quick Background: I was just hired on by a parent corporation that leverages SCCM 2012. They are partnering with smaller companies and building out SCCM servers for each company (maintaining separation if either party terminates relationship). I was hired based on experience with AD/Exchange and the parent company knows I lack any SCCM experience. With that said, I’ve been searching TechNet and other areas of Microsoft’s site trying to find a definitive guide/article about deploying SCCM 2012 (non-R2). I was turned on to this list by a former coworker and I’m just reaching to see if this group has any recommended starting points to read up on SCCM. Specifically on the deployment side of ConfigMgr. I have no clue what other information would be relevant to this post to give to you (due to my lack of any knowledge of SCCM), so if you need any additional info, I will gladly answer as I am here to kindly ask for a little “start here” arrow in the right direction. Thank you very much in advance. -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
