Infor store please help! 2

[favit]

Note: I have 2 other posts, if you respond to this one then you will solve other issues.

I just recently installed exchange2k server on a windows 2000 member server. The windows 2000 server is a member of a windows 2003 domain. When I try to start any exchange services under services I recieve the fallowing error message:

1. "Could not start the Microsoft Exchange Information Store service on Local computer. Error 1068: The dependecy service or goup failed to start"

The reason for me starting the service is because when i go to the exchange manager my first storage group is down with red arrows. When I try to mount the mail box the option is clear. An error message is also recieved when trying to expand on the first storage group and it is as fallows:

2. "The action could not be completed becuase the MS Exchange Info. Shore service is unavailable. Be sure the service is running and you have connectivity to the MS Exchange Server comp.

Operation: Retrieving mount information.
ID no: c1041721
Exchange System manager"

Can someone please help me.

Greatly Appreciate your help,

Please help I'm a newbie at his!

 

[favit]

I dont have dns installed on my exchange server 2000 becasue I thought that the domain controler wich is my 2003 will be taking care of the dns stuff. I just joined the 2000 server exchange to the domain. Thats all I did. are there other settings on the 2000 server that I missed? And your right there are no logs files in the mdbdata folder in C:\Program Files\Exchsrvr\MDBDATA. What should I do?

Please help I'm a newbie at his!

 

[Goner05]

A few of questions then:
1. How many users (rough number to keep confidential)
2. Is every person on the system needing an e-mail address?
3. Do you host your own domain or is your mail sent to an outside provider and you just POP in?

As a recommendation you should uninstall the Exchange on the win2K server an put it on the 2003 server as it is your domain controller. The Kerbreos error makes me think that your win2K server is not integrated properly. A good way to tell is to go to the Active Directory Users and Computer and under the users section all your users on your network should be listed as the domain controller will propogate to the slave controllers this information. Also on the 2003 Server you need to go into the Users and Computers and right click on the Win2K server (should be listed under domain controllers) and make sure the check box is on for the "Trust this computer for delegation".

A second recommendation is us your 2003 server for just authenication and Exchange server (and Norton if you have it) and use your win2K server for file and print sharing. It balances your load accros your network better.

As a heads up you may want to make sure you have the user names and passwords written down for as you will most likly have to redo the users from scratch in order to add a mailbox to thier account. I can't remeber if there is a wizard or not to just add a mailbox as it has been a few months.

Hope this helps

Goner05


~To most people a computer is an $1,800.00 deck of cards

 

[favit]

1. There are 25 users
2. Every one is needing an e-mail.
3. No pop only exchange server.

First, Which one should be my domain controller, which will authenticate the users? my win2000 or my win2003 server?

Second, which one will hold my exchange 2k? My win2000 or my win2003 server?

Last, I can use an apps server. So, which one should it be my win2k or my win2k3 server?

Note: When we talk about member servers, these are computer servers that are just joined to the domain correct?

Note2: Can we have a domain controler act as a member server aswell?

Thanks,





Please help I'm a newbie at his!

 

[Goner05]

To answer (Personal Prefernece, and as if brand new installation):
1. Install Exchange on the 2003 server

2. Make the Win2003 server the Domain Controller using active directory wizard with your domain name - Note only use the .com domain name if you are physically hosting this domain and you are the only office with this domain name otherwise use a .local behind your network name (eg test.local) This will save lots of headaches when you configure the exchange end of things later see below

3. Add all the users and computers to the 2003 server with a mailbox at the same time

4. After the 2003 server is promoted to master of the domain run dcpromo (start - run - type in dcpromo.exe) on the win2k server and just add it as a secondary domain controller. You can just leave this as a member of the domain, but I still recommend integrating it with the Active directory. You've paid for the software might as well use the features. There is other reasons but that one is the simplist

5. Depending on the horsepower of the servers you have I would use the 2003 server for mail, Norton (if applicable), Firewall Proxy (if this is your preference -personally recommend a Firewall router as it frees up resources on the sever). The win2K should be your app, file and print server once again depending on how big the machine is.

6. If you used the .local behind the local network name you will need to go into Exchange (under Server Adminstration) than to recipiant polcies and create a policy with your domain name (e.g test.com) and click on the check box stating that this organization is responcible for all mail to this domain - if applicable. This works really well if you are on a mail forwarding system from your ISP. (e.g your ISP hosts your domain name and forwards your e-mail to your exchange server. This way if your server goes down all new incoming mail will just be held in your ISP's mail queue till you get back up and running instead of getting bounced)

I made the assumption that the workstations are all WinXP Pro and that you don't have a mixed enviroment (i.e 98, 2000 and XP)

With this config you have two dedicated servers sharing the load across the network and security policies can easily be set up on the 2003 domain controller

Note: It may take up to 72 hours before your DNS is updated across the land for your e-mail to properly work (i.e. to come in)

This is the streamlined edition and others will probably add to this.

To answer your notes:
Note1: A member of the domain is a computer that logs on to the network (i.e a WinXP Pro machine with a user logged on)

Note2: This one is a little tough... A server will either be a domain controller (either primary or secondary) or just a member computer with server software installed. Its either one or the other. Member or Controller


Goner05


~To most people a computer is an $1,800.00 deck of cards

 

[favit]

Listen,

I would like to thank you, for all your smart and dedicated knowledge that you have in this I.S field. You have helped me a greatly.

Most Appreciative,


Please help I'm a newbie at his!

 

[Goner05]

Glad to be helpful, but more importantly did you get everything up and running?

Goner05

 

[favit]

Just finished my plan and started on it. If I have any more questions how can you help me?

Please help I'm a newbie at his!

 

[Goner05]

You bet. I'll do what I can for you.

Goner05