Re: SAP client advertisment runs on wrong computers
From: Shehzad Khoja [MSFT] (srkhoja_at_online.microsoft.com)
Date: 01/18/05
- Next message: Thierry: "Stop publication on client"
- Previous message: Shehzad Khoja [MSFT]: "Re: Package Distrubution."
- In reply to: Aidar Khasanov: "Re: SAP client advertisment runs on wrong computers"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 Jan 2005 09:15:48 -0800
SMS doesn't directly go to DNS to discover any records. If you enable
network discovery then SMS will go to DHCP to discovery machines.
I am not sure how wrong DNS entries can cause collection evaluator to put
wrong machines in a collection. To troubleshoot this issue, you will have to
get more data on this like which discovery agent discovered those machine
and if any discovery agent had a wrong 'name' field populated for the
machine.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Aidar Khasanov" <AidarKhasanov@discussions.microsoft.com> wrote in message
news:C06E0713-8726-414D-81B5-6E778B794E61@microsoft.com...
> Shehzad, thank you for the answer.
>
> Yes, the collection is targeting only systems - the collection membership
> rule is: System Resource.Name is equal to "comp1". Collection is not
> dynamically updated.
> It seems that we have solved this case. The problem was connected to
> DNS/DHCP issue. There is a "Discard A and PTR records when lease is
> deleted"
> checkbox in Win2003 DHCP server properties. Somebody has turned it off! We
> have just turned it on and cleared wrong DNS records.
> In our case this checkbox primarily affected reverse lookup zone. For
> example, we had one record in forward lookup zone «domainname.com»:
> - comp1 Host(A) 10.0.0.145
> and several PTR records for the IP address:
> - 10.0.0.145 Pointer(PTR) comp1.domainname.com.
> - 10.0.0.145 Pointer(PTR) anothercomp1.domainname.com.
> - 10.0.0.145 Pointer(PTR) anothercomp2.domainname.com.
> - 10.0.0.145 Pointer(PTR) anothercomp3.domainname.com.
> SMS 2003 SP1 enlisted these records in ResourceNames[0]. ResourceNames[n]
> fields. And when the advertisement was assigned to comp1, SMS installed it
> on
> ONE of these computer, randomly selected. ("System Status" in SMS
> AdminCosole
> and "Adv Client Spy" confirmed that advertisment was applied and actually
> installed only on ONE computer). Although these computers had wrong
> reverse
> lookup PTR records, in forward lookup zone Host(A) records were correct
> for
> each computer. And comp1 was the only member of particular SMS collection.
> But I still wonder, how discovering of PTR records is implemented in SMS?
> And why doesn't it use just simple Host(A) name-to-IP mapping?
>
>
> "Shehzad Khoja [MSFT]" wrote:
>
>> Is this happening all the time? This may happen if you have dynamic
>> collections and at the time you create advertisement your collections are
>> not updated. But if this is happening all the time then we need to
>> investigate this more. Can you make sure that policy and policy
>> assignment
>> is created only for the machines in the collection?
>>
>> Also the collection you are targetting has only systems? No users,
>> correct?
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Aidar Khasanov" <AidarKhasanov@discussions.microsoft.com> wrote in
>> message
>> news:5B1C10EA-41EB-4CB4-AE00-3C5D84622A91@microsoft.com...
>> > We use SMS2003 SP1. The advertisment is assigned to collection that
>> > contains,
>> > for example, 3 computers: Comp1, Comp2, Comp3. The problem is that
>> > advertisment also runs on another computer, say, AnotherComp1, that is
>> > NOT
>> > member of the collection.
>> > This is not a duplicate GUIDs problem. When I open "Properties" of
>> > AnotherComp1 computer account in "All Systems" collection, there is:
>> > Name: AnotherComp1
>> > NetbiosName: AnotherComp1
>> > ResourceNames[0]: Comp3 -- name of computer which IS a member of
>> > collection.
>> > Does anybody know what are all these fields about: ResourceNames[0],
>> > ResourceNames[1], ... ResourceNames[n] ? And is there any way to force
>> > SMS
>> > not to use these fields when determining whether to install
>> > advertisment
>> > on
>> > particular client?
>>
>>
>>
- Next message: Thierry: "Stop publication on client"
- Previous message: Shehzad Khoja [MSFT]: "Re: Package Distrubution."
- In reply to: Aidar Khasanov: "Re: SAP client advertisment runs on wrong computers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
