Server 2012 R2 clients

Author
jheaton558
Super Member
  • Total Posts : 74
  • Scores: 2
  • Reward points: 34350
  • Joined: 2009/09/23 13:04:24
  • Status: offline
2013/11/14 13:55:53 (permalink)
0

Server 2012 R2 clients

Current - CM12 SP1, no CU
 
I've had a couple of these being built in our environment.  Currently, it appears that the CM client gets installed, but SCEP doesn't.  The install file gets copied over to the box, but the program doesn't get installed.
 
I'm not looking at going to CM12 R2 yet, but I did see that CU3 adds functionality for Server 2012 R2 clients.  Will this allow SCEP to be installed as well?  I read the description of CU3, and it states:
 
Supported Platforms This update adds support for Windows 8.1-based and Windows Server 2012 R2-based client computers in Microsoft System Center 2012 Configuration Manager SP1. Windows 8.1 and Windows Server 2012 R2 are added to the supported platform list for the following features:
  • Software distribution
  • Software update management
  • Compliance Settings
 
I'm hoping that the Software distribution line addresses my concern, but wanted to verify with you guys.
 
Thanks,
Joe
#1

5 Replies Related Threads

    Riser
    Expert Member
    • Total Posts : 282
    • Scores: 10
    • Reward points: 110830
    • Joined: 2010/04/21 09:37:06
    • Status: offline
    Re:Server 2012 R2 clients 2013/11/14 15:18:26 (permalink)
    0
    Did you set the client policy to manage SCEP? On the SCEP policy, the first two drop downs should be True/Enabled. One is to manage them, the other is to install it.
    #2
    jheaton558
    Super Member
    • Total Posts : 74
    • Scores: 2
    • Reward points: 34350
    • Joined: 2009/09/23 13:04:24
    • Status: offline
    Re:Server 2012 R2 clients 2013/11/14 15:42:33 (permalink)
    0
    I'm not sure what policy you're talking about, but SCEP installation to a new PC goes right along with the SCCM client install.  Everything has been working perfectly there.  The issue is we now have a couple of Server 2012 R2 boxes in the environment.  My coworker was able to get the SCCM client installed, but SCEP wouldn't install.  I've found out today that this is because I don't have CU3 installed, which is what I'm now working on.  Once that's upgraded, I'll push the new client out to my endpoints.
    #3
    Riser
    Expert Member
    • Total Posts : 282
    • Scores: 10
    • Reward points: 110830
    • Joined: 2010/04/21 09:37:06
    • Status: offline
    Re:Server 2012 R2 clients 2013/11/14 16:30:20 (permalink)
    0
    I don't have my lab up right now but you need to set the Client Policy to tell SCCM to install the client and manage it. I would start by verifying your policy is getting deployed down to the client. I believe default settings are to  bring the SCEP installation files down but not to install until you set it within the policy itself.
    #4
    jheaton558
    Super Member
    • Total Posts : 74
    • Scores: 2
    • Reward points: 34350
    • Joined: 2009/09/23 13:04:24
    • Status: offline
    Re:Server 2012 R2 clients 2013/11/14 17:37:43 (permalink)
    0
    Ohhhhh!!! I gotcha now.  The Client Settings policy.  Yes, we do have that set to Manage Endpoint Protection and to Install Endpoint Protection.
     
    My guess is, that in the background, or if I go back and look at the logs, I'll find the error telling me that the current SCEP client doesn't work with Server 2012 R2.
     
    I'm working on planning the upgrade to CU3, but there's a couple of items that I need to take care of first.
    #5
    Riser
    Expert Member
    • Total Posts : 282
    • Scores: 10
    • Reward points: 110830
    • Joined: 2010/04/21 09:37:06
    • Status: offline
    Re:Server 2012 R2 clients 2013/11/14 18:56:09 (permalink)
    0
    Sorry I didn't realize you were talking Win2k12 R2.
     
    http://blogs.technet.com/b/configmgrteam/archive/2013/09/16/support-questions-about-win-8.1-and-winsvr-2012-r2-for-configmgr-and-endpoint-protection.aspx
     
    Yeah, you'll want to go to SCCM R2 but be aware there are some issues with R2 that may delay your decision to move to R2, or at least be in a position to do a site restore.
    #6
    Jump to:
    © 2018 APG vNext Commercial Version 5.5