Re: SMS Client issue

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 07/09/04

  • Next message: Anthony LaMark: ""legal values" for fields in sms_def.mof needed for Unix, Mac, AS400, etc."
    Date: Fri, 9 Jul 2004 11:05:20 -0700
    
    

    q1. The account with the error needs to be an administrator account on your
    SQL Server. You can also check to make sure the accoutn exists in the local
    SMS Groups on the site server. There is one that has to do with site to site
    communication and one to the SQL Server that account must exist in there.
    Q2. I am not sure what you are asking for? The SMS_SLP should be created in
    WINS and also the SMS_MP automatically.
    Q3. You can use ccmsetup.exe SMSSITECODE=XXX or client.msi SMSSITECODE=XXX
    advanced clients. For legacy clients you will need to make sure the
    boundaries are correct to assign and install. The issue with the SQL Server
    is probably preventing the boundaries to be updated in the site control
    file.

    -- 
    Thanks,
    Jeff Harbaugh [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.
    "Morne" <Morne@discussions.microsoft.com> wrote in message 
    news:59C9D9EA-7E3C-445F-91D7-1E98C7B1C1B7@microsoft.com...
    > Hi All. Thanks up fron for any assitance. I'm running a SMS 2003 on WIN2k3 
    > in a NT4 domain. Clients range from WIN98, WIN2k, WINXP and NT4. All pc's 
    > have been discovered but only a few (1%) have been assigned to a site or 
    > installed with the client software. I have configured the proper security 
    > accounts for all the machines. Push installation to client machines does 
    > not work. I manually installed the client on on nt4.0 pdc but it does not 
    > show the site which manages it.
    >
    >
    > I receive the following error in ddm.log:
    > *** [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login 
    > failed for user 'gss\admin'.
    >
    > Q1. Where do I configure the account that is causing the above error?
    > Q2. How do I create the SMS_SL 1a record on windows NT4 wins?
    > Q3. How do I manually assign a pc to a site?
    >
    > Thanks again,
    >
    > Morne
    >
    > 
    

  • Next message: Anthony LaMark: ""legal values" for fields in sms_def.mof needed for Unix, Mac, AS400, etc."

    Relevant Pages

    • Re: Advanced Client install nightmare
      ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
      (microsoft.public.sms.admin)
    • Re: sa password was inadvertently changed. With a kicker...
      ... Use some other account that the client has (any domain admin should have ... Did around there install package, and see if the sql script that changed ... Put the database files back where they should ... > I have a SQL Server 7 Standard edition server running in a ...
      (microsoft.public.sqlserver.security)
    • Re: SQL Sever 2008 RC0 fail to install almost all services
      ... Now I removed the account from local Administrators group. ... The SQL Server Log File reports an error 15209, ... Note that I use a specific account named SQLServerServices to install ... This is an informational message only. ...
      (microsoft.public.sqlserver.setup)
    • Re: Get "credentials not valid" message installing SQL2008 Failver
      ... The user account (domain account) has to be pre-created. ... The network name gets created during the install process. ... Microsoft SQL Server MVP ...
      (microsoft.public.sqlserver.setup)
    • Re: Compromise?
      ... >made the patches available and advised customers to ... >install it. ... >>Server was installed and if your SQL Server is running ... >>administrator account, you just gave anybody who has a ...
      (microsoft.public.sqlserver.security)

    Loading