Brief answers to some typical questions
Question: I have Adobe SKU products which are licensed for cross-platform use – the product can be installed and used on either Windows or Mac. How do I map this from Purchases to Products and then to Policies? For example, Adobe Creative Suite 5.5 Design Premium has been purchased with a concurrent use license Metric which specifies a maximum concurrent use limit that must not be exceeded – regardless of the mix of Mac and Windows users.
Answer: There are basically two strategies:
1) create a new Product record – include all programs for both Mac and Window that belong to the cross-platform suite. Create a Purchase record and a Policy to manage this Product.
2) create a new Product record – but don't include any programs in its definition ! Create a Purchase record and a Policy for this "cross platform place holder product". But now modify the Policy by adding the two platform specific Products to its products list (e.g. drag the Mac and Windows 'Creative Suite 5.5 Design Premium' products into the product pane of your Policy details window). The result is a Policy that is set up to manage first the "cross platform place holder product" and then also the Mac and Windows Products that are the basis of the cross-platform licensing rights.
Strategy 2 is preferable since it takes direct advantage of the standard Product definitions for each platform which have been pre-defined by Sassafras.
Question: We have 110 concurrent licenses of CS6 which includes Acrobat. We also have 10 concurrent licenses of Acrobat. How do we control those separately?
Answer: Acrobat is part of many products – such as the CS6 suites, as well as Acrobat Pro standalone. You can define one policy for a suite such as Master Collection, and another policy for standalone Acrobat Pro. You can specify priority for using these policies, and can also apply a scope to one or both policies.
Question: How can you differentiate the variant versus "all", when keying apps?
Answer: Keyed applications are always treated distinctly for each exact version. Unkeyed applications can have a variant mask set - e.g. "all" or "5.x" or "2.3.x".
Question: Do we need K2 v7 to manage Adobe CS6 products or will it work with K2 v6?
Answer: K2 v6 can manage Adobe CS6. On Mac, KeyAccess 184.108.40.206 is required in order to Observe or Manage SpeedGrade CS6. KeyAccess 220.127.116.11 (both platforms) also gets some Serial Numbers which older KeyAccess was missing.
Question: Is there web-based access to K2 for other authorized administrators of K2 within an organization?
Answer: We have a web interface, KeyReporter, which can be used to run and view reports. It cannot be used for configuration such as defining products or configuring policies.
Question: Can v7 be virtualized? Hyper-V running W2k8R2?
Answer: Yes. KeyServer can run in a VM, and we have many customers doing so. KeyAccess is compatible with all common types of virtualization. See Virtual Computing.
Question: With K2 v7.0, how easy is it now to show real-time computer availability in a web page (eg., Lab1 has 20 available computers for use)?
Answer: KeyReporter has a built in report for showing availability. You can also use ksODBC to write your own report that queries KeyServer directly.
Question: When adding a new or upgrade purchase, is there a place to store the Serial Number(s) along with other purchase information?
Answer: Yes, Serial Numbers can be recorded in the purchase. In addition, documents can be uploaded and stored by KeyServer in association with the purchase- they can then be accessed directly through KeyConfigure.
Question: Where can I find sample filters for the various windows in KeyConfigure?
Answer: There is a file named Sample Filters.xml in Admin/Misc. Drag it onto a running KeyConfigure, or into the filters section of a specific window.