ITIL v3 Service Management Lifecycle

June 9th, 2012 | Posted by admin in White Papers - (Comments Off on ITIL v3 Service Management Lifecycle)
Service Process Lifecycle

LiveTime Service Manager provides service organizations all they need to adopt a lifecycle approach to service management, irrespective of their current level of service maturity, available resources and capability. Such capacity guarantees organizations control over their ITIL adoption process, whether they choose to use internally trained staff or outsource to industry specialists for their ITIL implementation.


At the end of October in 2007, ITIL version 3 was released and the understanding of IT service management best practices was transformed to encompass a lifecycle approach to service. Processes are grouped into different segments based on their lifecycle. Many of these overlap into many segements of the framework as illustrated below.

ITIL v3 Processes

A ‘service’ is defined as delivering value to customers by facilitating outcomes customers want to achieve without ownership of specific costs and risks. The ITIL Service Lifecycle caters to the concept that services continually adapt and evolve with the changing needs of business. Through this evolution the service builds value through interaction, evolution, dependencies and relationships to provide positive results. The stages of evolution covered by ITIL are Strategy, Design, Transition, Operation and Continual Service Improvement.


ITIL service strategySuccessful service providers have a clear understanding of their customer’s business objectives and the role IT plays to ensure their customer’s success. They predict the customer’s needs by preparing, analyzing and examining customer activity and usage patterns.

LiveTime Service Manager provides service organizations with this capacity as the system includes Service Portfolio Management at its core. Although it may not be relevant to all organizations when they first start working with the system, in their own time, organizations can build their service strategy and record all proposed services along with forecasted costings in LiveTime. These services can be transitioned through the configured service lifecycle that begins with an idea or proposal, through approvals, design & implementation, into operation and subsequently through maintenance cycles until it is decommissioned.

Applying Service Categories that include business related attributes, such as business processes supported, business owners and users, and making these accessible to customers with a description of the services in a language they understand, ensures IT is evolving from supporting the business to a point of enabling business activities, and in some cases, even driving the business.

With the cost of providing a service often a deciding factor when developing services for the business, LiveTime includes the capability to track and report on service offerings and component usage, service level performance and costs as part of the fully integrated Financial Management.

Recording financial attributes against services, including the service cost, charges and revenue, allows service providers to calculate the expenses they incur for offering services and charge internal or external consumers appropriately.


ITIL service designMoving from the prediction and planning stages, successful service providers apply service management practices systematically, which ensures the services they offer are responsive, consistent and measurable.

Approved services that are transitioned into an operational state within the Service Portfolio, are made available to customers within LiveTime’s Service Catalog. Considered a filter view of the Service Portfolio, the active or ‘Live’ services offered by the service provider can be accessed by customers within LiveTime’s Customer Portal.

Within the Portal, customers can log Service Requests, Incidents or Change Requests against services, as defined relevant by the service provider. It should be noted that if the Service Portfolio, Service Catalog and Financial Management functionality is never enabled, service providers can still record requests against items and services owned or accessed by their customer base.

Responsive service is managed with all requests being associated with Service Level Agreements (SLAs), which is applied Service Level Management. Service providers can use LiveTime’s fully configurable SLAs supported by Operations Level Agreements (OLAs) and Underpinning Contracts (UCs) to ensure the quality of service delivered to their customers. Applying SLA-compliance reporting, Managers can define and track service availability and performance objectives that reflect business requirements and improved customer satisfaction.


ITIL service transitionProviding stable and predictable services that allow businesses to view IT as a utility is also crucial to a service provider’s success. This is achieved by using LiveTime to map the designed services to the IT infrastructure that provisions the services. LiveTime’s embedded CMDB encompasses the Service Portfolio and Service Catalog, allowing service organizations to construct a complete model of the IT infrastructure. This model can be leveraged to identify, control, maintain and verify the Configuration Items (CIs) that underpin the services.

The CMDB is built on CI Type templates that include user-defined attributes and a lifecycle editor that is applied to reflect the State of the CI. It is this State that is also used to define a service as being proposed, operational, decommissioned or any stage in between.

CI details can be automatically populated from multiple third party asset discovery and management tools and updated based on a regular schedule. This ensures the stability of services as information relating to all support infrastructure is maintained, while enhancing the efficiency and effectiveness of service desk staff when they are working on requests.

