Convert BDC to Standalone Server

[Burgal]

I have an Exchange 5.5 server running on NT 4 as a BDC. I realise now that this is a bad idea. I can't take the server down for very long, and I would like to convert this machine from a BDC to a standalone machine. What is the safest way to do this? I believe there isn't a microsoft method. Third party utilities? What is a suggested application to use? How trustworthy is it? And is there anything I have to do once the process is completed to avoid any potential problems?

Thanks a lot.

 

[Shurik]

First of all - backup all your Exchange data ...
on NT4 there is no way to demote a PDC/BDC to a stand alone server , it's not like 2000 where dcpromo works just fine .
another nice solution :
make a 'cold' backup of your exchange,
take another comp,install it as stand alone : install new exchange there , then copy the exchange db there and import the data ... there are some sings that you should know when doing that , In case you'll need it , let me know.

good luck.

Alex,
Problem? No Problem!
Drink more beer...

 

[Burgal]

Hmm.. I'd prefer to not do that as I don't have any spare machines at the moment. I do have a tool called UPromote

http://www.algintech.com/UTools/UPromote.asp

that says it can convert a BDC to a standalone server.

What do you think of tools such as this?

 

[Shurik]

well , in any other situation I would try it , but when it is exchange 5.5 we are talking about ... I prefer not to run 3-party tools on my company exchange server ...
I don't know how much you know about exchange , but there are a lot of complicated issues there , so I prefer to stick with Microsoft on that case , who knows where they messed up there ?
any way , Good luck man.

Alex,
Problem? No Problem!
Drink more beer...

 

[Burgal]

I'm going to give it a try. If it dies, well I can do a restore. I do full backups daily.

I have this info on upromote with exchange running. As long as I don't add it to another domain, it will be fine I think. I'm readding the machine as a member server.

Exchange Server
Exchange Server uses SIDs embedded in a private database to validate access to the message store. These SIDs are not updated by UPromote. Therefore you will lose access to mailbox information if you move Exchange Server to another domain. The only exception is if Exchange can continue to use the old SIDs (e.g., by rejoining the same domain as a member, or using a trust relationship).

 

[Shurik]

check also the site name and the domain name of the exchange , and also a user that runs the exchange services..
thay have to stay unchanged also ... Alex,
Problem? No Problem!
Drink more beer...

 

[Burgal]

Thanks. I'm going to give it a try tomorrow. I'll let you know how it goes.

 

[Burgal]

Hey, it worked great! That upromote tool worked like a charm. After the server was demoted, I just had to clean up the local user database, and add domain admins and domain users to a lot of the security things. All shares worked, exchange worked and services worked after that.

 

[tylan]

Burgal:
I happened to come across the same program (upromote) a while ago. I now have a client that could really use it. You said "After the server was demoted, I just had to clean up the local user database, and add domain admins and domain users to a lot of the security things". What exactly do you mean by 'a lot'? Services? Shares?

Thanks in advance!
Tylan

 

[Burgal]

Only had to do it for services. All the shares were set up fine. It was pretty painless.