DomStation

Situation : 
1 Windows 2000 srv with latest updates (incl. SP4 & update roll-up1)
This is the domain controller, simple setup : 1 domain in 1 forest.
AD
Also used as fileserver.

Situation to go to :
1 Windows 2008 R2 srv 
DC, 1 domain in 1 forest
AD
Fileserver

Since this is stated as an 'unsupported' upgrade by Microsoft, I will use a temporary Win2003srv as an extra step to complete this upgrade.

Already done :
Win2000srv resource kit & support tools installed
Win2003srv machine installed with latest updates + resource kit & support tools installed
Win2008R2 srv machine installed with latest updates

Steps :
FASE 1
1) On Win2000 DC, raise forest functional level to 'native'
2) On Win2000 DC, insert Win2003 srv CD
Do the '2003 ad preparation'
Command line (as administrator)
- adprep/forestprep 
-adprep/domainprep
-adprep.exe /domainprep /gpprep

3) On Win2000 DC, try the 'dcdiag.exe' and the 'netdiag.exe' to verify there are no errors
4) Boot up the temporary 2003 srv, insert IP settings + DNS (primary) is the WIN2000 DC
5) On Win2003 srv, do the dcpromo (check after if AD, DNS & DHCP settings are replicated OK)
6) On Win2000DC, change the 'schema master' to the temporary 2003 DC
7) Mark the Win2003 DC as 'global catalog' and unmark the 'global catalog' on the Win2000 DC
8 ) On the Win2000 DC, at Operations Master, change the FSMO roles to the temporary Win2003DC
9) Check replication
10) Shutdown old Win2000 DC, and check if users can make their logon, etc...
11) If test is OK, boot Win2000 DC and demote this server
12) Change DNS ip on Win2000 DC server to the temporary Win2003 DC server, and change DNS ip on Win2003 DC to localhost
13) Uninstall DNS on Win2000 DC server
14) On Win 2003 DC server, delete DNS name records for old Win 2000 DC server
15) On Win2003 DC server, raise domain functional level to '2003 domain level'

FASE 2
1) Boot up the new Win2008 R2 server
2) On Win2003 DC, insert Win2008R2 srv CD
Do the '2008 ad preparation'
Command line (as administrator)
- adprep/forestprep 
-adprep/domainprep
-adprep.exe /domainprep /gpprep

3) On Win2003 DC, try the 'dcdiag.exe' and the 'netdiag.exe' to verify there are no errors
4) insert IP settings in Win2008R2 srv + DNS (primary) is the WIN2003 DC
5) On Win2008R2 srv, do the dcpromo (check after if AD, DNS & DHCP settings are replicated OK)
6) On Win2003DC, change the 'schema master' to the new Win 2008R2 DC
7) Mark the Win2008R2 DC as 'global catalog' and unmark the 'global catalog' on the Win2000 DC
8 ) On the Win2003 DC, at Operations Master, change the FSMO roles to the temporary Win2008R2 DC
9) Check replication
10) Shutdown temporary Win2003 DC, and check if users can make their logon, etc...
11) If test is OK, boot Win2003 DC and demote this server
12) Change DNS ip on Win2003 DC server to the new Win2008R2 DC server, and change DNS ip on Win2008R2 DC to localhost
13) Uninstall DNS on Win2003 DC server
14) On Win 2008R2 DC server, delete DNS name records for temporary Win 2003 DC server
15) On Win2008R2 DC server, raise domain functional level to '2008R2 domain level'

FASE 3
Finish upgrade
- Copy file server shared folders
- Configure backup
- ...

Several ways.

1 - Use the package and deployment wizard to package the app, and setup will
install it in a folder that is automatically trusted.  (Probably too late for
that in your case.)

2 - You could digitally sign the app before deploying and the customer could
accept the digital signature before opening the db.  (Expensive and has to be
renewed every year.)

3 - The customer could hack the registry.  (Scary thought.  Build a registry
script for them to double click on.)  Create these 3 registry keys:

1 - VBA warnings setting (DWORD):

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\12.0\Access\Security

VBAWarnings = 1

2 - Sandbox mode setting (DWORD):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines

SandboxMode = 2

3 - Macro security setting, either for all users or current user (DWORD, 1 =
low level):

(For all users on pc)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Access\Security

Level = 1

-----------------------
(Or for single user on pc)

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\12.0\Access\Security

Level = 1