Rebuilding SBS 2011 from Scratch , Malware outbreak


I'm rebuilding an SBS 2011 server from scratch due to an Expiro/Xpiro outbreak. i'm being safe, rather than sorry because I think it's *possible* that the SBS 2011 has been infected, as it's reared its ugly head again.

So, I'm rebuilding SBS 2011 from scratch. I would normally employ Jeff Middleton's swing migration to xfer all of the ADUC stuff, but I'm scared the malware would transfer with it.

So, my question is, can I mount the Exchange 2010 DB from the old server, onto the freshly installed SBS 2011 server, and
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In order this to work you need the same domain name and organization name.
Also the exchange server should the same version i.e if its SP2 RU6 then you need to patch to new one as well.
When you mount the new database, the mailboxes will be in a disconnected state. You will have to either connect them to existing non-mail enabled users or use the restore mailbox procedure (New-MailboxRestoreRequest ).

Ok now how to do it :
1) When your users don't have a mailbox yet on the new server
-on the new server >Set-MailboxDatabase <Database Name> -AllowFileRestore:$true
-dismount the new database and delete all logs, leave only the edb file > rename it to edb.something
-copy the old edb over there and rename it to match the new database
-mount the database
- run Get-MailboxDatabase |Clean-MailboxDatabase
Now connect the users to the mailboxes using Connect-Mailbox

2)When users already have a mailbox on the new server. You need to merge the content from the old database
-create a new database with the same name as the old one
- run Set-MailboxDatabase <Database Name> -AllowFileRestore:$true
-dismount the new database and delete all logs, leave only the edb file > rename it to edb.something
-copy the old edb over there
-mount the database
- run Get-MailboxDatabase |Clean-MailboxDatabase
Follow the article as above to merge the contents like this :
New-MailboxRestoreRequst -SourceDatabase "OldDatabase" -SourceStoreMailbox "Tony Smith" -TargetMailbox -AllowLegacyDNMismatch
Tom-J-LaelAuthor Commented:
Thanks , I'm a few days out from trying it. What's your opinion about xferinf active directory over A La Jeff middleton's swing migration instead?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I'm not familiar with Jeff Middleton's  tool / process. It might be a good idea, but I would go that way only after a research on how the migration is done in details. At the end of the day if I have to seize FSMO roles, clean metadatabase and hunt for records of the old server, it doesn't make sense to me. Swing migrations in general are more messy than useful.
My opinion only.
S00007359Cloud Engineering OfficerCommented:
another opton would be to use the veeam backup and recovery tool [installed on a pc for recovery sake, and use the exchnage recovery tool and use the exchnage 2010 edb file, and export the mailboxes.

Tom-J-LaelAuthor Commented:
I ended up forgoing rebuilding domain all together
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.