Home Forums AC on it's own server?

I see this thread about servers is still active. Not really sure where to post this.

Sandeep says Windows SBS 2011 Essentials is on sale at NewEgg. Well, it sort of is -- and I am intrigued by his arguments in favor of a server-client network for AC (of course, the peer-to-peer, built-like Topsy network I have been using is working just fine, so it is hard to see what I gain other than bragging rights.)

I downloaded a trial copy of the OS -- and right off the bat, there are problems. Nowhere can I find the hardware requirements! I want to try it out, but I don't happen to have a high powered machine lying around, so will it work on an ordinary dual core machine with 2GB memory?

Second -- we run 2 printers off the "server" in present setup. I can't find anywhere whether printers can be connected to the Server under SBS Essentials, or whether I am going to have to have another machine to be the printer server.

Third -- There is all this talk about sharing folders over the internet and remote management of SBS Essentials -- but it looks like actually running AC remotely would still require RDP to a client machine in the office that I would access remotely as I do now. Looks like the remote machine (at the beach, say) wouldn't really be a "client" of the SBS Essentials -- that would be too slow. Is that true? It is so confusing, and I can't find any documentation anywhere that just answers basic questions -- all the Microsoft stuff looks like sales brochures, and the various tips and helping hands are scattered everywhere in blogs.

The biggest slowdown in our office comes when the front office is scanning in piles of correspondence and old records -- this is done sort of in batches as they have time. That seems to suck resources and slows down the performance in the exam rooms. Does SBS fix that, or is it a property of the database program that AC uses? Or would I be better off just sticking with Win7 and getting a faster "server" machine?

Anyone game to tackle this? Maybe it has already been answered, but I have dredged the boards and can't find exactly these answers.

Thanks in advance

With Server-Client, you have more control over permissions. Who can access what computer/folder, who can delete something, etc.

Single Sign On, logging into your windows account will give you access to your email (assuming you have Exchange), files, etc. If you have multiple computers, you don't have to configure each one individually.

Backups. SBS 2011 automatically backups up all client computer data. Most offsite backup services only allow you to use their plan on one computer. Also, one server is easier to backup than several workstations and "main" computer.

Software. Be able to deploy software to local machines via Group Policy. Or set up shortcuts. Configure WDS to deploy premade images of Windows 7 to any new computers.

Automatic setup of remote desktop for all computers on the LAN, etc etc. RWW over port 443. Widely recognized SSL port. Rarely blocked.

Watch a Vid of the setup video in my signature. I could go on and on.

Interesting: A quick search took me here (The Information Page for SBS 2011):
http://technet.microsoft.com/en-us/library/system-requirements-1


One 1.4 GHz single core (64-bit) or dual-core 1.3 GHz or faster processor.

2 GB RAM

At least one160 GB hard drive.

On that last one. You will get an error during setup if you don't use a 160 GB drive. You can change that though. Do it before you burn the disc/load the iso.

SBS 2011 can share printers easily. A print server is something different which Windows 7 can not do, but SBS 2011 can. Then again Print Servers serve little benefit in a small office environment. Basically, yes you can share printers no problem.

Yes, you'd just be using RDP to a client machine. Just as we recommend with any main computer; you should not be working directly on it. You should be able to RDP to any PC on the LAN without having to open ports for them. The only one you need is 443 which isn't blocked like 3389 (Remote Desktop Default) is in a lot of places.

You can direct access files as show in the image below. Possibly run Word/Excel/PowerPoint over a web browser if necessary (Office 365):

It's probably the network then. If you're scanning to a folder on the server. On a 100 megabits it only has about 12.5 Megabytes to distribute among all the computers on your LAN. When you do those large scans, sometimes the output files end up being 20 or 30 MB depending on the resolution. Scanning one of those would consume all of the bandwith intermittently, resulting in slowdowns. Also with the server handling DNS, DHCP, and all that other good stuff. Your router is basically acting as internet gateway. All traffic goes between the computers/server and the switch

Peer to Peer is good if it works for you, there are advantages to Server client, but...


