Craig Bricco
Guest
|
 Posted:
Fri Dec 17, 2004 12:04 am Post subject:
OWA Public Folder problem-revisited |
|
|
Hi,
I am migrating to new hardware & from E2K to E3K. I built a temp E3K server
to test mailbox move and practice on. Now new hardware is ready and
proceeded to move users from 2000 to 2003 on the new server.
OWA is published through ISA2004. No problems getting into anyone's mailbox.
Have begun process of 'How to remove first Exchange server from the site"
(KB 307917) All is done except actually uninstalling 2000 from the first
server, which at this point I'm highly worried about doing.
All public folders are rehomed on the new server, and replicas changed &
told no longer to be on the first server. My problem #1 is Every Outlook
client I have checked is still going to first server for PFs, even if it's
not running, so Outlook freezes when trying to access a PF (tried restarting
IS to clean referral cache). Also from OWA2003, when a user clicks the
Public Folder button, the new window opens and it times out.
https://owa.domain.com/exchange should open as
https://owa.domain.com/public, which works if I hand type it in a browser.
The button tries to open https://oldservername.domain.com/public
If it hand substitute owa for the servername, it opens fine.
All other aspects of OWA on the new server work great. So first question is,
once I uninstall Exchange 2000 from the first server to remove it from the
site, will the new server IS make the change properly to stop sending
Outlook clients to old server?
2. Will the new server's OWA also stop sending web users to the wrong server
address? Has anyone done this, seen this and this is the case? I'd hate to
uninstall and then have the phones start ringing off the hook because no one
can access PFs anymore.
Any ideas, help appreciated,
Craig
|
|
Craig Bricco
Guest
|
| Posted:
Fri Dec 17, 2004 4:29 am Post subject:
Re: OWA Public Folder problem-revisited |
|
|
Found it (with help)
Mailbox store properties on new server must have Default Public Folder Store
modified. If browse is grayed, change it in system policies.
Craig
"Craig Bricco" <cbricco@mwrgl.com> wrote in message
news:OPuRkm54EHA.3708@TK2MSFTNGP14.phx.gbl...
| Quote: | Hi,
I am migrating to new hardware & from E2K to E3K. I built a temp E3K
server to test mailbox move and practice on. Now new hardware is ready and
proceeded to move users from 2000 to 2003 on the new server.
OWA is published through ISA2004. No problems getting into anyone's
mailbox.
Have begun process of 'How to remove first Exchange server from the site"
(KB 307917) All is done except actually uninstalling 2000 from the first
server, which at this point I'm highly worried about doing.
All public folders are rehomed on the new server, and replicas changed &
told no longer to be on the first server. My problem #1 is Every Outlook
client I have checked is still going to first server for PFs, even if it's
not running, so Outlook freezes when trying to access a PF (tried
restarting IS to clean referral cache). Also from OWA2003, when a user
clicks the Public Folder button, the new window opens and it times out.
https://owa.domain.com/exchange should open as
https://owa.domain.com/public, which works if I hand type it in a browser.
The button tries to open https://oldservername.domain.com/public
If it hand substitute owa for the servername, it opens fine.
All other aspects of OWA on the new server work great. So first question
is, once I uninstall Exchange 2000 from the first server to remove it from
the site, will the new server IS make the change properly to stop sending
Outlook clients to old server?
2. Will the new server's OWA also stop sending web users to the wrong
server address? Has anyone done this, seen this and this is the case? I'd
hate to uninstall and then have the phones start ringing off the hook
because no one can access PFs anymore.
Any ideas, help appreciated,
Craig
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in