autumn
Active Member
- Reaction score
- 28
- Location
- Geelong, Victoria, Australia
G day all
hopefully someone can help me out quickly.
I've nearly completed a sbs 2003 to sbs 2011 migration and the sbs 2011 server has **** itself and it looks like the ntds database is corrupt only on the 2011 machine.
I can log in to 2011 with DSRM but that's it. I've tried the esentutl and get a jetdirect error.
So I'm looking at two things to do now:
1, try and recover the AD from 2003 to 2011 some how?
or
2, rebuild the 2011 machine again, taking back the FSMO's to the 2003 and restarting the migration.
NO I don't have a backup, yes I know I should have but I don't. This would have been easily repaired with the backup.
both the 2003 and 2011 are Hyper-v clients if that makes a difference.
Is there another way anyone can suggest?
Thanks in advance
Tim
hopefully someone can help me out quickly.
I've nearly completed a sbs 2003 to sbs 2011 migration and the sbs 2011 server has **** itself and it looks like the ntds database is corrupt only on the 2011 machine.
I can log in to 2011 with DSRM but that's it. I've tried the esentutl and get a jetdirect error.
So I'm looking at two things to do now:
1, try and recover the AD from 2003 to 2011 some how?
or
2, rebuild the 2011 machine again, taking back the FSMO's to the 2003 and restarting the migration.
NO I don't have a backup, yes I know I should have but I don't. This would have been easily repaired with the backup.
both the 2003 and 2011 are Hyper-v clients if that makes a difference.
Is there another way anyone can suggest?
Thanks in advance
Tim