• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4328
  • Last Modified:

SCCM - Clients cannot find site

Hi,

I have having trouble getting an inventory off any clients on a new SCCM 2012 server install.

I followed a set of instructions to get everything installed and all seemed to be going well, that was until I tried to get an inventory off the first test PC. Every client gives the error shown on SCCM.jpg attachment. The only one that inventories properly is the server itself.

I have researched the error but have been unable to find anything that can solve this problem.

Things I have done:

Active Directory schema has been updated (Forest level) Container added (Child domain where the server is located)

I have setup boundries and boudary groups and sites have been assigned.

I management point and fallback status point rolls and set up.


Please ask for anymore information if required

Josh
sccm.jpg
0
dgewin
Asked:
dgewin
  • 12
  • 7
  • 4
1 Solution
 
Element1910Commented:
Can you copy/paste or upload your ClientIDManagerStartup.log and contentLocation.log?

If you don't want to share this information, do that manual method of assigning a site code to your clients: In Control Panel, in Configuration Manager, specify the site code of your site.

I'm guessing there may have been something left out of the client push installation properties that your clients are for some reason unable to communicate back to the Site.
0
 
dgewinAuthor Commented:
Hi

Here is the ClientIDManagerStartup.log from one of the clients, the other log file I cant find.

I have tried manually adding the site code with no luck, still the same problems
ClientIDManagerStartup.log
0
 
Element1910Commented:
Ok, ClientIDManagerStartup.log shows that the client finally got registered. The other log file should be on the Distribution Point or the Site server itself...most likely the DP though. Check again if you can :)
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Element1910Commented:
Another thing you may want to try is to ping the management point from one of the clients to narrow down if it's a network issue or a client configuration issue.
0
 
dgewinAuthor Commented:
There is a "ClientLoacation.log" file on the server, but no "ContentLoacation.log"

There are no communication errors from the clients to the server, I can ping and also access port 80 through a web browser.

Its a single install, so the site server is also the DP in this case
0
 
Element1910Commented:
Ahh...my mistake...yup, ClientLocation is what I needed. Doing this from memory and haven't touched SCCM in almost 3 years ;) Uplaod that ClientLocation log if you could.
0
 
dgewinAuthor Commented:
Here is the client location log
ClientLocation.log
0
 
Element1910Commented:
Dang, that looks good too. Try looking at, or uploading the ccmexec.log. Basically we are just going through the logs to determine where the issue is. Try to run some fresh inventories on a client and make sure all the information we are going through is for sure current. Do this on a client:

1. Start -> cmd -> net stop ccmexec
2. Delete all client log files
3. Start -> cmd -> net start ccmexec
4. From the client GUI of Configuration Manager, click on the "Actions" tab then initiate a hardware inventory
5. Look at the InventoryAction.log

Make sure it's successful....tell me what you get. If successful it should say something like "Successfully sent report." or "Action Completed."...let me know.
0
 
dgewinAuthor Commented:
I removed all of the logs and went to the GUI on the client, The only options I have under the actions tab are

1. Machine Policy Retrieval & Evaluation Cycle
2. User Policy Retrieval & Evaluation Cycle



Also I have checked that ling before :)
0
 
Element1910Commented:
Ok, then run both of those, starting with machine policy first. It will put the other in a queue so you shouldn't have to worry about running them fairly close to each other. Give it a few minutes, then keep refreshing the Action's tab by simply clicking another tab or reopening Configuration Manager...hopefully that will reset your policy properly. You can also look at the client logs for this (namely the ones we spoke of previously, as well as ccmexec.log).
0
 
Nagendra Pratap SinghCommented:
What is the discovery type you have chosen to use?

What is the guide/white paper you have used to implement this environment?
0
 
dgewinAuthor Commented:
I have that with the same result as every other time, nothing seems to happen

I have been looking through several logs to try and see what might be happening

I attached the Policy Agent log, not sure whether that gives any insight.
PolicyAgent.log
CcmExec.log
ClientLocation.log
0
 
dgewinAuthor Commented:
The discovery methods I am using currently are :

AD Forest Discovery
AD System Discovery
AD User Discovery
Heartbeat Discovery.

I have been following CBT nuggets, as well as generally checking other websites etc. but mainly the nuggets.

Everything discovers fine, gets matched up to a site etc. using the boundries, but for some reason the clients wont talk to the site properly once the agent is installed (used a push install and manual install for testing). So I am unable to get an inventory or aything from the PCs with the agent installed. everyelse seems to be ok
0
 
Nagendra Pratap SinghCommented:
Can you check the alerts on the bottom part? Can you see any entries inside System management container?

BTW have a look at this guide and if needed rebuild your environment.



http://www.windows-noob.com/forums/index.php?/forum/92-configuration-manager-2012/
0
 
dgewinAuthor Commented:
Recent Alerts - none

There are entries in the System management container

As far as I can tell from that guide, the installation looks the same as what I used
0
 
Nagendra Pratap SinghCommented:
My net is slow today so cannot offer a screenshot, but try to find the equivalent of alerts.

Try looking under the monitoring section on the bottom. You may find some alerts there.

Is your SCCM server also running a client? Can you move a workstation to the same OU etc so it gets the same policy and reboot it?
0
 
dgewinAuthor Commented:
Hi,

I had a look under monitoring, there were no alerts at all.

Yes my SCCM has a client and it works perfectly.

I have a test server in the same OU with the client also installed, but that has the same issue as all of the other clients, cannot find the site server.
0
 
dgewinAuthor Commented:
I have read in places that this can be caused by active directory issues

Does anyone know what I should be looking for in particular in AD that might cause this?
0
 
Nagendra Pratap SinghCommented:
You can run DCDIAG and netdiag tools.

For the policy you can monitor it by using policyspy tool.


http://anoopcnair.com/2012/06/28/sccm-configmgr-2012-how-to-use-policy-spy-polic yspy-exe/


Also have a look in the client policy logs using trace32/cmtrace.
0
 
dgewinAuthor Commented:
Hi,

I had a look at one of the clients with the deployment monitor

I have posted a screen dump, seems like there is a bit of information missing
deployment.jpg
0
 
dgewinAuthor Commented:
Thanks to everyone for your help, After everything that happened, it turned out to be Nod32 antivirus that was blocking it, even though there was no firewall component to it.

I removed it as a part of a change over to a new anti virus and everything started working
0
 
dgewinAuthor Commented:
I found the problem within my own network
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 12
  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now