> Hi,
>
> I've installed Virtual Server on XP & 2003 a few times now, but this is
> the first for Vista.
>
> With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
> following address:
>
> http://MachineName/VirtualServer/VSWebApp.exe?view=1
>
> Sometimes I need to fully qualify the "MachineName", but that's okay.
> e.g. MachineName.MyDomain.local
>
> With Vista however, I get the following error when I use its MachineName:
> "Could not connect to Virtual Server. Please add the Virtual Server
> administration website to the Internet Explorer trusted sites list".
>
> So, I took a look at IE 7 trusted sites list and I find "localhost" as the
> trusted site (just like the other machines have). So I tried using this
> link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it
> does work (albeti it opens a new IE session, which is a pain).
>
> So why is it that XP and 2003 have no problem if I use there
> "MachineName", but Vista will only accept "LocalHost"?
>
> I suppose this is more to do with IIS than Virtual Server, but I thought I
> would try here first.
>
> btw, I did NOT have IIS installed on Vista before hand and therefore
> Virtual Server (at SP1), did this for me. I don't recall that pre-SP1
> would do this and would just exit the install until I did it separately
> (on XP). Could this be the problem? Maybe IIS is not installed just
> right?
>
> Thanks,
>
> Bob.

>Hi,
>
>I found something new. I found that if I run IE as an Administrator, I no
>longer have the problem finding the Virtual Server using "localhost" or my
>MachineName. At the moment, I have nothing entered into my trusted site
>location.
>
>Any ideas why this is?

>I suppose I could disable UAC and try again. I suspect it will work too.
>I'm logged on as a Domain Admin to Vista and I need to use "Run As
>Administrator". But when I log on as the local Administrator, I do not
>need to "Run As". I suspect that the UAC doesn't apply the the local
>Administrator UserID - but it does apply to users that have Administrator
>credentials.
>
> Anyway, shouldn't Virtual Server be able to bring up its own web site
> without having to open IE via "Run As Administrator"?
>
> Thanks
>
> Bob.

> Hi,
>
> I've installed Virtual Server on XP & 2003 a few times now, but this is the
> first for Vista.
>
> With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
> following address:
>
> http://MachineName/VirtualServer/VSWebApp.exe?view=1
>
> Sometimes I need to fully qualify the "MachineName", but that's okay. e.g.
> MachineName.MyDomain.local
>
> With Vista however, I get the following error when I use its MachineName:
> "Could not connect to Virtual Server. Please add the Virtual Server
> administration website to the Internet Explorer trusted sites list".
>
> So, I took a look at IE 7 trusted sites list and I find "localhost" as the
> trusted site (just like the other machines have). So I tried using this
> link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it does
> work (albeti it opens a new IE session, which is a pain).
>
> So why is it that XP and 2003 have no problem if I use there "MachineName",
> but Vista will only accept "LocalHost"?
>
> I suppose this is more to do with IIS than Virtual Server, but I thought I
> would try here first.
>
> btw, I did NOT have IIS installed on Vista before hand and therefore Virtual
> Server (at SP1), did this for me. I don't recall that pre-SP1 would do this
> and would just exit the install until I did it separately (on XP). Could
> this be the problem? Maybe IIS is not installed just right?
>
> Thanks,
>
> Bob.

> Thanks Christian, but that doesn't work either. The only thing that does
> work is to run IE in Administrator mode (even though I'm logged on as an
> administrator).
>
> --
> Thanks,
> Bob

>
>> Hi,
>>
>> I've installed Virtual Server on XP & 2003 a few times now, but this is
>> the
>> first for Vista.
>>
>> With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
>> following address:
>>
>> http://MachineName/VirtualServer/VSWebApp.exe?view=1
>>
>> Sometimes I need to fully qualify the "MachineName", but that's okay.
>> e.g.
>> MachineName.MyDomain.local
>>
>> With Vista however, I get the following error when I use its MachineName:
>> "Could not connect to Virtual Server. Please add the Virtual Server
>> administration website to the Internet Explorer trusted sites list".
>>
>> So, I took a look at IE 7 trusted sites list and I find "localhost" as
>> the
>> trusted site (just like the other machines have). So I tried using this
>> link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it
>> does
>> work (albeti it opens a new IE session, which is a pain).
>>
>> So why is it that XP and 2003 have no problem if I use there
>> "MachineName",
>> but Vista will only accept "LocalHost"?
>>
>> I suppose this is more to do with IIS than Virtual Server, but I thought
>> I
>> would try here first.
>>
>> btw, I did NOT have IIS installed on Vista before hand and therefore
>> Virtual
>> Server (at SP1), did this for me. I don't recall that pre-SP1 would do
>> this
>> and would just exit the install until I did it separately (on XP). Could
>> this be the problem? Maybe IIS is not installed just right?
>>
>> Thanks,
>>
>> Bob.
>
> Same problems here. I won't run IE as Admin, if MS can't get their own
> software to work properly why should i use it? Not problems whatsoever
> with VMWare.
>
> MS, don't say I gave you a chance, it just didn't work.
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
> Information Technology Shop - http://www.bitshop.com

