Re: Branch Office Deployment

I think Ryan added some interesting discussion points in a later post. But
some clarification for your planning is in order:
Active Directory - provides authentication functionality. Sure there's more,
but in this case, not sure if it's applicable to your needs.
Application - consumes authentication information and has it's own
requirements.

As I understand your requirements, you want to be able to continue the
authentication and application functionality in the event of a WAN failure.
Unless cached credentials are able to be used by your application, then that
indicates that the AD must be deployed to each branch office. I suggest you
find out what the latency and saturation levels are on your WAN links to be
sure you have a good plan for deploying the DC's. Also, be sure that your
outage windows for your WAN link are sufficiently understood so you can also
understand what will happen when the link does fail and how long before
particular actions should be employed.

Consider traffic shaping for your WAN links. You may want to prioritize
some of this traffic so that your application has a higher priority if
that's warranted.

Application replication of data - what was the plan there? How does the
application store its data? Small files? Large files? DB's? As Ryan
mentioned, there may be some value in using the SQL replication engine. But
that really depends on how your application is architected and I'm not clear
on that information.

Al



"Darryl" <Darryl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:078C0C29-C824-4F7C-8688-00C7D45385FA@xxxxxxxxxxxxxxxx
Thanks for the response. Interaction would be the logging on of network
users
and accessing the client/server app in addition to the files stored on the
network. I would think local processing at each site would be better as a
whole. As far as bandwidth...I don't know "exactly" but it is an
application
that has a small client that installs on the local machine. So I wouldn't
think it is too nasty. We want the app to be available in the event the
link
goes away to the main office. Each site would operate independently and
transfer the data when appropriate. That is one of the questions - What
would
be the best way to replicate that data back to corporate?

"Al Mulnick" wrote:


Some questions:
What is the interaction of the app and AD? That's not clear from your
post.
What are the bandwidth requirements of the app?
If your wan link goes away, what is the value of the app? does it
continue
to function without a WAN link to the central and just queue everything
up?
Or ?

Al

"Darryl" <Darryl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C616B42-2A0D-4AFA-B2FE-2F6CA4546513@xxxxxxxxxxxxxxxx
I asked a similar question in the Windows Server 2003 group but realized
I
probably should have posted here instead so here goes and I apologize
for
double posting.

I have a new custom app we are rolling out very soon and we currently
have
a
total of 9 sites - one of which is corporate where the app is being
developed. The app is written in .Net, VB and backended by SQL 2005. We
will
of course also use the reporting services included in SQL 2k5. I think
creating sites and having a server local at all remote offices not only
makes
the app more responsive but also provides a bit of a disaster plan in
the
event the T1 goes down. Extend AD to all the sites, create a DC at each
site,
all share one domain and Replicate.

My question is this: Is this the best practice for offering the
application
to all the branch offices? What about replication? SQL won't be a
problem
as
far as replication goes? Does replication care whether it's SQL or
plain
files or ????

I'm a bit of a newbie when it comes to this so please forgive me.

Thanks in advance for any help. I really need it.

DL





.

Relevant Pages

  • Re: Branch Office Deployment
    ... The question you are really asking goes beyond AD and SQL ... If this is a highly transactional environment where you would need ... We want the app to be available in the event the link ... What about replication? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Branch Office Deployment
    ... The question you are really asking goes beyond AD and SQL ... distributed transactions and locking before going that route. ... We want the app to be available in the event the link ... What about replication? ...
    (microsoft.public.windows.server.active_directory)
  • Branch Office Deployment
    ... I asked a similar question in the Windows Server 2003 group but realized I ... total of 9 sites - one of which is corporate where the app is being ... The app is written in .Net, VB and backended by SQL 2005. ... What about replication? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cancel SQL CE Replication gracefully?
    ... I have already deployed a Field Service app and a Delivery App ... One uses Merge Replication ... I work closely with the MS SQLMobile and CF ... After two dozen CF apps using SQL CE, I have learned to keep my usage ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: AD Intersite replication
    ... LocA and LocB are connected by a WAN link WanA-B ... Replication between LocA and LocB will take place over site link A-to-B (and ... Because you "told" by configuring the cost that is more fast to ... Site link transitivity is enabled or disabled by selecting the Bridge All ...
    (microsoft.public.windows.server.active_directory)
Loading