[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Domain and child domain setup , Exchange server set up

Hi all.  I have few questions I would like to ask. I have main domain abcd.com and I created child domain headquartes.abcd.com. I also have exchange 2003 server setup in main abcd.com domain. I want my local LAN users log into headquarters domain and not to be able to get to upper level (main domain browsing). Here is the problem I am running into. My local users accounts setup  in my main domain so they would have exchange email account but if they trying to login into child domain they cant because there is no name associated in child domain user account. Do I have to create identical user profiles/signon in main domain and child domain? Or is the any way I can set it up so the users will replicate from main domain trough the child domain and then I could set it up to what level they could go up? Or do I have to create users in my child domain for login and setup exchange server so it will pull users accounts from this child domain and associate with main domain? Next thing, I have few partitions setup on my exchange server, how do I assign separate partition for logs files, and for users mail boxes other partition, separate from exchange main partition and system partition? Next questions is, I couldn’t figure it out how to make exchange server assessable from web (site wont came up) I read all notes in here but still wont work. IIS is up and running port 80 OK.  Also I need to install SQL server and I want this SQL server be available for both main and child domain, where should I install this server, can I install on childe domain server, I don’t wont to overload my main domain server, its already running a lot of tasks. Thank you.
0
hulanet
Asked:
hulanet
  • 2
1 Solution
 
scottman29Commented:
Perhaps if you place a global catalog server for the main domain, in your headquarters domain, you would get the passthrough validation you need.  You would also have to change their login credentals, so that the domain selected is the domain they are loging into.  If you have resources that need to be hidden, why not just choose not to publish that item in the AD?

The separation of exchange files is done on the installation of Exchange.

Will the website come up locally?  If you can't access it via the web, make sure you've updated all the appropriate DNS info on the forwarded server out on the Web.

You can put the SQL server in the child domain, you can have your users access it by making a global group in one domain, and adding it to the appropriate places on the SQL server.

I know my answers are general, but if you need specifics, I figured you'd just ask me rather than me typing out an extremely detailed answer.  It seems like you already know some things, and did not require a long drawn out reply.

HTH,
Scott
0
 
hulanetAuthor Commented:
1. Placing global catalog to child domain unfortunately didn't help
2. The only option Exchange provide with installation is to place the whole exchange installation to different dire/partition but it doesn’t provide option to separate logs and data files in separate partitions from main exchange directory ( I am pretty sure there is a way to do it)
3. No website wont come up locally either, DNS set up correctly (will try to reinstall exchange)
I try to reinstall exchange server join into child domain, it wont run forest prep with error "I don’t have administrative rights" I'm sign on to local domain as administrator. Any suggestions how can I install exchange in child domain?
4. SQL so far working OK.
0
 
scottman29Commented:
have you made sure your web services are started?  

here are your directions to move the logs and db's
http://support.microsoft.com/?id=821915

this should help you with outlook web access:

http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html

hope this helps you out!  good luck!!!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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