Deploying SharePoint with Exchange 2007
I am planning to deploy a single server Exchange 2007 configuration and I would also like to start using Sharepoint for collaboration - which would be the recommended deployment script [Sharepoint will also run on its own server] to allow OWA + Sharepoint sites to be used as public resources as well as a common space for exchanging documents, etc. from inside and outside the local network?
I'm just trying to render, but what I would like to do is:
1) Start the internal Exchange 2007 server
2) Start the internal Sharepoint 2007 server
3) Have a server that is NAT'd external (for OWA and Sharepoint access) acting as a CAS Exchange 2007 <- but I'm not sure if this is necessary, however I basically want to expose my OWA and Sharepoint services using one [ external] IP.
Hopefully I'll make it clear to myself - I'd just like to get some guidance on the recommended configuration for what I've explained above.
a source to share
I don't understand a couple of things. Specifically, what do you mean when you say you want to allow SharePoint sites to be used both as shared resources and in a shared document sharing space?
I see this as one of 2 scenario (s) for your internal users to be able to access the SharePoint document libraries as soon as they are successfully logged into OWA. or
(b) You want to make sites publicly available in some type of extranet scenario.
Option B opens up many unresolved issues: authentication as well as licensing. Hopefully this is not what you want to do.
Option A is a little simpler - I can only speak in general since my experience is only SP and this is really (as far as I understand) more of an Exchange configuration issue. I believe that you need to use ISA Server to deploy OWA. Connecting to SP is pretty straightforward and well documented on TechNet.
What you get is access to the document libraries on SP sites that they have access to. This is not a complete SP site. But in 90% of cases it is enough.
My other information is that in order to do this - your end users need to access OWA through IE. Any other browser will pull OWA "lite" which doesn't support OWA to SP connectivity.
If I leave, write more details and we can try again.
a source to share