In all ITIL aligned service management implementations, getting the CMDB right is the biggest challenge. With LiveTime, service providers can set a simple list of services as CIs to provide immediate improvement for the creation and management of requests. Then as a background task, the service portfolio and service catalog can be built with all supporting infrastructure, bringing the services online when they are ready. By using the system whilst building the CMDB, service providers can take advantage of the single repository that shows customer activity and usage patterns. This is a valuable resource when fine-tuning the construction of the CMDB and the overall service strategy.

By building the Categories, Types and Classifications for all CIs in the CMDB, the foundations of the Knowledge Management system are also being implemented. All future solutions, known errors and back-out procedures, will use the CMDB model to store knowledge base articles for easy access when working across Service Requests, Incidents, Problems and Change Requests.

Change Management, with its default extension of Release and Deployment, allows service providers to mirror their change and authorization procedures into LiveTime. This ensures all changes in the environment are reflected in the CMDB and they are controlled and managed in accordance with the documented procedure. The tight integration with the CMDB means that third party tools that detect changes in the environment, initiate the creation of a request for change (RFC), when LiveTime synchs with the external systems.

Full visibility of current and planned outages also works to reassure customers about the availability and reliability of the services.


ITIL service operationServicing customers in line with their expectations and proactively identifying issues are key elements in a responsive and consistent service environment. Using LiveTime’s fully configurable workflows across Service Request, Incident and Problem management, ensures service providers handle all service issues with consistency and within service requirements levels.

Ready access to solutions and workarounds stored in the Knowledge Base during the request creation process minimizes the mean time to repair (MTTR) for incidents, and the proactive analysis of incidents automates the problem identification process to maintain the stability of services.

Tight integration and full visibility between all processes mean that a single click within a Service Request, Incident, Problem or Change can result in the creation of a related request within a different process. This new request will include the appropriate team, SLA and workflow assignment based on the CMDB configuration, and have the ability to update notes, time worked and status changes across the processes. LiveTime provides efficiency and effectiveness gains as all service desk staff have access to all the relevant information when working on a request and providing customer updates.

Service providers wanting to provide immediate value to their business customers when implementing LiveTime, can first roll out Incident Management or Request Fulfillment as they refine other parts of their service management strategy. Capitalizing on the embedded integration with authentication servers, email server and default system workflows, organizations immediately have a single point of access for handling all requests. They can use also use the newly captured data to audit their processes, classifications and customer requirements for future planning and implementing service management improvements.

Continual Service Improvement

ITIL continual improvementSuccessful service providers continuously analyze and refine their service offerings to perpetuate stability and reliability, while retaining adaptive and responsive services allowing the customers to concentrate on their business.

Managers across all service management processes are provided access to LiveTime’s inbuilt reports, allowing them to monitor the performance of all service offerings against the business requirements and agreed expectations.

The tight integration and visibility between all service management processes also provides Managers with ready access to information regarding the provisioned services, requests logged and committed agreements to identify weaknesses. The capability to automatically schedule review dates in LiveTime for service level agreements, knowledge base articles and change requests all combine to result in a professional, responsive and value driven service management environment.

What is a Service Desk?

June 9th, 2012 | Posted by admin in White Papers - (Comments Off on What is a Service Desk?)
ITIL Process Dependencies

What is an ITIL Service Desk

An ITIL Service Desk uses a standard set of best practices for lowering costs and improving the quality of IT service delivery. The aim of a Service Desk is to act as the operational interface between the IT organization and its customers, for achieving an organization’s goals.

Whereas a Help Desk consists of a single, or very few processes with no underpinning CMDB or Asset Management facilities, an ITIL Service Desk usually involves a number of processes that are highly integrated and work together seamlessly. This includes service request, incident, problem, change, release, deployment, knowledge and service level management processes. A Help Desk provides simple ticketing at the low end, through complete incident management at the high end, such as LiveTime Help Desk. This provides essential front line features for managing customer issues and providing communication and status updates. Many also provide limited workflows and basic service level agreements.

ITIL Process Dependencies

A Service Desk is End to End

In contrast, an ITIL Service Desk is concerned not only with taking and responding to calls, but managing the entire lifecycle of the request as it evolves through other relevant processes. For instance, a call may originate as a simple incident which may then evolve into a problem which is also related to several other incidents.

This problem may subsequently require a physical change in the environment to resolve, at which point it will trigger a change request and perhaps management approval against a specific workflow. This change request will then need to be assessed and actioned and eventually get rolled into a release which requires testing and deployment.

