No, Exchange 2K7 was installed on a member server. But the original problem was detected when we tried to install 2 W2K8 DC's into AD. Previous admin tried to lockdown everything within AD.
From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, March 23, 2010 1:08 PM To: MS-Exchange Admin Issues Subject: RE: Unistalling E2K7 w/Windows Firewall Service Down Was exchange installed on a DC? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Tuesday, March 23, 2010 12:58 PM To: MS-Exchange Admin Issues Subject: RE: Unistalling E2K7 w/Windows Firewall Service Down Yes, the policy was fixed per PSS support. But the fix for the Win2K8 DC's was to do a /forceremoval then metadata cleanup. After that reinstall Windows 2K8 and re-join the domain. Not sure I can follow if I want to prevent killing the Exchange org. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, March 23, 2010 12:23 PM To: MS-Exchange Admin Issues Subject: RE: Unistalling E2K7 w/Windows Firewall Service Down First things first - have you fixed the policy? Once you do that, you should be able to start the FW and etc.etc.etc. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Tuesday, March 23, 2010 10:58 AM To: MS-Exchange Admin Issues Subject: Unistalling E2K7 w/Windows Firewall Service Down All- I have a Windows 2K7 server installed into an E2K3 Org. The client has decided that they want to go to E2K10 since nothing has been done with E2K7 outside of the initial install. The issue I'm facing is that we cannot uninstall E2K7 because the Windows Firewall service won't start. Prior, we had an issue with Group Policies and an exiting Administrator decided to edit the Domain Controller Default Policy and Default Domain Policy and changed all registry permissions as well as Files System files. So anything added to the domain was hosed. Windows Firewall wouldn't start, couldn't RPC, couldn't connect to the server at all outside local terminal. Anyway, so the plan was since you can't upgrade in place the E2K7 server with E2K10, we needed to uninstall E2K7 first then wipe the server off, reinistall and then add E2K10. The problem is it won't allow us to uninstall E2K7 because of the Windows Firewall. Has anyone faced this issue when trying to remove an Exchange server? How did you work around it to get the box uninstalled? John Bowles | 301.473.2260
