• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 398
  • Last Modified:

will exchange 2010 work in a 2003 AD environment?

I currently have a 2010 exchange server in a 2003 AD enviroment.  I had to promote a 2008 machine to a DC to get exchange running, I then demoted it.   I am having issues getting permissions assinged to a few accounts correctly.  Is 2003 AD the issue?

Thanks
0
CraigM10
Asked:
CraigM10
  • 3
  • 2
  • 2
  • +1
1 Solution
 
B HCommented:
according to the requirements, your current setup shouldn't be any problem:
http://technet.microsoft.com/en-us/library/aa996719.aspx

0
 
Mike KlineCommented:
Yes in addition you have to at least be at 2003 functional level (forest/domain)   Another good matrix here:

http://technet.microsoft.com/en-us/library/ff728623(EXCHG.141).aspx

Thanks

Mike
0
 
Shreedhar EtteCommented:
Hi,

Refe this article for the Prerequisites:
http://technet.microsoft.com/en-us/library/bb125224.aspx 

Hope this helps,
Shree
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
CraigM10Author Commented:
Ive seen these links when trying to do research on the problem I am having but is anyone actually doing this?

here is my configuration.   2 domain, a parent and a child.  The 2010 exchange server is running on 2008 and in the child domain along with the user accounts.  All AD servers are 2003, 2 in the parent and 2 in the child.   Everyone's mail is working fine but when I try to run any shell commands on the exchange server it does not allow me.  I get " the term Get-MailboxDatabase is not recognized as a name of a cmdlet."   This also happens when running any other command from the shell.
0
 
CraigM10Author Commented:
Another issue pointing to a disconnect is that when I am on the AD servers and I try to access information about the mailbox like mailbox rights I get the following error.

"This action could not be completed because the Microsoft exchange Information Store service is not available".
0
 
Mike KlineCommented:
Haven't done it in production...we won't be at E2K10 until 2011
0
 
B HCommented:
Are you sure you're in the exchange command interface and not windows powershell?

Maybe reloading the exchange utilities will do it?
0
 
CraigM10Author Commented:
That was the issue, I was in the windows powershell not the exchange powershell.  Thanks for your help.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

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