I have just used demazter's SBS2003 to 2008R2 and exchange 2010 guide, most of it was pretty much inline with the guide until the end when attempting to demote the old SBS2003 server. It gave me an error saying it could not contact any other domain controllers, even though it was there, and i could get a ping response, name resolution etc.. Upon searching for hours i found a number of process' to use the /forceremoval thinking i could clean up metadata later. Well the SBS2003 server will now no longer logon, even using the local administrator password, so this is a writeoff.
- metadata removal process didn't even see the old server
- exchange management shell could not connect
- endless DNS errors
- unable to edit any GPO
- unable to use dcgpofix (didnt think i was an administrator)
and the list goes on...
However, the question that lurks for a small organization of 30 employees is: "do i re-do this whole domain from fresh, or is this a simple few loose ends to clean up" anyway, i went down the loose ends road, got gpofix to work, used the BURFLAGS fix to D4, and after a sleepless night ended up getting a clean "dcdiag" response except for "Unable to connect to the netlogon share" - which didn't seem to affect any logons, or operations...
After configuring SSL UCC signature and continuing on i though i had a reasonably functional DC. That is until i tried to remove some of the references to my old organization in exchange.
An overview of my machine
A summary of my situation now:
- Outlook web access will no longer work in exchange 2010 from an external address, it gets to the login page, then hangs when you click submit
- Exchange Best Practises reports first administrative routing group deleted
- unable to connect to routing master
- active directory domain has an unrecognized exchange signature
- DCDIAG reports unable to connect to netlogon share
- DCDIAG reports that SSL certificate for 0.0.0.0:443 has been deleted
- Task get-exchangeassistanceconfig throw unhandled exception
- exchange replication service could not find a valid configuration for exchange database xxx
- could not find a certificate in the personal store for the FQDN then it points to one of the OLD servers
- (in event viewer) Microsoft-Windows-Failoverclustering/operational - The specified channel could not be found
There are more errors but i am just trying to paint a picture. I HAVE had OWA working, but i have crashed it. - One of the problems i have in researching this is no one seems to acknowledge that the old server DOES NOT EXIST anymore. I cannot connect it back up and use system manager to change anything or replicate any AD info.
Where i am now is the following works:
- folder redirection
- full access to GPO
- exchange activesync (although VERY slow)
- OWA within organization LAN
- remoteapp on appserver VM using TS web access
- DHCP, DNS, etc..
but the deeper i dig, the more errors i seem to create. OWA does not work, exchange keeps telling me i have legacy servers, and keeps changing its own settings, and yeah. Etc.
My MAIN question is: GUYS, should i start again or is there a common theme to the above ?
If i start again, can i use my mailbox.edb (which, did successfully move over to 2010) to connect to the re-installed exchange ? I cannot get exmerge to work either. some dll/ocx error.
Thank you, VERY MUCH, for any assistance. I have this weekend where we are able to be offline if need be.