Re: SMS clients / Site boundaries

the two sites have different site codes.? or are sharing the site codes as
well. because if are different site code you can just change the the site
code for each clients one site code for one site and the other site code for
the other site.?



--
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org



"Kim Oppalfens <MVP>" wrote:

Hum, then the anything that is left is lmhosts files I am affraid.
Don't know whether I would want to go that route.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Brian Lev-Ari" <BrianLevAri@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:23A6AAD5-9E2A-4FAF-8077-3172A6BA620D@xxxxxxxxxxxxxxxx
We are sharing the same WINS

"Kim Oppalfens <MVP>" wrote:

Do you guys have a seperated wins infrastructure, or are you sharing that
as
well?

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Brian Lev-Ari" <BrianLevAri@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D58B9D92-ABEB-488A-AC5E-F75391FC259B@xxxxxxxxxxxxxxxx
From the two responds I got, I understand that our proposal is not
recommended, I must admit that we also do not like the solution we
offered.

Most of our subnets are dedicated in the company, this mean that we
have
subnets that belong to group A and are then assignes to SMS Site "A"
Boundaries.

but I have at least 50 clients that are physically connected to subnets
that
belongs to outher teams / groups, and these subnets are defined on
anothers
team SMS Sites. Solving this by physically connectivity networking will
be
very expensive and this is also very dynamically.

I know who the clients are as I discover the clients per OU and I get
these
clients unassigned.

What is the solution to make these clients a part of my SMS Site.

Thanks for the responds,

Brian Lev-Ari

"Kim Oppalfens <MVP>" wrote:

Expect problems.
If you auto assign clients they will all get assigned to the
alphabetically
lowest site.
So you would have to statically assign clients to avoid this issue.
Even if you work around this issue clients might ask the wrong
management
point about the dp location.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Santos Martinez,MCDBA"
<SantosMartinezMCDBA@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:84269DB9-6E43-479F-9EB1-8A6EC22DE4A9@xxxxxxxxxxxxxxxx
That will do a overlap in the Site Boundries why not use a Parent to
Child
SMS Server or Primary to Secondary and then put Site Boundries and
Roaming
Boundries.

?

--
Santos Martinez,MCSE, MCDBA
IT Community Staff of Puerto Rico


"Brian Lev-Ari" wrote:

We have two SMS sites managed by two different SMS admins on one
network
and
using one domain.

The workstations are fully seperated in two different OU's.

Each of these sites have been configures with different site
boundaries,
but
we have a lot of clients that are relaying on shared subnets.

We are considering to do the following:
1 - Define all subnets on both servers as site boundaries (this
mean
that
basically a client can be assigned to both of them)
2 - perform the discovery on each SMS site (primary server) based
on
the
active directory OU. the server A will only discover the relevant
clients
as
per the OU.
3 - push the clients from each site to the clients that were
detected
by
the
discover process

Will that be an acceptable mode to work or can we expect problems
if
same
site boundaries (all subnets) are defined on both SMS primary
servers
?

Thanks in advance

Brian Lev-Ari
Motorola Israel









.

Relevant Pages

  • Re: SMS Advance Client not assigned to the site
    ... added 3 subnets individually on top of that. ... In the Roaming Boundaries tab, ... all clients in our network are XPs so I don't need to worry ... Sms 2003 has 2 types of clients: ...
    (microsoft.public.sms.admin)
  • Re: Preventing Users who travel from switching SMS sites
    ... All of the VLAN subnets for Corp HQ are in one AD site, ... If the SMS client is not supposed to move from site to site, ... within the site boundaries of Primary1. ... The clients are XP SP2 mostly. ...
    (microsoft.public.sms.admin)
  • Re: SMS Advance Client not assigned to the site
    ... Not only have I added the SMSSite (which includes all the 3 subnets that were configured in AD Sites & Services) in the Site Boundaries, but also added 3 subnets individually on top of that. ... After doing this I ran the AD System Discovery and then updated the collection but still no clients got assigned to the site. ... Now since there was no way of knowing when sms 2003 went rtm which client you would install. ...
    (microsoft.public.sms.admin)
  • RE: SMS Advance Client not assigned to the site
    ... The very first time when I opened the SMS admin console, ... all clients from our building were dicovered. ... Before installing SMS, I went under AD Sites and Services and created a site ... called "SMSSite" and added all above subnets to it. ...
    (microsoft.public.sms.admin)
  • Re: SMS Advance Client not assigned to the site
    ... Legacy clients are assigned based site boundaries, advanced clients are assigned based on roaming boundaries. ... By configuring site boundaries, you by default also configure roaming boundaries. ... Now since there was no way of knowing when sms 2003 went rtm which client you would install. ... If you want to solve this without starting to push to "unassigned resources" than you could add your 3 ip subnets to the subnet boundaries. ...
    (microsoft.public.sms.admin)
Loading