> 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 do have it essentially with 127.0.0.1 in the intranet zone. I don't know if that is required at this point because I need that for some other software of mine. I had checked all the dcomcnfg settings but Vista had them correct and I did not have to modify anything there. After a long night of experimenting and checking and reinstalling and researching on the web, it all boiled down to simply unchecking that protected mode switch in the trusted sites zone in my case.

Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

I am still getting this error message even after I have done all these
changes... Any other suggestions?

"PS" wrote:

>
> > 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
do have it essentially with 127.0.0.1 in the intranet zone. I don't know if that is required at this point because I need that for some other software of mine. I had checked all the dcomcnfg settings but Vista had them correct and I did not have to modify anything there. After a long night of experimenting and checking and reinstalling and researching on the web, it all boiled down to simply unchecking that protected mode switch in the trusted sites zone in my case.
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
>