| |||||||||||||||||||||||
|
Moving IIS Not Easy Members of the ISP-NT list discuss moving files and web pages from one server to another.
On the ISP-NT list in November, AU asked,
A number of respondents noted that there really is no easy answer: [GB urged] "Just bite the bullet and reconfigure. At the same time, I would recommend a move to Server 2000 for ease of administration." [JC observed] "Restoring the metabase won't work; there are also entries in the registry that IIS needs. When you create a domain in IIS, entries are created in the metabase and the registry." [JM inquired] "What about restoring from a backup, or upgrading a server? There's got to be a simpler way. If not, then NT has no business touting itself as an enterprise class web server. I run NT web hosts, but luckily have never been through this. I don't relish the thought of reconfiguring hundreds of virtual servers by hand, I can assure you." TSR suggested that an application to take care of this would be a wonderful thing: "I have moved servers with over a hundred domains more than once, and had to do it all by hand. I've just learned to build a solid, stable server that I would not have to mess with for a while. I still have to change out hardware at least once a year, though. Software's never really done the trick before, but I am sure it is better by now. If not, someone could make a bundle of cash-I would probably buy it if the price was right." A couple of respondents had just the solution TSR was looking for: [BK advised] "Try http://www.serverautomationtools.com. DomainReportItPro worked for us." [AP suggested] "Try IIS Export Utility It's a shareware utility that worked for us. We just moved 200 web sites-it does not bring over FrontPage extensions, but the sites themselves went very smoothly. We had to manually add the FrontPage extensions, which was a small bummer, but otherwise it was great." End
|
|
|||||||||||||||||||||
|
| |||||||||||||||||||||||
#