Fascinating, I was about to say, just google it, but I did and you are right. The requirements should be similar to windows home server which are here: http://technet.microsoft.com/en-us/library/system-requirements-2.aspx . HP (http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02867737/c02867737.pdf ) states that you need 4 GB, but it works fine with 2 in the short run (I had to play with memory, it ran fine)


I haven't tried this, but it should. It will access remote printers similar to any other Windows 7 machine, I would see no reason why it shouldn't but did not try to look this up.

Yes, but RDP is very simplified with Essentials. You are right about not directly answering the questions though. You can run RDP easily thru Essentials to any computer in your network including the Essentials machine. It runs at a decent speed. Your limitation is that of the internet.

The biggest slowdown in our office comes when the front office is scanning in piles of correspondence and old records -- this is done sort of in batches as they have time. That seems to suck resources and slows down the performance in the exam rooms. Does SBS fix that, or is it a property of the database program that AC uses? Or would I be better off just sticking with Win7 and getting a faster "server" machine? [/quote]
Do not use the server as a client machine. Thus, scanning should be done on another machine and saved to the server.

your welcome

Get SBS 2011 or not. Just make sure you get reliable hardware and make good backups.

EDIT: Rephrased to be less mean.

Gene,

Things are calming down. I am completeing an interface between our system and another EMR that uses a screwed up XML format for their files, and finishing a nasty situation where another EMR vendor was going to dump their pitiful excuse of an HL7 file for encounters on us, leave us to parse it with no help, make demands on us for how our HL7 file for demographics should work for them, and then charge the client $9000 for all the setup work they had to do.

And people wonder why I'm so mean and cynical sometimes.

JamesNT

James,

May the Force be with you.

Gene

Thank You, Gene!

And I hope everyone on this forum is looking forward to a safe and relaxing holiday weekend.

JamesNT

[movie_reference]

Use your aggressive feelings, boy. Let the HATE flow through you!!

[/movie_reference]

JamesNT

Sandeep,

I saw your original response. It was far from mean. It seemed to reflect some frustration that not everyone is jumping on the bandwagon.

I have spent much of my life giving people advice, which is at best occasionally followed.

My suggestions:

Speak the truth in love.
Don't take it personally if people do not do as you suggest. You are not in their shoes.

Your contributions to this board, and to the AC user community, have been extraordinary. Thank you.

Gene

Thanks, Gene.

@James Will do

OK, so let's take a step back. While Sandeep and I have touted servers and server OS and stated how easy they are to set up, what Tom did simply wasn't a fair rendition of how to go about it. (I hope not to offend you Tom).

Installing server OS is a bit more difficult than a client desktop. You are laying the foundation for a client/server network. And, anything done wrong will come back to bite you. While installing WIN 7 or XP is something most of us have done hundreds of times, this will be the first install for a server OS for most.

While you can and there are exceptions, server OS are really meant to be installed on server hardware, just as client OS are meant for desktop hardware. You will probably right away run into trouble installing Windows Server 2008 R2 on a Dell Vostro.

Now as far as installation of SBS 2011 Standard (I prefer Standard over Essentials as I want everything on my server), this is a very good article on installation:

http://social.technet.microsoft.com....sbs-2011-standard-build-info-en-us.aspx

Pretty much anything by TechNet or anything by Robert Pearman or Susan Bradley is gospel on SBS or other things Microsoft. Not to go into all the hardware, you will need at least 8GB and preferably 10GB for Standard. 2GB is the minimum with Essentials while 4GB is optimal.

The above link will give step-by-step instructions on the Standard Install. Essentials is also on TechNet.

I still think for those who are actually going to go with an OS install, I HIGHLY suggest using online help but also Train Signal. I can't say enough about it. Actual Microsoft SBS MVPs teaching in videos are just more helpful.

If you have a server and you want to install the OS, there is no rule that you get one shot. You can install the OS over and over. Even use an install answer sheet. After, you can play with it as much as you want. To really get a feel, you need to connect a computer to it so you learn connecting to a domain and how to do things with a user. Set up accounts, email, an SSL certificate. Set up the SBS backup and restore a few times. Play with group policy.

