Discussion Locked

Move Exchange, Seperate from Domain

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A multiple part question. I have been asked to bring our Exchange 5.5 server local from a central corporate site. The admin there shares no experience and suggests I set up my own domain and leave them alone. I am a novice to mid level admin and need to accomplish this with little input from that admin. So, I need to do the following:
1) Move Exchange 5.5 mailboxes here. (Exchange server already set up)
2) Separate from DOMAINA and make DOMAINB
I have 35 workstations(mixed Win98/W2K), 3 NT 4.0 servers and 8 printers. All Internet access/firewall is through a WAN link to the central location. Access to WAN is through Cisco 2601, to which I have no access. Additionally, there is another location stub to me through a PtP T1 that gets theirWAN access through the same router.
The questions:
1) Should I move mailboxes, make new domain, join new domain, promote BDC to PDC, change workstations and servers, in that order.
2) Will I need my own Internet access as a result of setting up anew domain (I think no)
3) Would there be a need to have router access (I am finishing up CCNA)
4) Will I need to set up my own DNS/WINS server or can I continue to use the corporate one
5) Is all the above determined by the trust relationships? I presume I will have to be trusting to him and the way he sets up his will determine my access to his domain
6) How will this affect intranet connection to resources
7) How will this affect my Citrix connection to him

Thanks to all who made it this far. I am of the philosophy that 75% of all network problems are admin created and am cautious with changes. Thanks again.

2 replies

by lordinfidel

Assuming that I read this read...

The CO has basically said, take your exchnage server and make it local for your users. If you have to make your own domain, leave us alone, we don't care what you do.

Now obviously if you make your own domainand you need to access resources at the CO, then there will be a trust going on there. But that is beyond the scope of the crux of the question.

1. In order to run exchnage you need a connection to the outside.

2. Exchnage must be in a domainand able to contact the PDC (little known fact)

3. Exchange must be able to resolve names via dns. The DNS server can be anywhere, it just needs to be able to make queries against it.

Since this is a good time to break away from the CO, sinceit seems like they don't care anyways.
Create your domain first, and get it stable.

Once it is stable, create your exchnage server, from scratch. This may mean building another machine. If you don't have the resources to build a beefy mailserver, Then build a temp one that you can create your users mailboxes without putting mail on it. Plus your distro lists. You can move these later on.

The next project is actually a 2 full day weekend project. You will be dumping users mail into pst's. Then you will be re-building the real mailserver. (Get Managing Exchange Server from O'reilly, it will open your eyes how to properly install exchnage and how to stay away from containers.)

Once the real server is built, transfer their mailboxes from the temp server to the real one. Configure their outlook client to point to the new mail server, and then import their e-mail.

It sounds like a lot of work, because it is. The CO will have to allow port 25 in and out from your exchange server.

by lordinfidel

How will your users be receiving e-mail?/are they getting external e-mail.

Are they part of the top level domain name or are they a sub-domain?

Does this exchange server have to be a member of an exchange site?

How many other exchange servers does it need to contact?

Final-- Get that book first... Managing Exchnage Server from O'reilly!

This discussion is closed to new replies.