finance_teacher
asked on
Windows Server -- 2003 to 2012 R2
Does anyone have a GOOD step-by-step checklist
like the below when I replace my two 2003 32bit
DC, AD, DNS, DHCP, GP, file, and print servers,
one server at each location, with newer
2012 64bit servers ?
-------------------------- ---------- ---------- --
Timeline
1. add new 2012 64bit servers to domain
2. use "Windows Server 2012 Migration Tools",
Microsoft's ROBOCOPY or XCOPY, etc to do the below
** copy files and security
** copy assocaited user and security
** copy DC, AD, DNS, DHCP, GP, RAID, etc settings
** install 32 and 64 bit NETWORKED printers
** deal with any Deprecated features
3. make sure EqualLogic SAN connections and
old site #2 2003 DC can still be replicated/etc
4. promote them at the same time to avoid
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
5. change a few CLIENTS primary DNS server
to be new 2012 64bit servers' IP
6. test both locations
7. demote old servers
8. change new 2012 64bit servers' IP address to old
servers' IP so remaining clients get new server
9. setup "file server resource manager"
on new server to move to OLD folder if
"last file access time"
is over 365 days ago
** http://technet.microsoft.com/en-us/library/dd759233.aspx
** http://blogs.technet.com/b/filecab/archive/2009/05/11/dealing-with-stale-data-on-file-servers.aspx
like the below when I replace my two 2003 32bit
DC, AD, DNS, DHCP, GP, file, and print servers,
one server at each location, with newer
2012 64bit servers ?
--------------------------
Timeline
1. add new 2012 64bit servers to domain
2. use "Windows Server 2012 Migration Tools",
Microsoft's ROBOCOPY or XCOPY, etc to do the below
** copy files and security
** copy assocaited user and security
** copy DC, AD, DNS, DHCP, GP, RAID, etc settings
** install 32 and 64 bit NETWORKED printers
** deal with any Deprecated features
3. make sure EqualLogic SAN connections and
old site #2 2003 DC can still be replicated/etc
4. promote them at the same time to avoid
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
5. change a few CLIENTS primary DNS server
to be new 2012 64bit servers' IP
6. test both locations
7. demote old servers
8. change new 2012 64bit servers' IP address to old
servers' IP so remaining clients get new server
9. setup "file server resource manager"
on new server to move to OLD folder if
"last file access time"
is over 365 days ago
** http://technet.microsoft.com/en-us/library/dd759233.aspx
** http://blogs.technet.com/b/filecab/archive/2009/05/11/dealing-with-stale-data-on-file-servers.aspx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.