XPe TS CAL Issue

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #123
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    Hi Guys,

    We have an issue which has appeared recently on our XPe terminals.

    All of our XPe Terminals have the Write Filter enabled, and as a result it seems that when they shutdown/restart any TSCALs (temp or perm) that have been written into HKLMSoftwareMicrosoftMSLicensingStore….. aren’t held on the terminal.

    As a result, this causes each terminal to be tied to a huge number of CALs in the Terminal Server Licensing component of Windows and causes Windows to allocate several permanant TSCALs to a single terminal and therefore we run very low on the total number of TSCALs that are available.

    Is there a known fix for this issue, or somewhere that we can exclude the SoftwareMicrosoftMSLicensingStore keys from being flushed by the Write Filter on reboot?

    Cheers

    #8637
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    If you are using per device licencing make sure you are using XPe SP2 and this should resolve the issue.

    Not sure what model terminal you are using or if you have a 2000 or 2003 TS licence server so its a bit of a guess,

    Cheers,

    -TT

    #8639
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    TT,

    They are still on XPe SP1 (Wyse Build 330) – we will shortly be rolling out the XPe SP2 Build now that Wyse has released it for those terminals finally 😉

    We’re using per-device licensing in a 2003 environment – hence the terminals constantly stealing TSCALs on reboot was starting to hurt!

    I’ve done some sums, and we should just survive until we roll out XPe SP2 across the terminals. Just out of interest – was it a Wyse change (to the write filter) or Microsoft change (in SP2) that fixed the bug of terminals stealing extra TSCALs?

    #8640
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    It’s a weird one. All XPe terminals have a feature called netXclean, on log off this cleans up files that could fill the flash and copies registry settings (namely the MC Licence key) to a small 1MB partion on the device. When the device boots again it reads the TS CAL back again. In this way the CAL is saved.

    There are loads of terminals out there still with SP1 and no issues but for some reason a small amount have this issue. There is a batch file that you can put in the start up folder to ensure the TC CAL back up happens but I have only had limited success with this. I have seen this first hand and it’s a strange issue that Wyse and MS tried to resolve and “went away” with SP2.

    Interestingly I have never seen this with XPe no service pack and the process of TSCAL backup is identical. One cool thing I found with my old XPe environment (no service pack) was they told the Windows 2000 TS licence server they were full XP Pro and so I never had to buy a TS CAL! Back in 2002 CALS were like $190 AU so this was very sweet.

    Moral of the story, sometimes the MS bugs can even be good. As a FYI I have never heard of the TC CAL issue on XPe SP2, maybe someone will post if they have fixed this issue with the upgrade so we know for sure,

    Good Luck!

    TT

    #8641
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    Cheers Mate for the advice.

    We’ve only got about 100 of the 9450’s so hopefully everything will be ok with SP2. Why can’t they be as easy to rollout/upgrade as 1200’s/S10s…. Good old legacy applications 🙂

    Now if only Citrix and Wyse would sit down and use the mpeg chip that Wyse have on the 1200’s to decode video via SpeedScreen Multimedia that would eliminate the need for about 75% of the 9450’s we have.

    That Wyse Player app was very cool, but it seems to have been killed off now?

    #8642
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    Yep, I agree. The problem was the MPEG Player was OK at MPEG1 but with all the formats now it would not work. There is work being done to try and replace this but Citrix is using the DirectX6c direct show instructions to decode the media and this will not work on Blazer. A whole new way needs to be developed – lets hope they pull it off!

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.