Unity Computing

Andy Kurth · Posted: Wed Jun 06, 2007 11:12 am Post subject: K2 Client 7.x (Keyclient)

K2 Client 7.x will be installed for the fall 2007 semester. This thread will be used to track the progress of building, testing, and shipping this application.

jaklein · Posted: Wed Jun 06, 2007 2:11 pm Post subject: KeyClient latest version is 6.1

I checked with Bill C. , and the latest KeyClient is version 6.1
It's located under \\unity.ad.ncsu.edu\dfs\itd\applications\sassafras

jrwells

The latest flavor of Keyclient 6.1 was released on 20070520.
The internal version number is 6.1.2.0 for keyacc32.exe.

Tom Farwig · Joined: 23 Mar 2006 Posts: 23

I'll update the MST file I have for the AD install to work with 6.1.2.0 instead of 6.1.1.0 and then migrate it over to a NAL install.

Tom Farwig · Joined: 23 Mar 2006 Posts: 23

Looks like no update is needed to the MST, it works with the newer MSI.

K2 Client 6.1.2.0 Installer should be showing up in Beta Test\Fall 2007 and has been associated using the guidelines for the app bulding phase in the blog post about the Fall 2007 Apps & Image Schedule.

Debbie Carraway · Joined: 03 Mar 2006 Posts: 28

I tried installing the K2 client, and received a message that uninstall couldn't continue because there were still some keyed applications running. I had just logged in and nothing was running except the NAL. However, there were 2 oddities. In the Task Manager, acrodist.exe and acrotray.exe were running (my guess is that these caused Key Client to activate). Killing them was insufficient. I also had to kill the keyserver process. Then, install proceeded normally.

Tom Farwig · Joined: 23 Mar 2006 Posts: 23

Any recommendations on what to use to kill off the keyaccess process during the uninstall?

And yes, those acrobat items are supposedly keyed.

Debbie Carraway · Joined: 03 Mar 2006 Posts: 28

I like PSKill from SysInternals:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/PsKill.mspx

srleap · Joined: 11 Jun 2007 Posts: 5

I sent this email to Tom - just thought I should probably post it here too:

Hey Tom,

I've deployed the 6.1.2 keyclient to the Textiles AD environment. On several machines the key access executable has been pegging the CPU and has to be killed manually. Have you seen this? Any tips in troubleshooting? I have a feeling that this will be happening to more of our machines as professors return and reboot their systems so I was hoping to head off the problem if possible.

Thanks,

Ryan