locked
SCCM 2012 Reinstall - Client Status RRS feed

  • Question

  • I'm wondering what the implecations will be by removing SCCM 2012 from our environment to reinstall it?  It has been installed on about 1100 clients, and I want to ensure those clients will check back in to the new install.  We also have Endpoint Protection running on several clients.  Are there any guides for this procedure?
    • Edited by aacajo Friday, October 4, 2013 3:00 PM
    Friday, October 4, 2013 2:57 PM

All replies

  • Why do you want to reinstall at all?

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

    Friday, October 4, 2013 3:00 PM
  • Looks as though the initial setup was done incorrectly, since they're not using SCCM for anything but Endpoint Protection I figured I'd save myself some troubleshooting time and install fresh.  Looks like there's port conflicts, SQL is running as "Administrator", and a few other things.  The MP keeps spitting out these errors which seem to be fairly generic.

    Call to HttpSendRequestSync failed for port 80 with status code 404, text: Not Found

    Friday, October 4, 2013 3:04 PM
  • I'd probbaly fix it but if you want reinstall it that's fine too. Personally I'd uninstall the clients first. They won't just "check-in" to a new environment, you'll have to force the client to reinstall. Make sure to use a new site code.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Friday, October 4, 2013 3:42 PM
  • Why a new site code?  Any input on the Endpoint Protection Client?

    Friday, October 4, 2013 7:15 PM
  • Because you should never reuse a site code. That could really break things in an environment where clients had been assigned to the site.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Friday, October 4, 2013 8:19 PM
  • If I uninstall current site, then reinstall site with new site code will clients automatically get the new site code via client push (Including the Security Client)?

    I'm working on a script to uninstall both clients at computer shutdown via group policy scripts, but I know not all of them will reboot by the time I need to build the new server.

    Wednesday, October 9, 2013 4:13 PM
  • If you can use CM to distribute a package you can uninstall the client by doing ccmsetp.exe /uninstall.

    Once the old site is gone, remove everything from the System Management container and reinstall. When the client installs they will get the correct site code.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, October 9, 2013 6:33 PM
  • I can't deploy packages right now with SCCM.  Clients are unable to check in to the site.  The group policy is working fine so I'll go down that road for the uninstall.

    I'm just wondering what happens if I try to client push a new site code to a machine that already has both clients on it?  The reason I'm asking is I know not every single computer will be able to run the GP by the time I need to spin up a new server.  There will be "one offs" that still have the software stuck on their machines when I deploy fresh.

    Friday, October 11, 2013 11:13 PM