locked
Discovering groups and AD objects RRS feed

  • Question

  • Hello,

    Outside the help of these forums, TechNet articles and other online forums (Windows-Noob) I am on my own migrating from SCCM 2007 to 2012. So This question is more a logistics thing. I know how to discover AD Objects, but what I don't want is for SCCM 2012 to take over. I have noticed in the OU that I am pulling computers from for testing that other computers outside that OU showed up in the Console as active clients, but checking the computer they still have the old agent, which is fine for now, don't understand why they showed having the Client installed...

    Here is my fear and what I am trying to avoid. I fear that I will discover 4000+ computer and server objects, the new agent will install automatically. I want to discover all AD objects and push the agent to a select 10 computers, then later the rest of the IT department, then after a while start migrating the rest of the computers.

    Another thing I do have to account for is keeping the current 2007 system up and responding to client requests, except for the 2012 clients I have updated, so between 2007 and 2012 they will have overlapping boundaries, not sure if this matters or not.

    So, is there a safe way to do this?

    Thanks!

    Wednesday, September 18, 2013 4:55 PM

Answers

  • So, don't enable auto client installation and just selectively push the agent to clients and/or collections as needed.

    Jason | http://blog.configmgrftw.com

    • Marked as answer by RCCMG Friday, September 20, 2013 2:47 AM
    Wednesday, September 18, 2013 6:47 PM
  • Overlapping boundaries (for site assignment) are not supported.
    That's unrelated to the issue you're experiencing. You have to double check the assigned site on a client.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by RCCMG Friday, September 20, 2013 2:46 AM
    Thursday, September 19, 2013 4:30 PM

All replies

  • One way to do this is to define the boundaries of only that group of computers that you want to migrate.  The computers must belong in a boundary in order to be site clients and that boundary must be defined in some boundary group.

    Clients that are outside of the defined site boundaries will not be installed.  As you progress further along you can add additional site boundaries to the boundary group.


    Thanks, Mark

    Wednesday, September 18, 2013 5:13 PM
  • That would work, except the way our network is the range of computers in that boundary is way beyond just the ones I want to test with.

    Wednesday, September 18, 2013 5:24 PM
  • So, don't enable auto client installation and just selectively push the agent to clients and/or collections as needed.

    Jason | http://blog.configmgrftw.com

    • Marked as answer by RCCMG Friday, September 20, 2013 2:47 AM
    Wednesday, September 18, 2013 6:47 PM
  • Is it normal behavior for SCCM 2007 clients to show active in SCCM 2012?

    Thursday, September 19, 2013 3:04 PM
  • What is assigned site of SCCM 2007 when the it show active in SCCM 2012.

    Configuration Manager 2007 clients do not check for the site version and can incorrectly assign to a System Center 2012 Configuration Manager site.


    Juke Chou
    TechNet Community Support

    Thursday, September 19, 2013 3:25 PM
  • So by that, are they actually allowing the new Site to take over or do they still respond to the old site?
    Thursday, September 19, 2013 3:27 PM
  • Clients will never be reassigned automatically. This has to be done manually or by script etc. What sitecode does the CM07 client display?

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, September 19, 2013 3:51 PM
  • Ive been removing them as a couple popped in for some reason, but in the console they showed CM1, which is the Site Code for SCCM 2012. I didn't check the PC though.
    Thursday, September 19, 2013 4:08 PM
  • Are they within the boundaries of the CM2012 site?  You may want to investigate as like Torsten has said the clients will not automatically reassign themselves to another site.


    Thanks, Mark mark.mears@cireson.com Check out our System Center App Store: www.cireson.com/app-store

    Thursday, September 19, 2013 4:18 PM
  • As stated above, they do share the same boundaries. Due to the way our network is setup I don't have much of a choice on this.

    Thursday, September 19, 2013 4:22 PM
  • Overlapping boundaries (for site assignment) are not supported.
    That's unrelated to the issue you're experiencing. You have to double check the assigned site on a client.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by RCCMG Friday, September 20, 2013 2:46 AM
    Thursday, September 19, 2013 4:30 PM
  • Ok - I am going to discover some more computers today. Trying to take this in strides. Will update what I see on those clients.
    Thursday, September 19, 2013 4:32 PM
  • Well, I didn't see the same behavior I saw the other day today. I will keep an eye out. Torsten, could you elaborate on what Overlapping boundaries are? I guess I am missing the point on what they are. I thought overlapping is both systems sharing the same boundaries, which seems like it would be the only likely-hood since I cant imagine IP subnets changing when a new system is brought up like this.

    If you have a link that explains this I would appreciate it, otherwise I will search the web to gain an understanding of this.

    Thanks everyone for your assistance.

    Friday, September 20, 2013 2:46 AM
  • Overlapping = the same boundary (AD site, subnet, IP address range etc) is used in both ConfigMgr sites. It's not a problem for content locatio boundaries, but for site assignment.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, September 20, 2013 7:22 AM