A Service Desk provides Visibility

At each stage of its evolution any Team member has complete process visibility whereby they can see the underlying request hierarchy. Throughout the entire process information with the knowledge base is scanned, together with the properties and attributes of the Configuration Item (CI). This simple example demonstrates how different business units or groups can be involved in the process and how they can work together very easily, ultimately improving the efficiency of the entire process, rather than using a single isolated Incident Management process.

In addition, a service desk, or service management product will control each process within a service level agreement, which may also include Operation Level Agreements (OLA’s) and/or Underpinning Contracts (UPC’s). A Help Desk will normally provide simple timers and often call these service agreements.

An ITIL Service Desk is for the Business

So while the Help Desk provides basic features to assist an organization in providing customer service and support, the ITIL Service Desk tightly integrates many other processes such as incident, problem, change and release management (in addition to other core processes such as knowledge management) within the workflow. Together, these processes, when married to service contracts and knowledge management ensure customer requests are managed through the entire lifecycle within the business.

A Service Desk is NOT Ticketing

There are many ways of managing tickets, ranging from excel spreadsheets or shared email accounts, through to simplified web consoles. They rarely provide more than a technique for collecting information in an organized manner.

A good Help Desk solution will allow an organization to perform these functions but also provide an evolutionary pathway to best practice service management.

Implementing ITIL Service Management with LiveTime

June 8th, 2012 | Posted by admin in White Papers - (Comments Off on Implementing ITIL Service Management with LiveTime)
fluid livetime icon


Adopting ITIL to design an organization’s support infrastructure is a critical undertaking. It should be managed as a formal business project with clear ownership, defined business goals, responsibilities, deliverables and management commitment.

Before designing the new Service Desk, all existing service workflows should be assessed and potential for improvement identified. It is an opportunity for business analysts to rethink and redesign existing processes and activities, in order to increase productivity, add value, and reduce costs. As the shop front for organizations, the service desk is an opportunity to enhance the customer’s perception of the organization.


LiveTime Service Manager is a comprehensive ITIL Service support solution that incorporates 11 ITIL v3 processes, the core of which are Incident, Configuration, Problem and Change management.

LiveTime’s recommended two-stage approach includes:

  • Phase I: Implement Configuration, Service Level and Incident Management
  • Phase II: Progress to Problem and Change Management.

Following is a summary of the steps that organizations are guided through when implementing LiveTime Service Manager as either a phased or all-in-one installation.


Adopting ITIL best practices will require a culture change for the organization, in addition to the changes to the service desk process itself. This will require:

  • Educating staff about the benefits of ITIL, and winning champions to the cause
  • Train service desk staff about working with the relevant process
  • Maintain & support process improvements by completing self-audits.


Setup & Install

  • Hardware, O/S, RDBMS, Application Server, Web Server, LiveTime Service Manager application

Migration of Service Desk data (Optional)

  • Perform data mapping between existing & new system
  • Perform data migration
  • Validate migration


  • Asset Discovery
  • Authentication (ADS/LDAP/SSO)
  • Mail
  • Web Services

Process: Phase I

[colored_box variation=”blue” title=”Incident Management”]
Incident Management can be fully configured and automated to reflect the preferred workflow of your organization.

  • Review current process
  • Define objectives
  • Create Incident Management workflow
  • Create incident support teams and assign members to relevant escalation layer
  • Plan review of process using employee feedback and relevant reporting metrics.


[colored_box variation=”green” title=”Service Level Management”]
Service Level Management in LiveTime improves internal and external communication for Service Desk users and assists in the timely management of the support requests. Service Level Agreements (SLA) within LiveTime Service Manager can be underpinned by Operational Level Agreements (OLA) to guarantee the internal capacity meets customer service expectations.

  • Review IT services offered to the organization
  • Establish teams for areas of specialty with relevant escalation layers
  • Create a list of services offered by each team and associate with the service catalog
  • Establish SLAs relative to the business unit requirements and support by appropriate OLAs
  • Define metrics for measuring efficiency and effectiveness of process
  • Implement a review/audit program to ensure service levels meet the organizational needs.


[colored_box variation=”slategrey” title=”Configuration Management”]
Configuration Management is only effective if the data associated with the core IT operational processes is stored and managed appropriately. To guarantee the validity and accuracy of the CMDB:

  • Assign owner(s) to the Configuration Management process
  • Assign accountability for operational repository – setup, ongoing maintenance and support of the CMDB
  • Synchronize with 3rd party asset management and discovery tools (optional)
  • Create baselines for CIs
  • Plan audit and validation of CMDB data.


