For evaluation runtimes, the countdown to expiration begins when the runtime goes through the First Boot Agent phase.

For the evaluation testing, it's important that the machine being used has its CMOS clock set to the correct date. If the runtime 'sees' the clock move forward several months suddenly, you may find your runtime expiring much sooner than expected. This sudden change in date may occur if you transfer the runtime to a new device that has a correct date or if you try to fix the date manually in that original machine's CMOS.

If your evaluation runtime expires, your only course of action is to re-run the original image through FBA again.

- Andy