Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 13675 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SGN center on vmware issuing tokens??

Ad_ministrator

Hi all,

I want to use SGN 5.6 with Aladdin eTokens we already possess. My trial installation on a test machine worked (eventually; the manual is not all to clear).

After obtaining the licensed version I started to install this on a virtual Win2008R2 server on a VMware ESXi 4.1 host. Article 108133 says this should be okay; only there could be trouble when host does not support USB.

Esxi 4.1 host does support USB. I can read the token with the PKI Client 5.1; via a console session when the etoken is in an USB port on the host and via RDP session when the etoken is on the client.

However SGN Management Center does NOT find the token. Therefore I can not set the middleware module in the policy for machine settings. Therefore I can not virtualize the SGN MC.

Has anyone of you run into this and solved it (and please do not reply that I have to upgrade to latest version)??

Thanks

:42928


This thread was automatically locked due to age.
Parents
  • 0

    Hello Moderator,

    thanks for your reply.

    As stated earlier, I'm using Aladdin eToken Pro with eToken PKI Client 5.1SP1 as middleware. With this I have initialised the token on the vm.

    I've tried this manual once more with the same result. In the policy for machine settings I can NOT select the Aladdin eToken PKI Client; only possible choise is "not configured".

    As you suggested there might be something with the license, I opened the xml-file. This mentiones licenses for Management Center, Configuration Protection, Device Encryption and Data Exchange. Is the license for token-support not included?

    Regards

    Ad Ministrator

    :43127
Reply
  • 0

    Hello Moderator,

    thanks for your reply.

    As stated earlier, I'm using Aladdin eToken Pro with eToken PKI Client 5.1SP1 as middleware. With this I have initialised the token on the vm.

    I've tried this manual once more with the same result. In the policy for machine settings I can NOT select the Aladdin eToken PKI Client; only possible choise is "not configured".

    As you suggested there might be something with the license, I opened the xml-file. This mentiones licenses for Management Center, Configuration Protection, Device Encryption and Data Exchange. Is the license for token-support not included?

    Regards

    Ad Ministrator

    :43127
Children
No Data
Unfiltered HTML