HI all, I have urgent case . I have Exchange server 2003 and windows of server was 2003 R2 enterprise windows falls down and I've backup for mailboxes 2 weeks ago what is the best solution to avoid lost mailboxes during 2 weeks ago ? if I install windows again . Is it will affect and change in system manager of exchange server?? and if I do that can I find all message before? please help me, thanks alot for all

This is not the place for urgent requests. If you still have the log files intact from the last backup until the present, when you restore the database, all the log files should play into the database when you restore it, if you do it properly. Make sure you keep a copy of those log files if you do any restoring of the server. When rebuilding the server, make sure to create the database and log volumes with the same drive letters and paths as before.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

thank you ED for reply but I need to leave the same name of server but when I rename new server message appeared that this account already exists this is the problem now

Hi Right click on the computer object in AD Users & Computers and then click Reset. That will allow you to use the same computer name. Steve

I did that but still this message appeared when rename computer

Just delete the existing computer account.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

if I delete computer account it will affect on exchange schema

No.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, You can try to recover Exchange server to new machine with Setup.com /M:RecoverServer and then restore database to the new machine. How to use Recovery Storage Groups in Exchange Server 2003 http://support.microsoft.com/kb/824126Xiu Zhang TechNet Community Support

That command is wrong for Exchange 2003, it's setup.exe /DisasterRecovery.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

That command is wrong for Exchange 2003, it's setup.exe /DisasterRecovery. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Yes, it should be setup.exe /DisasterRecovery, it is for Exchange 2003Xiu Zhang TechNet Community Support