Concurrent Distribution of Files to Site Servers
Brian Snead
Why wouldn't I want the remote sites to be Logon Servers?
Our plan is to have a BDC located at each site so users will not
authenticate across the 56K link. It seams to make sense to make each site
a SMS Site and a Logon Server. Each site will have approx 30 workstation.
Thanks
Brian.
CE <Cliveea_ms@NO_JUNKmsn.com> wrote in article
<01bc66d1$99801f80$5984379d@funkybunker>...
> If the 150 sites were to have secondary sites created, it is
> 'theoretically' possible for SMS to concurrently send packages to all 150
> sites simultaneously.
>
> This is cause very much dependent on topology and connections to the
sites.
> The LAN sender under SMS is multi-threaded and is configured by default
to
> handle upto 5 concurrent sendings. Via sender manager it is possible to
up
> this (don't know the top limit). I know of one company which 64+
secondary
> sites who concurrently send packages to these sites. You need a good
> infrastructure and site server to handle this. You could of course tier
two
> primary sites at the central location each handling 75 sites each.
>
> Just a thought since having sms logon servers at each site would be a no
> no.
> --
> Cliveea_ms@NO_JUNKmsn.com
>
> Remove NO_JUNK from my email address to send mail.
> The above comments are my own, and may not be
> generally endorsed by my employer. No guarantee
> or warranty is implied on suggestions or comments
> given. So don't take it as gospel !
>
ellen
Because a logon server out there would be nasty for network traffic.
Maintenance Manager Service would be polling every server out there on its
polling cycle... packages would NOT be sent compressed...
You would not be happy with this.
Put a secondary site on the BDC's, use the SMSLS.INI to map clients to
their specific sites...
--
Ellen
The comments above are my own, and not representative
of my employers... past, present or future.
Brian Snead <bsn...@ishub.com> wrote in article
<01bc66e9$a0a4a890$3e0e85ce@hopi>...
John Hollcraft
I know of a company (Starburst Communications) that is planning on
releasing a SMS add-on to their product.
The Starburst product does IP Multicasts to any number of IP addresses.
I.E, one IP broadcast to
any number of receiving stations.
The SMS integration is very good. I would recommend the product (not yet
release) to anyone that has a large number of sites and want to cut down on
network traffic.
--
Regards,
John Hollcraft
The SMS Experts at jrh Group Limited
http://www.jrhgroup.com
Brian Snead <bsn...@ishub.com> wrote in article
<01bc66b7$25c7ca30$3e0e85ce@hopi>...
> I am looking for advice and experiences with file distribution to
servers.
> Here is the situation:
>
> I am designing a network which will require distribution of presentations
> to servers located in 150 sites. All these sites have a dedicated 56K
> connection to a central data center where SMS Central Site resides. We
will
> need to distribute multiple 10 - 50 MB files to these remote sites each
> night. Because the limiting factor is the 56K channel to each site, I
would
> like the SMS Central Site to maintain many concurrent connections.
>
> Is this possible?
>
> How do I implement - the docs don't seem to clearly explain the
procedure?
>
> Has anyone worked with Starbursts Multicast product?
>
> Thank you,
> Brian Snead
> InfoSys Service, Inc.
> bsn...@ishub.com
>
Herman Verkade
I think Clive meant that having each remote location as a Logon Server
off a central site would not be a good idea. Having each remote location
as a separate SMS site with one or more Logon Servers in it is exactly
what you should do.
Herman Verkade