Friday, 15 February 2013

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 7: Client and Client Agents

Back to main menu

Part 7 describes the initial configuration of the Config Mgr Client Agents and the process of deploying the Config Mgr Client to your estate. 

1. Client Agents

Browse to Client Settings and configure the Properties



Typical configuration is shown



Config Mgr Clients will report to Config Mgr Management Point every 15 minutes (default is 60)


Enter your Organisation Name here. It will be displayed on Task Sequence progress bars


Default computer retart is 90 minutes


Configure EndPoint Protection if you are licensed to do so








Add Inventory Schedule and configure to search for .exe files





User Device Affinity can determine the Primary Device of a user - these are the default settings

2. Install Config Mgr Client

Highlight the discovered devices, right click and select Install Client












View client installation progress using the ccm.log


See clients appearing in console


Open Control Panel on client and open Configuration Manager applet. Browse to components. See the enabled components that we selected while configuring the client agents
Posted by at
Labels: , ,

28 comments:

  1. Unknown2 June 2013 at 15:51

    Dear Gerry
    SCCM Client agent not installed until i added SCCM Computer account in Domain Admin Group and local administrator group on client machine
    please correct me ? is this required for correct installation or not
    Thanks

    ReplyDelete
  2. Unknown2 June 2013 at 16:33

    Dear Gerry
    is it possible when you comment on our requests. the blog send automatic notification on personal mail.
    thanks for your efforts

    ReplyDelete
  3. Gerry Hampson3 June 2013 at 09:17

    It's best practice to configure a Client Push installation account (if this is not configured SCCM tries to install a client using it's computer account).

    The client push installation account must be a local administrator on all the devices that need clients. This can be achieved using Active Directory Restricted Groups. Making the account a domain administrator is the lazy way to do it and is not best practice.

    ReplyDelete
  4. aMe@aBeN15 June 2013 at 06:14

    Dear Gerry
    I Follow step by step your guides but during the client push installation, the client receive the installation files and stored in the C:\Windows\ccmsetup. I monitor the process ccmsetup.exe at the task manager (That's mean the installation is started). My problem is the installation seems failed because agent is not installed. I open the ccmsetup.log and receive error message "CcmSetup failed with error code 0x80004005". At the ccm.log I found an error message "Unable to connect to WMI (root\ccm) on remote machine "EP1", error = 0x8004100e. The client OS is Win 7 Pro x64. Thanks.

    ReplyDelete
    Replies
    1. Unknown30 October 2014 at 20:17

      I had a similar problem. After looking at the computer's event viewer I found the BITS service was disabled. After I enabled/started the service, the client installed properly.

      Delete
  5. Gerry Hampson16 June 2013 at 19:15

    Is this a general or specific issue? Examine the ccm.log file on the server.

    ReplyDelete
  6. aMe@aBeN17 June 2013 at 07:36

    Hi Gerry
    This is a general issue. All the client push installation failed and in the ccm.log, there is an error message "Unable to connect to WMI (root\ccm) on remote machine "WINDOWS7EP", error = 0x8004100e."

    ReplyDelete
  7. Gerry Hampson19 June 2013 at 11:56

    "Unable to connect to WMI (root\ccm) on remote machine "WINDOWS7EP", error = 0x8004100e."

    Config Mgr tries to connect to the clients using both it's computer account and the client push installation account. It's quite possible that one of these has failed to connect and these are the errors you are seeing - that's fairly normal. What's important is that you said the files are copied to the clients. This means that the initial connection has been made so these errors can be ignored.

    The problem seems to be the local client installation afterwards.

    CcmSetup failed with error code 0x80004005

    This is an unspecified error. There must be more information in the log. Have you configured a boundary group and added your boundary and DP to it?

    ReplyDelete
  8. aMe@aBeN20 June 2013 at 07:35

    Yes. I already configured the boundary group and added the boundary and DP to it.

    FYI, during installation of SCCM 2012 SP1, I got an error message "CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e" in the ConfigMgrSetup.log. Is it related to my client push installtion issue?

    Thanks for your reply.

    ReplyDelete
  9. Unknown20 April 2014 at 04:13

    Hi Gerry,

    With the help of your guide i have so far working clients and i even captured profiles using USMT 8.0 version, and restored profiles using USMT again.
    thanks a lot to you!!

    Now i am trying to create an image from windows 8 machine using SCC 2012 R2.
    but facing issues like,,

    ( i already have Restricted Group configured for network account and local administrator account)

    1 i installed windows 8 on a client machine, but i can't install client agent on this machine.
    2. Please help me with the best and detailed way to install client on machines.

    3. the machine i am trying to install client on, should it be domain member or workgroup.
    because if i join client machine to domain, only then i see "Restricted Group" as a member of "Local Administrators" group.

    If i leave it to workgroup, i don't see "Restricted Group" as a member of "Local Administrators" group.

    Thanks!

    ReplyDelete
    Replies
    1. Gerry Hampson22 April 2014 at 17:19

      This is my preferred way of creating customised images (using MDT). You don't need to worry about clients or Restricted Groups for this.

      http://www.gerryhampsoncm.blogspot.ie/2014/03/create-customised-reference-image-with.html

      Delete
  10. Unknown22 May 2014 at 21:05

    Hi Gerry, I have a question. I can't install the client agent in my management server where deployed the SCCM 2012.

    ReplyDelete
    Replies
    1. Gerry Hampson23 May 2014 at 11:54

      You haven't given enough information. What happens when you try to install the client?

      Delete
  11. Unknown8 June 2014 at 12:44

    Hi Gerry,
    I have a SCCM 2012 R2 environment, and performed all the configuration according to your previous posts.
    Now I'm trying to install the client on a Workgroup client server.
    I did the following steps:
    1. Checked Management point record in DNS is available.
    2. Changed DNS IP address on client to my domain environment & Enabled NetBIOS on TCP option in advanced features.
    3. Edited LMHOSTS & HOSTS file.
    4. Mapped the \\SCCM\SMS_SITE\CODE\client folder to network drive Z:.
    5. Ran the ccmsetup.exe with following parameters: CCMSetup.exe SMSMP=sccm.server.lab.local /logon SMSSITECODE=P01 /source:z:

    The setup runs fine, with configuration manager appearing in Control panel. But when i checked its properties, I saw it wasn't assigned a Site.
    Checked logs and saw errors it could not assign site and also it could not contact MP.
    Could you tell where I'm going wrong. Could you guide how to edit the LMHOSTS file correctly, and how to check if Workgroup computer can contact MP.
    Greatly appreciate if you suggest some step by step blog that I can follow.
    Thanks in Advance.
    Jose

    ReplyDelete
    Replies
    1. Gerry Hampson9 June 2014 at 15:31

      This blog post explains the process well:

      http://eskonr.com/2013/08/sccm-configmgr-2012-manage-workgroup-computers-for-deploymentremote-tools-etc/

      Delete
  12. Unknown25 November 2014 at 18:55

    Hi Gerry, I am not able to get my remote office computers to use the local distribution point for SCCM client installs. Even though I have setup boundary and boundary groups all pointing to the dist point. They continue to come back to the site server for the client. Is there something specific that has to be configured to get the clients to grab the install form the dist point server instead of the site server?
    thanks!

    ReplyDelete
    Replies
    1. Gerry Hampson27 November 2014 at 07:51

      Have clients EVER used the local DP? Is there something wrong with it? Check distmgr.log file for clues.

      Delete
  13. Anonymous13 January 2015 at 13:58

    In SCCM i get the Test-PC ans start the Client installation. On the Test-PC i can see the ccmsetup in the task manger and under Windows/ccmsetup i can find the install-Data, but the Agent isn't installed. Can you help me with my problem?




















    ReplyDelete
    Replies
    1. Gerry Hampson16 January 2015 at 17:10

      Do you mean the agent is not installed or the console does not report that the agent is not installed? Have a look in Control Panel? Is there a Configuration Manager applet? If so the agent has successfully installed and your problem is elsewhere.

      Delete
  14. Unknown14 January 2015 at 11:10

    Thanks Gerry for your great effort,

    I configured a new server 2012 R2 as per your procedure and its working fine.
    But In some client, while clicking find site in server able to find but same while clicking OK its throwing an error not able to connect.
    In some clients find site option in SCCM client is not getting enable.
    Steps Taken
    Enabled forest discovery and enabled automatic creation of site boundaries and IP address range
    Enabled all discovery methods
    Created a boundary & boundary group and assigned site and enabled use this boundary group to enable site assignment.
    But still problem remains same.
    Clients connected with server subnet are able to connect with server.

    Please reply.

    Thanks

    ReplyDelete
    Replies
    1. Gerry Hampson16 January 2015 at 17:17

      You're welcome Dinesh. Did you solve this? Did you check that there are indeed boundaries that cover all your clients?

      Delete
  15. Anonymous23 February 2015 at 13:47

    Hi Gerry,

    When we enable Automatic sitewide client push, will it install the client agent only for the first time, or will it continue to install client agent as computers are discovered by discovery methods. Please clarify.

    ReplyDelete
  16. justme28 January 2016 at 15:09

    Hi Gerry,

    If i don't want to use predefined rules (File/Printer sharing and WMI) and use Port based rules (445 and 135 ), what other ports do i need to open to enabled client push?I have tried opening those two ports but i can't deploy till i use predefined firewall rules which i am trying to avoid.

    ReplyDelete
    Replies
    1. Gerry Hampson28 January 2016 at 15:45

      You will find that here - Ports that are used with client push installation
      https://technet.microsoft.com/en-us/library/gg682180.aspx?f=255&MSPPError=-2147217396

      Delete
  17. Unknown8 November 2017 at 20:35

    Hi Gerry, the client push installation failed and in the ccm.log, there is an error message "Unable to connect to WMI (root\ccm) on remote machine "Windows 10", error = 0x8004100e. On the PC i can see the ccmsetup in the task manger and under Windows/ccmsetup. I am new on to this could you please help.

    ReplyDelete
  18. socarandy7 December 2017 at 18:09

    Hi,
    Can I make an internet Base machine a DP.
    Randy

    ReplyDelete
    Replies
    1. Gerry Hampson11 December 2017 at 15:22

      No, you can only select an on-premise or cloud based computer.

      Delete

Subscribe to: Post Comments (Atom)