Chris
Sun Jun 05 18:23:23 CDT 2005
Lanwench [MVP - Exchange] wrote:
> In news:I5une.47839$lQ3.44962@bignews5.bellsouth.net,
> Chris <LudwigVonB007@hotmail.com> typed:
>
>>Lanwench [MVP - Exchange] wrote:
>>
>>>In news:z4_me.29423$6k7.18664@bignews4.bellsouth.net,
>>>Chris <LudwigVonB007@hotmail.com> 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.
>
>
> Great.
>
>>>
>>>>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.
>
>
> Well, 1) cached mode will make this less of a problem and 2) if the DSL
> flakes out on either end, RPC over HTTP isn't going to work for connecting
> either, right?
>
>>>
>>>>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.
>
>
> Shouldn't be any different - presuming you're actually connected to the
> server. I have never tried creating a PF within Outlook while connected over
> RPC/HTTP(s) so I can't say for sure what you'll see when you try. Connect
> using MAPI and you'll be able to do whatever you wish (presuming you have
> permissions to create/modify PFs).
>
>
>>>>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.
>
>
> Shared folders meaning, file system? Look into DFS.
>
>>>
>>>>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.
>
>
> It's configured already - you just may not've opened up access to it. I
> recommend forcing SSL and using 443 rather than 80. If you then have an A
> record like mail.mydomain.com that points at the correct public IP, and have
> done your port forwarding properly, https://mail.domainname.com/exchange
> will get you there from the Internet. For info on SSL, see
>
http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html (yes, it's
> for E2003 but should be pretty much the same)
>
>
>>>>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.
>
>
> Which IP points to what? Where is your domain's DNS being hosted? Should not
> be internal - leave it with your ISP or another third party.
>
>
>>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.
>
>
> Try logging into it internally (https://servername/exchange) and then
> externally, to see whether it's working.
>
>
>>>>My PDC is also a certificate server, so i would want https access to
>>>>OWA.
>
>
> Good idea - see above.
>
>
>>>>If someone can give me an idea as to what is best in terms of
>>>>implementation, i would appreciate it.
>
>
> Hope this helps.
>
>
>
>>>>Thanks
>>>>
>>>>Chris
>
>
>
I took out rpc over http, and am using mapi, but i still dont remember
how i can create a public folder that everyone can see and add to it. Id
like to have a global address list with contacts which are set up on the
public folder. Again, i havent worked on exchange for a while, so am
quite rusty. your help is greatly appreciated.
In terms of the DFS, i have it set up so both servers have the same
folders on dfs, but i dont know if i need to set them up on both
servers, or just one. In other words, have the source and target folders
in one server set up to replicate, or do the source and target folders
on both servers to replicate.
In terms of owa, i have the exchange icon on IIS, but i am not sure if i
have it set up correctly, since when i try to http to the domain, i get
error 404, both internally and externally.
In terms of the ip's, the register.com site has our external ip of our
server as the mail server, and the dns records of bellsouth as our dns.
(it used to be the mail server AT bellsouth before).
Thanks for the help.
Chris