Checklist for Moving to A New Webserver
Does anyone have a checklist of the things they do when moving client websites to a new server? This is a quick list I threw together from memory. The next time I do this, I will keep exact notes and update this post. This info applies to a dedicated server or a virtual private server (VPS) hosting account running Windows 2003.
If you have a similar checklist, please leave me a link.
As you'll see below, I set up some very limited access user accounts and there are a few extra steps because of this.
- rename all standard user accounts such as “Administrator”; and make sure “Guest” account is disabled
- change Remote Desktop Connection port (see http://support.microsoft.com/kb/306759 -- ONLY takes effect after a REBOOT!)
- set up Windows firewall on new server. Add exceptions for:
- RDC (custom port)
- FTP
- HTTP
- create a special very limited Windows account for FTP use.
- get FTP working on new server
- set up logging and upload folders for FTP
- create folder structure on new server. Here are some examples I use on a system with three drives:
- D:\InetPub\Subtext
- D:\SQLData\Subtext
- E:\SQLLogs\Subtext
- E:\Logs\WebLogs\websitename.com
- E:\Settings\IIS (for config files, etc.)
- Etc.
- install NTFS Link and set up junctions for Community Server as per http://davestechshop.net/CommunityServerMultipleCommunities
- add Windows user account for LimitedWebAccount and make it a member of IIS_WPG on web server
- add read permissions for LimitedWebAccount account to:
- C:\WINDOWS\Temp (and maybe C:\temp) for LimitedWebAccount account
- Logging folders
- Website folders
- install MS SQL
- add login for LimitedWebAccount account
- Add custom trust policy as per http://davestechshop.net/CustomTrustLevelForCommunityServer or http://blog-howto.com/CustomizingTrustLevelPolicy
- create config files for IIS web sites and app pools on existing server
- edit IIS config files:
- change server name
- change logging folder
- create database backups on existing server
- copy website applications (CommunityServer, DNN, Subtext, etc.)
- zip up all stuff on existing server
- FTP it to new server
- add security login for LimitedWebAccount to MSSQL
- restore databases to new server
- add custom app pools in IIS (use config file)
- set app pool Identity to LimitedWebAccount account & set password
- set app pool Identity to LimitedWebAccount account & set password
- add web sites from config file (after checking edits for new server)
- copy website applications
- edit web.config files for db connection string and folders
- Set up backup jobs
- Set up offsite backup (FTP transfer)
- Dave's blog
- Login to post comments