Like i sade in my thread below i have installed the adv.client on the client and the service is started, but it don show in the collection on the site. WHY??
It takes time for the SMS client to report back to the SMS site after the client software has been installed. And even once it reports back to the SMS site server, you may not see it in the Collections immediately.
This is because collections are query based and the queries run periodically. You can force the query to run at any time by doing the following:
Right click the ALL SYSTEMS collection and choose ALL TASKS --> Update Collection Membership
After the Update collection membership runs, right click the collection again and choose REFRESH.
This will force the collection to show the new clients immediately.
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please contact
Do you have any clients? It sounds like you either have an SMS boundary problem or the client isn't talking to the SMs site properly.
To check the client, make sure that you see your components enabled on the client (not just installed). All components get installed by defualt, but they don't do anything until they are Enabled. So, you should see various components enabled on the client machines. You should also check the client to make sure that it belong to the proper SMS site.
On the client, there are various log files, you should look for errors in the client log files: c:\windows\system32\ccm\logs
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please contact
No on the client its say that compenents are installed but not enabled.have try to reinstall adv client over again, but same thing.which log is that i can see this in?
its seems that only have been installed and not enabled.
here is a log from a client.
CAS.Log
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="10:44:49.050+-60" date="01-14-2005" component="ContentAccess" context="" type="3" thread="512" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="10:44:49.050+-60" date="01-14-2005" component="ContentAccess" context="" type="3" thread="512" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="12:07:44.610+-60" date="01-14-2005" component="ContentAccess" context="" type="3" thread="228" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="12:07:44.610+-60" date="01-14-2005" component="ContentAccess" context="" type="3" thread="228" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="13:23:01.173+-60" date="01-17-2005" component="ContentAccess" context="" type="3" thread="2024" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="13:23:01.189+-60" date="01-17-2005" component="ContentAccess" context="" type="3" thread="2024" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="14:45:32.156+-60" date="01-18-2005" component="ContentAccess" context="" type="3" thread="2024" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="14:45:32.156+-60" date="01-18-2005" component="ContentAccess" context="" type="3" thread="2024" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="08:40:59.172+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="2900" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="08:40:59.172+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="2900" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="11:43:48.263+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="1668" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="11:43:48.263+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="1668" file="cachemanager.cpp:1739">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="13:48:14.387+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="176" file="softdistpolicy.cpp:1025">
<![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="13:48:14.402+-60" date="01-19-2005" component="ContentAccess" context="" type="3" thread="176" file="cachemanager.cpp:1739">
have found out now that is about permission rules. Have reinstall the smsserver and run it on standard sequrity mode. before it was in advanced sequrity mode.Now then i run it on standard mode everything works fine.
MAybe you didnd't modify the Active Directory schema? Or maybe you didn't properly give your SMS Site Server's computer account proper access to Active Directory.
I can't tell specifically why this didn't work for you.
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please contact
Well, if you are using SMS 2003 in Advanced Security mode (recommended if you have Active Directory), you will need to modify the Active Directory Schema to add SMS objects to Active Directory. After this is done, you will need to give the SMS Site Server computer accounts rights in Active Directory so that SMS information can be published to AD.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.