What is the best way to use AC in more than one office while keeping one data base?
I appreciate any input?
This was the question. The question was not, "How can I log in to computers at my other office. Wendell's suggestion of using LMI works for him because he uses TWO databases you stated one.
If you can set up LMI (takes 30 seconds) at home and log into your computer at work, that's great. That is what it is for. It is NOT for connecting two offices.
You asked how to set up a satellite office so it connects to one database. That is both easy and hard. But, you can't do it correctly by logging into several different computers on the other end. S = Satellite computer. PC-S1 can log into PC-H1 but only if there is no one using the host one computer. And on down the line. From what I am reading above (and I may be reading it incorrectly), the scenario is this: Imagine my setup. I have 10 client computers connected to one SBS 2008 computer. If I set up another office with three computers, how are they going to log in? Are they going to log into the server? They could if TS was set up. But, no one in their right mind will let other users log into the main server. When I said domain controller, sorry. That just designates the actual server that your office runs on. A TS is separate.
I know that my first answer got too complicated. But, then you would have asked what is a terminal server, etc. To answer the above question, they would have to log into a client machine that is connected to the server. Great if no one is on that computer. Great if that computer is on. Great if everything is working with AC, etc. Try this experiment. You could do this at work but to make it a better experiment, go home and use LMI or RDP to log into a computer someone is using and see how happy they are.
Basically, most are saying you can log into various computers on your host network and connect to the database. That will cause issues. If you have five computers on your host network, the users at the remote office will have to log into one of those computers or the server. Why not have just ONE powerful computer to log into that is made for this type of setup. Now all five of your remote computers can log into the terminal server until their heart's content. You also can put AC on there or office or whatever.
Look at it this way. Sorry to give so many scenarios. You have your host network with five computers connected to a server. You could enable terminal services on the server and log in there. The ONLY problem is no one wants to have their main computer being used by remote clients. Solution. You add one more server. That's all. Get an HP ML110 for $1500 and add the second OS that Sandeep and I mention.
You mention you want 1, 2, 3. It is easy for an IT tech, but it isn't 1, 2, 3. I say this all the time, but if you have to ask, then you need help. This is your patient data. Don't screw with it. Get a professional who will give you all your options and tell you I am crazy. Go to Google, look for Microsoft Certified IT Professional and MVP and pay him or her to consult and set up. It will be the best investment you'll make. I guarantee you, you can't do this by yourself.
My answer to you is either cloud or something like Terminal Server. Your question is a good one, but when this question comes up, two things happen. First, this is the most challenging thing to set up for a beginner, and two, the asker wants a simple answer. It is simple but only if you are somewhat skilled in networking.
Questions such as DSL vs Cable vs T1 or even T3 have to be looked at. Do you have a backup plan if your Internet goes down? What access do you have to your IT. I mean Microsoft IT, not the infamous IT guy down the street.
With TS and what Sandeep mentioned, your users would turn on their computer, click on RDP and be in TS and with their session running, they wouldn't even know it wasn't on their own computer. Why not RDP into one of the clients. You can if it is not in use. But, TS will allow multiple, concurrent sessions.
Yes, if you go with a Terminal Server (which I am assuming both offices will be running simultaneously unless one is open in the day and the other at night). It will cost you an extra server, OS software and CALS. And, it will DEFINITELY cost you an IT person.
I have a friend in Canada who has been doing networking for 35 years. Strictly Microsoft. He is always blown away by the fact that doctors do not want to invest in their networking when their entire patient data is at stake. His analogy, which is obvious, is if you told your a patient that you were worried about pancreatic cancer and recommended an MRI (sorry if it is CT), and they opted for a plain film, you would go nuts.
What I am talking about is two offices using AC, finishing a note, and all the data seamlessly being saved to the same server.
