Vista - MSI install issue

How can I install software in a Windows XP Mode VM if "the Windows
Installer does not permit installation from a Remote Desktop
Connection"?

On Tue, 22 Sep 2009 07:14:51 -0700, "Tim Frost"
<tim.@newsgroup> wrote:
You have probably found a bug in Windows 7...

Since the console in XPMode on Win7 uses Remote Desktop this will be a
problem.

There are others as well:
I know by bad experience that Safenet Sentinel protection dongles have
an issue in the driver that makes it refuse to hook onto a dongle if
the user is operating the software from a RDP session. How they detect
this I don't know, but it is a fact thta at least in some driver
versions this is blocked.

So this also will screw up Win7 XPMode handling, I guess....

MS needs to make the virtual XP machine believe it is NOT accessed via
an RDP console to solve this problem.

--

Bo Berglund (Sweden)

Disable the integration components, install software, reenable the
integration components is the easiest way.

--
Bob Comer


On Tue, 22 Sep 2009 07:14:51 -0700, "Tim Frost"
<tim.@newsgroup> wrote:

>MS needs to make the virtual XP machine believe it is NOT accessed viaJust disable the integration components and the VM doesn't know its
coming over an RDP connection. If needed, you can always install the
old VPC additions for time sync and video...

--
Bob Comer


On Tue, 22 Sep 2009 16:26:20 +0200, Bo Berglund
<boberglund@newsgroup> wrote:

I forgot to mention if you do want to install the VPC additions,
uninstall the integration components before you do that.

--
Bob Comer


On Tue, 22 Sep 2009 10:27:55 -0400, Robert Comer
<bobcomer-removeme-@newsgroup> wrote:

I know this is an old topic, but with the release of Windows 7, I'm sure more
than one person has stumbled upon this. (I know I had)

Ignore everything everyone has posted; it has nothing to do with integration
or Remote Desktop (directly). It's because you're accessing an installer from
your main PC over the Terminal Services file share. (\\tsclient) All those
virtual drives appearing in My Computer on your virtual machine are mapped to
your Windows 7 computer using that technology.

Solution:
Pick one of the three:

Copy the installation files to your virtual C hard drive first, and run the
installers for your software from the virtual C drive.

OR

Set up a (or use an existing) network share on your Windows 7 computer; that
way, you're using a standard UNC path. (e.g., if your Windows 7 computer has
an IP address of 192.168.1.100, from your virtual machine, go to
\\192.168.1.100 and open up the share you created).

OR

Supposedly you can map the TSClient drive, and the MSI Installer won't check
to see what it's actually mapped to, however, I'm not a big fan of that idea
-- the protection scheme is there for a reason.