exchange server question

[rasczak]

We're doing a major hardware software upgrade to our network infrastructure. Currently we're running 2003 server AD using POP3 as our internal email server (I know I know, but this is what I inherited). We're going to 2008 standard, but noticed that pop3 does not come with this edition.

The question is, could we use 2008 SBS for exchange services only on the 2008 network? Or am I limited by the fact that SBS would probably need to be a DC (which we cannot allow on this network)?

 

[dphantom]

SBS is a DC with additional functionality. When installed, it will be a DC on the network.

 

[rasczak]

SBS is a DC with additional functionality. When installed, it will be a DC on the network.

I had thought I read somewhere that it is limited to being the "only" dc on the network. I'm trying to find the literature on it. We're ordering sometime between this week and next and the pop3 issue was something that was overlooked.

 

[Nothinman]

AFAIK SBS has to be the only DC, although other servers can be members. And POP3 is part of Exchange, not Windows.

 

[rasczak]

AFAIK SBS has to be the only DC, although other servers can be members. And POP3 is part of Exchange, not Windows.

Ahh, I thought so on the only DC part. However, in Server 2k3, there was a standalone POP3 service. No exchange was necessary.

Now I just need to find the literature on the part regarding it being the only DC on the network. I need to show my boss this before he starts ordering next week.

Thanks nothinman.

 

[Nothinman]

Ahh, I thought so on the only DC part. However, in Server 2k3, there was a standalone POP3 service. No exchange was necessary.

Now I just need to find the literature on the part regarding it being the only DC on the network. I need to show my boss this before he starts ordering next week.

Thanks nothinman.

I'm not sure what POP3 service you would be talking about, POP3 is just a MUA protocol and AFAIK Exchange is the only MS mail server.

 

[rasczak]

I'm not sure what POP3 service you would be talking about, POP3 is just a MUA protocol and AFAIK Exchange is the only MS mail server.

I see that now. Sorry for the confusion. Another question, is there a viable government approved alternative to Exchange for the windows platform? Otherwise I am looking at having to use sendmail on our solaris system which I really don't want to do.

 

[yinan]

Nope, why would you not want to run Exchange? It is a really good mail platform.

 

[dphantom]

I am not sure what you mean by government approved but there are a number of alternative Windows compatible email systems. Two major ones are Lotus Notes and GroupWise. Mercury is a client based alternative to a client/server email system.

So there are many alternatives out there.

 

[Lifted]

Exchange has POP3 support, as well as IMAP, and Active Sync, and ...

What is the issue exactly? You can't go with Exchange Standard or Enterprise, but running SBS just for Exchange is acceptable?

 

[dphantom]

Here is a possibility. Note this is not reviewed, tested, warranteed, use at own risk, blah, blah.

http://weblogs.asp.net/hpreishuber/...tp-pop3-extender-for-windows-2008-server.aspx

 

[Lifted]

Currently we're running 2003 server AD using POP3 as our internal email server (I know I know, but this is what I inherited). We're going to 2008 standard, but noticed that pop3 does not come with this edition.

Question - if you're doing a major upgrade, and you realize POP mail is absurd for internal use, why continue using it? Is it not possible for you to make a recommendation to move to Exchange? Now would be the time as the purse strings are opening, even if it's only just enough to grab a few bucks.

 

[rasczak]

Question - if you're doing a major upgrade, and you realize POP mail is absurd for internal use, why continue using it? Is it not possible for you to make a recommendation to move to Exchange? Now would be the time as the purse strings are opening, even if it's only just enough to grab a few bucks.

The issue is that we're not a big project. At the most we only have 200 users, and do not need the most of the functionality that exchange comes with along with its big price tag. Hence why I'm looking at a simple mail solution.

Here is a possibility. Note this is not reviewed, tested, warranteed, use at own risk, blah, blah.

http://weblogs.asp.net/hpreishuber/...tp-pop3-extender-for-windows-2008-server.aspx

thanks for the link. I saw this yesterday as i was doing some research. Unfortunately, I need it to be a commercially available, "DoD Approved" software.

I've found some and if it's ok, I'll link them here for some feed back.

 

[rasczak]

Exchange has POP3 support, as well as IMAP, and Active Sync, and ...

What is the issue exactly? You can't go with Exchange Standard or Enterprise, but running SBS just for Exchange is acceptable?

It really does come down to cost/functionality. If I could get an SBS exchange server to run without having to become the root DC as well as get past the 1 DC per domain limit, then I'll go that route. But as it stands I can't find anything to disprove the notion that SBS exchange will run without having to become a DC and become root DC. This network will be a regular 2008 standard network, and the SBS exchange server will only be a component.

 

[dphantom]

It really does come down to cost/functionality. If I could get an SBS exchange server to run without having to become the root DC as well as get past the 1 DC per domain limit, then I'll go that route. But as it stands I can't find anything to disprove the notion that SBS exchange will run without having to become a DC and become root DC. This network will be a regular 2008 standard network, and the SBS exchange server will only be a component.

That cannot be done. SBS will not work in your environment - at all. You need an Exchange server as that is DoD approved.

 

[rasczak]

That cannot be done. SBS will not work in your environment - at all. You need an Exchange server as that is DoD approved.

I thought as much. Thanks!

 

[Lifted]

It really does come down to cost/functionality. If I could get an SBS exchange server to run without having to become the root DC as well as get past the 1 DC per domain limit, then I'll go that route. But as it stands I can't find anything to disprove the notion that SBS exchange will run without having to become a DC and become root DC. This network will be a regular 2008 standard network, and the SBS exchange server will only be a component.

Along with not being supported (which would be BAD if 200 users are depending on it), and probably not even being possible with the version of Exchange on SBS, I'm 100% sure it's not legit w/r to the licensing agreement.

SBS has a limit of 25 or 75 users/devices accessing the server anyway (Essentials vs Standard/Premium).

I'm not sure how you came to the conclusion that SBS would somehow be cheaper for 200 users than Exchange Standard. SBS 2011 Standard only includes 5 CALs, and if it were possible (it's not), you would need to purchase another 195 CAL's.

 

[rasczak]

Along with not being supported (which would be BAD if 200 users are depending on it), and probably not even being possible with the version of Exchange on SBS, I'm 100% sure it's not legit w/r to the licensing agreement.

SBS has a limit of 25 or 75 users/devices accessing the server anyway (Essentials vs Standard/Premium).

I'm not sure how you came to the conclusion that SBS would somehow be cheaper for 200 users than Exchange Standard. SBS 2011 Standard only includes 5 CALs, and if it were possible (it's not), you would need to purchase another 195 CAL's.

My mistake. I was misinformed about pricing. I'm looking at the prices now.

 

[stash]

AFAIK SBS has to be the only DC, although other servers can be members.

This is not true. You can have as many DCs you want in an SBS network. The limitations are that you can only have one *SBS* server on the network, the SBS server must hold all five FSMO roles, you can only have a single domain forest, since SBS does not support any kind of trust. The SBS server must also be a global catalog, but you can make other DCs GCs as well.

You could also dcpromo a SBS 2003 server into an existing domain with the same rules above, but I'm not sure about the newer versions of SBS.

 

[Nothinman]

This is not true. You can have as many DCs you want in an SBS network. The limitations are that you can only have one *SBS* server on the network, the SBS server must hold all five FSMO roles, you can only have a single domain forest, since SBS does not support any kind of trust. The SBS server must also be a global catalog, but you can make other DCs GCs as well.

You could also dcpromo a SBS 2003 server into an existing domain with the same rules above, but I'm not sure about the newer versions of SBS.

Ah, for some reason that never sticks in my head...