What is the best way to install the SCCM client

[guest]

I had installed the SCCM client a few Panasonic Toughbooks as part of a test to check if we can get the new computers managed as soon as they are joined to our new domain.

The way I did the client install is by copying all the following folders & files from \\Site server\Program Files(x86)\Microsoft Configuration Manager\client

i386

ia64

x64

ccmsetup.cab

ccmsetup.exe

domain-login.bat (\\sccm01\D$\Program Files (x86)\Microsoft Configuration Manager\Client\ccmsetup.exe /mp:sccm01 /logon SMSSITECODE=AUTO)

to the C drive of the relevant computer and running ccmsetup.exe without any switches

It installed without any issues but after it was installed, when I go to Control Panel - Config Manager Properties - Advanced tab and click Discover it says the action was unsuccessfull (the site code in the box is already the correct one but it fails to discover it)

Once this is done I run the Active Directory System Group Discovery and Active Directory System Discovery on the central site server.

I also run the Hardware Inventory Cycle and Machine Policy Retrieval & Evaluation Cycle on the client.

In spite of doing the above the tablet appears in SCCM only after a few hours and shows that is does not have the client and shows N/A in the Approved Column.

What is the best way to install the client on startup so that it can be managed as soon as it is joined to the domain?

In the above senario what should I do to make sure that the computers start showing in SCCM as having the client installed and approved so that we can start pushing out other software without additional delay?

[guest]

I'd consider a GPO startup script: http://social.technet.microsoft.com/For ... c793561ef0

However... it appears you may have other issues; not just "how to install the client"; but it looks like "discovery" isn't working as expected? That's not in and of itself a problem, but it may indicate that you have boundary issues. You'll want to look at the logs on a client to really see if it is detecting a management point. It might not be boundary issues at all... could be something else. I'm just bringing it up as a potential possibility.

As to why it takes several hours to show up in the console; again, there could be multiple issues. It could be that you have a really poorly designed infrastructure; and need better hardware. Or you need to revisit all of your site settings: perhaps you have discoveries defined in a way detrimental to your goals; and are experiencing chronic inbox backlogs.


--------------------------------------------------------------------------------

[guest]

I concur with Sherry. Your process is not necessarily wrong, but there is some technical issue in your infrastrucutre preventing proper functionality; you must first figure out what this is.

What command-line are you using to install the client?

Part of the issue at hand is that you are mixing of what different pieces of ConfigMgr is doing.

AD Discovery has nothing to do with client installation; as it's name imples, AD disocvery simply discovers systems (client agent or not) from AD. There is no interaction with the actual system and thus there is no way for ConfigMgr to know if the cient is installed or not.

Approvals will only happen after the client begins communication with the server which in this case has not happened.

Also, just because the client installed successfully, does not meen it can communicate with the server properly.

Have you reviewed the logs on the client? Specifically, ClientLocation.log and ClientIDManagerStartup.log?


--------------------------------------------------------------------------------