Re: Undiscovered site code



You were correct, there were no subnets attached, it is attached now.
There is a System Management container in the System container for the site.
It has two containers in it, SMS-MP.... and SMS-SLP...., which have no items
in them.

Site code still not being discovered.
Thanks

"Kim Oppalfens <MVP>" wrote:

Seems like your ad site configuration does not have subnets attached.
Check ad sites and services.

Additionally verify whether active directory users and computers has a
system contain (in advanced features view).
This container should have a system management container.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP


"assets411" <assets411@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:32CE82D6-0909-43E1-B9A5-276AB7C08049@xxxxxxxxxxxxxxxx
The ad site name and ip subnet are the same on all three clients,
Default-First-Site-Name and 192.168.1.0. The site and roaming boundaries
are
'assets' (the AD site) and 192.168.1.0.

One other observation; The locationservices log on the clients errors
'attempting to refresh certificate information from (AD and HTTP) - the
error
states 'Failed to update certificate information from (AD and HTTP).

My AD has been sucessfully extended. All three clients have been
discovered
but inventory data is only available for the client on the host/site
server.

Maybe uninstall mannully installed client and reinstall using push? I am
not sure how the maually installed clients obtain connection permissions?
Thank you very much for your help....

"Kim Oppalfens <MVP>" wrote:

Right-click one of the clients in the all systems collection, select
properties.
Note down, ad site name and ip subnet values.

Compare these values to the values on your site & roaming boundaries tab
(in
the properties of your site).

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP


"assets411" <assets411@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CB08EAD5-6A06-4E35-8B23-AED410B198B1@xxxxxxxxxxxxxxxx
As far as I can tell the MP is set up correctly. Everything in System
Status
is green and all tests pass with the MP troubleshooter from tools 2.

"Michel-Vincent" wrote:

Hello

Is your MP correctly set up?
Anything red in Systems Status?

Hope it helps
Cheers

MV
--
Michel-Vincent Leriche
http://mvleriche.spaces.live.com


"assets411" wrote:

I have three agents that I have installed manually by using
ccmsetup.
The
agent installed on the site server, which plays all roles, is able
to
'Discover' the site code through the Systems Manageemnt
Properties/Advanced
tab. The other two clients are unable to 'Discover' the site code
using the
same method on those machines. The AD has been extended and they
are
advanced clients with advance security. Any ideas?
Thank You four your help.


.



Relevant Pages

  • Re: 4913 errors on some sites, but not all
    ... System Management container and all child objects. ... > This is an SMS 2003 installation, not an upgrade, and consists of a> primary site and five secondary sites. ...
    (microsoft.public.sms.admin)
  • Re: Event 4319 after secondary site server rebuild
    ... if I were to delete the system management container. ... What are the exact permissions that should exist on the system management ... Windows Server System SMS - MVP ...
    (microsoft.public.sms.admin)
  • Re: clients not getting assigned
    ... But I am still not sure why my clients ... > I also notice on the 2003 server DC that the System Management Container ... > There is no parent site, no need to forward any site control images. ... > Publishing U2 as a Management Point into Active Directory. ...
    (microsoft.public.sms.setup)
  • Re: Client install
    ... It successfully detected two clients. ... client push installation and I'll try again to install the rest of the ... System / System Management container in AD. ... This site's SMS Service account or the site server's ...
    (microsoft.public.sms.admin)
  • Re: SMS - System Management container
    ... The System Management container is created in the domain where the SMS ... SMS server sits on the child ...
    (microsoft.public.sms.admin)

Loading