Re: SCCM 2007 Discovering Computers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



it doesn't appear after I click "Update collection membership"
but after a while ( like 1 hr), I click it again, then it appears in the
"All Windows XP systems" collection

I believe there is a time interval.

"Kim Oppalfens [MVP]" <""Kim dot Oppalfens\"@google mail.com">
???????:%23wsCiUcAIHA.5752@xxxxxxxxxxxxxxxxxxxxxxx
Andrew wrote:
I assigned domain admin to run the SMS EXECUTIVE and SMS COMPONENT
MANAGER services. I am waiting the results
"Kim Oppalfens [MVP]" <""Kim dot Oppalfens\"@google mail.com">
???????:%23Wbb%23ZaAIHA.464@xxxxxxxxxxxxxxxxxxxxxxx
Andrew wrote:
environment:
Vmware:
Windows 2003 server SP2 as Domain controller (DC1)
Winodws 2003 server R2 SP2, with SQL 2005 SP2, SCOM 2007, SCCM 2007 and
those hotfixes need to run these things, assigned 2gb ram. (SC1)
Windows XP SP2. (PROF1)

I am now using SCCM, the first step I want to discover the computers
and make a push installation to them.

After I enable the "Network Discovery" and set the interval to 5
minutes. I dont' see my WinXp computer appear in the "All Windows XP
system collection"

But all my SC1, DC1, and PROF1 exist in the "All System" collection.

Then I try to make a push installation to the PROF1 computer. I saw the
activities ( harddisk loading and Network), but after quite a while, I
still see the PROF1 computer marked "NO" under client

sorry there are too many questions, please save me out of the chaos,
thank you very much

Regards,
Andrew Chan
Let's start with the discovery issue, once we get that fixed we'll move
on to client push.

Network discovery isn't your best in this environment, it requires the
client to get a lease from a microsoft dhcp server, or anonymous access
to the ARP cache of your router, or the snmp agent installed.

You have the best change to discover something with network discovery
with the dhcp option.

I would advise you to take a look at Active directory system discovery,
this would make detecting machines in your environment a whole lot
easier.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx


You shouldn't do that, all services should remain running as localsystem.

Checking in all windows xp systems is fine, but you might want to trigger
the update of the collection. Just right-click it and select update
collection membership, or update it from the action pane.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx


.



Relevant Pages

  • Re: SCCM 2007 Discovering Computers
    ... Windows 2003 server SP2 as Domain controller ... Let's start with the discovery issue, once we get that fixed we'll move on to client push. ... Kim Oppalfens - Sms Expert for lack of any other expertise ... Windows Server System MVP - SMS ...
    (microsoft.public.sms.setup)
  • Re: Is Network Discovery necessary
    ... we found the major decision point for network discovery was ... SMS clients?". ... Windows Enterprise Management Division User Assistance ...
    (microsoft.public.sms.setup)
  • Re: SCCM 2007 Discovering Computers
    ... I keep looking in the "All Windows XP system" in the collections for the ... After I enable the "Network Discovery" and set the interval to 5 minutes. ... Then I try to make a push installation to the PROF1 computer. ...
    (microsoft.public.sms.setup)
  • Re: Vista GPO: Disable File Sharing
    ... you would need to use the Windows ... Discovery" predefined group. ... be able to enable network discovery anyhow. ... you will want to disable the LLTDIO and RESPNDR drivers on all Vista ...
    (microsoft.public.windows.server.active_directory)
  • Re: Network Discovery
    ... Take a look at the network discovery FAQS in the Discovery chaphter of the ... Windows Enterprise Management Division User Assistance ... > 10.10.2.0/255.255.255.0 of machines not in Active Directory. ...
    (microsoft.public.sms.setup)