Remote Desktop Connection 7.0

[Florent]

Hello all,

I am trying to sequence "Remote Desktop Connection 7.0" for XP SP3 under sequencer 4.2.2.15.

During the sequencing process I modify the registry keys as explained in the Microsoft KB (http://support.microsoft.com/?scid=kb%3 ... &x=11&y=13) to turn Credssp on and install Remote Desktop Connection 7.0.

Unfortunately, when I try to connect to a 2008 server I am presented with a nice error message :
"An authentication error has occured.
The requested security package does not exist."

I guess it is related to the modification of the registry keys during the sequencing that take precedence over the local registry.

Locally installed, it works like a charm.
Same applies if I modify the keys before the sequencing.

Is there a workaround for this problem ?
Can it be virtualize with 4.2 sequencer or you need a higher version ?

Thank you for your hepl.

[aaronparker]

The 4.2 Sequencer is very old, I would attempt with a more recent version. However, the RDP client is a Windows component, so I'm surprised that it would sequence anyway.

[Florent]

We sequenced version 6.0 without a problem.

I tried with a sequencer 4.5 but achieved the same result.

[aaronparker]

What's the reason for virtualising this application instead of deploying, if you don't mind me asking?

[jur]

The security bits are in a place of the registry which feels like are being loaded before the App-V client can perform any action on them. Or are used by processes outside of the VE.

Like Aaron says: As a guide line I would says to follow the best practices and not virtualize OS components. I never tried sequencing RDP.
I wonder how far you'll get. Keep us posted.

[Florent]

What's the reason for virtualising this application instead of deploying, if you don't mind me asking?

It has to do with the registry settings.
We wanted to inclued them in the VE to avoid problems for machines without those settings trying to connect to 2008 servers.

Unfortunately, it looks like it won't work.

[Florent]

According to Microsoft Support, what we want to do is not possible but I am still waiting for the official statement.