Guest JJ Posted March 30, 2008 Posted March 30, 2008 Hi All, I have an app that needs to be used in multiple branch offices by 25 users on average. The application is built using c# with a thin client front end and Sql server 2005 for back end. What would be the best way to get the data back to HQ? I could pop servers at each location and replicate the data down to HQ every night but would prefer to have a solution that pushed the data on a 10 min cycle back to HQ. Any thoughts on the way to go with this? From a network and application stand point how would you set something like this up? Thanks, Jam
Guest Frankster Posted March 30, 2008 Posted March 30, 2008 Re: Multiple Branch Office HookUps "JJ" <JJ@discussions.microsoft.com> wrote in message news:DE0B81DE-B7AB-484B-A791-2DDD110688E8@microsoft.com... > Hi All, > > > I have an app that needs to be used in multiple branch offices by 25 users > on average. The application is built using c# with a thin client front end > and Sql server 2005 for back end. What would be the best way to get the > data > back to HQ? > > I could pop servers at each location and replicate the data down to HQ > every > night but would prefer to have a solution that pushed the data on a 10 min > cycle back to HQ. Any thoughts on the way to go with this? From a network > and > application stand point how would you set something like this up? > > > > Thanks, > > Jam > With the somewhat limited info in your post, I would say this sounds like an ideal scenario for a MS Terminal Server implementation. -Frank
Guest Anthony [MVP] Posted March 30, 2008 Posted March 30, 2008 Re: Multiple Branch Office HookUps Terminal Services. Much easier I would have thought than trying to manage distributed data - unless there really is no connection between the data at different sites. Anthony, http://www.airdesk.co.uk "JJ" <JJ@discussions.microsoft.com> wrote in message news:DE0B81DE-B7AB-484B-A791-2DDD110688E8@microsoft.com... > Hi All, > > > I have an app that needs to be used in multiple branch offices by 25 users > on average. The application is built using c# with a thin client front end > and Sql server 2005 for back end. What would be the best way to get the > data > back to HQ? > > I could pop servers at each location and replicate the data down to HQ > every > night but would prefer to have a solution that pushed the data on a 10 min > cycle back to HQ. Any thoughts on the way to go with this? From a network > and > application stand point how would you set something like this up? > > > > Thanks, > > Jam >
Guest JJ Posted March 30, 2008 Posted March 30, 2008 Re: Multiple Branch Office HookUps Well thats the thing, we would have a server at each branch with the application running on it and Sql Server, then we would need a way to send the data over to HQ. As was mentioned Terminal Services but how well does that work with applications in terms of performance and would it be possibe to have multiple apps running through it? Is Terminal Services like Citrix? "Frankster" wrote: > > "JJ" <JJ@discussions.microsoft.com> wrote in message > news:DE0B81DE-B7AB-484B-A791-2DDD110688E8@microsoft.com... > > Hi All, > > > > > > I have an app that needs to be used in multiple branch offices by 25 users > > on average. The application is built using c# with a thin client front end > > and Sql server 2005 for back end. What would be the best way to get the > > data > > back to HQ? > > > > I could pop servers at each location and replicate the data down to HQ > > every > > night but would prefer to have a solution that pushed the data on a 10 min > > cycle back to HQ. Any thoughts on the way to go with this? From a network > > and > > application stand point how would you set something like this up? > > > > > > > > Thanks, > > > > Jam > > > > With the somewhat limited info in your post, I would say this sounds like an > ideal scenario for a MS Terminal Server implementation. > > -Frank > >
Guest Frankster Posted March 31, 2008 Posted March 31, 2008 Re: Multiple Branch Office HookUps From your perspective, I suppose Terminal Services is "like" Citrix. Actually, Citrix is simply a client for TS. There is no compelling need to run Citrix on the client since Windows workstations (XP and Vista) have a TS client built-in, called Remote Desktop. Citrix is normally only required for cross-platform capabilities or unique added security configurations. -Frank "JJ" <JJ@discussions.microsoft.com> wrote in message news:49958E95-EDB1-4E3F-9772-7820CFAF8025@microsoft.com... > Well thats the thing, we would have a server at each branch with the > application running on it and Sql Server, then we would need a way to send > the data over to HQ. As was mentioned Terminal Services but how well does > that work with applications in terms of performance and would it be > possibe > to have multiple apps running through it? Is Terminal Services like > Citrix? > > > "Frankster" wrote: > >> >> "JJ" <JJ@discussions.microsoft.com> wrote in message >> news:DE0B81DE-B7AB-484B-A791-2DDD110688E8@microsoft.com... >> > Hi All, >> > >> > >> > I have an app that needs to be used in multiple branch offices by 25 >> > users >> > on average. The application is built using c# with a thin client front >> > end >> > and Sql server 2005 for back end. What would be the best way to get the >> > data >> > back to HQ? >> > >> > I could pop servers at each location and replicate the data down to HQ >> > every >> > night but would prefer to have a solution that pushed the data on a 10 >> > min >> > cycle back to HQ. Any thoughts on the way to go with this? From a >> > network >> > and >> > application stand point how would you set something like this up? >> > >> > >> > >> > Thanks, >> > >> > Jam >> > >> >> With the somewhat limited info in your post, I would say this sounds like >> an >> ideal scenario for a MS Terminal Server implementation. >> >> -Frank >> >>
Guest Frankster Posted March 31, 2008 Posted March 31, 2008 Re: Multiple Branch Office HookUps More accurately than my previous post, Citrix is an *add-on* for TS. Granted, it is more than a client since there is also a server side component. In any case, I think you may be misunderstanding TSs capabilities. There is no need for Citrix in the typical MS implementation (i.e. without UNIX clients). Yes, the performance is good, if done right. You would only have one server to manage. No need to "sync" any data, ever, since everyone is working on the same database in real time. Numerous applications can be run simultaneously by numerous people simultaneously. TS Client Access Licenses run around $80-$100 per seat, depending on volume and where you buy them. -Frank "Frankster" <Frank@SPAM2TRASH.com> wrote in message news:UoGdnR1iHc2zpW3anZ2dnUVZ_g-dnZ2d@giganews.com... > From your perspective, I suppose Terminal Services is "like" Citrix. > > Actually, Citrix is simply a client for TS. There is no compelling need to > run Citrix on the client since Windows workstations (XP and Vista) have a > TS client built-in, called Remote Desktop. Citrix is normally only > required for cross-platform capabilities or unique added security > configurations. > > -Frank > > "JJ" <JJ@discussions.microsoft.com> wrote in message > news:49958E95-EDB1-4E3F-9772-7820CFAF8025@microsoft.com... >> Well thats the thing, we would have a server at each branch with the >> application running on it and Sql Server, then we would need a way to >> send >> the data over to HQ. As was mentioned Terminal Services but how well does >> that work with applications in terms of performance and would it be >> possibe >> to have multiple apps running through it? Is Terminal Services like >> Citrix? >> >> >> "Frankster" wrote: >> >>> >>> "JJ" <JJ@discussions.microsoft.com> wrote in message >>> news:DE0B81DE-B7AB-484B-A791-2DDD110688E8@microsoft.com... >>> > Hi All, >>> > >>> > >>> > I have an app that needs to be used in multiple branch offices by 25 >>> > users >>> > on average. The application is built using c# with a thin client front >>> > end >>> > and Sql server 2005 for back end. What would be the best way to get >>> > the >>> > data >>> > back to HQ? >>> > >>> > I could pop servers at each location and replicate the data down to HQ >>> > every >>> > night but would prefer to have a solution that pushed the data on a 10 >>> > min >>> > cycle back to HQ. Any thoughts on the way to go with this? From a >>> > network >>> > and >>> > application stand point how would you set something like this up? >>> > >>> > >>> > >>> > Thanks, >>> > >>> > Jam >>> > >>> >>> With the somewhat limited info in your post, I would say this sounds >>> like an >>> ideal scenario for a MS Terminal Server implementation. >>> >>> -Frank >>> >>> >
Recommended Posts