Similar Threads:
1.Exchange Outlook Web Access & Windows SharePoint Services
Hi,
Is it possible to install Windows SharePoint Services on the same server as
Exchange 2003, with Outlook Web Access enabled. All I can find is that it
can't be done, but these are all topics about SharePoint Portal
server/SharePoint Team Services.
Since Small Business Server 2003 installs (among others) both products on
the same server it should be possible. Doe anyone know how to do this?
Best regards,
Dennis.
2.Windows Sharepoint Services vs Outlook Web Access Deathmatch
Greetings wise WSS users,
perhaps someone could help out a baffled beat-up Exchange administrator....
I have a single Windows 2003 Standard edition server, DC, GC, ABC, ETC,
running Exchange 2003 with SP1 and Outlook Web Access with Forms Based
Authentication. The server also runs Microsoft Virtual Server 2005. I have
little IIS expertise but I will try and describe my configuration to you.
I have a site on port 443 which contains a basic web page, I have the
exchange virtual directories for outlook web access (exchange, exchweb,
public, etc), and have recently installed Windows Sharepoint Services with
SP1, creating a virtual directory called SPS (probably should have called it
WSS to avoid confusion, but I digress) Not that I can actually see the damn
thing in IIS Manager -Is it actaully a Virtual Directory?
I have another site running on port 1024 which is used for the interface to
Virtual Server 2005.
And of course I have another site called SharePoint Central Administration
on port 6202.
When I installed WSS, I 'upgraded' the Default Web Site which seems to have
killed both OWA and the Virtual Server 2005 administration site.
I followed (and quadruple checked) the instructions in KB823265 and KB832769
(configure sharepoint services to use Kerberos, and configure sharepoint
services to exclude the exchange directories)
When I attempt to access OWA I get '440 login timed out'
When I attempt to access Virtual Server 2005 I get a nice interface from VS
2005 teling me it: Could not connect. Access was Denied blah blah.
Both of these seem to point to some sort of Evil which may have been
installed with WSS. No actually I think it's pointing to some Kerberos
issue.
I have tried resetting the IUSR_ and IWAM_ passwords to no avail.
Can someone please please help me as this is very frustrating.
Thank you in advance for any information you may be able to provide
Regards
Glyn
3.HTTP / RPC and Outlook Web Access Stopped Working
Running Exchange 2003. I just installed SP2 for Windows 2003 server. Not
sure if this is related but now my remote users connecting via Outlook 2003
HTTP over RPC and Outlook Web access is not working.
Outlook web access does work from inside the network. just not remotely.
Please Help!!!
4.Outlook Web Access - HTTP/1.1 503 Service Unavailable
5.Outlook Web access error HTTP/1.1 503 Service Unavailable
hi guys, heres my situation.
We have 2 exchange server. Exchange A the original one and we
recently
added a new one for our VPN clients ExchangeB. Problem is user with
mail boxes on Exchange B can not access their mailboxes from Exchange
A thru //exchangeA/exchagne. Bigger problem is by using //exchangeB/
exchange i can access mailboxes on exchange A but can not access
mailboxes on exhange B the local server. Havnt yet tested from
outside
cause i think it should work internally first. Now i made Exchange B
as the front end server as i could not make Exchange A the front end
server cause of Reciepent Update Services running on it.
Wht am I missing here ppl.. is there a virtual directory i need to
make on Exchange A so it will relay to Exchange B. which i do not
think is problem cause if relays fine for mailboxes on B from A...
or
is it an IIS issue ??
Please help me .. clients are getting impatient
Thanks in advance,