If you do it this way, you will do fine. If you download it to a desktop, your hardware, as Sandeep pointed out, will likely be inadequate.

Maybe not fair, but probably not atypical. My impression has been that Tom is a pretty sophisticated user.

It was extremely atypical. I am sure he is sophisticated, but I know of almost no one who can install a server OS correctly the first time. I have to say this, but I consider myself very sophisticated, and I didn't even consider setting up my server or network the first time. I hired someone. See one, do one, teach one. This isn't to say it is very hard, it is just to say that one should not expect to download and install an OS without issues.

Now, Tom wasn't setting up a network, but he was describing his install of a server OS on a non-server computer (as far as I can tell).

I apologize for this, but I feel compelled to state this, but the hardware requirements are all over the Internet.

I am writing this post because of my stance on servers. I have always said that I prefer servers, I think your computers and AC will run better, BUT one does not need to use a server to use AC.

On the other hand while one can easily use P2P and while the install of a network with a server is more difficult, I feel I need to let people know that if they decide to go with a server setup, that they should not have the impression that "there will be problems right off the bat."

Once again, please no offense Tom.

You can install a server on desktop hardware without issue as long as you meet the requirements. (Which aren't that high, 2GB RAM, 160GB HD, Dual Core Processor.) You can test it in a virtual machine which is my usual recommendation as you don't really have to allocate the full 160GB to install it and you can keep using your personal computer. Download the free VMWare Player (http://www.vmware.com/products/player). You'll need to enable virtualization in the BIOS first.

You can follow the Technet Articles or you can follow the video in my signature. Sets everything up including AC on Essentials. The training videos are just for basic SBS Setup. I took it a step further with optimization for AC. So anyone can follow it.

I'm with Bert on SBS Standard, but it's no walk in the park for a first time user. It's also a lot more than essentials if you don't have proper network and computers in place. The typical gotcha's when installing Standard:
1) Need all Client Computers to be Win 7 Pro, XP Pro, or Vista Pro. (This is rarely the case)
2) Need CALs when you have more than 5 users or Computers
3) Need a domain name
4) Need an SSL Certificate
5) Costs $700 (Not Really Con when you realize you got Exchange 2010 and Server 2008R2 for less than $2000)

Why I recommend SBS Essentials over SBS Standard for first Time Users:
1) Works will Home Premium/Home Editions too.
2) Don't need to buy CALs (25 Free)
3) Free Domain Name
4) Free SSL Certificate

Essentially, no extra "unforeseen" costs. You can see how the additional cost piles up if you have all home editions and/or multiple computers/users. (Bear in mind there is no enforcement of CALs.) With that said, I used SBS Standard because I knew exactly what I would need going in and had it ready in a day.

Wow!! Thanks for all the comments and advice.

First of all, I take no offense. I'm not exactly a newbie -- but I'm not really very sophisticated, either. I'm sorry if I am being annoyingly indecisive.

I started using medical office computers with an Apple IIe in 1980 -- had to hack the Applesoft program to make it work in our office. (The hard drive was as big as the IIe, and it was 4 MB! Made by Corvus, wonder whatever became of them?)

Since then, I have tried to keep up but advanced networking and domains and all the rest is beyond me (even Win7 throws me sometimes) -- and there are only so many hours in a day which have to be shared with other interests. Also, to add to the challenge, my wife who is my medical partner as well, is dead set against allowing EMR into her life, so we run a hybrid paper/EMR scheme. She is also extremely jealous of the time I devote to the EMR -- sometimes I think a real flesh-and-blood affair would be better tolerated.

