Exchange 2003 and DC on same box

[lesleint]

I had this running for awhile and recently I have demoted the Exchange server back to a member server but I am now getting these 2 event ids.

Event ID 8231
Permanent failure reported by policy group provider for 'CN=System Policies,CN=BC01-BBB-EXCHANGE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domian,DC=com':'MAD.EXE', error=80040103. Taking provider offline.


Event ID 8213
System Attendant Service failed to create session for virtual machine XCHANGE. The error number is 0xc103073a.


Any help would be much appreciated.

 

[mlichstein]

Is there another domain controller on the network? More importantly, is there another global catalog on the network?

 

[hunterdw]

Likewise, with the other DC, did you transfer all of the FSMO roles to the other DC including the Schema role which is installed by default on the FIRST DC in the network?

 

[dearingkr]

The Global Catalog role should really be on the same server as Exchange.

 

[xmsre]

This is likely why changing the role of server with dcpromo after you have installed E2K3 on it is not supported.

*Reason not to install Exchange on a domain controller #42

http://support.microsoft.com/default.aspx?scid=kb;en-us;822179

(end of second paragraph below bulleted lists in "more information" section)

 

[lesleint]

Sorry I have been taken so long to repost. So would my best bet be to reinstall Exchange 2003. Can I just install another Exchange 2003 server move eveythign off number 1 then reinstall and move it back?

 

[tfarley]

You should just need to do a re-install. I did the same and it worked fine

TF