Need advice on how to delegate server roles

[JM]

Small network, medical clinic, Windows 2000 Server (Enterprise), +/- 18
workstations, 2
wireless tablets, 3-4 shared printers, a network scanner, and
soon-to-be-deployed network cameras. Today the server is a file server, a
DC, running
AD, and it hosts their primary corp software, a medical billing and CRM app
called Practice Partner (PMSI).

Currently, their AD is a mess. The users are all screwed up, and the
previous IT person had all the users logging in with a master password of
"1234." Group policy isn't properly configured, network resources aren't
properly shared, and most of the users can log in as admin if they so
choose. Everyone knows the passwords. In general, the AD needs to be built
from the ground up, imo.

They want to deploy MS Exchange, which they purchased - along with a way
over-priced server and a copy of Server 2003- prior to my beginning working
with them. For several months, this new server has just been sitting in a
closet, with [burned] copies of Exchange, Outlook, and Server 2003 in jewel
cases sitting on top. The clinic paid good for these disks from the prior
IT guy, but I've yet to work up the nerve to see if they are valid licenses.
At any rate, it's beside the point. If the clinic has to purchase again,
they will.

With these things in mind, how should I integrate the new server running
2003? One important consideration is I will have to leave the current
server running Server 2000. I will not have the option of upgrading it to
2003. The PMSI people are very, very stuck in their ways, and they -
perhaps rightly, I don't know - vehemently insist that the current server
stay at 2000 and continue to run the PP software.

Therefore, here's the situation: I've got a nasty AD on the current 2000
server. It's the DC. It's a file server. It's running the PP software.
It must continue to run 2000 Server and the PP software.

I've got a new server running 2003. The clinic wants Exchange.

What's the best path for integration of the new server and deployment of
Exchange?

Please forgive my leaving out critical info; I'll be glad to fill in the
blanks.

thank you,

jm

 

[Joe Richards [MVP]]

You should probably be looking at Small Business Server version of Windows.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm

 

[JM]

You should probably be looking at Small Business Server version of
Windows.

With all due respect, what kind of answer is this? And why do yo usay this?

jm

 

[JM]

Didn't mean to snip out all the info on my previous reply.

I'm by no means an expert on SBS, but I see two problems: First, the
software has already been purchased. Secondly, I failed to mention that the
doctors access to the PP sofware via terminal services.


jm

You should probably be looking at Small Business Server version of
Windows.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm

Small network, medical clinic, Windows 2000 Server (Enterprise), +/- 18
workstations, 2
wireless tablets, 3-4 shared printers, a network scanner, and
soon-to-be-deployed network cameras. Today the server is a file server,
a
DC, running
AD, and it hosts their primary corp software, a medical billing and CRM
app
called Practice Partner (PMSI).

Currently, their AD is a mess. The users are all screwed up, and the
previous IT person had all the users logging in with a master password of
"1234." Group policy isn't properly configured, network resources aren't
properly shared, and most of the users can log in as admin if they so
choose. Everyone knows the passwords. In general, the AD needs to be
built
from the ground up, imo.

They want to deploy MS Exchange, which they purchased - along with a way
over-priced server and a copy of Server 2003- prior to my beginning
working
with them. For several months, this new server has just been sitting in
a
closet, with [burned] copies of Exchange, Outlook, and Server 2003 in
jewel
cases sitting on top. The clinic paid good for these disks from the
prior
IT guy, but I've yet to work up the nerve to see if they are valid
licenses.
At any rate, it's beside the point. If the clinic has to purchase again,
they will.

With these things in mind, how should I integrate the new server running
2003? One important consideration is I will have to leave the current
server running Server 2000. I will not have the option of upgrading it
to
2003. The PMSI people are very, very stuck in their ways, and they -
perhaps rightly, I don't know - vehemently insist that the current server
stay at 2000 and continue to run the PP software.

Therefore, here's the situation: I've got a nasty AD on the current 2000
server. It's the DC. It's a file server. It's running the PP software.
It must continue to run 2000 Server and the PP software.

I've got a new server running 2003. The clinic wants Exchange.

What's the best path for integration of the new server and deployment of
Exchange?

Please forgive my leaving out critical info; I'll be glad to fill in the
blanks.

thank you,

jm

 

[Jmnts]

Yes Sbs would be a very nice choice in this case, but be carefull with the
hardware, SBS Boxes need powerfull hardware. you should also know that cals
for licensing with Sbs are not the same as for a regular Windows 2003
Check sbs2003 Premium for better security (ISA Integrated and SQL server)

--
Systems Administrator
MCSA + Exchange

You should probably be looking at Small Business Server version of
Windows.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm

Small network, medical clinic, Windows 2000 Server (Enterprise), +/- 18
workstations, 2
wireless tablets, 3-4 shared printers, a network scanner, and
soon-to-be-deployed network cameras. Today the server is a file server,
a
DC, running
AD, and it hosts their primary corp software, a medical billing and CRM
app
called Practice Partner (PMSI).

Currently, their AD is a mess. The users are all screwed up, and the
previous IT person had all the users logging in with a master password of
"1234." Group policy isn't properly configured, network resources aren't
properly shared, and most of the users can log in as admin if they so
choose. Everyone knows the passwords. In general, the AD needs to be
built
from the ground up, imo.

They want to deploy MS Exchange, which they purchased - along with a way
over-priced server and a copy of Server 2003- prior to my beginning
working
with them. For several months, this new server has just been sitting in
a
closet, with [burned] copies of Exchange, Outlook, and Server 2003 in
jewel
cases sitting on top. The clinic paid good for these disks from the
prior
IT guy, but I've yet to work up the nerve to see if they are valid
licenses.
At any rate, it's beside the point. If the clinic has to purchase again,
they will.

With these things in mind, how should I integrate the new server running
2003? One important consideration is I will have to leave the current
server running Server 2000. I will not have the option of upgrading it
to
2003. The PMSI people are very, very stuck in their ways, and they -
perhaps rightly, I don't know - vehemently insist that the current server
stay at 2000 and continue to run the PP software.

Therefore, here's the situation: I've got a nasty AD on the current 2000
server. It's the DC. It's a file server. It's running the PP software.
It must continue to run 2000 Server and the PP software.

I've got a new server running 2003. The clinic wants Exchange.

What's the best path for integration of the new server and deployment of
Exchange?

Please forgive my leaving out critical info; I'll be glad to fill in the
blanks.

thank you,

jm

 

[Joe Richards [MVP]]

Powerful is a relative term. Most of the DC only machines I have deployed to
most enterprises would blow an SBS box out of the water in terms of required
capacity/power.

You simply need a box that can stand up to the applications/services and client
load that will be thrown at it.


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm