PDA

View Full Version : Need help! TSE detection



NewsArchive
12-04-2001, 01:00 AM
Hi,

I've 2 install shield projects for our product. One for standard install and
one for TSE install.

Until there, we used to detect the TSE capabilities of the user system by
checking the registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server

And it worked fine with NT4 TSE and W2000 TE with InstallShield Pro 6.1.

Now, we 've got InstallShield Developer 7.01 and tried our setup on XP Pro.
It's seems that XP Pro includes the TSE services by default, and our setup
find the same key in the registry as for W2000, even if XP pro is not a
multisession system.

The question are :
Is there a way to detect that the Windows target is tse AND server ? Is the
TerminalServer propertie of Windows Installer can help me? If yes, how can i
get the value of this TerminalServer propertie in my installscript?

Thanks for answers.

Edgard BAUDRY

NewsArchive
12-04-2001, 01:00 AM
I would set the install conditions:

'MsiNTProductType=3 And TerminalServer'


"Edgard Baudry" <e.baudry@symbiose-informatique.com> wrote in message
news:3c0ccb29@news.installshield.com...
> Hi,
>
> I've 2 install shield projects for our product. One for standard install
and
> one for TSE install.
>
> Until there, we used to detect the TSE capabilities of the user system by
> checking the registry key:
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
>
> And it worked fine with NT4 TSE and W2000 TE with InstallShield Pro 6.1.
>
> Now, we 've got InstallShield Developer 7.01 and tried our setup on XP
Pro.
> It's seems that XP Pro includes the TSE services by default, and our setup
> find the same key in the registry as for W2000, even if XP pro is not a
> multisession system.
>
> The question are :
> Is there a way to detect that the Windows target is tse AND server ? Is
the
> TerminalServer propertie of Windows Installer can help me? If yes, how can
i
> get the value of this TerminalServer propertie in my installscript?
>
> Thanks for answers.
>
> Edgard BAUDRY
>
>