outlook2k3 + smallBusinessServer2k3

Ruroni

Senior member
Sep 9, 2002
216
0
71
I'm not a technician, I'm not even particularly computer savvy.

I work in a Doctor's office with 3 computers.
1)His secretary
2)His room
3)The closet in which they hide from the patients.
And there would be a 4th remote computer
4)His home computer.

What he wants to do:
He wants to be able to manipulate outlook 2k3 from his office for all the computers (and at some point manage his outlook from home, as well).

The kind of setup:
the 3 computers hook up to a switch, the switch hooks up to an SMC Wireless Broadband router. Only one computer is actually wirelessly connected, the others have an ethernet cable running to the NetGear Switch.

The process we had conceived... Somehow the Doc figured Windows Small Business Server 2003 would be a one pill deal. So he went out and bought himself a 5 license copy. I tried calling MS and they said "That'll be 245" To which I said thanks, but not thanks. In any event, the plan is to install the SBS2k3(standard edition) on the computer in the backroom (wherein they hide me).

I gather installation ought to be pretty cake walk... What I have no idea is how are we going to get it to where he can manipulate everyone's contact list, be able to send messages to his secretary (whose even less tech savvy than me -if that's possible!) all through outlook 2k3?

Any help/suggestions would be greatly appreciated.

If there is something I should have mentioned, to help create a better picture of the situation please let me know.

I've tried googling and stuff, but I've really not found anything concrete enough... Hence I turned to these forums for help.


Thanks


P.S. In case you're wondering why the Doc figured to have a chart filing clerk(me) do this... It's because He knows I play computer games all the time... And I have built a system or two for that purpose... But this is so out of my league... This is for grownups!
So why did I agree to do it? 1)I was cornered into it 2)I thought it might be a learning experience 3)I figured if I could pull this off, I'd look cool...
 

RebateMonger

Elite Member
Dec 24, 2005
11,586
0
0
[Opinion Mode On]

First, although SBS 2003 has wizards for setup and installation, there are some "gotchas" that can cause problems. Your boss should consider hiring an outside consultant who does SBS installations all the time for the initial setup. He'll save a lot of time, money, and frustration by doing so. And a consultant will show you how to take full advantage of what you've purchased. There are dozens of hidden features that could be valuable to your office that you may miss out on.

If you are intent on doing your own installation, a common recommendation is to do TWO SBS installs:
1) Do a practice install and make the mistakes that you will surely make. Add a client PC that you don't care about. Doing the Client PC join to the Domain is the hardest part of installing SBS.
2) Wipe the box and do a second, REAL install.

Frankly, having played computer games and building a couple of home PCs is NOT enough experience to manage an Active Directory Domain Controller and Email Server. Yes, SBS 2003 IS simple to install. Yes, it has great Wizards. Yes, it is relatively reliable and trouble-free. But if you start messing with it and don't know what you are doing, you can easily end up with a mess that somebody else is going to have to come in and fix for you.

[Opinon Mode Off]
----------------------------------------------------------------------------
SBS can do what you want. No problem. It's an excellent choice for the needs you've described. The Doctor will have FULL access to both the Server and all of the Office Computer desktops from his home. Each employee will be able to work "at their desks" from home, too, if you allow them to.

The normal setup:

1) Install the Server in a secured area. One of the points of a Server is to have security. Leaving your Server and your Company's data in an open area is not a good idea.
2) Use two NICs on the SBS Server. That way, SBS can serve as a Firewall for all the internal computers.
Use a Static IP address on the "External (Internet)" NIC and hook it to your Router.
Hook the second NIC to your switch. Hook the client computers to the switch.
3) Have the Router forward ports 25, 80, 443, 444, 3389, and 4125 to the SBS Server's IP address. The your email, web, secure email, remote access, and Remote Web Workplace servers. Forward 1723 if you want to VPN into your network. Be sure to turn on Protocol 47 (GRE) forwarding if you are using the PPTP VPN protocol.
4) Be sure to name your Domain with a NON-INTERNET name, like the suggested "xxxxxx.local". Naming your domain with the same name as your Internet Domain Name will cause problems.
5) After running through the Setup and the "To Do" checklist, you should have a working server, with email, internal Sharepoint site, and full Remote Access.
6) Add User Accounts and Computer Accounts to the SBS Server.
7) Join all your (Windows XP Professional and 2000 computers only!) clients to the Domain using the "ConnectComputer" Wizard. Make sure you understand how to do this properly or you will lose User's profiles on their PCs and will have to search for their old data and desktop files. You want to migrate their profiles over to their new Domain Profile on their PC.
8) SBS will automatically install Outlook 2003 on each computer and automatically create new Domain Email profiles for each user. You'll have to migrate old emails from their old email program to their new Exchange mailbox (using .PST migration if they used to use Outlook).
9) Set up desired Security Groups to easily set up who can access what on the Server.
10) Set up required shared folders (for secure sharing of files) on the Server and set the desired sharing and security permissions, using the Security Groups you've created.
11) Implement and TEST your backup system. Hard drives fail all the time and people make mistakes. SBS makes it REALLY EASY to have reliable, automated backups of your Server and all your Office's important data. Don't ignore this capability. And be sure to make offsite storage of backups part of your backup process.

I STRONGLY recommend that you host your own email. This requires a business-level Internet connection, which doesn't block the required Server ports. Continuing to use the common POP-3 email accounts that many people use is a constant source of complication to email flow. You'll need to register a Domain Name ($10 per year) and set the public DNS settings to point to your new Server.

Each user will now have his/her own mailbox on the Exchange Server, and can read that mailbox from virtually anywhere, using Outlook, OWA, SmartPhone, PDA, etc. This includes personal mailboxes and contacts, as well as shared contacts.

To create a shared contact list, you can create it in a Public Folder in Exchange. After giving each User Account access to the Public Folder, they'll all be able to see and modify (if you allow it) the common office contact list. You can also use Microsoft's Business Contact Manager (Version 2) to create shared contacts. BCM is a free add-in to Outlook 2003.

Sending email, both inside and outside of the Office, to each person will be automatically handled by Exchange and Outlook.

There are a couple of books on how to configure SBS. Harry Brelsford's two SBS 2003 books are popular. Microsoft has one, too. There's also a three-day Microsoft course and certification on SBS installation and management.

Security-related recommendations:
Install SBS SP1.
Install Exchange SP2 and configure the IMF (Spam Filter).
Allow SBS to update all XP Professional clients to SP2.
Use third-party IP-based Spam Server block lists for Exchange.
Insist (and enforce through SBS) LONG passphrases.
Insist that everyone use their own account/password for logons. You have HIPAA compliance to worry about.
Perform monthly patching of the Server and all clients.
Don't allow Windows 95, 98, or ME clients on your network. They are NOT secure.
Install both Server-based and client-based Antivirus products. Get an email-server-aware antivirus for the Server, that will catch viruses BEFORE they enter your email system.
Do monthly tests of your backup integrity.
Do monthly security and patch scanning, using MBSA.