Re: SMS 2.0 Re-Install Problems

From: Ross Jonas (Ross.Jonas_at_No.Transport.sa.SPAM.gov.au)
Date: 06/03/04 

Date: Fri, 4 Jun 2004 09:14:53 +0930

Our SMS2 User is in the Domain Admins group.

Currently there is about 1100PC's in our SMS "All Systems Collection" with
about 100 of these assigned but not clients. We are using Logon Script
installation , with a manual SMSMan commandline installation being done.

This is happening at multiple secondary sites aswell as the primary site
where most clients seem to assign correctly but others are missing the boat
with the ABEXPERT error in their CCIM log files(on the client).

Back on the server, there are issues in the CCM.log file showing SMS cant
connect to some of the PC's via the Admin$ shares with the SMS account. We
did have c$ and admin$ shares turned off via a group policy but thats since
been re-instated.

Any other idea's ?

Thanks

Ross
"Richard Threlkeld <MVP>" <pleasenospam@hotmail.com> wrote in message
news:%23D5Gj9GSEHA.2468@TK2MSFTNGP11.phx.gbl...
> Have you specified a valid Client Connection Account with access to the
CAP
> and ensured that it is a member of the Domain Users group?
>
> --
> Richard Threlkeld
> Microsoft MVP - SMS
>
> Management Blog: http://www.msmvps.com/Threlkeld/
>
> Join the SMS email discussion list today:
> http://lists.listleague.com/mailman/listinfo/mssms
>
> "Ross Jonas" <epoch@adam.com.au> wrote in message
> news:OMw64pDSEHA.2772@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > I recently re-installed SMS 2.0 (and went straight to sp5) on our
primary
> > site , after having formatted the server and de-installed all the
> secondary
> > sites previously.
> >
> > Im having issues getting clients into SMS, the Clients are assigning to
> the
> > correct IP boundry then saying they cannot find a CAP to continue, while
> > other pc's in the same physical network are assigning and becoming
> clients.
> >
> > Both sets of users are running the same installation script.
> > An example of the error im getting is ABEXPRT:\\CAP List for site WV1
not
> > accessible
> >
> > I have checked licencing on the server and everything is in per seat
mode
> > that i can see.
> >
> > Any idea's ?
> >
> > Regards,
> >
> > Ross
> >
> >
>
>

Relevant Pages

  • Re: Client push works but doesnt...
    ... If so have you extended the schema for SMS? ... This will allow you clients to search AD for the Site and MP that they ... > After reassigning all resources to the primary site I can now make all> machines at the secondary site connect to SMS by manually entering the site> code in Control Panel -> Systems Management on each machine. ... Am I right in assuming that the same discovery mechanism> is used here as is used for assigning the correct site code within SMS? ...
    (microsoft.public.sms.setup)
  • Domain Admin Acct
    ... With SMS 2003 Deployed, supporting 15,000 mixed clients in an NT domain and ... local admin rights and no domain admin rights ... How do you troubleshoot corrupt clients or run scripts or do manual client ...
    (microsoft.public.sms.misc)
  • Admin Acct
    ... With SMS 2003 Deployed, supporting 15,000 mixed clients in an NT domain and ... local admin rights and no domain admin rights ... How do you troubleshoot corrupt clients or run scripts or do manual client ...
    (microsoft.public.sms.admin)
  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Changing Site Boundaries
    ... SMS has been working great. ... Site Boundaries are setup using IP Subnets. ... subnet for all servers. ... Office using a known good package but the clients could not Locate the DP. ...
    (microsoft.public.sms.setup)