| |||
|
| |||
Overview
Downloads and extras
Support
Training
Frequently Asked Questions
General
- What is Quark Licence Administrator?
Quark Licence Administrator (QLA) is a server-based, licence management system developed by Quark. When you purchase five or more licences of a
Quark application, QLA, which is included with the application, simplifies the installation and maintenance of the application on multiple computers.
- How does the Quark Licence Administrator server work?
The Quark Licence Administrator server monitors the network for licence requests for copies of Quark software. When it receives a licence request, the
server checks to see if the user or computer is a member of a specific licence pool. If there are licences available in the user's or computer's licence
pool, then a licence is checked out and the application launch proceeds. If no licences are available, the server will not allow the Quark product to launch.
- What are licence pools?
Licence pools are used by Quark Licence Administrator (QLA) to categorise and allocate Quark software licences. You can assign three different types of
QLA licences: runcount pool, node-lock list, or node-lock pool.
By default, the runcount pool is the total number of Quark application licences you purchased. As you assign licences to other lists or pools, they are
removed from the runcount pool. Licences from the runcount pool are granted on a first-come, first-served basis to users or computers that are not assigned
to node-lock lists or node-lock pools.
A runcount pool can be effective for many sites, but some configurations require more control. The node-lock pool and node-lock list options provide a more
precise level of management.
Individual users or computers are assigned to a node-lock pool by the system administrator. The number of licences available to the group can be smaller
than the number of pool members. This allows the administrator to prioritise some users without reserving an individual licence for each of them.
The node-lock list is a list of users for whom a Quark software licence is reserved. A Quark software licence can also be reserved for a specific
computer. When the administrator allocates licences to a node-lock pool, those licences are always reserved for pool members and are unavailable for
the rest of the users on your network. A member of the node-lock list will always be granted a licence even if the general runcount licences and
node-lock pool licences are all checked out.
Some Quark customers may want to designate an auxiliary pool so that they can purchase auxiliary licences on an as-needed basis. If you need more
licences than you purchased and you do not have time to wait before ordering more, you may be able to use auxiliary licences to increase your
runcount pool. Auxiliary licences are temporary; they are active only for a period determined by Quark. Not all customers qualify for an auxiliary pool.
- When would I use an extended licence?
Use an extended licence when a licence is needed for a specified period without being connected to the Quark Licence Administrator (QLA) Server.
Extended licences are for users who need to use a Quark application on a computer that must be removed from the network for a while. For example,
a user can check out a licence on a laptop and then remove the laptop from the network for use in a remote location.
When users check out an extended licence, they specify how long they will use the licence remotely — within parameters the administrator has specified.
At the end of the specified time period, the licence no longer launches on the remote computer. The extended licence is unavailable to other users until
it has been checked back in.
Extended licences are also for users who do not want to connect to the QLA Server each time they launch their Quark applications. For example, a one-month
check-out interval can be specified, and users can launch the application for a month without connecting to the QLA Server.
- My network does not have a connection to the Internet; can I still use Quark Licence Administrator?
You can use Quark Licence Administrator (QLA) without an Internet connection. When you order a Quark application, tell your customer service representative
that you are not connected to the Internet. Your representative will request information about the computer on which you will install QLA. The
representative will mail the licence file with your software order.
- Can Quark Licence Administrator monitor the use of Quark application licences on Mac OS® and Windows®?
Yes, one Quark Licence Administrator licence file can monitor the use of licences on both Mac OS and Windows clients.
- Can Quark Licence Administrator control the entire licence runcount of my company even though the company has multiple locations?
Quark Licence Administrator (QLA) can support multiple locations. However, we recommend that you install a QLA Server at each site. Then if a server
stops responding, it will not interrupt the use of Quark applications at all of your locations.
- Can Quark Licence Administrator manage QuarkXPress® XTensions® licences?
Yes. Quark Licence Administrator (QLA) Server monitors third-party XTensions software licences associated with QuarkXPress and provides efficient
and one-point management of all your XTensions software licences.
QLA Server manages XTensions module licences associated with QuarkXPress only. This functionality does not extend to licences for QuarkCopyDesk®.
- What should I do if I change address information or the network card on the Quark Licence Administrator Server computer?
The Quark Licence Administrator (QLA) licence file is locked to the DNS name or IP address and the Ethernet card address for the computer on which
it is installed. If you change the server name or the network card, you must download a new licence file from the Quark Web site. There is no charge
to download a new licence file.
- What happens if my server stops responding?
In the event of server failure, any Quark software licences that are launched will continue to function without interruption. However, users will not be
able to launch additional licences until the server is restored.
- How can I avoid losing access to my application if the network or server fails while I'm working on a critical project?
If you have computers that are critical to a project, consider checking out extended or remote licences for those computers. Extended licences permit
the application to launch without the server. Critical users or computers will be able to work regardless of what happens to the server.
- Can I back up my licence file and restore it on a different computer if my server crashes?
The licence file is locked to the Ethernet hardware address of the computer on which it is installed. If the Quark Licence Administrator (QLA) Server
crashes and cannot be restored, install the QLA Server on a new computer and then download a new licence file.
- What should I do if my server fails?
In the event of a Quark Licence Administrator (QLA) Server failure, you can reinstall QLA and download a licence file from Quark. Quark applications
will not be affected providing that the new server is given the same IP address as the old server, and the QLA Server is set to receive check-out requests
on the same port number. For additional information regarding server failure, see QLA Server
Recovery.
- What should I do if my entire network fails?
In the event that you experience a complete network failure, you can:
- Use the Emergency Key Launch* feature to temporarily launch copies of
Quark applications on client computers for up to 120 hours.
- Have the administrator generate a remote licence file and send it in an e-mail message to users who do not have access to the Quark Licence
Administrator (QLA) Server.
* Users must have launched the Quark application through the QLA Server at least once in order to take advantage of the Emergency
Key Launch feature.
- What can I do if Quark's server is unavailable when I need to download a new licence file?
In the unlikely event that you cannot access the Quark server to download a new licence file, you can use the emergency licence file. When you download
the licence file, Quark sends an e-mail message to you with a file named 'QLALicenseBak.dat.' This file is a temporary emergency licence file that you
can use if you cannot immediately download a new licence file. The emergency licence file supports licence check-out for up to 72 hours.
- How do I install the emergency licence file?
You can install the emergency licence file on any computer where you have installed the Quark Licence Administrator (QLA) Server. To install the
emergency licence file, install the QLA Server software making sure to enter the same IP address and port number that you registered with Quark.
Do not check Register and Download a Licence File during this installation. After the installation is complete, drag-copy the
emergency licence file into the QLA application folder on the server. As long as you have entered the same IP address and port number that you registered
with Quark, no Quark applications will be affected.
- If an extended licence is checked out on a computer that stops working, how can I get that licence back?
You must wait until that extended licence expires; it will then be available for check-out by the Quark Licence Administrator Server.
- Does Quark® Licence Administrator support Intel® Core? Duo Macintosh® computers?
Yes. Quark Licence Administrator (QLA) Server and Control Panel Client can be run on both PowerPC and Intel-based Macintosh computers.
- Does Quark Licence Administrator support FireWire?
Yes. Quark Licence Administrator (QLA) supports FireWire® networks. While downloading a licence file for the QLA Server, you can specify the address
of your FireWire Ethernet card and of the default Ethernet card.
- Can I set priority levels for error and event logging?
Quark Licence Administrator (QLA) 4 introduces five levels of error and event logging. You can set different levels for different errors and events,
according to their significance to your workflow, in QLA Control Panel.
Emergency key launch
- What is an Emergency Key Launch?
If your Quark Licence Administrator (QLA) primary and backup servers are both unavailable, or if your entire network becomes disabled, you can use
the Emergency Key Launch (EKL) capability to temporarily launch Quark application licences on client computers. This capability provides time to get
the network or server running again.
The EKL capability is enabled only after a Quark application successfully connects to the QLA server at least once after QLA installation.
- How long can an application run using Emergency Key Launch?
Emergency key launch (EKL) can run a Quark application without servers for up to 120 hours. If the Quark application is not connected to a QLA Server
after 120 hours of EKL use, the application will not launch. After the Quark application has reconnected to the QLA server, EKL 'recharges' itself,
and you again have the ability to use EKL to operate the application for a maximum of 120 hours.
- What do the terms 'minimum remaining duration limit' and 'maximum charge' mean?
When Emergency Key Launch (EKL) is in use, 'minimum remaining duration limit' indicates the time left before the application connects to the QLA server
to re-charge EKL. 'Maximum charge' is the amount of time EKL will operate before needing to connect to the QLA server to recharge.
- Is it possible to change the parameters 'minimum recharge limit' and 'maximum charge'?
No. It is not possible to change these parameters.
- When I launch my application, does it use Emergency Key Launch or the Quark Licence Administrator Server?
The application uses the Quark Licence Administrator (QLA) Server if it is available. If the QLA Server is not available, the application automatically
uses Emergency Key Launch.
- Does the Quark Licence Administrator Server keep a record of Emergency Key Launches?
No. The Quark Licence Administrator (QLA) Server logs recharge requests but does not keep a specific record of Emergency Key Launches.
- Do I need to do anything to Emergency Key Launch when I install the application?
No. When you launch the application the first time and the Quark Licence Administrator Server is running, it will activate Emergency Key Launch.
- Is Emergency Key Launch a failover mechanism for Quark Licence Administrator?
Yes. Emergency Key Launch is a failover mechanism for Quark Licence Administrator.
- Are there alternatives to Emergency Key Launch as a failover mechanism?
Yes. Quark Licence Administrator (QLA) also has failover server functionality. If you have two QLA servers and one of them fails, the other server
will take over. If both servers fail, then Emergency Key Launch will take over
- Can the Emergency Key Launch file be copied to another computer and used to access an application?
The Emergency Key Launch file cannot be copied and used on another computer because it is locked to the original computer's address.
- How has Emergency Key Launch functionality improved?
You can now use Emergency Key Launch as often as you need to as long as you periodically reconnect to the Quark Licence Administrator
Server to recharge.
Overview
Downloads and extras
Support
Training
Frequently Asked Questions
General
- What is Quark Licence Administrator?
Quark Licence Administrator (QLA) is a server-based, licence management system developed by Quark. When you purchase five or more licences of a Quark application, QLA, which is included with the application, simplifies the installation and maintenance of the application on multiple computers. - How does the Quark Licence Administrator server work?
The Quark Licence Administrator server monitors the network for licence requests for copies of Quark software. When it receives a licence request, the server checks to see if the user or computer is a member of a specific licence pool. If there are licences available in the user's or computer's licence pool, then a licence is checked out and the application launch proceeds. If no licences are available, the server will not allow the Quark product to launch. - What are licence pools?
Licence pools are used by Quark Licence Administrator (QLA) to categorise and allocate Quark software licences. You can assign three different types of QLA licences: runcount pool, node-lock list, or node-lock pool.
By default, the runcount pool is the total number of Quark application licences you purchased. As you assign licences to other lists or pools, they are removed from the runcount pool. Licences from the runcount pool are granted on a first-come, first-served basis to users or computers that are not assigned to node-lock lists or node-lock pools.
A runcount pool can be effective for many sites, but some configurations require more control. The node-lock pool and node-lock list options provide a more precise level of management.
Individual users or computers are assigned to a node-lock pool by the system administrator. The number of licences available to the group can be smaller than the number of pool members. This allows the administrator to prioritise some users without reserving an individual licence for each of them.
The node-lock list is a list of users for whom a Quark software licence is reserved. A Quark software licence can also be reserved for a specific computer. When the administrator allocates licences to a node-lock pool, those licences are always reserved for pool members and are unavailable for the rest of the users on your network. A member of the node-lock list will always be granted a licence even if the general runcount licences and node-lock pool licences are all checked out.
Some Quark customers may want to designate an auxiliary pool so that they can purchase auxiliary licences on an as-needed basis. If you need more licences than you purchased and you do not have time to wait before ordering more, you may be able to use auxiliary licences to increase your runcount pool. Auxiliary licences are temporary; they are active only for a period determined by Quark. Not all customers qualify for an auxiliary pool. - When would I use an extended licence?
Use an extended licence when a licence is needed for a specified period without being connected to the Quark Licence Administrator (QLA) Server. Extended licences are for users who need to use a Quark application on a computer that must be removed from the network for a while. For example, a user can check out a licence on a laptop and then remove the laptop from the network for use in a remote location.
When users check out an extended licence, they specify how long they will use the licence remotely — within parameters the administrator has specified. At the end of the specified time period, the licence no longer launches on the remote computer. The extended licence is unavailable to other users until it has been checked back in.
Extended licences are also for users who do not want to connect to the QLA Server each time they launch their Quark applications. For example, a one-month check-out interval can be specified, and users can launch the application for a month without connecting to the QLA Server. - My network does not have a connection to the Internet; can I still use Quark Licence Administrator?
You can use Quark Licence Administrator (QLA) without an Internet connection. When you order a Quark application, tell your customer service representative that you are not connected to the Internet. Your representative will request information about the computer on which you will install QLA. The representative will mail the licence file with your software order. - Can Quark Licence Administrator monitor the use of Quark application licences on Mac OS® and Windows®?
Yes, one Quark Licence Administrator licence file can monitor the use of licences on both Mac OS and Windows clients. - Can Quark Licence Administrator control the entire licence runcount of my company even though the company has multiple locations?
Quark Licence Administrator (QLA) can support multiple locations. However, we recommend that you install a QLA Server at each site. Then if a server stops responding, it will not interrupt the use of Quark applications at all of your locations. - Can Quark Licence Administrator manage QuarkXPress® XTensions® licences?
Yes. Quark Licence Administrator (QLA) Server monitors third-party XTensions software licences associated with QuarkXPress and provides efficient and one-point management of all your XTensions software licences.
QLA Server manages XTensions module licences associated with QuarkXPress only. This functionality does not extend to licences for QuarkCopyDesk®. - What should I do if I change address information or the network card on the Quark Licence Administrator Server computer?
The Quark Licence Administrator (QLA) licence file is locked to the DNS name or IP address and the Ethernet card address for the computer on which it is installed. If you change the server name or the network card, you must download a new licence file from the Quark Web site. There is no charge to download a new licence file. - What happens if my server stops responding?
In the event of server failure, any Quark software licences that are launched will continue to function without interruption. However, users will not be able to launch additional licences until the server is restored. - How can I avoid losing access to my application if the network or server fails while I'm working on a critical project?
If you have computers that are critical to a project, consider checking out extended or remote licences for those computers. Extended licences permit the application to launch without the server. Critical users or computers will be able to work regardless of what happens to the server. - Can I back up my licence file and restore it on a different computer if my server crashes?
The licence file is locked to the Ethernet hardware address of the computer on which it is installed. If the Quark Licence Administrator (QLA) Server crashes and cannot be restored, install the QLA Server on a new computer and then download a new licence file. - What should I do if my server fails?
In the event of a Quark Licence Administrator (QLA) Server failure, you can reinstall QLA and download a licence file from Quark. Quark applications will not be affected providing that the new server is given the same IP address as the old server, and the QLA Server is set to receive check-out requests on the same port number. For additional information regarding server failure, see QLA Server Recovery. - What should I do if my entire network fails?
In the event that you experience a complete network failure, you can:- Use the Emergency Key Launch* feature to temporarily launch copies of Quark applications on client computers for up to 120 hours.
- Have the administrator generate a remote licence file and send it in an e-mail message to users who do not have access to the Quark Licence Administrator (QLA) Server.
- What can I do if Quark's server is unavailable when I need to download a new licence file?
In the unlikely event that you cannot access the Quark server to download a new licence file, you can use the emergency licence file. When you download the licence file, Quark sends an e-mail message to you with a file named 'QLALicenseBak.dat.' This file is a temporary emergency licence file that you can use if you cannot immediately download a new licence file. The emergency licence file supports licence check-out for up to 72 hours. - How do I install the emergency licence file?
You can install the emergency licence file on any computer where you have installed the Quark Licence Administrator (QLA) Server. To install the emergency licence file, install the QLA Server software making sure to enter the same IP address and port number that you registered with Quark. Do not check Register and Download a Licence File during this installation. After the installation is complete, drag-copy the emergency licence file into the QLA application folder on the server. As long as you have entered the same IP address and port number that you registered with Quark, no Quark applications will be affected. - If an extended licence is checked out on a computer that stops working, how can I get that licence back?
You must wait until that extended licence expires; it will then be available for check-out by the Quark Licence Administrator Server. - Does Quark® Licence Administrator support Intel® Core? Duo Macintosh® computers?
Yes. Quark Licence Administrator (QLA) Server and Control Panel Client can be run on both PowerPC and Intel-based Macintosh computers. - Does Quark Licence Administrator support FireWire?
Yes. Quark Licence Administrator (QLA) supports FireWire® networks. While downloading a licence file for the QLA Server, you can specify the address of your FireWire Ethernet card and of the default Ethernet card. - Can I set priority levels for error and event logging?
Quark Licence Administrator (QLA) 4 introduces five levels of error and event logging. You can set different levels for different errors and events, according to their significance to your workflow, in QLA Control Panel.
Emergency key launch
- What is an Emergency Key Launch?
If your Quark Licence Administrator (QLA) primary and backup servers are both unavailable, or if your entire network becomes disabled, you can use the Emergency Key Launch (EKL) capability to temporarily launch Quark application licences on client computers. This capability provides time to get the network or server running again.
The EKL capability is enabled only after a Quark application successfully connects to the QLA server at least once after QLA installation. - How long can an application run using Emergency Key Launch?
Emergency key launch (EKL) can run a Quark application without servers for up to 120 hours. If the Quark application is not connected to a QLA Server after 120 hours of EKL use, the application will not launch. After the Quark application has reconnected to the QLA server, EKL 'recharges' itself, and you again have the ability to use EKL to operate the application for a maximum of 120 hours. - What do the terms 'minimum remaining duration limit' and 'maximum charge' mean?
When Emergency Key Launch (EKL) is in use, 'minimum remaining duration limit' indicates the time left before the application connects to the QLA server to re-charge EKL. 'Maximum charge' is the amount of time EKL will operate before needing to connect to the QLA server to recharge. - Is it possible to change the parameters 'minimum recharge limit' and 'maximum charge'?
No. It is not possible to change these parameters. - When I launch my application, does it use Emergency Key Launch or the Quark Licence Administrator Server?
The application uses the Quark Licence Administrator (QLA) Server if it is available. If the QLA Server is not available, the application automatically uses Emergency Key Launch. - Does the Quark Licence Administrator Server keep a record of Emergency Key Launches?
No. The Quark Licence Administrator (QLA) Server logs recharge requests but does not keep a specific record of Emergency Key Launches. - Do I need to do anything to Emergency Key Launch when I install the application?
No. When you launch the application the first time and the Quark Licence Administrator Server is running, it will activate Emergency Key Launch. - Is Emergency Key Launch a failover mechanism for Quark Licence Administrator?
Yes. Emergency Key Launch is a failover mechanism for Quark Licence Administrator. - Are there alternatives to Emergency Key Launch as a failover mechanism?
Yes. Quark Licence Administrator (QLA) also has failover server functionality. If you have two QLA servers and one of them fails, the other server will take over. If both servers fail, then Emergency Key Launch will take over - Can the Emergency Key Launch file be copied to another computer and used to access an application?
The Emergency Key Launch file cannot be copied and used on another computer because it is locked to the original computer's address. - How has Emergency Key Launch functionality improved?
You can now use Emergency Key Launch as often as you need to as long as you periodically reconnect to the Quark Licence Administrator Server to recharge.