http://www.windowsitpro.com/authors/author/author/5777475/rsscomment/5777475en-USSun, 27 May 2012 07:27:38 GMTSun, 27 May 2012 07:27:38 GMThttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchorSun, 16 May 2004 08:53:12 GMT
I am trying to install Internet Information Services 5.0 on my computer but I never installed it with XP before. Can anyone help?]]>comptec Sun, 16 May 2004 08:53:12 GMThttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchorhttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchorTue, 25 Jul 2000 00:02:26 GMT
Hi, You wrote that clustered Web sites can be managed from the IIS MMC by adding the IIS site’s virtual server name to your IIS MMC and that this means that the IISSYNC utility isn’t needed anymore. This is not entirely right. If you make changes in the MMC, regardless wich name you use, it only changes the metabase of the node that the IIS resource group is runing on. To publish the changes to the other node you must use the IISSYNC util. Therefor I recommend to place all IIS resources (of the cluster) on one node, make the changes, publish the changes with the IISSYNC utility to the other node and move the resource groups to the nodes they belong to. P.S. MetaEdit 2.1 (Metabase editing tool) can also sync (backupo and restore) the metabases of IIS server, regardless if they are on a cluster or not. I haven’t done I doe, I only read it. With kind regards, ]]>Sander van Beek Tue, 25 Jul 2000 00:02:26 GMThttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchorhttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchorMon, 04 Oct 1999 11:19:25 GMT
In "Build a High-Availability Web Site with MSCS and IIS 4.0" (June), Jim Plas describes installation and configuration tips for deploying Microsoft Internet Information Server (IIS) 4.0 in a cluster using Microsoft Cluster Server (MSCS). The article contains several statements that could cause significant deployment problems.
First, the author mentions that he’s uncertain whether clustered IIS needs Microsoft Internet Explorer (IE) to run or just to install IIS’s application installation engine. IE is absolutely necessary for clustered or nonclustered IIS 4.0 installations. IE provides the Protected Storage service (among other things, such as the Windows scripting environment), which provides IIS with certificate management and access to protected parts of the Registry.
Second, the author states, "Although no negative effects occur if you install the Option Pack components on a shared drive, you should install the components in their default locations ..." However, installing the components to the shared drive will cause negative effects during Windows NT Option Pack setup and confusion for the person running the setup on the second node. The person who runs setup on the second node will be asked where to place the components. The shared drive will be unavailable on the second node because the first node of the cluster owns the shared drive and the first node has locked the shared drive for exclusive use. The person running the setup on the second node must place the components locally on the second node (the components are on the shared drive for the first node). This scenario results in a different IIS configuration on each node of the cluster. Microsoft doesn’t recommend that you configure IIS this way. If the first node owns the shared drive, the default and administration Web sites would be available on only the first node. If for any reason the first node didn’t own the shared drive, things such as the Administration Web site and the IIS online Help would not be available to the second drive.
Third, the author states that when you create a new IIS instance, you need to select Web Site and identify the directory that you previously created. Instead, you need to select Web Site and identify the Web site that you previously created. You don’t specify a physical directory in this wizard.
Fourth, the author has users run Iissync next. But at this stage of his instructions (without configuring Micro- soft Transaction Server--­MTS--­for replication), doing so would be unsuccessful. First, you must configure MTS for replication via a special user interface (UI) that the MTS snap-in provides for the Microsoft Management Console (MMC). The "Configuring MTS and IIS for Replication" section of the Microsoft article "How to Install the Windows NT Option Pack on Microsoft Cluster Server" (http:// support.microsoft.com/support/kb/articles/q191/1/38.asp) outlines this process. If you don’t configure MTS, Iissync won’t run successfully.
Finally, the author mentions that to avoid using Iissync, you can add your virtual server name to the IIS MMC and manage your Web site. The author implies that all synchronization will be taken care of for you. The only way to ensure that the Web sites are synchronized is to run Iissync from the command line or to manually configure both nodes. Connecting to the virtual server name via the MMC works only if you’ve configured MTS for remote administration, and makes changes to only the metabase or Registry of whichever node (not both) that currently owns the virtual server resource.
--­Kevin Briody
Product Manager, Windows Clustering
Microsoft]]>Kevin Briody Mon, 04 Oct 1999 11:19:25 GMThttp://www.windowsitpro.com/article/clustering/build-a-high-availability-web-site-with-mscs-and-iis-4-0#commentsAnchor