Re: SMS Admin Issues
- From: "Nospam" <nospam@xxxxxxxxxx>
- Date: Tue, 20 Sep 2005 06:58:38 -0400
""Lee Li[MSFT]"" <leelili@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:hJ%23rEJcvFHA.1472@xxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response!
>
> Q3: During our review of SP2 installs, we found that many had the update
> but the current scan was out-of-date. What would cause the last hardware
> and
> software inventory scans to be out-of-date.
> I am not sure what do you mean by "many had the update but the current
> scan
> was out-of-date"
> Please help me to clarify the symptoms in more detail.
> If the hardware/software inventory did not run on the client computer, no
> information can be sent back to the SMS site server.
> You need to make sure the SMS client is installed and working correctly on
> the computer.
>
I'm currently reviewing a SMS report about the status of SP2 installation.
The report indicated that 82 machines were missing SP2. We have validated
most of the machines and with the exception of laptops found that SP2 was
installed on those machines. The anomoly was that the last inventory
hardware and software scan was out-of-date. Most of our SMS inventory scan
information reports a current (i.e., the same day) information. Many of
these machines didn't have recent scan information. Some machines hadn't
been scanned in months.
> Q4: How can you have an hardware inventory scan but not a software
> inventory scan?
> You can disable the inventory agent on the SMS site server.
> Open the SMS admin console => client agents => software inventory client
> agent => then disable this agent by unchecking box in the dialog.
>
We have the software inventory client enabled in SMS. However, I've found
that software inventory scans were missing on some of the 82 reported
machines. The SMS client was installed on all machines.
> Q5: What would cause SMS to return 10018 error message for machines where
> we attempted to install SP2. We verified before our push that the
> machines
> did
> not have SP2 installed. Note: These are the same machines where the
> installation delay is occur (i.e., scheduled install at 10:00pm. Actual
> install at 9:00am next day). We are running SMS 2003.
>
> We will need to trace the SMS log files to find the root cause of this
> issue.
> I recommend you create a new new thread regarding this issue in the
> newsgroup so we can have a clear trace on this issue.
Will do
> Q7: What would cause a discrepancy between an OU collection and AD? I'm
> not seeing a one-to-one match between the two. I would assume there's
> some
> type
> of synchronization problem.
>
> "Active Directory System Group Discovery" this discovery can detect the OU
> name in your domain.
> Active Directory System Group Discovery works ONLY for systems that are
> already discovered and assigned to the local primary site and any direct
> child secondary sites. Active Directory System Group Discovery is not
> available for secondary sites. If a resource has been discovered and is
> assigned to the SMS site, Active Directory System Group Discovery extends
> other discovery methods by retrieving details such as organizational unit,
> global groups, universal groups, and nested groups. Active Directory
> System
> Group Discovery cannot discover a computer that has not already been
> discovered by another method.
Hmm. I'm seeing issues with new machines not getting discovered and the OUs
not getting updated. We have new machines in AD but they aren't getting
updated to the appropriate collection. Should we be using Active Directory
System Discovery to ensure that our OUs are kept current?
> Q8: If a machine has been reimaged or rebuilt, shouldn't SMS have the
> latest information hardware and software inventory? What would cause it
> not to
> have updated information on rebuilt or reimaged machines?
> You need to delete the original client in the collection and install the
> SMS client again on the new built client computer.
> Then it will get the latest information hardware and software inventory
> information.
Wow. We rebuild.reimage machines all the time. The security team/SMS
administrator have no idea when this happens. I just assumed that SMS would
update the hardware and software information automatically if the computer
name stayed the same but the machine was rebuilt or reimaged.
> Q9: What method are you using to ensure that every user has the SMS client
> installed?
> Using the client push installation usually can install the SMS client on
> all the computers that had been detected by the SMS site server.
>
> Hope the above information helps. Have a nice day!
Thanks!
.
- Follow-Ups:
- Re: SMS Admin Issues
- From: "Lee Li[MSFT]"
- Re: SMS Admin Issues
- References:
- RE: SMS Admin Issues
- From: "Lee Li[MSFT]"
- RE: SMS Admin Issues
- Prev by Date: Re: Central site collection
- Next by Date: Duplicate entries/old entries not purging
- Previous by thread: RE: SMS Admin Issues
- Next by thread: Re: SMS Admin Issues
- Index(es):
Relevant Pages
|
