Branch Office Deployment
- From: Darryl <Darryl@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 Oct 2007 09:06:00 -0700
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
.
- Follow-Ups:
- Re: Branch Office Deployment
- From: Andy
- Re: Branch Office Deployment
- From: Al Mulnick
- Re: Branch Office Deployment
- Prev by Date: Re: Installing Windows 2003 Active Directory on VMWARE
- Next by Date: Re: Create home folder via Active Dir, Admin becomes owner instead of
- Previous by thread: Create home folder via Active Dir, Admin becomes owner instead of
- Next by thread: Re: Branch Office Deployment
- Index(es):
Relevant Pages
|
Loading
