Exchange Server Forums

uninstall E2k3 from DC

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Migration >> uninstall E2k3 from DC

Page: [1]

Message

<< Older Topic Newer Topic >>

uninstall E2k3 from DC - 28.Jun.2008 3:53:06 PM

gregg_hughes1

Posts: 10
Joined: 25.Jul.2006
Status: offline

Good afternoon!

We migrated our Exchange 2003 Standard from the domain controller it was installed on to its own virtual world where it seems to be working great. I just uninstalled the Exchange from the domain controller today, and that seems to have also worked.

The old installation was in C:\Program Files\Exchgsrvr, just like normal. The mailstore, however, was on D:\Exchsrvr. The Exchange services on that machine haven't been running for a couple of months and the .edb files are timestamped the date we decommissioned.

Question: The logs, the old mailstore, and miscellaneous other files haven't been touched. Did the uninstall miss them, or do I need them there for some obscure reason? Can I move/delete them?

Thanks!

Gregg

Post #: 1

Featured Links*

RE: uninstall E2k3 from DC - 28.Jun.2008 5:11:25 PM

uemurad

Posts: 5326
Joined: 7.Jan.2004
From: California, USA
Status: online

Uninstalling Exchange doesn't touch the data files. In fact, deleting a Mailbox Store doesn't touch them either. You can do with them as you see fit.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to gregg_hughes1)

Post #: 2

RE: uninstall E2k3 from DC - 1.Jul.2008 4:40:21 PM

gregg_hughes1

Posts: 10
Joined: 25.Jul.2006
Status: offline

Thanks!

I also took a quick look at the C:\Program Files\Exchsrvr folder and found another 43Mb of files. Is this another place the uninstaller didn't remove files?

Also, how about security patches listed in Add/Remove programs? The space isn't big and there are no errors thrown over them, but I'd like the DC to be nice and tidy.

Thanks!

Gregg

(in reply to uemurad)

Post #: 3

RE: uninstall E2k3 from DC - 1.Jul.2008 4:53:17 PM

uemurad

Posts: 5326
Joined: 7.Jan.2004
From: California, USA
Status: online

You uninstalled Exchange and the Exchange patches are still listed in Add/Remove? I've never uninstalled Exchange from a server and kept it around, so I can't tell you if that is normal behavior or not.

What types of files are left in the Exchsrvr folder?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to gregg_hughes1)

Post #: 4

RE: uninstall E2k3 from DC - 2.Jul.2008 9:36:21 AM

gregg_hughes1

Posts: 10
Joined: 25.Jul.2006
Status: offline

Good morning, Dean!

Thanks for the reply!

In the Add/Remove Programs I have listed updates for the following KB articles:
931832
924334
916803
926666
911829

In the C:\Program Files\Exchsrvr folder (43.4Mb) I have the following folders:
\bin contains assorted .dll and .ini files, mostly content filter or managment pack related
\exchweb has a fistful of folders, mostly labeled 6.5.72.xx or 6.5.76.xx
\mailroot\vs1\queue has some files NTFS_$string$.eml files dated the uninstall date
\MDBData has isinteg.pri and tmp.edb files
\mtadata has assorted log files from before decommission date
\OMA has assorted .dll files that seem to be language based
\schema only has ex2003servicepack.txt

There's also an \Program Files\Exchange SDK folder (10mb) with an SDK folder under that.

Thanks!

Gregg

(in reply to uemurad)

Post #: 5

RE: uninstall E2k3 from DC - 2.Jul.2008 10:16:38 AM

uemurad

Posts: 5326
Joined: 7.Jan.2004
From: California, USA
Status: online

If you have to keep this server around (i.e. it's your one and only Domain Controller) and you have uninstalled Exchange, then my recommendation would be to attempt to uninstall the updates you see in Add/Remove Programs. That may remove some of the files you see in C:\Program Files\Exchsrvr. Next, I'd remove the Exchsrvr folder and the SDK folder.

At that point, before you do anything else, run a scan to see if any updates are needed.

My real recommendation would be instead to build yourself a new Domain Controller. Having Exchange on a DC is not ideal, and taking Exchange off of that doesn't necessarily mean it's clean. As the saying goes - "you can put lipstick on a pig..."

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to gregg_hughes1)

Post #: 6