Re: Collection Membership issues
- From: "altria" <urbantec92@xxxxxxx>
- Date: Mon, 18 Dec 2006 13:24:33 -0500
Hello Michel-Vincent,
Thanks for your reply..in response to some of the points you have made;
"Clients show as installed only if a) they are discovered b) they are
assigned c) the client is deployed. If I understand this right, c) is OK, a)
and b) are not."
A ;seems to be correct because without actually enabling client push
installation (using AD discovery) some machines simply showed up in the
collections with all columns showing appropriately (Site CODE-XXX,
Assigned-YES, Client Type-Advanced).
B; Would be ok because under the column Assigned it states YES, just does
not have Site Code or Clent Type.
I used AD discovery and configured SMSsites. I also properly extended the AD
schema.
I am simply not sure why some machines show up and others dont. At first I
thought that it was site related but upon closer examination I have found
machines across all my AD sites to have the client installation show up
properly. Even after doing a manual intallation to "failed systems" it tells
me that installation successful under CCM logs then nothing shows in the
console to reflect this.
Thanks
Altria
"Michel-Vincent" <MichelVincent@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E913F870-7300-4356-B436-176C290C59A1@xxxxxxxxxxxxxxxx
Hello Altria
Many interesting topics in your post, let's see them:
1. Clients appear in your collections, but they don't show up as
"installed", although they are installed locally.
Clients show as installed only if a) they are discovered b) they are
assigned c) the client is deployed. If I understand this right, c) is OK,
a)
and b) are not.
How did you configure your discovery settings? AD discovery is
recommended,
use Network Discovery only if you cannot AD discover.
2. Site Code remains empty.
=> Did you successfully update the AD Schema and AD itself? If not, then
did
you set up a SLP?
3. Subnets and Site boundaries
I would recommend using AD sites as boundaries instead of subnets.
Conclusion: make sure your AD is updated with site code (eventually review
White Paper "SMS and AD" by Msoft), make sure the discovery is using AD
and
use AD sites as boundaries.
Hope it helps,
MV
--
Michel-Vincent Leriche
http://mvleriche.spaces.live.com
"altria" wrote:
Hello All,
I am running SMS 2k3 sp2 with SQL 2k sp4 on Win2k3 sp1.
I have successfully installed SMS but it seems that the collections (SMS
Admin Console) is not getting updated.
All the clients within my Domain do appear but under the columns; client
(NO) and site code it remains empty. I have updated membership for All
Systems and nothing shows up.
I have looked at the ccm.log and it states that client installation was
successful. On the client, I can see the ccmsetup and ccm logs both show
the
client installation succeeded. Any reason why the clients would not be
updated within the console?
Also on a separate issue, I have created a site boundary of my local area
network which works fine but since I have vlan setup do i have to create
a
site boundary for each subnet? Also, do I have to create separate SMS
site
for my branch locations?
TIA,
Altria
.
- References:
- Collection Membership issues
- From: altria
- RE: Collection Membership issues
- From: Michel-Vincent
- Collection Membership issues
- Prev by Date: SMS 2003 and Aproduct called DeepFreeze
- Next by Date: SMS installation on Windows 2003 SP1.
- Previous by thread: RE: Collection Membership issues
- Next by thread: RE: Issue creating Secondary Site
- Index(es):
Relevant Pages
|
Loading