Process: Phase II

After the initial phase has settled, the following processes are rolled out:

[colored_box variation=”red” title=”Problem Management”]
Problem Management is tightly integrated with Incident and Change Management in LiveTime Service Manager. This allows problems and changes to be manually created from incidents. Further, parameters can be customized in the application to allow for automatic detection and escalation of incidents to problem management.

  • Review current process and set objectives
  • Define workflow
  • Define team and assign staff to relevant escalation layers
  • Define parameters that are to be included in LiveTime, which will allow for auto-detection of problems
  • Define metrics for measuring the efficiency and effectiveness of the process
  • Plan review and audit of process.


[colored_box variation=”orange” title=”Change Management”]
Change Management typically includes defining multiple workflows relevant to the types of changes that are handled by the service desk. To implement Change Management using LiveTime Service Manager, an audit of the current processes needs to be completed so all change workflows can be defined within the application.

  • Define Change Management workflows – identify the types of changes to be handled and how priority is assigned to the change request
  • Allocate the roles and responsibilities of the IT support staff within the workflows
  • Define measurements that will be used to track the efficiency of change implementation
  • Monitor/review process by evaluating and reporting on implemented changes.


Release Notes 7.0

May 30th, 2012 | Posted by admin in Release Notes - (Comments Off on Release Notes 7.0)

LiveTime 7.0

May 30, 2012

LiveTime 7.0 is the next major release of LiveTime’s Service Management platform. The focus of this release was on reporting and usability. LiveTime 7.0 includes a completely new Dashboard with drag and drop capabilities and the ability to select from over 140 predefined widgets. In addition, this new dashboard can be set as your home page so you have all the information available at your fingertips.

In addition, LiveTime 7.0 has significantly expanded the customer report writer, allowing users to build virtually any report they desire. Users may also schedule these for delivery using the new report scheduling facility.

LiveTime 7.0 also includes hundreds of refinements and significant new features such as Multi-source LDAP/AD, New relationship impact map analysis with active lifecycle states, Line Manager Approvals, Calendaring (with synchronization to Outlook, iCal or Google Calendar) and Knowledge import.

LiveTime has also been able to squeeze out even more performance in version 7.0 with some tasks operating more than 400% faster. We all hope you have as much fun using it as much as we have in developing it.


In order to upgrade to LiveTime v7, a new license key will need to be issued. Customers with an existing support contract can contact our support team to have a new key generated.

Federated Directory Server Support

This feature of LiveTime 7 is only available in the Service Manager Application. Users of LiveTime Helpdesk requiring this functionality will need to upgrade to LiveTime Service Manager.

Users of the old ‘multi-directory’ implementation of this functionality, accessed through a single point of contact between LiveTime in the Directory Server environment will need to re-assess their LiveTime configuration in a test environment before upgrading any production systems as there may be configuration changes necessary which should be tested prior to rolling out into the live environment.

Important notes for web services users using a directory server for authentication

Due to the federated directory server support in LiveTime v7, the authentication method requires the directory server id to be passed in conjunction with the user credentials. This can be retrieved using the ‘getLdapSources’ method on the ‘Authenticate’ web service. See the ‘Extend’ section of the LiveTime web site for further information.

Deprecation Notice

Please note that with the addition of LiveTime’s built-in report writer in version 6.5 we have deprecated the Pentaho Report Writer. This will be removed in a subsequent version. We suggest that any custom reports you have designed are now migrated to LiveTime’s report writer.

LiveTime has removed support for IE 6 as of 6.5 and requires Java 6 for the runtime environment. Future versions will require a minimum of IE 8. All other browser support remains the same.

Web Services Notice

Please note that LiveTime has changed the name of 3 web service calls in this release to remove method overload contention on languages such as PHP. The following methods have been renamed:

Create Incident Methods (for a Customer) have changed as follows:

createIncident -> createIncidentCustomer
createChangeRequest -> createChangeRequestCustomer
createServiceRequest -> createServiceRequestCustomer

All users of web services should begin migrating their legacy applications to the new interfaces (underscore prefix) in preparation of the old interfaces being overhauled in a future release.

Important localization notes

The upgrade to version 7.0 of LiveTime will use the locale of the user running the upgrade for processing various localization routines. It is vitally important that the operating system of the user performing the upgrade match that of the default messages stored within the previous version of LiveTime.

Upgrade procedure

Upgrades to v7 are supported from Versions 5.5.x+. Supported users of earlier versions will need to contact support to arrange an intermediate upgrade (to v6.0) prior to upgrading to v7.0.

For existing users of LiveTime v5.5.x or 6.x.x, a database upgrade will be required. Please follow these steps:

  1. Stop LiveTime
  2. Backup the current database, LiveTime.war and application banners (to reload after upgrade)
  3. Install the new version of LiveTime
    1. If using the installer:
      1. Run the uninstaller to remove the old version
      2. Run the installer and select the upgrade option
    2. If installing manually using the WAR file:
      1. Stop the servlet container and delete the old deployment folder
      2. Install the new WAR file for LiveTime v6.5
  4. Start LiveTime
  5. At Database Configuration page, enter the database details
  6. Click Test to ensure the database connection is correct
  7. Click Advanced
  8. Click Upgrade, followed by the next Upgrade button
  9. Once the migration is complete click Save
  10. When the upgrade is complete, the login page is displayed.

Oracle RDBMS Users Please Note. When upgrading an Oracle database, a restart of LiveTime is necessary after the database has been migrated and login page displayed.

Important notes for Informix RDBMS Users. If upgrading from LiveTime v5.5.x, you will need to first upgrade to LiveTime v6.0.x, and subsequently upgrade from LiveTime 6.0.x to LiveTime v6.2.x, and then to LiveTime 7.0.

Post Upgrade Activities

After the upgrade the Administrator must:

  1. Re-upload application banners. Go to Setup > Customize tab.
    Due to banners having to be served by the web server rather than the LiveTime Application, these currently aren’t preserved between upgrades.
  2. Review the Authentication Server configuration and update to reflect any federation changes
    The Federated Directory Server Configuration is not compatible with previous Authentication configuration options within LiveTime due to the previous approach of a single entry point being virtually responsible for sub-domains. If multiple domains were being accessed previously, the new configuration requires each of these sub-domains to have their own entry point defined.Every effort has been made to implement something that is approximately compatible to the existing system, but this is unlikely to work in most cases, and it is recommended the Directory Server setup be reconfigured
  3. Review any customized AMIE mapping files
    Due to some changes in the database access facilities in LiveTime, some of the AMIE mapping files will require modification. The default mapping files included will be upgraded to use the new techniques and these should be used as a base to understand any required modifications.
  4. Verify the new options are defined as per the service desk requirements (v6.2 and earlier).The ‘Terminate Active Session’ option located in Setup > Privileges > System, which will allow users to logout sessions they have in-use elsewhere, rather than having to ask an Administrator to log them out.

    The ‘Allow Unknown’ option located in Setup > Privileges > Requests, which if set to ‘No’ will force technicians to assign a real item to requests that are created before allowing them to save changes made to that request.

  5. Review the email template messages and ensure they have been successfully upgraded (v6.2 and earlier).Localization has been extended to cover email messages and as such, all users will receive correspondence templates in the language assigned to their account. This doesn’t translate the message content itself, so if a single language is desired, all accounts should be set to use that language.
  6. Update labels for Priority, Urgency and Impact to reflect the needs of the Service Desk (v6.2 and earlier).Navigate to Setup > Localization > Content, select the primary language and ensure the Priority, Impact and Urgency labels are defined as required.

After the upgrade, Supervisor users should:

  1. Review the configuration of Service Request and Change Teams (v6.2 and earlier).

    LiveTime v6.5 has streamlined the way technicians are assigned to workflow states for these processes. Groups of technicians can now be defined, that are common to particular workflow states and allocated as a group to the states that apply to them. It is no longer possible to assign individuals to a workflow state outside of these structures.

    A Change Management workflow might have (for example) design, build and re-work phases, all of which are assigned to the same people. These people can now be collected into a development group, and this group assigned to these states. As time passes, staff changes become a matter of changing the group as new developers come and go.

  2. Review Partner accounts, and Partner Organizations (v6.2 and earlier).
    Partner Organizations are a new concept in LiveTime v6.5 allowing partners to be grouped together, working for a partner organization. This allows several partners (working for a common partner org) to access to the same data.
  3. Review the knowledge base content and reformat any articles by the change to the rich text editor
    This rather time consuming task is likely to be necessary for organizations formatting articles using whitespace (carriage returns). The new rich text editor formats content into HTML, but to parse this during the upgrade would potentially introduce more problems that would be harder to locate, and make the upgrade take far longer.

