OK, so for some reason, I can't find the thread I wanted to comment on, so I am starting a new one. While my title is witty and inviting, it is also meant to give Jon and John obvious fodder for poking fun at me as only they can do.

The thread was on SBS 2008 and SBS 2011 Standard and Essentials. I was with Sandeeep on using 2011 Standard even though I am on SBS 2008 Standard.

Wendell, who I find very intelligent on these subjects predicted I would disagree, and I do, so we will agree to disagree.

First, a domain is a group of accounts and network resources sharing a common database known as Active Directory and Security Policies. As such, it can use single sign-on allow clients to authenticate against the server and access certain services based on their account. The admin can do everything from the server including making users, mailboxes, permissions, etc.

A workgroup is a network of computers that does not use a single server and may require users to use multiple passwords to access certain resources. One could argue that given they are usually connected to a switch and the main computer is also connected to the switch that the main computer is the central computer.

In order to have a client/server domain, there must be a domain controller usually on the server. It so happens that with SBS, you can only have one domain controller on a network.

While one only needs a P2P workgroup to run AC basically as effectively as a client/server configuration, having a domain network does give multiple, multiple advantages, but it is necessary only if you want those advantages. Certainly, it takes a certain level of expertise for a client/server network compared with a P2P, but again, please let me state that a P2P is all that is necessary for AC.

I may be missing something but I do not see WHERE AMAZING CHARTS FINDS AC SHOULD NOT RUN ON A DOMAIN CONTROLLER. Please correct me if I am wrong.

EMAIL: Maybe Wendell is leaving some explanation out of his logic, but I find there are three levels of communication with AC, all of which having distinct advantages. We use, and I think many use some type of messenger system to allow instant communication across the network such as telling the physician Dr. So and So is on the phone. Using email or AC does not facilitate that communication as well. Most messages that are not speed-critical but are patient dependent work best with AC. Finally, email is simply email. I can't imagine not having email in any type of busiess.

While you can use any ISP with SMTP and POP3 for email and even combine these with a domain name, the advantages of using an Exchange Server are too many to mention. As Sandeep says, your email resides on your server and not on Roadrunner's or Yahoo. You can control your MX records and AREC (to point incoming email directly to your Exchange without even passing through an ISP. You can send email through your intranet without its going over the Internet. You can set up Journal Mail to copy EVERY email coming and going and even coming and going over your network. If this is not HIPAA required now, it will be. I have EVERY email copied from the day I opened. There are many, many other things you can do. When you look at the perceived complication of MX records and AREC, etc. (used also in regular ISP POP3 email), this can be set up in an hour by an IT specialist. Not one that is good at X-Box, but one that is good with Exchange.

Finally, SharePoint. This is where the Sushi analogy comes in. Microsoft considers SharePoint to be the most under utilized, highly rated product in their arsenal. I could sit here until I am blue in the face, but I can't even do justice to how helpful SharePoint is. Sure, I could say that one can put a website address on it for everyone, but you will just say we use favorites. I could say that you can put every file and folder on it so everyone can access it, but you will just say we share them from the server. So, I won't even attempt to explain why putting them on SharePoint is advantageous. Plus, SharePoint can do many other things including being the company website (not externally but on the intranet.

It is rather cool to be able to click on the companyweb (SharePoint) from home an instantly have that website appear at home with all the information you have in your office. This is much more secure than allowing users direct access to the user.

I also left out one of the neatest things with Exchange. Sure, you can use many techniques to get to Outlook Web Access or Outlook Anywhere, but to be able to use Outlook via HPPT/RPC and actually have Outlook at home which is identical to the Outlook on your desktop. In other words it is directly accessing Exchange Server. There are times that email sent to my server hits my Outlook at home before it does on my desktop. This is not sync. This is an actual Outlook connection to your Exchange Server.

Please understand that Exchange Server on your network server is somewhat akin to your ISP server that holds your email, but you have to access it so often.

Now the sushi part. It seems that most of us have acquired a taste for certain foods from so young that we can't even recall when we liked them or when we didn't. Sushi is almost the only example of a food that many don't necessarily like or dislike. They just haven't tried it. Many just assume they won't like it. SharePoint is like Sushi. You won't know how good it is until you've tried it. Or, like some, you won't like it.

I will say that SharePoint was down for a few days due to my ineptitude, and my staff nearly quit.

Bert
Pediatrics
Brewer, Maine