I know that, this topic has ben referred some time ago, but it seems that it has not been resolved… Therefore, I need to revisit the issue, to get a concrete implementation approach… We have a customer, with the following nature: It is one single legal entity, one company, one tax ID; but, with 4 manufacturing plants at 4 distant and different sites, with 10 users at each site. The Headquarters is also located at a distant place, with 20 users. The requirement is to have one single database (or a shared ? database on different physical servers) (or multiple databases synchronized at real time), because the sales people at the HQ office has to know which product is available at which site, and therefore place sales orders, issue invoices etc. The communication between the plants and the HQ offices is provided via satellite connections, since a dedicated terrestial leased line is not possible. It looks like that, we need to install Navision 3.70 locally at each site. But, this causes each plant to work as if they are independent organizations. This is not good. Replication of the databases daily may be a solution. But the customer does not like the idea. Because they want to work on realtime data. If we install the Navision at the HQ office, then the users at the plants have to reach the server via Terminal Services. But, this requires (4 plants x 10 users =) 40 concurrent sessions to be serviced at the HQ office, which is not appreaciable, for the performance of the Terminal Services as compared to the bandwidth. Is there an intelligent solution, where multiple site installations of Navision can be wrapped up in one single database? Does anybody have a strong reference on this kind of implementation?
If we install the Navision at the HQ office, then the users at the plants have to reach the server via Terminal Services. But, this requires (4 plants x 10 users =) 40 concurrent sessions to be serviced at the HQ office, which is not appreaciable, for the performance of the Terminal Services as compared to the bandwidth.
What bandwith do you deal with ?
each plant has its own 256Kbps satellite connection to the HQ office. Some people say that, the bandwidth should not be the issue. They say, it is rather due to the latency (around 800ms) of the access that can be achieved by the satellite.
In this case give CITRIX a chance. But you are right with the central server, it has to be at least a dual processor with 512 MB Ram.
hello, we have a similiar setup, hq in germany and sites in south africa. connecting to 2* citrix servers in hamburg. we have had problems in the beginning with a internet satellite connection, latency was around 800-1000 ms, performance was no problem. this has now been changed to a fiber connection (not routed through satellite, buit through cable via coast of africa-protugal) and latency is now around 350-400ms and working is ok, not fine. working is ok if you only have to work occationaly, but working in the accounting, where you have to make lots of enties can be a pain. so we do think about putting a seperate server down to south africa. btw. working from usa is absolutely no problem, as the latency is only 100ms. -joern richter / MACS Hamburg