locked
Windows 2003 servers as clients for SCCM 1602/1606 ? RRS feed

  • Question

  • Hi

    We are currently running SCCM 2012 R2 to manage 1000+ servers.

    We would like to upgrade SCCM to the current branch (1602/1606), but we still have about 70x Windows 2003 R2 x64 servers which are SCCM clients and we need to manage with SCCM for about the next 6 months.

    I know its not supported by MS (since Windows 2003 itself is not supported), but does the new SCCM client still install and work ok on Windows 2003 clients ?

    Does anyone else still have Windows 2003 R2 x64 servers as SCCM clients ?

    Ours are remote servers at branch offices so its going to take a while to replace them all with new servers and current OS.

    Thanks

    Mark.

    Thursday, June 30, 2016 1:58 AM

Answers

All replies

  • Windows Server 2003, along with Windows XP is no longer supported as a ConfigMgr Client Operating System.

    Check: https://technet.microsoft.com/en-us/library/mt589738.aspx#bkmk_ClientOS


    Simon Dettling | msitproblog.com | @SimonDettling

    • Proposed as answer by Benoit LecoursMVP Thursday, June 30, 2016 10:49 AM
    • Marked as answer by Frank Dong Thursday, July 7, 2016 11:51 AM
    Thursday, June 30, 2016 3:23 AM
  • Dear Sir,

    Not supported does not mean that the client can't work at all. Actually, it works for those basic components supported at the time the two OS being supported. It's that those new added components haven't been tested against those unsupported OSs.

    What does not supported mean by Microsoft:

    https://blogs.msdn.microsoft.com/pcreehan/2007/05/04/what-does-unsupported-mean/

    Best regards

    Frank


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




    • Edited by Frank Dong Thursday, June 30, 2016 8:33 AM
    Thursday, June 30, 2016 8:24 AM
  • We are in the same boat - we are planning an upgrade to 1602 and above but would like to find out if Windows 2003 SCCM client will continue to work on the latest SCCM build. We understand that Windows 2003 are officially out of support, but would just like to have confirmation if it will continue to function on the latest SCCM build. 

    Thanks.

    Tuesday, September 20, 2016 9:00 PM
  • So does anyone got the client, CSEP & SUP working on Server 2003 OS or not. I have deployed 1606 client to my 2003 servers right know and the client has been installed but I dont know yet if it will work. Nothing have happend for a wile and I can't find or start Software Center!?

    Anyone got it to work?

    Wednesday, January 18, 2017 5:40 PM
  • Don't care about if the SCCM Agent still works on this outdated and unsecure OS.

    Instead care about the migration to a supported OS.




    • Edited by Michael-CM Friday, January 27, 2017 12:12 PM
    Thursday, January 19, 2017 7:40 AM
  • Works if you have BITS and SP 2 in your 2003 servers.
    Saturday, February 25, 2017 6:27 PM
  • Probably a bit old now, and certainly know that Server 2003 is no longer supported.

    Pulled with v1511 ConfigMgr ...

    https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/removed-and-deprecated-features

    However ... we have fully working the v1511 Client on Server 2003, reporting to v1606 & v1610 Site Versions.

    v1606 Client (RTM, not Update Rollup 1) on Server 2003 had issues.

    v1606 with UR1 may work, as the RTM v1606 Client on Server 2003 had the "CoCreateInstance ContentAccessService failed 0x80040154" issue.

    Shane

    Thursday, April 6, 2017 1:00 AM
  • Pease note that a v1511 SCCM Agent is also not supported anymore.
    Thursday, April 6, 2017 4:53 PM