Outlook Web Acccess loading.......

[RebateMonger]

Microsoft Exchange MVP discussing removal of IIS on an Exchange 2003 Server:

"You mean uninstalling IIS? Nope - nothing special. Just go into the
Control Panel, Add/Remove Programs, Windows Components, uncheck IIS, let it
go through, then go right back in and re-check it to reinstall the
components. Once that is done, re-run Exchange setup, and from the install
type dropdown, choose Reinstall. Once that is complete, reinstall SP1 and
you are good to go. Unless these are symptoms of a larger problem, this
ought to fix IIS/OWA.
--
Ben Winzenz
Exchange MVP"

Exchange 2003 requires IIS for installation, but, apparently, you can REMOVE IIS without removing Exchange. HOWEVER, Exchange apparently modifies some IIS files, so you have to re-run the Exchange Setup to "fix" IIS so it'll work with Exchange (OWA).
And, NO, I've never actually done it. It'd be easy enough to try (risk-free) in a Virtual PC image.

 

[klnyc]

Originally posted by: Blackforge
A front-end servr that is a DC? Thats bad news to begin with...

Yeah I know, it was like that before I came into the company.
Dumb ideal....thats why I wanted to seperat them. I posted some where in this forum about backing up exhange and restore onto another server.

 

[klnyc]

Originally posted by: RebateMonger
Microsoft Exchange MVP discussing removal of IIS on an Exchange 2003 Server:

"You mean uninstalling IIS? Nope - nothing special. Just go into the
Control Panel, Add/Remove Programs, Windows Components, uncheck IIS, let it
go through, then go right back in and re-check it to reinstall the
components. Once that is done, re-run Exchange setup, and from the install
type dropdown, choose Reinstall. Once that is complete, reinstall SP1 and
you are good to go. Unless these are symptoms of a larger problem, this
ought to fix IIS/OWA.
--
Ben Winzenz
Exchange MVP"

Exchange 2003 requires IIS for installation, but, apparently, you can REMOVE IIS without removing Exchange. HOWEVER, Exchange apparently modifies some IIS files, so you have to re-run the Exchange Setup to "fix" IIS so it'll work with Exchange (OWA).
And, NO, I've never actually done it. It'd be easy enough to try (risk-free) in a Virtual PC image.

You know what? I'm going take a chance. I did few time re-reinstall Exhange before.
By re-reinstalling doesnt alter any mailbox anyway, its just reinstalling the sys files. I hope this work.

 

[spyordie007]

Exchange 2003 requires IIS for installation, but, apparently, you can REMOVE IIS without removing Exchange. HOWEVER, Exchange apparently modifies some IIS files, so you have to re-run the Exchange Setup to "fix" IIS so it'll work with Exchange (OWA).
And, NO, I've never actually done it. It'd be easy enough to try (risk-free) in a Virtual PC image.

Wow, I'd definetly want to try this one in the lab but that's interesting to see.

Obviously while IIS is uninstalled the Exchange services would be stopped (and you couldnt start them if you wanted to due to dependancies); but it's good to know that repairing the Exchange install would fix Exchange after a reinstall of IIS.

I wonder if this works on both Server 2000 or only 2003.

You know what? I'm going take a chance. I did few time re-reinstall Exhange before.
By re-reinstalling doesnt alter any mailbox anyway, its just reinstalling the sys files. I hope this work.

You're correct; the mailboxes *shouldnt* be effected by doing a repair install of Exchange. I would still try this procedure in a lab enviroment first and make sure you have good backups before proceeding; but if this information is correct you should be fine.

You never answered my question earlier; have you verified whether URLScan is installed on this server?

 

[RebateMonger]

Originally posted by: spyordie007
Obviously while IIS is uninstalled the Exchange services would be stopped (and you couldnt start them if you wanted to due to dependancies); but it's good to know that repairing the Exchange install would fix Exchange after a reinstall of IIS.

I went throught the Service Dependencies:
IMAP, POP3, and The Exchange Routing Engine are dependent on IIS Admin Services.
It APPEARS that Exchange can function without the Routing Engine. The Information Store will keep running, it seems. You'll certainly lose IMAP and POP3 services (if you use them.....I don't....)

Microsoft Exchange Routing Engine:
Description: Provides topology and routing information to Exhange Server 2003 servers. If this service is stopped, optimal routing of messages will not be available.

 

[RebateMonger]

Originally posted by: spyordie007

A front-end server that is a DC? Thats bad news to begin with...

I agree that it's less than ideal; granted there are a lot of SBS servers running this way out there...

It's certainly possibly to argue the pros and cons of having a DC on the front-end of a network. But, as you point out, Microsoft "validates it" with SBS, but, at the same time, says it's not a "Best Practice". Security is always subject to tradeoffs with cost and complexity.

 

[spyordie007]

This is true; they've changed the service dependency hierarchy in Exchange 2003 and that will help a lot. (Exchange 2000's Information store was dependant on the IIS Admin service).

Some more info for you if you're still planning on doing an IIS reinstall Klnyc:
http://support.microsoft.com/kb/320202/EN-US/

According to the article they suggest dismounting the information stores and stopping the Exchange services while you are doing a reinstall of IIS and than not re-mounting the information stores until you've done a repair install of Exchange and reapplied the SP. In 2003 you might be able to get away with leaving the Information stores (and service) up and running (along with management and the system attendant).

 

[RebateMonger]

Yeah. personally, I would:
a) Test this all on a virtual server
b) Back up the mail stores and dismount them during the removal/re-install
c) Do it on a weekend

 

[spyordie007]

