Re: exchange issues
- From: Chris <LudwigVonB007@xxxxxxxxxxx>
- Date: Wed, 01 Jun 2005 22:38:54 -0400
Lanwench [MVP - Exchange] wrote:
In news:z4_me.29423$6k7.18664@xxxxxxxxxxxxxxxxxxxxxx, Chris <LudwigVonB007@xxxxxxxxxxx> typed:
Hello,
I have not set up exchange in a while, and i know there are many new changes in exchange 2003 so i thought maybe someone could give me some ideas in terms of implementation.
I have two offices, one in miami and one in west palm beach, both offices are connected with a vpn, and can talk to each other without a problem. One office has a win2003 server (ent.) which is acting as a primary domain controller, the other office also has a win2003 server (ent.) which is acting as a backup domain controller. Both are under the same domain and are replicating fine, and i have some DFS folders in both which are updating fine.
NB: There's no such thing as a PDC/BDC in AD - all DCs are peers, with the exception of the FSMO roles held by the first DC (presuming they weren't transferred elsewhere)
Sorry, i forgot about the tree, used to the old way, since i have been out of the loop for a while. And you are right, both dc's replicate and do everything correctly.
I installed exchange 2003 on the pdc, and using rpc over http i set up the clients outlook 2003 mailboxes without problems.
Just curious why you'd do this rather than have them go through the VPN tunnel (MAPI connection) ?
The problem is that the vpn sometimes disconnects, since one of the connections is a dsl connection, which is not totally reliable. Thats why i chose to use rpc over http.
Since exchange 2003 uses the AD, it was a snap to do. The only issue is setting up the public folders, since exchange admin is not the same as in previous versions, i am lost as to how to implement the public folder on users mailboxes.
They should be there already.... ?
Yes, the public folders are there, however, i am trying to ad public contacts and public calendars, and honestly because i have not used exchange in a while, and this new version is quite different, i dont know my way around it yet. I would appreciate any assistance in doing so.
The issues i would like to know, is whether i should install exchange 2003 on the 2nd DC, would there be any advantage to doing so.
You could replicate your public folders, you could move the relevant mailboxes to that server. Sadly, you cannot replicate mailboxes.
I chose not to setup a 2nd server. Speed and network traffic is not an issue at this time. The only thing i would like to do, is have both servers replicate shared folders, so that when information is put in one shared folder in one server, it is automatically updated into the same named shared folder in the other server. Both DC's of course.
I do want to use Outlook Web Access, but not sure how that will work in one or two servers.
Depends. Either have each set of users learn how to to to the appropriate server that holds their mailboxes for OWA (i.e., https://newyork.company.com/exchange and https://florida.company.com/exchange) or get yet another Exchange server & do a front-end/back-end config.
Not everyone will be using the OWA, so the users can learn how to do the appropriate https setup. I have not configured owa yet, but would like for users to type mail.domainname.com/exchange to view their mailbox. If you have any ideas as to what i need to set up, i would appreciate any comments and ideas.
The domain website is hosted by bellsouth, even though it could be hosted locally on the machine.
Don't know exactly what you mean - if you mean, your company's public website is hosted by an external third party, leave it that way. If you mean, BellSouth handles your domain's public DNS, leave it that way.
Actually, the domain name expired and when it was renewed, the ip now points to the server, instead of the bellsouth server where it was hosted before. not a big deal, because i can add the files into the server. Ive modified the dns entries on the server, and the mx records to reflect these changes.
We have a static ip and dns is configured on both dc's.
My question is basically, should i install exchange 2003 on the 2nd server,
Really depends. What is performance like right now? If you have a lot of remote users connecting to your server, it might be necessary, but if all you're asking is how to make the PFs available, well, they should be already. As mentioned, you don't really need RPC/HTTP(s) since you have a site-link/WAN VPN connection.
Cached mode should be a good thing for you (and you can include PFs in the local cache if you drag them to the PF\Favorites in Outlook & tell Outlook to use cached mode for that, too)
and how can i configure outlook web access and test it to make sure that ive done the changes right.
My PDC is also a certificate server, so i would want https access to OWA. If someone can give me an idea as to what is best in terms of implementation, i would appreciate it.
Thanks
Chris
.
- References:
- Re: exchange issues
- From: Lanwench [MVP - Exchange]
- Re: exchange issues
- Prev by Date: RE: Exchange 2003 ADC Error
- Next by Date: OWA Problem
- Previous by thread: Re: exchange issues
- Next by thread: Re: exchange issues
- Index(es):
Relevant Pages
|
