To follow on from Trevor’s comment I did a bit of research into this when we started planning our 2012 deployment, and the simple answer is that SCCM primary site roles are not supported on core edition, as there are certain components that require components that are only available when the GUI is installed.
In theory there is a way around it by installing server 2012 r2 full edition, set up SCCM, then turn off the GUI, in saying that you should validate that it would work. Hope this helps Steve From: Trevor Sullivan Sent: Saturday, 2 August 2014 5:59 AM To: [email protected] Andrew, I’m not familiar with the using the Software Center on Windows Server Core. Are you sure that this is a supported scenario? It looks like Jan Egil Ring (fellow PowerShell MVP) has run into the same behavior: http://blog.powershell.no/2013/06/16/automating-the-system-center-configuration-manager-2012-client/ Cheers, Trevor Sullivan Microsoft PowerShell MVP cid:[email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Sanders Sent: Friday, August 1, 2014 1:57 PM To: [email protected] Subject: [mssms] Software Center on Server 2008 R2 Core I am having problems getting Software Center to load on Server 2008 R2 Core. It launches fine on 2012 R2 Core. Has anyone got this working? The SCCM client seems to be functioning correctly, because I am getting inventory data in the system. I suspect it has something to do .NET. I do have .NET 3.5.1 enabled. I get an error message about KERNALBASE.dll when launching scclient.exe. --- Andrew Sanders | Enterprise Systems Specialist Enterprise Systems | Information Technology Services | Appalachian State University 828-262-7803 (p) | 828-262-6034 (f) | [email protected] Peacock Hall - Rm 1127 | 416 Howard St. | Boone, NC | 28608 http://cio.appstate.edu | http://its.appstate.edu | http://support.appstate.edu Microsoft Certified IT Professional | Microsoft Certified Technical Specialist Need Help? Enter a Support Request at http://support.appstate.edu/help
