Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2612
  • Last Modified:

Exchange 2007 OWA folders problem

HI,
We are in process to migrate our exchange 2003 to exchange 2007. We have one exchange server 2003 do mailbox, OWA, RPC.

I install a new server with Exchange 2007 with Mailbox, Hub and CAS role on it. (small organization less than 50 mailbox). All work good in the instillation process, i do not transfer any user at this time. my goal is to use nuew SSL certificat, new public IP, making exchange 2007 working good and then transfer user on the new server.

Now I try to configure SSL for OWA part but in the Exchange Management console->Server Configuration-> Owa Web Access i can only see the OWA folder. The Exchange, exchweb and public are not displayed here...
I go in IIS to see wath append, this 3 folder (exchWeb, exchang and public) if I try to explore i got this error: Could not find a part of the path  \\.\BackOfficeStorage\MyDomain.com\MBX
If I use a browser and go to https:/localhost/exchange  owa open on the old exchange 2003.

Questions:
1- This behaviour is normal? I think when I will remove the old exchange server i will not need these 3 folder anymore? Exchange 2007 use only the owa virtual directory?
2- It is normal that these 3 folder are not displayed in the Management console->Server Configuration-> Owa Web Access ?

for now I try to reinstall CAS, remove and recreate virtual folder with powershell: same result.

Thanks for your help
0
pdsavard
Asked:
pdsavard
1 Solution
 
flaphead_comCommented:
do the installation give any errors?
Have you looked at the setup progress log?
 - located in the <Installation Drive Root>\Program Files\Microsoft\Exchange\Scripts  run  Get-SetupLog.ps1
- Any errors?

Running Get-OwaVirtualDirectory should list:
owa (Default Web Site)
Exchange (Default Web Site)
Public (Default Web Site)
Exchweb (Default Web Site)
0
 
pdsavardAuthor Commented:
Thanks for reply.
No error and yes when I use the Get-OwaVirtualDirectory I got the list you mention.
I think all is working good, but the folder are not displayed in the Exchange console.
0
 
flaphead_comCommented:
which console?  the Exchange 2007 "Exchange Management Console" or the Exchange 2003 Admin?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
pdsavardAuthor Commented:
Exchange Management Console

I finished to configure ActiveSynch, Outlook Anywhere, OWA. All work good on echange 2007. But the folder do not show it up. When I will remove the exchange 2003 server from the organisation, I will see if the folder appears in the Exchange Management Console.
0
 
pdsavardAuthor Commented:
I remove the old Exchange 2003 server. It is normal that the owa directory do not appear?
it is normal that when i try to explore direcly in IIS7 i got a Path not found error. The path was: \\.\BackOfficeStorage\baultar.com\ExchWeb for EXCHWEB for example.

thanks
0
 
flaphead_comCommented:
what do you get if you run:

Get-ClientAccessServer  | Get-OwaVirtualDirectory
0
 
pdsavardAuthor Commented:
Name                       Server                     OwaVersion
----                       ------                     ----------
exchange (Default Web S... SRV-EXCH01                 Exchange2003or2000
public (Default Web Site)  SRV-EXCH01                 Exchange2003or2000
Exchweb (Default Web Site) SRV-EXCH01                 Exchange2003or2000
owa (Default Web Site)     SRV-EXCH01                 Exchange2007
0
 
KorbusCommented:
Hi pdsavard,

I see you picked the output of that "Get-ClientAccessServer  | Get-OwaVirtualDirectory" command as your accepted solution.  Why was that?  I am running into the same error as you, and get the same results from that command.  

But I dont see how that output resolves the IIS "Could not find part of path" error.  Or did you determine that this is normal behavior?

Thanks,
Korbus
0
 
David_CitrusCommented:
It's normal behavior.
0
 
pdsavardAuthor Commented:
Hi I do not choose this as the accepted solution. Expert-Exchange does it., I think this post timed out! I never found a good reason, but all 2007 server work like expected with this behavior. Now we migrate to 2010 and do not have this problem on 2010.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now