Problems installing Security Scan and Office Scan

From: Luther (Luther_at_discussions.microsoft.com)
Date: 08/16/04 

Date: Sun, 15 Aug 2004 19:59:01 -0700

Some background that I stole from one of my other posts:

I'm new at SMS and I'm having some problems that I can't
figure out. I have been to the MS Managing SMS 2003 class. I have also read
through the Concepts and Planning Guide, but can't find a solution to this
problem.

I am our resident SQL DBA and have set up our SQL 2000 SP3a servers running
on Win 2003. Following the security recommendations from the MS courses, I
have removed the "Builtin\Administrators" group from the SQL server and given
access to the SQL servers to only those that know what they are doing.

I have installed SMS 2003 on a Win2003 server and placed the database on one
of our existing SQL servers. Our setup is using advanced security. I have
installed the SMS Provider on the SQL server. I followed the recommedations
in the CPG on page 153 for mapping the SMS site server account to the dbo of
the SMS database.

The current problem:

I initially had some problem getting the reports to install. After reading
some of the posts on the boards, I ended up editing the smsrprt.mof file so
that it pointed to my "remote" sql server (I know that it says not to do it,
but I couldn't get them to install any other way). I then ran a mofcomp on
the smsreport.mof file and the reports intalled without a hitch. Or seemed
to.

Now I'm trying to install the security scan and office scan tools and they
are failing. I get an error that says the following:

Security Update Inventory Tool Installation
Unable to query package information in server <MySMSServer>, site code
<mysitecode>.
Error code:1
Please make sure that the site server name and site code are correct. Do
you want ot igmore the error and continue?

No matter what I choose here, I cannot complete the installation
successfully. It refuses to query the site server to get the required
information.

Can anyone offer any suggestions? I can't find any logs that give me any
useful information about this. Maybe I'm just missing the one that I should
be looking at.

Relevant Pages

  • Re: Failed upgrade to SCCM
    ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ... SQL Server security mode and as we require the SQL server to be in SQL & ... however fails at "Install SMS provider components". ...
    (microsoft.public.sms.setup)
  • Re: Problems installing Security Scan and Office Scan
    ... I have been to the MS Managing SMS 2003 class. ... > I have installed SMS 2003 on a Win2003 server and placed the database on ... > installed the SMS Provider on the SQL server. ... > I initially had some problem getting the reports to install. ...
    (microsoft.public.sms.tools)
  • Re: Failed to get a SQL Server connection
    ... SMS is installed on a Windows Server 2003 SP1, ... We already did SMS ... Possible cause: SQL Server problem. ... Verify that SMS can access the SMS site database. ...
    (microsoft.public.sms.setup)
  • Re: MP Control Manager detected MP is not responding to HTTP requests
    ... IIS lockdown isn't needed for Windows server 2003. ... Did you get an error status message in the SMS admin console for MP control ... The SQL server site system is turned off, ...
    (microsoft.public.sms.setup)
  • Re: cannot add primary site in different domain
    ... computer account for the site server has been added to the SQL server. ... During the install, the local group for SMS_sitesystemtosqlconnection is created and populated correctly. ... is it using my credentials to connect to the remote sql server or does it use the local machine account? ... SMS installed into domain B. Central site server with SQL, ...
    (microsoft.public.sms.setup)
Loading