Re: SMS2003 - Systems discovered but not assigned
From: MtnGoat (NotGiven_at_InPublic.org)
Date: 04/09/04
- Next message: Evan [MSFT]: "Re: sms console not working"
- Previous message: Geoff Walker: "[SMS2k3] - Clearing content cache remotely"
- In reply to: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Next in thread: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Reply: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 09 Apr 2004 15:30:51 GMT
Right, they show up as "Assigned" No.
AD Site shows as "Default-First-Site-Name".
Boundaries are defined as the AD site and four subnets (xxx.xxx.130.0,
xxx.xxx.131.0, xxx.xxx.74.0 and xxx.xxx.76.0. Site server and SQL
server are on .74.0).
Discovery is using Network, Active Directory System, Active Directory
User, and Active System Group.
Still not clear if enabling push installation (which I want to do
eventually) will automatically push out clients to everyone (which I
definitely DON'T want to do now).
C.
On Thu, 8 Apr 2004 13:18:34 -0700, "Jeff Harbaugh [MSFT]"
<jeffharb@online.microsoft.com> wrote:
>How are you verifying they are not assigned? Are they showing as assigned =
>no in the UI? If you double click one of machines in the collections do they
>have an AD Site associated with it and does it match the site boundary you
>have?
>Your ddm.log is just showing that you are finding the systems but since you
>do not have push installation enabled no CCR's are being created.
- Next message: Evan [MSFT]: "Re: sms console not working"
- Previous message: Geoff Walker: "[SMS2k3] - Clearing content cache remotely"
- In reply to: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Next in thread: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Reply: Jeff Harbaugh [MSFT]: "Re: SMS2003 - Systems discovered but not assigned"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|