This, and my natural inclination to keep things simple (isn't that partly why we all use AmazingCharts?) leads me to spend a lot of time evaluating possible new setups before I actually go for them. I'm sorry if Bert and Sandeep are annoyed by indecisiveness and frequent questioning. I try not to ask the same question more than once -- but I find with computer and network setup, what seems the simplest thing can be a major sticking point. For example, after long frustration with inability to track down what seemed to be a bug preventing transmission of certain prescriptions, I finally discovered that one of the receptionists was entering the address "Lewis and Clark Road" as "Lewis & Clark Road" -- and the ERx program simply stopped because of the ampersand. There are so many little things like that. I'm not going to embark on a major system revamp without a lot of thought and preparation.

I think I will eventually get to the server setup, but it looks like a bigger deal than I first thought -- even with Essentials, which seems to be relatively more forgiving. Actually, Sandeep, I haven't installed the Essentials program anywhere yet. I downloaded and burned the ISO and checked to make sure it would boot. I haven't got even to the point of loading it on a machine yet. Your suggestion to put it in a virtual machine is helpful -- but of course, since I have only ever used VirtualBox (which I don't think would work for this) I would have to learn another program in VMWare.

Even after all these years, I find medicine pretty challenging -- the electronics can be a major distraction, frequently adding to, rather than reducing frustration.

Tom Duncan

Thanks Tom. I am certainly not annoyed by your indecisiveness. Changing to a client/server network is a big step especially when your network is already working. I must confess that one of the big reasons I am on here so late is I am working on my computers. I am about to upgrade to SBS 2011 Standard Premium, which means quite a bit of work for me especially because I am not concerned with my song collection but all of my data for my office. I am considering changing from RAID 1 and RAID 5 to a RAID 10. There will be glitches with my clients.

I must say that SBS 2011 Essentials is an inviting way to go for the first time and certainly cheaper. If you are going to have more than 25 users, you can't use it, but that is unlikely. No CALS is a good drawing point. With SBS Essentials, you get:

An extremely user-friendly, wizard based dashboard.
Automatic backups, which will centrally back up all computers on the network.
Remote Web Access. (Forget RDC, LMI, VNC, VPN). Although you can still use those. But, it is an incredibly centralized remote access program, which is super secure.
Windows Server 2008 R2 Standard Technologies for Terminal Services or the perfect backup server for your domain if your system goes down. (With SBS, you can only have one SBS server on the network).
Subscription services to Office 365 allowing Office and Email and Calendar, etc.

You don't get:

SharePoint Foundation 2010
Exchange Server
SQL Server

With SBS 2011 Standard Premium, you get:

Centralized monitoring
Automatic backup
SharePoint Foundation 2010
SQL Server
Exchange Server 2010 SP1
The ability to run 75 clients
Remote Web Access
Windows Server 2008 R2 Standard Technologies w/premium
Windows Software Update Services
Windows Update Services

It definitely is more difficult to install, set up and tweak the standard version. But, if you use the wizards (in both versions you should ALWAYS use the wizards, it is much easier. I just prefer having Exchange, SharePoint and the networking of Office locally. I have much more control with my email with Exchange. And, while SharePoint can be purchased, it comes with the standard version and is probably the best networking software program designed.

I also found an excellent video on SharePoint. Unfortunately, it still doesn't show the simplified home page of content.

I WILL SAY THAT ONE THING THAT HAS HAPPENED GIVEN THE SANDEEP AND BERT SHOW ON SERVERS IS THAT WE HAVE SOMEHOW MOVED FROM WINDOWS SERVER 2008 STANDARD R2 TO WHAT SEEMS TO NOW BE THE DEFAULT: SBS!

Agreed, but if you are going to use Home Editions, then you aren't ready for a server. IMO

Lets you join those computers to your SBS domain. I think it was brilliant on Microsoft's part. So many people turn down the whole Active Directory server/client because they already bought 10 computers with Home Premium. Rather than upgrading those and then having to buy SBS 2011, they can move to Essentials.

That's one of the main features of Professional over Home Premium(domain join) which they giving away for free. The only downside is that those computers can't be remotely accessed. At least not w/o a little tweaking.

A minor correction to Bert's post. SBS 2011 has 2 main versions. Standard and Essentials. With SBS 2008, there was Standard and Premium. The "equivalent" to SBS Essentials was Foundation Server.

Now, you can apply the premium add-on to either one. You can use the Premium Add-On with SBS Essentials as well if desired. The add-on is just Server 2008R2 and SQL Standard. (Bundling them together saves you a few hundred bucks and the CALs are cheaper too.) Which means you can get SQL Standard too if desired on Essentials.

SharePoint foundation can also be installed separately (which I demonstrated earlier on Windows 7). It's free. Obviously, it won't be the same as the tailored SBS 2011 Standard one, but still pretty good.

I probably love Exchange as much as Bert loves SharePoint. Having control over your own email server is awesome. SBS Standard is definitely worth the money. Most people don't care much about Exchange so they go with Essentials.

You should be able to use VirtualBox too. I just mentioned VMWare Player because that was the one I used to demo. It's free. I just like VMWare more. Just make sure you have a lot of RAM because you have to feed 2 Operating Systems. (I remember trying to run a SBS 2011 Standard VM (while I was running Win 7) with 6GB of RAM and dual core processor. Brutal.) Runs great in my current desktop though 16GB (4x4GB) is 80 bucks. 32 Gigs (4x8GB) is less than 200, gotta love the pricing.

Not trying to scare you but you should just consider running SBS 2011 Essentials in a VM all the time when/if you actually deploy it. If something happens you can move it to another computer with ease. That is probably the best thing about virtual machines. Much much much easier to move around on different hardware.

Thaks guys.
I just changed out the broken hinges on an old T41 that my nuse uses -- what a pain. Took a couple of hours. Why do I waste my time on this sort of thing?? That frees up the T61P that I lent her, and so today, I will put the old hard drive back in the T61P and boot up the SBS Essentials disk. Have to get some hands on with it before I make any further decisions.

I'll create a trial network with some other machines around the house and load AC over the next few days.
You understand, I have to do this when my wife isn't looking -- I think she would prefer I look at pornographic sites than spend time with this office computer stuff!
I always have to do my office work from home -- staying late isn't an option -- so this server setup with better remote access and control sounds like just the ticket. When I figure it out, that is.
I can't see much point in Exchange, and I don't understand what
SharePoint is for -- that may come after I get my feet wet with the basics.

I trialed it on my desktop. All virtualized. In fact, that entire SBS Installation tutorial was done on virtual machines. Using nothing more than the high spec computer in the recommended section. Those SandyBridge processors are pretty powerful.

So, what is Exchange, Bert and Sandeep? Well, rather than tell you, let's take a trip. OK. Sounds fun.

So, they all hop in Sandeep's transporter and head to an ISP far, far away. After heading through the clouds and quite some space (actually probably a mile down the road), we arrive at Roadrunner. Sandeep parks the transporter and they all hop out. After knocking on the door, it opens and a very pleasant man welcomes them in. "Hi, welcome to Roadrunner, a subsidiary of Time-Warner. We are quite a large ISP for many customers including you. Our major job is proving you with Internet access and email services."

We're here to look at Tom's email system. The caretaker walks over to a room marked Tom's email. On the door, there is a sign stating POP3 and Port 110. There is a pile of email on the floor. "I do wish you guys would set your POP3 check on a schedule." So, Tom makes a note of this. "So, what is POP3." The man starts to talk, but Sandeep interrupts him. "POP3 is a protocol for receiving email. It is simply Post Office Protocol v3. Your email is stored here until your email program checks for it." "So, where is my sent mail." "Roadrunner relays it for you. No need to keep it around." "It generally is sent here, and we send it right out using SMTP or Simple Mail Transfer Protocol." "Well, what if I need a copy of it?" "Well, you are out of luck."

So, Bert begins to grab all of the email, and copies the entire room's code to his Flash Drive. "What are you doing?" "Don't worry Tom. We are going to move your entire ISP's email and put it on your computer. It is called Exchange. Of course, it makes sense since it exchanges email from your business to the outside world and vice versa, AND, it allows the sending of email to all of your users for HIPAA compliance."

So, we get back to Tom's computer, enter the code, set some things up, and he has Exchange. "So, how am I going to get email?" "Well you could use the POP3 connector and you would still be stuck with your ISP. The POP3 connector is lame, plus you have to wait on your incoming email."

"We are simply going to have all email come directly to your Exchange Server." "That would be cool." "You will need a domain name so the DNS servers can recognize your email address. So, you simply set up your domain name and change your AREC and MX Records, and all your email will be sent directly to your server."

"It seems complicated, but basically when someone sends an email to you, it is sent to a DNS server. The domain name server takes your domain name and changes it to your IP address 72.45.xx.xxx. Using your MX Exchange and ARECs that you set up on your domain host, the email is sent to your server or Exchange Server. Once this is set up, it is transparent so that email does not go to your ISP but directly to your computer. Your sent mail still goes through your ISP."

Sandeep jumps in, "The advantage of this besides quickness (e.g. mail sent, mail received) is that now your entire ISP's mail server is on your computer. The amount of things you can do now are endless. Compare this to Word. We all uses 1% of Word and then add things along the way. Same with your Exchange Server. You can journal all your mail so you have a copy of every email in and out. You can send emails with patient names to your staff. You can set properties on each user's email. With group policy and Exchange Management Console, you can do pretty much anything. To some, this ability is incredible. To others, why not just use their ISP."

Sandeep parks the transporter.

This is getting interesting.

Just so you know that I am not a total flake, I will give you a progress report.

I put my old hard drive back into the T61 laptop and installed the trial version of SBS Essentials. Sandeep said it would work on dual core, and it does.

So far, Essentials works great on the laptop/server, and I have connected another machine to the server with the Connect program (over a wireless connection). Of course, there are no programs on it except Internet Explorer

I also figured out how to log back into my local machine -- at first, I thought I was stuck using it as a client of the Essentials server.

However, now my Network and Sharing center now says I am part of TEST.local domain -- I don't know how to get back onto my original home network. I haven't gone to the office to see what will happen when I try to connect there. Maybe it won't be a problem.

Tomorrow, I will put AC on the Essential server to run on my TEST network.

I'm not ready to think about doing this to the real office yet -- so far I have just been using defaults and wizards -- I haven't the slightest idea what I am doing!
***************
New insight-- I just went to "advanced system properties" and I see the computer is now in the TEST.domain. I presume I can change it back to the LCC workgroup to get back into the home and office network. Is there any way to switch between domains and workgroups without changing the domain in the System Properties window and rebooting? Seems clumsy.

I do think I understand what Exchange is for after Bert's story -- but the idea of emailing patients (or worse, allowing them to email me!) is just too horrifying to contemplate. I could spend my entire life trying to keep up with their foolish spew-- and you can't bill a nickel for all that work.
I don't think I want Exchange!

Tom,

Sounds like fun although be careful Bert and Sandeep will have you deep in the bowels of a server if you let them. Personally I just use logmein from wherever onto my network and not get too complicated. To each their own.

I use Windows 2003 server Enterprise edition which I purchased with 25 cals on Ebay. it works fine although I really use it as peer to peer without a domain. Have fun - stop and smell the roses - or go the Flavel House or Maritime Museum (local fun).

Steven

Tom,

There are workgroups and domains. Once you install SBS Essentials and connect to it using the Connect feature, you are now part of a DOMAIN. That small network is now a client/server domain. This is why I constantly say that client/server is simply P2P with a fancy OS until you connect to it with Active Directory and make it a domain, hence the name TEST.domain.local. I hope the .local is at the end. As Steven says, he uses his as P2P, not a domain.

You can't go back and forth. Well you can by changing to a workgroup and rebooting, but then you are back to your plain computer and on your other network.

Once you connect the way you did (the correct way), you essentially have two different networks.

The whole idea of connecting to Essentials and having a domain is to have all the benefits of being on a domain. In this instance, no offense -- but in order to explain it, P2P 1 point, domain 100 points. THIS IS NOTHING AGAINST P2P JUST AN EXPLANATION. And, it certainly makes it a little more difficult, at first.

This is why I said (I think) to add a client to it. Remember, this is a test. To install Essentials only would be to see it, play with it and at least see what it feels like. To add a client to it USING THE CONNECT METHOD, as you did correctly, is to make a network that you can see. You can always go back by going to:

System Properties | Computer Name tab | Change | Click Workgroup (unchecking Domain) | Type in Workgroup name of your network | Follow the prompts and reboot (MAKE SURE YOU HAVE THE PASSWORD TO THE WORKGROUP COMPUTER.)

WIN 7 now has a wizard above that. I haven't used it, but it looks like it would work much smoother.

One thing you should do just for fun is bring up a command prompt and type >ipconfig /all and compare it with an ipconfig /all of a workgroup. They will be different, and you will see you are on a domain with the domain name and the domain info of your server.

I think we misled you a bit and will hear back from the naysayers. Installing Essentials is relatively simply. Making your network is considerably harder. Actually, that isn't fair to say. Making your network is easy. Look how easily you used Connect and made a domain network. You now do have a domain network (if you stop switching back and forth). This is a TEST. You test it like you did, kick the tires, just see what it is like and get the hell out. LOL. This is also why I, personally, would never suddenly change from a peer to peer to a domain by myself for the first time. And, I didn't. I used someone with considerable networking experience. I had to be set up properly, because while it is MUCH easier to use in the long run, things like DNS and Active Directory are tricky in the beginning.

CURIOUS:

Do you not have email at your office? Why would your patients be any more likely to be able to email you on Exchange than on your current email. Email is email. tomastoria@youroffice.com works just as well as tomastoria@yourdomain_name.com

You don't need Exchange. But, it doesn't make you more vulnerable; it makes you more secure.

PS All in all, I think you did fine. I think all you did wrong was to panic when you say that the client computer was now on a domain and not on your P2P network. But, you would NOT want to change over to a domain network by yourself. It's not that hard, but there are just things you need to know. IF you were going to try it (which I highly think you shouldn't), then get TRAIN SIGNAL. You can also use Sandeep's videos, but research it.

On the other hand, if you were to connect the other clients using Connect, install AC on the Essentials machine, you would have a domain network.

FYI: With Essentials, you don't use Exchange. You basically have Exchange in the cloud. You subscribe to Microsoft Office 360, and everyone has Word, Excel, Powerpoint and Exchange. Some versions come with SharePoint that dreaded program, which remains clouded in secrecy, lol.

Looks like I missed out on the recent posts.

That was quite the story, Bert. Just when I thought the journey through the interwebs couldn't be more enjoyable. Now I'm driving the transport ha. Tom, just in case you missed it, Exchange is like having your own GMail or Hotmail. Even if the Internet were to go down, your emails will all be accessible and you can still email within your network. You can use it internally and externally. You control everything. Shared mailboxes, contact lists, group emails, distribution groups, transport rules (attaching legal disclaimers), etc. Something you can't do with most other services. E.g. a staff account shared by everyone.

Another nice thing is single sign on. No separate logins for email and Windows. Log into windows and your Outlook email will be good to go.

That's exactly what you're supposed to do!
http://amazingcharts.com/ub/ubbthreads.php/topics/41344

I think you've figured out how easy it is to setup. Just run a little connect wizard and you're on a domain network. DNS and Active Directory tend to just work if you're not tweaking stuff. SBS 2011 just works for me. I don't really do anything. Centralized Reporting and backups make life easy. Just an email report once a week to see how things are going.

Tom, this was the way Microsoft was trying to get people legal. Not many people can license Microsoft Office Professional Licenses up front. $300-400 per computer.

SBS Essentials is all about the Cloud while Standard is about on-site. Obviously on-site will be more work. I avoid cloud-based solutions if possible. One of the main reasons, we went with AC over other EMRs. Things tend to cancel out when you have to pay $400 a month to have a reliable internet connection. Then there's the monthly subscription costs which is often licensed per user. For larger corporations, it's a no brainer to go with an onsite solution vs a cloud-based ones. (Bandwith, licensing, etc.) Without internet, a cloud-based business would stop. While the hosting companies rarely go down, your connection is more likely to go down. I'd hate to close the office just because Roadruner wasn't working. Which you would have to do if you were using something like AC's hosted services.

Basically, get Standard if you want on-site Exchange and/or have more than 25 users.

Acrobat does the same with its $400 professional license. They really need to dial down the prices.

Ebay is your friend when trying to get these pieces of software. I scored a copy of Acrobat Pro for $180 last week. Almost paid $400 on Amazon.

Hey Sandeep, Good to see you. Great job of driving, by the way.

After my epiphany, do you think Tom should just go ahead and connect the other computers and go with it. Can't hurt.

And, you are so right about Adobe. How do they live with themselves? They are the only software that I can't keep up with as far as upgrading.

Great advice, Bert. I lol'd at this "The man starts to talk, but Sandeep interrupts him." I was just driving too ha.

I think he should wait to connect the SBS 2011 Essentials until he gets the actual server. I mean he's probably figured it out with one client. That nice little dashboard for managing the server and the launch pad with easy access to shared files and folders among other things.

I think the best part is the summary report on every computer in the domain: https://www5.ibackup.com/qmanager/ibsjsp/IBSGetShare.jsp?key=iowvj20573

Clearly, I have an update pending. There's detailed reports as well that tell you how many emails passed through, whether or not there were any errors, or if someone's mailbox is filling up. I.e. I got an alert that one of the employees used 1.6GB of her 2GB mailbox. So, I just expanded her to 10GB. Not something you can do with a free email account.

I know. Both MS and Adobe need to take it easy. If they reduced the price, they wouldn't be in the Piratebay's top 100 downloads for past 9 years. I know very few people that actually legitimately buy them. I'm probably the only one out of my friends.

Larger organizations get them so cheap. Schools get Office 2010 Pro and Acrobat for less than $100. Windows 7 Enterprise for <$30. It's the people in the middle that really have to pay the price.

Bert/Sandeep/Steven--

Continuing thanks.

Now I have a little network of three laptops, one of which is my Essentials server, the other two are clients.

I figured out how to go back and forth between the TEST domain and my LCC workgroup at the office -- but only by re-jiggering it in the Computer Name window and rebooting. I guess there is no easy way for a single machine to switch between domains and workgroups.

I put the AC on the server, and it works fine on the server desktop. Loaded my whole database on thru restore --- on that machine it works fine.
I have yet to get the clients to connect with AC -- must be some sharing problems.
I might work that out today -- but the weather is pretty nice, and there are other options! (No problem connecting with the server )

I also discovered that Essentials is a lot like Win7 -- I was thinking you couldn't attach a printer to it, but you can, and you can share it. Why don't they answer the most obvious questions in the promo literature??

When I finally get around to building the server, do you think it is worth going with SSD? Are they reliable enough to go without RAID? Does it speed up loading charts and imported items?
Can I go with 128MB SSD for the OS and program and a conventional drive for internal backup?

Cheers, and enjoy Memorial Day -- we should remember in thanks those who sacrificed to bestow us our freedoms, and think about how to neutralize those who would take them away. (The bad ones aren't all Arabs or Russians, either).

Lol it's kind of a assumed. Every Windows OS since Windows NT 4.0 has had easy printer sharing.

Tom,

That is awesome. You have to quit thinking about going back and forth. Sure, I think you want to know if you can go back to the other network, but don't worry about the steps. As Sandeep says, you are either on the domain or on the workgroup. My computers have been on the domain for years. Occasionally, I remove one and reattach it to fix it. You are changing it exactly the way I wrote. It is cumbersome, because you are not meant to do it. By the way, when you attach the same computer back to the server, you should change the name such as amazing to amazing1. Not good to install over the other user.

You can't connect the other ACs because they are on the workgroup. Different networks. Computers have to be on the same network to connect. You can see them, just can't connect.

As far as SSDs, I am in the same boat. Tough question. But, in my opinion, I would go with 256GB if you are going that way. You ALWAYS do RAID.

Will it speed things up? It will pretty much speed everything up. I see Sandeep is typing faster than I am.