Previous Next

• 02-12-2008, 9:54 AM

  OWScott Joined on 08-12-2002, 1:25 PM Posts 57	IIS Manager 7.0 for Vista Reply Contact Where is the RTM version of IIS Manager for remotely connecting to Windows Server 2008?  I had thought that the one in Vista SP1 would connect to w2k8, but that doesn't appear to be the case.  There isn't a 'connect to' option.  Is it a separate download?  Where can I get a copy?  And, what about w2k3 and XP?  Is the RTM version available yet? Thanks, Scott

• 02-12-2008, 11:46 AM

  In reply to

  rlucero Joined on 09-29-2006, 3:35 PM Seattle, WA Posts 114	Re: IIS Manager 7.0 for Vista Reply Contact In order to get the "Connect to.." Option you need Remote Manager installed for Vista SP1.  The currently available version should allow you to connect to RTM Win2k8.   If you browse the Download Center you can find the RC1 version of remote manager for Win2k3 and XP. The RTM version is not available at this time. -- -Robert Lucero SDET IIS

• 02-12-2008, 12:52 PM

  In reply to

  OWScott Joined on 08-12-2002, 1:25 PM Posts 57

  Re: IIS Manager 7.0 for Vista Reply Contact Are you saying that Remote Manager for Vista SP1 should be on the system already?  I went to add programs and ensured that I have "IIS Management Console" enabled.  That's the only option I see related to this. I'm running Vista SP1. I can see the icon for "Connect to.." but it's grayed out. I guess I don't understand what I need to do to get remote Manager on Vista SP1.

• 02-13-2008, 10:58 AM

  In reply to

  rlucero Joined on 09-29-2006, 3:35 PM Seattle, WA Posts 114	Re: IIS Manager 7.0 for Vista Reply Contact Sorry, let me clarify.  In order to use Remote Manager functionality through the IIS Management Console in Vista you need to download and instal IIS Remote Manager.  It isn't on the system by default.

• 02-13-2008, 11:33 AM

  In reply to

  OWScott Joined on 08-12-2002, 1:25 PM Posts 57	Re: IIS Manager 7.0 for Vista Reply Contact Thanks.  So this is still in RC0 at this time.  Somehow I thought that for Vista it wasn't a separate downtime, but I guess I was mistaken.