Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 546
  • Last Modified:

sbs 2003 to 2011 migration

I'm planning on doing a customers migration (SBS 2003 to SBS 2011 (25 Users)) this comming weekend(Friday, Saturday, Sunday).  During the pre-install preparation it wants me to upgrade MSDE 2000 to sp4.  That part is failing.  The customer does not use sharepoint nor companyweb.  Although it's there.  Can I ignore this error? And continue with the migration?
0
ktaczala
Asked:
ktaczala
  • 3
  • 3
1 Solution
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Are you able to virtualize the source server and run the whole migration virtually first?

Make sure you have a System State and a good backup before touching that source!

Philip
0
 
ktaczalaAuthor Commented:
Can't virtualize 1st.  No resource for that.  Why would I want to virtualize 1st anyway?  Will definately be running a full backup before attempting anything.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
For the more crusty source servers we P2V and run the migration virtually on the virtualized source leaving the actual server in production. This way there are no real surprises.

Make sure a System State backup is taken as well. This gives you a reboot --> DSRM --> SS Restore --> Start again process.

Ultimately, there are a few services running in the MSDE instance(s), but if they are not being used or are under utilized you _should_ be okay. (Remember: Should, Could, Would! YMMV).

That's why it is so important to have that fall-back.

Philip
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ktaczalaAuthor Commented:
Thanks, I will post afterwards with results.
0
 
ktaczalaAuthor Commented:
I finished the migration, with the exception of removing exchange 2003 and demoting the old sbs 2003.  I will wait a week before I do that.  The migration went fairly smooth.  Biggest issue was making sure all workstations (XP and Win7) had current updates.  Otherwise the http://connect would fail!  Total time was 3 days from start to finish(12 to 16 Hours each).  I did take the option to P2V the old Servers first.  That Made me feel much safer.  The original Physical machines remain untouched.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Excellent! :)

Philip
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now