How to Migrate IIS Website to Another Server.pdf
•
0 likes•27 views
Get a step-by-step guide for migrating an IIS website to a new server. You will get full insights to ensure a successful transfer of your site.
Report
Share
More Related Content
Similar to How to Migrate IIS Website to Another Server.pdf
Similar to How to Migrate IIS Website to Another Server.pdf (20)
Recently uploaded
Recently uploaded (20)
How to Migrate IIS Website to Another Server.pdf
- 1. How to Migrate IIS Website to Another Server? Hey there! Are you planning to migrate your IIS website to another server for - Improving the performance Enhancing security Upgrading to a different server technology Optimizing expenses Constant support & technical assistance Then, this article is for you! Migrating an IIS website to a new server can be complex and time-consuming, especially when it has extensive content and functionalities. However, it's always better than going through the hassle of developing a website from scratch. In fact, migration comes with ample benefits, such as preservation of the website’s assets, stability of the rankings, cost-effectiveness, and of course, scalability. Although it is important to know migration should be planned and executed with careful consideration. Since you have already decided to shift to a new server, the next step is to understand how to migrate an IIS website, which we will discuss step by step in this write-up. Without further ado, let’s jump at it! Also Read: How To Connect To A Windows VPS using RDP? How to Migrate an IIS Website to Another Server? Generally, there are two methods of migrating an IIS website to a different server -
- 2. 1. Shared Configuration 2. AppCmd.exe We will explain both methods in detail for you to choose the one fitting to your comfort and convenience. Also Read: How to restart the RDP without rebooting the Windows server? Method 1. Shared Configuration Step-1: Start by opening the IIS Manager and then click on the main server node. Step-2: In the main server node, scroll below to find the Shared Configuration option. Generally, this option is on the right corner of the page. Step-3: Double-click on the Shared Configuration option, and you will be redirected to a new page where you have to locate the Export Configuration link.
- 3. Step-4: After tapping on the Export Configuration link, you will be diverted to a new window wherein you have to input a Physical Path of the configuration files you wish to store. Note - Ensure to choose an existing folder rather than creating a new one to avoid potential issues or receive error messages. Next, add a configuration password with a mix of numerals, upper & lower case, and special characters to ensure your account is fully secured. After creating the password, press OK. Step-5: Open the Export Configuration folder, and you'll see three files. Copy all three files and paste them into the new server.
- 4. In case you are still confused about which files to choose, here are the names - 1. administration.config 2. applicationHost.config 3. configEncKey.key Step-6: After copying the files, repeat the initial process. Open the IIS Manager and search for the main server nodes. Step-7: In the main server nodes, scroll down to the Shared Configuration option, and click on it.
- 5. Step-8: In the Shared Configuration window, tick the Enable Shared Configuration box and fill in the details like the Physical Path of the configuration files, your user name, and the password. Finally, reconfirm the password and tap ‘Apply’ right above the window. Note - If you don’t want to add the username and password for accessing the Physical Path in the future, you can add your NTID or service account username and password Step-9: Once you click Apply, you will be asked to add your encryption password, which you created earlier. Step-10: After adding the encryption password, you will get a pop box stating, “Your existing IIS encryption keys will be backed up in the current configuration directory on your local computer. To restore these keys later, turn off the shared configuration.”
- 6. All you need to do is click OK, and you will receive another pop-up saying, “The changes have been successfully saved. You must close and reopen IIS Manager for it to recognize the configuration changes that you have made.” Click on Ok and follow the instructions mentioned in the pop-up box. Usually, this method should be preferred when your existing server is entirely new. However, if you have a legacy website, avoiding this method is recommended, as you might come head- on-head with potential problems which can complicate the overall migration process. Also Read: How to Download My Full Website From cPanel as a Backup Method 2. AppCmd.exe Step-1: Start by launching the Command Prompt on your server and input the following Command Line to export websites and application pools - C:> %windir%System32inetsrvappcmd list apppool /config /xml > C:AppPools.xml Note - Delete the default application pools, as you might face issues during the import process.
- 7. Step-2: After the command line has exported all the Application pools, the next step is to export the website settings individually. Step-3: Now navigate back to the Command Prompt and add the below-mentioned command line - %windir%system32inetsrvappcmd list site /config /xml > c:sites.xml Step-4: Copy both xml files, AppPools.xml and Websites.xml, to a similar folder in the new server. Step-5: Head to the new server and run the Command Prompt. Step-6: To import the Application pools, paste this command line - %windir%system32inetsrvappcmd list apppool “MyAppPool” /config /xml > c:myapppool.xml Once this command is successful, import your website by adding the other xml file - %windir%system32inetsrvappcmd list site /config /xml > c:sites.xml Congratulations! You are now all set! Conclusion We hope this knowledge base article helps you migrate your website to the new server efficiently and seamlessly. If you have any concerns or cannot handle the migration process on your own, contact a professional immediately. The expert will assist you at every step and streamline the transition. Source