[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Grace period expired on sbs 2003 to sbs 2008 migration

I started this migration 21 days ago but am still using the 2003 server as I didn't get much further than the first few steps.  Can I extend the grace period or just cancel the migration and start over again when I have time to do it?  
I am getting Event 1001 - "The server was shut down because it did not comply with the EULA. For more information, contact Microsoft."  Maybe if I just shut down the 2008 server until I'm ready?  Thanks for any help.
0
eldtech
Asked:
eldtech
  • 2
  • 2
1 Solution
 
Cliff GaliherCommented:
Unfortunately you've gotten far enough into the migratoin that the AD roles have been transferred, hence the licensing compliance issue.

Circumventing the licensing service, even for a migratoin, is against policy hence against EE's usage polcies to answer.

As far as going back, you can restore a backup (the clean way) or you can seize the FSMO roles and manually clean up AD (the dirty way) and run into potentially *SERIOUS* issues down the road.

My suggestion? Make plans to finish the migratoin.
0
 
lscarborCommented:
Shutting down the SBS2008 server will have no effect on the shutdown problem. As cgaliher states, your only choice at this point is to restore the sbs 2003 server and start the migration over. I agree that seizing the roles will be nasty and usually unacceptable.

If you call Microsoft and use the for-pay service they can help you pick up the migration and finish it.

If you bite the bullet and restore the 2003 server, then plan to do your migration on a weekend (start Friday night and take a break during the public folder migration) or restore the 2003 and set up the 2008 server as a new domain (you will not be able to use both servers, you will have to move the users and machines all at once and retire the old 2003 unit).

Restoring the 2003 unit and having a proper plan is the only sane way out unless you call Microsoft and declare an emergency.
So that leaves you with the choice cgaliher gave you which is a restore and re-migrate or the Microsoft tech help.
Pay the fee and get help or restore the 2003 unit.
0
 
eldtechAuthor Commented:
Luckily this was not a customer server, it was our own.  I guess cgaliher's suggestion made the most sense and I continued the migration.  Almost done.  Something interesting occured though.  I am not sure at what point but the server is no longer shutting down.  Maybe because I started using the Migration Wizard and there are items pending or in process?
0
 
lscarborCommented:
That's probably it. Good job. Good luck.
The migration process it controlled by an XML file that is modified at each step. It changes the running state of both machines at several junctures, so I suspect you are correct about the shutdown being affected.
0
 
eldtechAuthor Commented:
Unfortunately there doesn't seem to be a way around the grace period so I accepted the recommendation, moved ahead with the migration and completed it successfully.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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