locked
Clients migrated but still shown in the old console and active RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    For several time now we did a migration from 2007 agents to 2012. The migration went well but for some they are still in the 2007 console as active and in the 2012 too. When I go on 1 machine I can see that all files and folders are created for the 2012 agent.

    How can it still gives info to 2007 and how to delete those or be sure they are ok?

    Wednesday, June 14, 2017 5:49 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Bring up the properties of such a system and check which discovery method updated it (it's most likely AD System Disc).

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

    Wednesday, June 14, 2017 6:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ConfigMgr 2007 has no built-in process to mark client Inactive so this is not a big deal. As long as the clients themselves show that they are properly assigned to the new site and reporting to it successfully, you can ignore what your 2007 site is "reporting".

    Side question here though: why in the world did you migrate to an old version of ConfigMgr instead of ConfigMgr Current Branch?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, June 14, 2017 2:21 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Bring up the properties of such a system and check which discovery method updated it (it's most likely AD System Disc).

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

    Wednesday, June 14, 2017 6:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ConfigMgr 2007 has no built-in process to mark client Inactive so this is not a big deal. As long as the clients themselves show that they are properly assigned to the new site and reporting to it successfully, you can ignore what your 2007 site is "reporting".

    Side question here though: why in the world did you migrate to an old version of ConfigMgr instead of ConfigMgr Current Branch?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, June 14, 2017 2:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    How are things going? Please let us know if there is any progress.

    If the issue has been resolved, please mark it as "Answered".

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 27, 2017 9:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry for my late reply but I never receive updates on my posts from technet forum :'(

    To answer your question, we migrated to ConfigMgr because we are still in a migrating process 2007 -> 2012 and when it's done (Q4) we will go to 1511 -> 1606 -> 1702 -> ...

    Wednesday, July 26, 2017 8:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That still doesn't make sense. Why didn't you just migrate directly to CB instead of migrating to 2012? Your performing a completely unnecessary migration to 2012.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 26, 2017 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Because the migration began in 2015 and we still have some old clients and because some actual clients wouldn't pay to upgrade :-)
    Wednesday, July 26, 2017 4:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    OK, fair enough. Kind of crazy, but OK. Sounds like you should be charging penalties though.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 26, 2017 4:19 PM