While technically speaking, this is feasible, it is not a recommended solution due to a myriad of factors such as: Load, IIS sites/requirements, I/Ops, traffic, security, etc etc etc. Is there any particular reason you want to place them on the same server? -Allen Firouz

Thanks a lot Allen! Well. I only have one server! LOL. This is an in-house deployment to get me prepared to deploy to customers. I kinda figured i needed a second server because of the IIS issues, exchange and sharepoint were fighting to be my default website. I just wanted verification. I was planning on server number 2 down the road, but i guess now is the time. Thanks for the reply!

Allen. Do you know the workaround that i could deploy to avoid the IIS site issues? I would like to try it to see if i could get it to work. I'd experiment with a Symantec security product to see if it would coexist with mail security. if it works, that would be helpful to my small business clients. If you know the work around to IIS confilcts, please share that with me. Thanks again!

Patrick, The workaround is to enable a second IP Address and bind it to the server. You can then either use Port 80 or use another port (if it is only for testing). This is the simplest workaround if this is a test environment. Let me know how it works out for you. -Allen Firouz

Can you give me a bit more detail on how to do this?