Originally posted by: RebateMonger
Yeah. personally, I would:
a) Test this all on a virtual server
b) Back up the mail stores and dismount them during the removal/re-install
c) Do it on a weekend

Definetly; the only thing I would add in would be upgrading to server 2003 along the way.

 

[Blackforge]

Originally posted by: RebateMonger

Originally posted by: spyordie007

A front-end server that is a DC? Thats bad news to begin with...

I agree that it's less than ideal; granted there are a lot of SBS servers running this way out there...

It's certainly possibly to argue the pros and cons of having a DC on the front-end of a network. But, as you point out, Microsoft "validates it" with SBS, but, at the same time, says it's not a "Best Practice". Security is always subject to tradeoffs with cost and complexity.

Its one thing to make a back-end server a DC, but a front-end? I don't see this as being recommended in any situation security-wise.

If it truly is a front-end server then it should be fairly easy to remove and move to a new server. Is OWA exposed directly to the internet? SSL on the front-end server should be used in this case.

 

[spyordie007]

There's not really a good answer here.

Generally I agree it's a bad idea to have a DC anywhere except for protected networks. On the networks that I design/admin there are no DCs on perimiter networks/open ports/etc. because it's not worth the security risks.

On the other hand if you have a very small organization with a single SBS server opening up OWA to SSL may be an acceptable risk.

The risks/benefits have to be weighed carefully when opening connectivity to any servers; especially DCs.

 

[klnyc]

Originally posted by: spyordie007

Exchange 2003 requires IIS for installation, but, apparently, you can REMOVE IIS without removing Exchange. HOWEVER, Exchange apparently modifies some IIS files, so you have to re-run the Exchange Setup to "fix" IIS so it'll work with Exchange (OWA).
And, NO, I've never actually done it. It'd be easy enough to try (risk-free) in a Virtual PC image.

Wow, I'd definetly want to try this one in the lab but that's interesting to see.

Obviously while IIS is uninstalled the Exchange services would be stopped (and you couldnt start them if you wanted to due to dependancies); but it's good to know that repairing the Exchange install would fix Exchange after a reinstall of IIS.

I wonder if this works on both Server 2000 or only 2003.

You know what? I'm going take a chance. I did few time re-reinstall Exhange before.
By re-reinstalling doesnt alter any mailbox anyway, its just reinstalling the sys files. I hope this work.

You're correct; the mailboxes *shouldnt* be effected by doing a repair install of Exchange. I would still try this procedure in a lab enviroment first and make sure you have good backups before proceeding; but if this information is correct you should be fine.

You never answered my question earlier; have you verified whether URLScan is installed on this server?

Man, I really appreciated everybody it's soo freaking nice to help me out.... OMG!!!

Spyordie: Nope, no URLScan installed on my E2k. I bet its the stupid SUS, those updates are over killed sometime. You know?
If, I ever pull this out, I'm going do a step by step write up. T

 

[RebateMonger]

Originally posted by: Blackforge
Its one thing to make a back-end server a DC, but a front-end? I don't see this as being recommended in any situation security-wise.

If it truly is a front-end server then it should be fairly easy to remove and move to a new server. Is OWA exposed directly to the internet? SSL on the front-end server should be used in this case.

I've been told that there are more total Exchange installations on Windows Small Business Server than on ALL other Windows Server boxes combined. Virtually all of these are "front-end" servers. They may be behind a hardware firewall/router.

The "Best Practice" for these single SBS boxes is to run ISA on them and publish OWA and other sites via ISA. SBS uses OWA SSL by default. If companies running SBS have a second server, it's usually BEHIND the SBS server, acting as a terminal server or other application server.

 

[klnyc]

Okay, if I want to delete the virtual dir, will this automatically recreat it self?
If not, how would I go about backing it up prior removing it?

thanks

 

[spyordie007]

The Exchange reinstall should recreate the virtual directories under IIS.

Unless you are refering to a virtual directory of your own; in that case I would use the IIS 6 snap in and right click on the VD>all tasks>save configuration to a file

 

[klnyc]

Originally posted by: spyordie007
The Exchange reinstall should recreate the virtual directories under IIS.

Unless you are refering to a virtual directory of your own; in that case I would use the IIS 6 snap in and right click on the VD>all tasks>save configuration to a file

No,it'snot my own, its the Webadmin,Exchange and Public folder. Btw, I still using IIS5.0.
So, bottom line its... all those 3 folders *should* automatically recreat it self when its been delelted? Just wanna make sure.

 

[spyordie007]

Yes, the Exchange reinstall will recreate its virtual directories.

Btw, I still using IIS5.0

I know, but it's easier to backup the virtual directories with IIS 6's snap-in and I had thought that it would work from an XP client. Unfortunetly I just tried it with a 2000 server and it wont let you save VD configurations to file from an IIS5 server when running the IIS 6 snap-in under XP (it does if you connect to an IIS 6 server). So you can disregard that comment.

So basically if you want to make a backup of those VDs you'll need to backup the IIS Metabase. Granted this would happen as part of a system state backup which you really should be doing before you perform any of these steps we've been talking about anyways.

 

[klnyc]

Ahh I finally fixed this problem. All the tips and links didnt work for me, maybe for some of you did. Here's what I did. I delete all Vir Dir from the Default Website on the IIS. I also remove sp2 and reinstall over again. Now, everthing works great. Thanks for you all you help here.

 

[Brazen]

Originally posted by: spyordie007

Originally posted by: RebateMonger
Yeah. personally, I would:
a) Test this all on a virtual server
b) Back up the mail stores and dismount them during the removal/re-install
c) Do it on a weekend

Definetly; the only thing I would add in would be upgrading to server 2003 along the way.

Won't he have to purchase Server 2003 CALs then?