>I understand what you say Colin, but how does this help me? I still must
>start IE with "Run as Administrator" in order to get Vista to display its
>own VS. Vista has no problem displaying other VS's, but when it comes to
>its own. I have to jump through hoops to get it to work.
>
> It doesn't matter if I have UAC on or off. Nor does it matter if I have
> IE Protect Mode on or off. I suspect it doesn't even matter if I'm logged
> on as an Administrator. All that works is IE "Run as Administrator"
> (which btw takes IE a much longer time to launch when I do this).
>
> --
> Thanks,
> Bob

> Hi,
>
> I've installed Virtual Server on XP & 2003 a few times now, but this is the
> first for Vista.
>
> With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
> following address:
>
> http://MachineName/VirtualServer/VSWebApp.exe?view=1
>
> Sometimes I need to fully qualify the "MachineName", but that's okay. e.g.
> MachineName.MyDomain.local
>
> With Vista however, I get the following error when I use its MachineName:
> "Could not connect to Virtual Server. Please add the Virtual Server
> administration website to the Internet Explorer trusted sites list".
>
> So, I took a look at IE 7 trusted sites list and I find "localhost" as the
> trusted site (just like the other machines have). So I tried using this
> link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it does
> work (albeti it opens a new IE session, which is a pain).
>
> So why is it that XP and 2003 have no problem if I use there "MachineName",
> but Vista will only accept "LocalHost"?
>
> I suppose this is more to do with IIS than Virtual Server, but I thought I
> would try here first.
>
> btw, I did NOT have IIS installed on Vista before hand and therefore Virtual
> Server (at SP1), did this for me. I don't recall that pre-SP1 would do this
> and would just exit the install until I did it separately (on XP). Could
> this be the problem? Maybe IIS is not installed just right?
>
> Thanks,
>
> Bob.

> Hi,
>
> I've installed Virtual Server on XP & 2003 a few times now, but this is the
> first for Vista.
>
> With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
> following address:
>
> http://MachineName/VirtualServer/VSWebApp.exe?view=1
>
> Sometimes I need to fully qualify the "MachineName", but that's okay. e.g.
> MachineName.MyDomain.local
>
> With Vista however, I get the following error when I use its MachineName:
> "Could not connect to Virtual Server. Please add the Virtual Server
> administration website to the Internet Explorer trusted sites list".
>
> So, I took a look at IE 7 trusted sites list and I find "localhost" as the
> trusted site (just like the other machines have). So I tried using this
> link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it does
> work (albeti it opens a new IE session, which is a pain).
>
> So why is it that XP and 2003 have no problem if I use there "MachineName",
> but Vista will only accept "LocalHost"?
>
> I suppose this is more to do with IIS than Virtual Server, but I thought I
> would try here first.
>
> btw, I did NOT have IIS installed on Vista before hand and therefore Virtual
> Server (at SP1), did this for me. I don't recall that pre-SP1 would do this
> and would just exit the install until I did it separately (on XP). Could
> this be the problem? Maybe IIS is not installed just right?
>
> Thanks,
>
> Bob.

>
> > Hi,
> >
> > I've installed Virtual Server on XP & 2003 a few times now, but this is the
> > first for Vista.
> >
> > With XP & 2003, I can go to the "Virtual Server 2005 R2" site using the
> > following address:
> >
> > http://MachineName/VirtualServer/VSWebApp.exe?view=1
> >
> > Sometimes I need to fully qualify the "MachineName", but that's okay. e.g.
> > MachineName.MyDomain.local
> >
> > With Vista however, I get the following error when I use its MachineName:
> > "Could not connect to Virtual Server. Please add the Virtual Server
> > administration website to the Internet Explorer trusted sites list".
> >
> > So, I took a look at IE 7 trusted sites list and I find "localhost" as the
> > trusted site (just like the other machines have). So I tried using this
> > link instead: http://localhost/VirtualServer/VSWebApp.exe?view=1 and it does
> > work (albeti it opens a new IE session, which is a pain).
> >
> > So why is it that XP and 2003 have no problem if I use there "MachineName",
> > but Vista will only accept "LocalHost"?
> >
> > I suppose this is more to do with IIS than Virtual Server, but I thought I
> > would try here first.
> >
> > btw, I did NOT have IIS installed on Vista before hand and therefore Virtual
> > Server (at SP1), did this for me. I don't recall that pre-SP1 would do this
> > and would just exit the install until I did it separately (on XP). Could
> > this be the problem? Maybe IIS is not installed just right?
> >
> > Thanks,
> >
> > Bob.
>
> I had pretty much the same problem. After setting the prerequisites for Vista in the Add Windows components. I could get access ONLY by running iexplore as administrator. Removing the protected mode switch in the browser was the answer for me. I am using it in a non-production environment and only in a workgroup which I thought might be part of my problem when using the authenticated user group--but it wasn't. I did also initially have some problems with the windows firewall as this is a home machine I use for testing and I am using Windows Onecare which kind of hijacks the normal windows firewall for the Onecare version so initially it was still blocking and didn't pop-up to notify it was blocking. I had also initially did the IIS manually (prerequisites mentioned above) although the VS installation said it would too, but I didn't catch that until after I did it manual and more reading. Having http://localhost in the trusted sites does not appear to be required, though I
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
>