Pfeiffer

Physical and Virtual. The answer I got from Microsoft was interesting to say the least. I assumed that the 35 licenses we have would allow for 35 physical server with two physical processors and 70 VM's (Server OSE's). At least that the way I read it, apparently I was wrong. 1 Physical 2 CPU Server (License = 1 Server ML Standard) 2 Virtual Server OSE's (License = Covered under 1 Server ML as VM's) No, you need three, the server OSE are not covered under the Server ML. *facepalm* What?!?! But...but...but... begin 30 minute debate over verbiage in System Center 2012 R2 Licensing Datasheet. Q: So where is the SKU for a System Center 2012 R2 Client ML for Server OSE's? A: Unfortunately there is no such SKU, but we will mention it to the team that deals with licensing. So now I have resorted to sending pictures, with direct snippets from the Datasheet. Who knows if they will change their tune. I give this about a 2% of positive resolution. I am going to lose, I just need to learn how to accept it with some dignity.

Is it possible you have a Group Policy push that has a conflicting switches? I had something similar happen and there were 3 client deployment methods (Client Push, Group Policy, OSD) and the site code from the GPO was from our old environment.

I would like to manage a Server as a device, I do not want to extend my infrastructure. Here is the scenario in it's simplest form. 1. Build Windows 20008 R2 Server using OSD 2. Join the Domain 3. Add it to a collection. ...and the price quote of is $1,323 - $3,607 (ERP) If I wanted to add a SCCM server to the environment these costs makes total sense. If I just want Software/Hardware inventory this price seems hefty. Having seen a few SCCM environments I know many people have all their production servers listed in a collection. I would be surprised to hear that they have a full SCCM 2012 license per server, but maybe I am wrong.

Here is my scenario and I am hoping someone here can point me in the right direction. Our server team has asked to use SCCM 2012 to build and inventory servers. Using OSD task sequences this is a no brainer. I have done it hundreds of times in the LAB. According to Microsoft I need to buy a Full System Center 2012 License (retails $1,323) per server I build with OSD as it leaves the ConfigManager client on the machine. I keep trying to explain that I need a license (if any) that allows me to manager a server as a device. OSD, HW/SW Inventory, may patching, nothing fancy. Using this cost model I cannot believe anyone uses SCCM to manage servers. Does anyone have a similar experience trying to add servers to SCCM?

I had the same issue. I found adding the server to the Local Intranet Zone did the trick. I am still not certain why Automatically Detect Intranet zone is not picking this up. http://www.cb-net.co.uk/microsoft-articles/34-configmgr/2039-configmgr-application-catalog-login-popup-cross-domain