Salut,
Comment fonctionnement le client ICA pour MAC ?
je m’explique j’arrive pas à comprendre comment le client ICA peut fonctionner du fait qu’il faut que le mac est une cal TS non ?
bonjour,
les clients non Windows utilisent la base de registre du serveur Presentation Server pour stocker les TSCALs (HKLMSoftwareCitrixMSLicensing)
http://forum-citrix.com/index.php/topic,350.0.html
http://forum-citrix.com/index.php/topic,1121.0.html
ok thanks et simple curiosité… en rdp ça se passe comment ?
avec le client Mac RDP ? aucune idée… mais je pense que le serveur TSE doit lui aussi jouer le role de passerelle car tu n’a de toute façon pas la possibilité de bypasser les TSCALs
oueps ça doit-être ça…
je regarderais chez MS afin de voir le cheminement pour obetnir un cal sur un mac qui fait du rdp
"karl1403" wrote:
oueps ça doit-être ça..
je regarderais chez MS afin de voir le cheminement pour obetnir un cal sur un mac qui fait du rdp
je regarderais chez MS afin de voir le cheminement pour obetnir un cal sur un mac qui fait du rdp
http://www.brianmadden.com/content/article/TS-CAL-token-storage-on-client-devices-with-no-local-storage
"He said that the official RDP specification from Microsoft requires that client devices have a local storage capability, and that the TS License server does not track CALs in this way for clients without any local storage."
Donc visiblement elle est stockée localement...
Mais de la même source :
How Linux and the open source clients deal with client devices with no local storage
To understand how these work, we went to Claudio Rodrigues, the original developer of the server-based computing software bought by 2X, and now the guy behind TSfactory.com.
Claudio said that since Linux-based Thin Clients usually use RDesktop, which was developed without the RDP specs, what happens really depends on the manufacturer. For example, PXE-based solutions grab the stored information about the TS CAL token from a server and present that to RDesktop software after Linux loads but before RDesktop is called. If you have no TS CAL token and the terminal server sends you one, the Linux OS could simply get it and save it somewhere on the network. The weird thing is that this is completely up to the vendor to implement, so depending on the vendor this may or may not be implemented. (And if it is, it may be different from vendor to vendor).
"ThinIsFat" wrote:
Mais de la même source :
How Linux and the open source clients deal with client devices with no local storage
To understand how these work, we went to Claudio Rodrigues, the original developer of the server-based computing software bought by 2X, and now the guy behind TSfactory.com.
Claudio said that since Linux-based Thin Clients usually use RDesktop, which was developed without the RDP specs, what happens really depends on the manufacturer. For example, PXE-based solutions grab the stored information about the TS CAL token from a server and present that to RDesktop software after Linux loads but before RDesktop is called. If you have no TS CAL token and the terminal server sends you one, the Linux OS could simply get it and save it somewhere on the network. The weird thing is that this is completely up to the vendor to implement, so depending on the vendor this may or may not be implemented. (And if it is, it may be different from vendor to vendor).
How Linux and the open source clients deal with client devices with no local storage
To understand how these work, we went to Claudio Rodrigues, the original developer of the server-based computing software bought by 2X, and now the guy behind TSfactory.com.
Claudio said that since Linux-based Thin Clients usually use RDesktop, which was developed without the RDP specs, what happens really depends on the manufacturer. For example, PXE-based solutions grab the stored information about the TS CAL token from a server and present that to RDesktop software after Linux loads but before RDesktop is called. If you have no TS CAL token and the terminal server sends you one, the Linux OS could simply get it and save it somewhere on the network. The weird thing is that this is completely up to the vendor to implement, so depending on the vendor this may or may not be implemented. (And if it is, it may be different from vendor to vendor).
Ce n'est pas contradictoire... Microsoft dit seulement: "le client doit pouvoir stocker le token"... peu importe où...
La solution est ici:
"Le client RDP pour Macintosh stocke la licence dans un fichier dans la hiérarchie de dossiers de l'ordinateur local sous /users/Shared/Microsoft/RDC Crucial Server Information/. "
http://support.microsoft.com/kb/187614/fr
merci pour la soluce !
ha ben merci beaucoup… même pas eu le temp de faire un search…chez MS…