Re: new sms installation

Also consider setting up and DP if you think about distributing something
from the secondary sites to its clients rather from the primary sites to all
other clients over WAN

-Vj

"Cathy Moya [MS]" wrote:

inline:

"Darkz" <dash71@xxxxxxxxxxx> wrote in message
news:1138913595.052595.52090@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am brand new to SMS and still trying to grasp it .
cathy: Welcome to the club! It can be frustrating at times, but never
boring. ;-)

We have a single
domain enviroment, about 80 locations on a WAN ... from what i
understand every site needs its own sms site database
cathy: Not necessarily. It depends on how fast the WAN is and how big the 80
locations are. SMS is always a balancing act between how responsive you need
SMS to be and how much bandwidth you can afford to let SMS suck down. If you
had T3s between every sites, you had only 10 clients in each site, and you
weren't using the WAN link for anything except SMS you might be fine using a
single site. Maybe. Also sort of depends what you're doing with those 10
clients. If all 800 clients all want to install Office at exactly the same
time, it could get tricky.

Now, you could also install one primary site and let the other 79 be
secondaries. Secondary sites do not require a database, they just use the
parent primary site database. Again, you have to think about how that
traffic will affect your WAN link. The benefit is, unlike 800 (+?) clients
all using the WAN link anytime they want (=unmanaged) but if you use a
secondary site, the traffic is mostly managed. Advanced Clients in that
location might still have some unmanaged traffic to get policy if you don't
configure a proxy management point. That's not necessarily a bad thing.
Again, it all comes down to bandwidth. Other advantages to secondary sites:
they don't require you to buy additional SMS licenses (assuming you are
using SMS 2003) and they are totally managed from the parent site.


which could be
hosted on the same sql server..
cathy: Well, yes, in theory you could put 80 site databases on the same
computer running SQL Server. But at that point I start thinking "why aren't
you using secondary sites instead?" SMS talks to the database A Lot. If they
all have to hop the WAN just to talk to the database, you're racking up some
unmanaged traffic. Better to make it a secondary site so the database
traffic will be managed.

must the sms provider be on the same
server as the database or can it stay or be moved back to the site
server
cathy: You can install only one SMS provider on the SQL Server. So the site
A provider could be installed on the SQL Server but B-n would have to be
installed on each site server. You would not be able to move the Site A
provider back to the site server after you install it on the SQL Server.

Thank you for your time
cathy: You're welcome!
Ahmad

cathy: If you haven't seen our product documentation page yet, I invite you
to check it out:
http://www.microsoft.com/smserver/techinfo/productdoc/default.mspx

Good luck!

--
Cathy Moya, CISSP, MCSE: Security
Technical Writer, Windows Enterprise Management Division User Assistance

Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided AS IS with no warranties and confers no rights.



.

Relevant Pages

  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: Help need desperately!
    ... > Have you given your SMS Server's machine account FULL CONTROL of the Systems ... > machines are already discovered or you wouldn't be able to push to them. ... > Check through the SMS Server logs, ... All clients are discovered, assigned and have successfully installed the ...
    (microsoft.public.sms.inventory)
  • RE: Advanced client cannot auto discover management point
    ... then was to delete the site boundary from the central site and correctly ... have SMS clients that are getting site assignments, ... child site server. ...
    (microsoft.public.sms.admin)
  • Re: Secondary Sites
    ... I don't have to create secondary sites? ... Can the advanced client talk to the existing primary site server if ... your SMS sites tend to correlate with your Active ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
Loading