Re: SMS 2.0 Re-Install Problems

From: Richard Threlkeld (pleasenospam_at_hotmail.com)
Date: 06/02/04

  • Next message: Richard Threlkeld : "Re: Client Push installation"
    Date: Wed, 2 Jun 2004 00:01:09 -0700
    
    

    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
    >
    >
    

  • Next message: Richard Threlkeld : "Re: Client Push installation"

    Relevant Pages

    • Re: Client Install Location (not just SMSMAN)
      ... we did try assigning that "server share" ... is cannot be used as a remote CAP for an SMS 2003 site. ... "all-in-one" package (as in the client.msi for the advanced clients) without ...
      (microsoft.public.sms.misc)
    • Re: Client Install Location (not just SMSMAN)
      ... That machine just has to be a share on the server machine which is created ... IF you are asking about manually just creating a share and putting the cap ... > what if that "CAP share" is just an "NT box share", its not an SMS server ... > You can then create a script that runs for those clients pointing to a ...
      (microsoft.public.sms.misc)
    • Re: Hardening CAP Permissions
      ... Cathy is completely correct. ... Legacy clients need the CAPS open, because they have no form of Client ... > can't report DDRs, inventory, or status messages, which means the CAP is ...
      (microsoft.public.sms.setup)
    • Re: Routing Question; Plan B
      ... Local being my country's internet which all falls within ... The other is slower and provides unlimited "local" route ... SlowModem for internet access _only_ when near/at the bandwidth cap on ... route to 196.0.0.0 with gw=Linux box IP to the clients, ...
      (comp.os.linux.networking)
    • Re: Hardening CAP Permissions
      ... you really have to get rid of those Legacy Clients ... Windows Enterprise Management Division User Assistance Check out the SMS Technical FAQ: ... > Our security people are concerned that failing to harden the CAP could> allow a user to inject rogue data into the site server through the CAP. ... > Given that users have RWX permissions to the following folders beneath> the CAP; ...
      (microsoft.public.sms.setup)

  • Quantcast