Would shutting down legacy domain controller for a year cause problems

A few years ago, two companies merged. We have just completed a
migration and consolidation of multiple legacy domains into a new
domain. As we were working to shut down the DCs of the legacy domains,
an email administrator reminded us of an SEC requirement to be able to
access all email for up to 6 years.

Today we use Lotus Notes for email (I know, I feel bad for me, too!);
before the merger one of the companies used Exchange. In order to more
easily access those Exchange-based emails, we will keep one legacy DC
and the Exchange 5.5 server powered off, but available until the SEC
requirements expire.

HOW? We thought to move all FSMO roles to one DC. Then we will demote
all other DCs and remove them from the domain. The remaining DC and the
Exchange server would then be powered down and mothballed for
(potentially) a year or more.

QUESTION: Will the DC freak if it is powered up after a year of being
shut off? Will it have problems with either user or machine objects
that haven't been updated in a year? Are there other issues that make
this a bad process?

Thanks in advance for your thoughts on this issue.

.

Loading