Version 7.0

New features and Enhancements

Authentication, User Management and Licensing

  • Directory Server Federation (for user authentication)
  • Directory Server Field mappings can now refer to a Line Manager for Customers
  • Users can now have all correspondence sent to an alias, rather than their primary email address
  • Challenge-style password reset functionality (for non-directory server access) has been added
  • New licenses are required to access v7

User Portal Interface Enhancements

  • The dashboard has been rebuilt and uses dynamic (Web 2.0) components
  • Dashboard widgets have been created for request streams which refresh every minute
  • The events calendar has been rebuilt and supports integration with calendar applications
  • Workflow Maps have been further refined to aid readability and tooltips have been added
  • Item Relationship Maps have been rebuilt to allow easier navigation of the item relationships

Customer Portal Interface Enhancements

  • The ‘Home’ page of the Customer portal has a new request list to aid readability
  • A ‘Related Requests’ box is available to customers when viewing a request
  • The welcome message is now templated in the admin (localization) setup

Requests (Service Requests/Incidents/Problems/Change Requests/Deployments)

  • Service Request and Change Requests now allow Customer or Line Manager approval states
  • Visual Cue added to the left edge of the editor to help identify the process being worked in
  • Item Relationship Map for CI shadow management is now accessible from the main editor
  • Scheduled Quick Calls can now be targeted at specific customers if necessary
  • Quick Calls can now be shared by team, restricting visibility to those requiring access
  • Quick Calls can now be triggered to be created directly into an approval state
  • New option to assign queued requests to the closing technician has been added
  • Searching ‘List’ style custom fields now allows multiple selection of values
  • Workflow visual includes Tooltips to aid identification of state transitions
  • Incidents can now be converted to Service Requests (and vice-versa)
  • Problem Teams now support queueing of problem records
  • Problems no longer have customer notification options

Configuration Management

  • Outages can now be created to affect multiple of CI’s and trigger item status changes
  • Outage notifications have been improved to be more inline with request notifications
  • FSC dates will be applied to requests allocated to Outage windows
  • CI Attachments can now be toggled to have public or private visibility
  • ZENWorks Desktop Management is no longer supported by AMIE
  • AMIE mapping file included to support Spiceworks v5
  • Item Types can now be duplicated

Knowledge Management

  • Knowledge base content can now be imported via CSV
  • Forums module now makes use of the Rich Text Editor
  • Customer Survey ‘scale’ is now user configurable (using the 1 to X response option)
  • Article Filter selection will now be preserved between sessions (like all others)

Service Level Management

  • It is now possible to queue support contracts up for customers, organisations and items
  • Management of support contracts has been reviewed and refined
  • SLA Reports have again been reviewed and refined


  • Scheduled reports are now completely customizable and can include many system reports
  • Custom reports built using the report writer can also be included in the scheduled report
  • Custom scheduled reports are defined ‘by role’ and adhere to process based permissions
  • KPI reports now allow a date range of up to 3 months (up from the previous 30 days)
  • KPI request distribution chart now treats an hour as the half hour either side of that hour
  • Report Builder supports many more entities, and many more fields on existing entities
  • Report Builder now allows aliases for selected fields to aid report presentation
  • Excel and PDF outputs of lists will retain the user sort in the user interface

Email & SMS Processing

  • Partner banners will now be used in partner account email messages
  • Request allocation refined when using a single email inbox
  • Out of office email markers are now user configurable


  • CSV Imports using the LiveTime template will attempt to auto-match the fields using the headers
  • Many performance enhancements have been implemented at the data access layer to speed up the UI

ZENWorks Integration

  • A ‘reset’ button has been added to the ZENWorks configuration to reset the certificate
  • The remote control client will now display version information if the client is incompatible

Other Notable Customer Requests addressed in this release:

Many of the new features were inspired by customer requests relating to existing features. In addition to those customer requests addressed by the changes above, the following were also incorporated into this version:

(CR 1013913)

Ability to switch off geo-location of customers who have no other access to the system

(CR 1013995)

Ability to assign a partner org to customers imported via CSV

(CR 1015474)

Technician emails relating to queued requests should use the system default language instead of defaulting to english

(CR 1015584)

New Timezone added to allow for timezone uniqueness in Mexico City