Yes, big thanks to SCCM 2007. You served us very well. It’s time for you to take some rest. Today (9th July 2019 – It’s already 9th July in India) is the day we should officially say bye-bye to SCCM 2007 with a well-deserved firewall!
It’s the day of 9th July 2019, and SCCM 2007 is officially going away from us. I did learn many things about SCCM from this 2007 version.
I started my device management career with SMS 2003 as an application deployment engineer. But, SCCM 2007 is closer to my heart. With SCCM 2007, I started working on more complex SCCM infrastructure admin-related tasks with more responsibilities.
SCCM 2007 End of Support
Yes, that is true. SCCM 2007 extended support will end today (9th July 2019). So, if you are still using SCCM 2007, please STOP using it.
I know it’s easy to say STOP using SCCM 2007. But, I know the organizations are still using SCCM 2007, and they will continue to use it for many more months.
OK, Are you planning to use SCCM 2007? Let me warn you. It’s a RISKY affair!
Ensure your internal security team is aware that you are using SCCM 2007, a more than 12 years old device management application. Microsoft no longer supports any components of SCCM 2007!
Do you want to know more details about the risks of running an old SCCM 2007 application in your organization? If so, check out the various SCCM KB articles and known issues of SCCM 2012 & CB (Current Branch) versions of SCCM.
How do you migrate from SCCM 2007 to SCCM CB? What are the options to migrate directly from SCCM 2007 to SCCM CB? Do you need to migrate from SCCM 2007 to SCCM 2012?
The answer is NO! You don’t need to go from SCCM 2007 to SCCM 2012 before going into SCCM CB. However, an In-place upgrade from SCCM 2007 to CB is NOT supported. You might need to go through side-by-side migration scenarios.
You might need to create other SCCM CB infrastructure with the latest SCCM version 1902 and migrate SCCM 2007 objects and devices to SCCM 1902. More details on SCCM 2007 migration strategies.
NOTE! – The SCCM 1902 is a baseline version; you can download SCCM 1902 ISO from VLSC or Microsoft Eval center.
What is Next?
OK, SCCM 2007 is gone and dusted. End of Story. What is next going out of support in the device management world (SCCM)?
Next is SCCM (ConfigMgr) 2012! Get ready to migrate to SCCM’s current branch (CB) versions as soon as possible. SCCM 2012 is already out of mainstream support as of 11th July 2017.
SCCM (ConfigMgr) 2012 – Extended Support END date >>12th July 2022
5 thoughts on “Thank You SCCM 2007 Time to Say Good Bye”
I share your same sentiment, I was working in a company where I helped transition from 2003 to 2007 and worked on it for almost 5 years where they were about to migrate to SCCM 2012. I didn’t stay to help them migrate and changed jobs to another company that was in the same position but they didn’t want to upgrade, so I worked on it for another 4 years hoping they would have had the money for CB.
I had at least 9 years of working with the product and it became increasingly difficult to find MS support engineers knowledge in that version. Towards the end of my 4~ years at that company, 2003 server was out of support so we had to build and restore 4 site servers on to Windows 2008 R2 servers and SQL 2008 R2 then built out the infrastructure to support IBCM. Unfortunately, they let us go before I was able to troubleshoot why the patching part wasn’t reporting properly.
Thank you for sharing your story and connections with SCCM 2007 !!
The end of an era in SMS history.
Started my own SMS journey with SCCM 2007 R2, but working in the EduTech space where we are covered by DoE SA’s, I’ve been fortunate enough to be able to upgrade to the latest and greatest as it comes out.
SCCM 2007 could be temperamental, compared to SCCM CB is.
Change is constant in sccm CB. SCCM 2007 was stable like a rock
Yes, Anoop. Very true in the SAAS/IAAS/PAAS world we live in. 🙂