Quantcast
Channel: Shavlik User Community : All Content - Ivanti Patch for Windows
Viewing all 2126 articles
Browse latest View live

Manual installation of agent fails on registration.

$
0
0

1604_157_49_cache.png


Symptoms


You attempt to manually install an agent and it fails during the registration process.


  Error found in registration.log

  • 'Error during registration. Error: Error 1300: Not all privileges or groups referenced are assigned to the caller'

  Error found  in the STAgentUI.log

  • 'Error 1314: A required privilege is not held by the client'
  • 'class STWin32::CWin32Exception at X509Certificate.cpp:65: Error 5: Access is denied'

  Error found in the STAgentManagement.log

  • Error: 'class STServiceModel::Wws::CWebServiceException at RegistrationServiceClient.cpp:401: Unable to register the agent with the provided registration key


 

Cause


This error is seen if the user account used to install the agent does not have the correct permissions.

 

Resolution

 

Ensure the SYSTEM account, as well as the user installing the agent has full control over C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder as well as the files in the directory.

 

Add required rights in User Rights Assignments.

 

    Known rights needed to install and register agents.

    • "Act as Operating System"
    • "Take Ownership"

 

1. Open Local Security Settings.
2. In the console tree, click User Rights Assignment.
  - Security Settings/Local Policies/User Rights Assignments
3. In the details pane, double-click the user right you want to change.
4. In UserRight Properties, click Add User or Group.
5. Add the user or group and click OK.

  To open Local Security Policy, click Start, point to Settings, click Control Panel, double-click Administrative Tools, and then double-click Local Security Policy.

You can also check what rights the current user has by running the following command from a Windows Command Prompt.

>whoami /priv

 

Additional Information

 

Settings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on the local computer at the next Group Policy update:

Local policy settings
Site policy settings
Domain policy settings
OU policy settings

  When a local setting is greyed out, it indicates that a GPO currently controls that setting.

 

Affected Products


Shavlik Protect 9.x



java7-60 install file?

$
0
0

Hello,

 

Using agent to install Java7-60.   The agent log appears to attempt to download a file with the name "jre-7u60-windows-i586.exejre-7u60-windows-i586.exe" 

 

Is there a mistake in the XML, or some other place that is giving it the duplicated name string.?   I have deleted and redownloaded jre-7u60-windows-i586.exe and got the same results.  Both have the same MD5 hash.

 

Please advise

Flash 13 to 14

$
0
0

Adobe has released Flash 14.   Shavlik is supporting Flash 14.

 

However, scans detect Flash 13 and then update it to the latest version of 13.

 

Please Shavlik, can you make it so Flash 14 will get updated to Flash 14?

 

Please don't do this:  Flash 10 to Flash 11

Install Error - Your system does not meet the minimum supported operating system and service pack level.

$
0
0

1604_157_49_cache.png

 

Symptoms


Installing Protect fails with error:

 

Your system does not meet the minimum supported operating system and service pack level. The minimum requirements are:

 

- Windows XP x86 SP3

- Windows XP x64 SP2

- Windows Server 2003 SP2

- Windows Vista SP2

- Windows Server 2008 SP2

- Windows 7 SP1

- Windows Server 2008 R2 SP1

 

Windows Server Core installations are not supported.

 

If you are running Windows Server 2012 or later make sure that Server Graphical Shell (Server-Gui-Shell) feature is enabled.

 

Install Fails - Unsupported OS on Supported OS.png

 

Cause

 

  • The operating system being installed on is unsupported.
  • The file is set to run under compatibility mode for an unsupported OS.

 

Resolution


Disable 'Compatibility Mode'

 

Right click the File, and choose Properties.

In the files properties, click the Compatibility tab.

Un-select 'Run this program in compatibility mode for:'

 

compatibility mode.png

Verify that the computer meets the minimum Operating System Requirements.

Version 9.1:

Operating System (one of the following):
Shavlik Protect supports 64-bit versions of the listed operating systems. 32-bit
versions are not supported for the console.
• Windows Server 2012 Family R2, excluding Server Core
• Windows Server 2012 Family, excluding Server Core
• Windows Server 2008 Family R2 SP1 or later, excluding Server Core
• Windows 8.1 or later, excluding Windows RT
• Windows 7 SP1 or later, Professional, Enterprise, or Ultimate Edition

 

Version 9.0:

Operating System (one of the following)
Shavlik Protect supports 32- and 64-bit versions of the listed operating systems for
both console and target systems.
• Windows XP Professional SP3 or later (SP2 or later if using 64-bit version)
• Windows Server 2003 Family SP2 or later
• Windows Vista SP2 or later, Business, Enterprise, or Ultimate Edition

 

This can be verified several ways:

 

Method 1 - Computer Properties

Right click Computer and choose Properties.

 

3-computer properties.png

 

In Properties, view the Windows Edition and Service Pack level..

 

4-properites output.png

Method 2 - WinVer

Run 'winver' to get the version number and compare against Microsoft's OS Version page:
Operating System Version

 

winver.png

 

winver output.png

 

Method 3 - Registry

In the registry editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
The CurrentVersion value will indicate the OS version.
The EditionID will indicate the edition of windows in use.

 

registry.png

 

 

Affected Product(s)

Shavlik Protect All

How To: Manually updating patch data files for Shavlik Protect

$
0
0
Purpose

 

When running the Shavlik Protect or VMware vCenter Protect console in a secure environment without Internet access, it is necessary to download the latest data files on a system that has internet access and then transfer them to the console machine.

 

This article applies only to patch data.

 

Description

 

This article discusses both methods:

 

  • PowerShell (Highly Recommended)
  • Individual file download (All Files Are Required)

PowerShell

To use the PowerShell script:

  • Download and install PowerShell 1.0 from Microsoft, if it is not already installed. For more information, see Microsoft KB article 926140.
  • Shavlik NetChk Protect and VMware vCenter Protect patch files are released twice per week. To download the patch files, you can use a PowerShell script to automate the process or you can download each file individually.
  • If you need a compression utility, download and install the 7-Zip extraction utility from http://www.7-zip.org/download.html.

          Shavlik does not endorse or recommend any particular third_party utility.

 

  • Create an output directory.
  • Download and extract the PowerShell script attached to this article: DownloadProtectData90.zip

 

  This script works for all versions of these products.

 

  • Open a command prompt.
  • Enter PowerShell by typing powershell.
  • Navigate to the location where you extracted the PowerShell script.
  • At the PowerShell command prompt, launch the script with this command:

    .\DownloadProtectData90.ps1 "<outputdirectory>" <major or minor version> "<7-zip directory>"

      The command begins with the characters . before the script name. These characters are required if the script is in the current working directory. If you are in a different directory, enter the full path to the script.

    The major/minor version argument has a two-digit value. Use the value corresponding to your version:

 

  • Protect 9.0: 90
  • Protect 9.1: 91


Example:


The command you run looks like this: .DownloadProtectData90.ps1 "C:\Data" 90 "C\:program Files\7-Zip"

The command has these elements:

    • .\DownloadProtectData.ps1: This is the script itself.
    • c:\Data: This is the folder to which you are downloading the data files.
    • 90: This is the version of vCenter Protect or Shavlik Protect files you are downloading.
  1. Type exit to leave PowerShell.
  2. Navigate to the folder containing the data files and move or copy them to the DataFiles folder on the Shavlik Protect or vCenter Protect server in the DMZ. This is the default location:

      If the files already exist in the output directory, they are overwritten.
    • 8.x on Vista, 2008, & Windows 7: C:ProgramData\Shavlik Technologies\NetChk\DataFiles
    • 8.x on Windows XP or 2003: C:Documents and Settings\All Users\Application Data\Shavlik Technologies\NetChk\DataFiles
    • 9.x on Vista, 2008, & Windows 7: C:\ProgramData\LANDesk\Shavlik Protect\Console\DataFiles
    • 9.x on Windows XP or 2003: C:Documents and SettingsAll UsersApplication Data\LANDesk\Shavlik Protect\Console\DataFiles
    1. You may see this error:

      execution of scripts is disabled on this system

      If this occurs, enable the execution of scripts by entering this command:

      set-executionpolicy RemoteSigned

        This command is case-sensitive.


      Alternatively, you can sign the script instead of changing the execution policy. For more information, see http://www.hanselman.com/blog/SigningPowerShellScripts.aspx  The preceding link was correct and last checked as of June 11, 2013.

    Individual file download


    You can manually download the necessary data files. To download the files:

    1. Right-click each link and select Save Link As.
    2. Save the files to the console, in the DataFiles folder. This is the default location:
      • 8.x on Vista, 2008, & Windows 7: C:ProgramData\Shavlik Technologies\NetChk\DataFiles
      • 8.x on Windows XP or 2003: C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\NetChk\DataFiles
      • 9.x on Vista, 2008, & Windows 7: C:\ProgramData\LANDesk\Shavlik Protect\Console\DataFiles
      • 9.x on Windows XP or 2003: C:Documents and SettingsAll UsersApplication Data\LANDesk\Shavlik Protect\Console\DataFiles

     

      The Protect console requires both the .CAB and the files archived within the .CAB files for Protect to function correctly. The PowerShell script downloads the .CAB files, places the files in the output directory, and extract the files to the output directory. You need to manually extract the .CAB files using an archiving tool like 7-Zip if you choose to manually download the .CAB files.

     

    Update files for Shavlik Protect 9.0:

     

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STPlatformUpdater.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/AssetInstaller.msi

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/PatchInstaller.msi

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/ThreatInstaller.msi

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/cl5.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/ST.Licensing.Data.dll

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/DplyEvts.dll

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/7z.dll

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/SafeReboot.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/SafeReboot64.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STSchedEx.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STRemoteCommand.exe

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STScheduleView.exe

    http://xml.shavlik.com/data/hf7b.xml

    http://xml.shavlik.com/data/pd5.xml

    http://xml.shavlik.com/data/iadata.xml

    http://xml.shavlik.com/data/ai_dpd.xml

    http://xml.shavlik.com/data/scriptcatalog.zip

    http://xml.shavlik.com/data/assetinventory.xml

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STPlatformUpdater.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/cl5.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/ST.Licensing.Data.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/DplyEvts.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/7z.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/SafeReboot.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/SafeReboot64.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STSchedEx.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STRemoteCommand.cab

    http://xml.shavlik.com/data/Protect/v9/90/Protect/1182/STScheduleView.cab

    http://xml.shavlik.com/data/hf7b.cab

    http://xml.shavlik.com/data/pd5.cab

    http://xml.shavlik.com/data/iadata.cab

    http://xml.shavlik.com/data/ai_dpd.cab

    http://xml.shavlik.com/data/hypervisors.cab

    http://xml.shavlik.com/data/assetinventory.cab

    http://xml.shavlik.com/data/Protect/v9/90/manifest/protect.manifest.cab

     

    Update files for Shavlik Protect 9.1:

     

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/7z.dll

    http://xml.shavlik.com/data/hf7b.xml

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/cl5.exe

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/safereboot.exe

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/safereboot64.exe

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stschedex.exe

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stremotecommand.exe

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stscheduleview.exe

    http://xml.shavlik.com/data/pd5.xml

    http://xml.shavlik.com/data/ai_dpd.xml

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/assetinstaller.msi

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/patchinstaller.msi

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/threatinstaller.msi

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/st.licensing.data.dll

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/dplyevts.dll

    http://xml.shavlik.com/data/iadata.xml

    http://xml.shavlik.com/data/scriptcatalog.zip

    http://xml.shavlik.com/data/supportedHypervisors.obf

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stplatformupdater.exe

    http://xml.shavlik.com/data/assetCatalog2.obf

    http://xml.shavlik.com/data/assetCatalogMetadata2.obf

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/7z.cab

    http://xml.shavlik.com/data/hf7b.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/cl5.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/safereboot.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/safereboot64.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stschedex.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stremotecommand.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stscheduleview.cab

    http://xml.shavlik.com/data/pd5.cab

    http://xml.shavlik.com/data/ai_dpd.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/st.licensing.data.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/dplyevts.cab

    http://xml.shavlik.com/data/iadata.cab

    http://xml.shavlik.com/data/supportedHypervisors.cab

    http://xml.shavlik.com/data/protect/v9/91/protect/4334/stplatformupdater.cab

    http://xml.shavlik.com/data/assetCatalog2.cab

    http://xml.shavlik.com/data/assetCatalogMetadata2.cab

    http://xml.shavlik.com/data/Protect/v9/91/manifest/protect.manifest.cab

     

     

    Additional Information

     

    Shavlik Protect and VMware vCenter Protect consoles that have no internet connectivity, but that still try to download updates automatically can experience other issues. Shavlik recommends setting consoles with no internet connectivity to Disconnected Mode. To enable Disconnected Mode from the console application:

     

    Version 8.x: Go to Tools and select Run Disconnected.

    Version 9.x: Go to Tools and deselect Auto-Update Definitions.

    Document Content Update History

    11/1/2011 - Updated article for VMware vCenter Protect 8.0.x 

    07/16/2013 - Updated article for Shavlik Protect 9.0.x

    05/21/2014 - Updated article for Shavlik Protect 9.1.x

     

     

    Affected Products

     

    Shavlik Protect 9.x

    VMware vCenter Protect 8.x

    9.1 Protect crashes when opening

    $
    0
    0

    Symptoms

     

    When you open Protect and error appears and the program crashes

    ErrorSorryanUnexpectederror.PNG

     

    In the ST.ProtectManaged log you will see the following error

    Logs are located

    C:\ProgramData\LANDesk\Shavlik Protect\Logs

     

    2014-06-05T14:51:09.0756408Z 0001 I TaskbarNotification.cs:138|Connection failed to "Name of the Hosted Virtual Machine": No credential supplied.

    2014-06-05T14:51:09.1293593Z 0008 I WorkItemController.cs:304|Starting...

    2014-06-05T14:51:09.1303360Z 0008 I WorkItemController.cs:339|...done

    2014-06-05T14:51:09.3032119Z 0001 C Launcher.cs:73|System.InvalidOperationException: Crash from main UI thread

    ---> System.InvalidOperationException: Crash from main UI thread ---> System.NullReferenceException: Object reference not set to an instance of an

    object. at ST.UI.Controllers.Machines.VirtualServerController.<SaveAsync>b__25(FindVirtualInventoryResult r)

    at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext() at ST.UI.Controllers.Machines.VirtualServerController.<SaveAsync>d__27.MoveNext()

     

    Cause

     

    The crash is being caused by missing credentials for hypervisors.

     

    Resolution

     

    Do not click on the "OK" in the error this will allow you to navigate in the Program, instead move the pop up out of the way and create valid credentials for these hypervisors under Manage > Credentials. Set these credentials for the hypervisor under the Virtual Inventory view.

     

    If the Console does not launch and you only see the error. Edit the user.config file to bypass the virtual machine refresh when launching protect so that you can make the proper credential edits.

    Open the following folder. Replace <logged on user name> with the use that is logged on, and the strongName might be different.

     

    C:\Users\<logged on user name>\AppData\Local\LANDesk_Software,_Inc\ST.Protect.exe_StrongName_d0lqlz1kmud40uzklaub23nzftivjxwo\9.1.0.0

     

    Backup the User.config file

    Open User.config

     

    Under the console node, add or replace the following attribute changing the date to be 1 day out:

    timeOfLastVMServerAutoRefresh="05/02/2014 17:15:32"

     

    It should look like this:

     

    <?xml version="1.0" encoding="utf-8"?>

    <configuration>

    <st>

    <st.ui>

    <console windowSize="1441, 800" windowLocation="0, 0" windowState="Normal"

    navigatorWidth="180" navigatorCollapsed="false" treeWindowSplitterDistance="225"

    navigatorArchiveItems="true" navigatorAssetScanTemplates="true"

    navigatorDeploymentTemplates="true" navigatorFavorites="true"

    navigatorMachineGroups="true" navigatorPatchGroups="true"

    navigatorPatchScanTemplates="true" navigatorPowerTemplates="true"

    navigatorPolicies="true" navigatorPatchScansAndDeployments="true"

    gridWindowSplitterDistance="225" deploymentTrackingViewSplitterDistance="250"

    mvTopSplitterDistance="250" mvBottomSplitterDistance="449"

    pvSplitterDistance="400" threatEventsSplitterDistance="400"

    networkMonitorwindowLocation="270, 50" networkMonitorWindowSize="1065, 700"

    reportGalleryWindowLocation="32, 32" reportGallerySummaryWindowSize="975, 700"

    scanStatusWindowState="Normal" showPatchInformationalItems="true"

    timeOfLastVMServerAutoRefresh="05/02/2014 17:15:32" navigatorITScriptsTemplates="true" />

    <viewOptions threatEventsCutoff="30.00:00:00" lastRole="Role Based Administration is not enabled"

    autoCloseRefreshFiles="false" myScansOnly="false" daysInRecentScans="15"

    ignoreBulletinOpenWarning="false" autoCloseDownloadWindows="false"

    showNewsfeedColumn="true" scriptResultsCutoff="30.00:00:00" />

    <chartOptions top10MissingPatches="Rotate" top10VulnerableMachines="Rotate"

    patchLevel="Rotate" missingPatchBySeverity="Rotate" osDistribution="Rotate"

    agentVsAgentless="Rotate" threatStatusByCategory="Rotate"

    percetInfected="Rotate" percentThreatsByRisk="Rotate" top10InfectedMachines="Rotate"

    top10Threats="Rotate" />

    <taskbarNotification eventDigestInterval="00:05:00" scansCompletedInterval="00:01:00" />

    <trackerOptions showDone="true" showFailed="true" showInProgress="true"

    updateInterval="00:00:30" visibleDays="7" />

    </st.ui>

    </st>

    </configuration>

     

    Open Protect and verify credentials associated with the all ESX servers..

     

    Affected Products

     

    Protect Version 9.1

    Patch progress stays at status scheduled , but no patch gets deployed

    $
    0
    0

    Patch progress stays at status scheduled , but no patch gets deployed . Machine progress stays at executing the patch but it never progress.

    Using shavlik 9.1 . port 5120 and 3121 is open from bidirectional.

    No relevant event id gets logged on the target server.

    No other patches will deploy when one patch gets the below error.

    $
    0
    0

    The error states that "Patch download failed - retry scheduled.  No other patches will deploy when one hangs like this.  It will simply sit on executing but will go no further.

     

    We recently moved Shavlik to a WIndows 2012 server.  We have checked credentials and they all look good.  Any help would be appreciated.  Thank you.

     

    JG

     


    Unable to install the Scheduler Service

    $
    0
    0

    I have two machines on which I cannot install the scheduler service. When I try to install the scheduler I get the error "The scheduler on machine 'xxxx' is not available. (Error: 10060)" and an option to upgrade which is just a loop. I compared this server to one of its counterparts and one thing I noticed is on the working machine there is a process called STSchedEx.exe *32 (and associated service) but that process is not found on the failing machine. I confirmed that the application is located in the windows\ProPatches\Scheduler folder and even copied all the files from the good server. I'm not able to manually start the process as it indicates that it can't find the file.  My main reason for looking into this is during deployment all the files and patches will copy but the install of patches will not initiate. If you go to the server and run the batch file that was copied everything works fine so it seems the scheduler is not functioning.  Looking for any suggestions.

    Overlooked Patches....

    $
    0
    0

    Hi there,

     

    I am using Shavlik Protect Standard 9.1.0  Build: 4334 on a W7, 64-bit with MS-Office 2010 installed.

     

    I scan 'My Machine' and it lists 11 patches as missing (see Pic1 - below).

    A reboot is scheduled and completes (normal countdown timer, etc).

     

    Once the machine reboots I do a further scan of my machine but find it has no installed any of the 11 patches (see Pic2 - below).

    Running Windows Update I am told that 'Windows is up to date'.

     

    Any assistance would be appreciated.

     

    Thanks,

    Kim.

     

    Pic1:

    Pic1.png

     

    Pic2:

    Pic2.png

    Scripted uninstall of Shavlik Protect Agent?

    $
    0
    0

    So now that we have our installation script working. What options are there for uninstalling?

     

    If we do it manually through Add/Remove Programs, we first have to uninstall any Engines (Patch and/or Asset) and then we can remove the Agent itself.

     

    Is there a switch for the STPlatformUpdater.exe file that will result in everything being uninstalled from the machine?

     

    Or will I have to script msiexec /X for each item?

     

    Thanks,

    Agent Registration for reimage/reloaded systems?

    $
    0
    0

    How does Shavlik handle agent registrations for systems that have been wiped and reloaded for one reason or another?

     

    For example, PC01 was active in the domain and had active agent on it. Issue occurred and PC01 was reloaded with fresh install of the OS and joined to domain as PC01 again. The Shavlik install script appeared to work normally, but the agent window showed "No Policy" and agent check-ins were failing.

     

    The registration log appeared normal as well. There were no errors or warnings that a machine named PC01 was already registered with the console.

     

    It wasn't until we deleted PC01 from the machines view and reran registration from the client that everything started working again.

    Trying to patch a VMware template

    $
    0
    0

    This is our first attempt to patch a VMware template and after configuring the correct permissions and accounts it access the host and guests but I receive the following when doing a scan.

     

    "Complete with errors, Check the hypervisor network configuration and firewall settings".

     

    What is this error directing me to check or what could be the issue?

    Shavlik Protect End-User License Agreement

    $
    0
    0

    1604_157_49_cache.png

     

    Purpose


    This document lists the Shavlik Protect End-User License Agreement:

     

    Shavlik Protect \EULA

     

    END USER LICENSE, MAINTENANCE, AND SUPPORT SERVICES AGREEMENT

     

    This End User License, Maintenance, and Support Services Agreement (“EULA”), is a legal agreement between Licensee and LANDESK (as such terms are defined below).  This EULA describes the terms and conditions upon which LANDESK is willing to license its products and provide Maintenance and Support Services to Licensee.

     

    BY INSTALLING OR USING ALL OR ANY PORTION OF LICENSED SOFTWARE, LICENSEE AGREES TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS EULA.  IF LICENSEE DOES NOT AGREE TO ANY TERM OR CONDITION OF THIS EULA, LICENSEE SHOULD STOP INSTALLATION OR USE AND PROMPTLY RETURN THE LICENSED SOFTWARE IT PHYSICALLY POSSESSES, IF ANY, AND ANY ACCOMPANYING MATERIALS IN AN UNDAMAGED CONDITION TO THE VENDOR FROM WHICH IT WAS ACQUIRED.

     

    1.  DEFINITIONS.

     

    “Concurrent Users” means the maximum number of users that may concurrently use or access the Licensed Software.

     

    “Documentation” means the user documentation LANDESK provides with the Licensed Software.

     

    “Infringement Claim” means a claim by a non-affiliated third party against Licensee asserting that Licensee’s use of Licensed Software in accordance with this Agreement violates that third party’s patent, trademark, or copyright rights.

     

    “LANDESK” means:

     

    ·    LANDESK International Limited d/b/a Shavlik, an Irish company, if Licensee has its primary office located outside of North America, Central America, South America (excluding Brazil), (collectively, the “Americas”), Japan or the People’s Republic of China.

     

    ·    LANDESK Software, Inc. d/b/a Shavlik, a Delaware corporation, if Licensee has its primary office located in the Americas.

     

    ·    LANDESK Comércio de Software Brasil Ltda, a Brazilian company, if Licensee has its primary office located in Brazil.

     

    ·    LANDESK Software K.K., a Japanese company, if Licensee has its primary office located in Japan.

     

    ·    LANDESK (Beijing) Information Technology Co., Ltd., a Chinese company, if Licensee has its primary office located in the People’s Republic of China.

     

    “Licensed Software” means the software, in object code form, and any Documentation accompanying this EULA or the software.

     

    “Licensee” means the person or entity licensing the Licensed Software from LANDESK pursuant to this EULA.

     

    “Maintenance” means LANDESK’s provision of Updates and Upgrades to the applicable Licensed Software.

     

    “Node” means each electronic device using the Licensed Software including without limitation (a) a physical device such as a computer, handheld device, workstation, console, Seat, server, or any other electronic device; (b) a virtual machine, such as an operating environment that may be running concurrently with another operating environment on a single physical device; or (c) for the LANDESK Antivirus for Mail Servers product, an electronic or virtual mailbox (e.g., a mailbox for email).

     

    “Node Count Data” means information periodically generated by the Licensed Software about (a) the quantity and type of current usage of the Licensed Software on a server, and (b) the non-personal, encrypted hardware configuration of that server.

     

    “Seat” means the number of Concurrent Users authorized to use the Licensed Software.

     

    “Support Services” means the services regarding installation, configuration and usage detailed at http://www.landesk.com/support/ and available to Licensee for purchase.

     

    “Update” means content used to update the License Software and includes bug fixes, minor enhancements and patches, but does not include Upgrades.

     

    “Upgrade” means a new version of Licensed Software that replaces a pre-existing version of such Licensed Software.

     

    “User” means a natural person employed by or who otherwise provides services (whether as an independent contractor or otherwise) to Licensee who is supported with or uses the Licensed Software.

     

    2.  LICENSES. The licenses that are available from LANDESK include, without limitation, the following:

     

    (A)  TRIAL USE LICENSE:  A “Trial Use License” is a nonexclusive, non-transferable, restricted, forty-five (45) day limited license that allows Licensee to evaluate the Licensed Software before purchasing a Full-Use License for the Licensed Software.  At the end of the forty-five (45) day evaluation period, Licensee agrees to promptly discontinue use and delete the Licensed Software from Licensee’s systems.  It is the sole responsibility of Licensee to back-up its system and perform all other measures to prevent any loss of files or data.  Use of the Licensed Software under a Trial Use License is entirely at Licensee’s own risk.

     

    (B)  FULL-USE LICENSE:  A “Full-Use License” is a non-exclusive, non-transferable, perpetual, and limited license to copy, install and use the Licensed Software within Licensee’s organization on the total number of Nodes for which Licensee has paid the required license fee.  A Full-Use License does not include Maintenance or Support Services.  Maintenance and Support Services must be purchased in addition to the Full-Use License.

     

    (C)  SUBSCRIPTION LICENSE: A “Subscription License” is a non-exclusive, non-transferable, time-limited license to copy, install and use certain Licensed Software within Licensee’s organization on the total number of Nodes for which Licensee has paid the required subscription license fee.  Unless a different term is specified in the purchase order to LANDESK, the term of Subscription License or renewal thereof is one (1) year.  During the term of the time-limited subscription, Licensee is entitled to receive Maintenance for the Licensed Software (additional Support Services also may be available for purchase by Licensee). If the Subscription License is provided as software as a service (SaaS), the terms and conditions found at www.landesk.com/saas/termsandconditions/ <http://www.landesk.com/saas/termsandconditions/> shall also apply in addition to the terms and conditions contained within this EULA.

     

    (D)  USER-BASED LICENSE: A “User-Based License” is a non-exclusive, non-transferable, perpetual, and limited license to copy, install and use the Licensed Software within Licensee’s organization to support the total number of Users for which Licensee has paid the required license fee.  A User-Based License does not include Maintenance or Support Services.  Maintenance and Support Services must be purchased in addition to the User-Based License.

     

    3.  LICENSE GRANT.  Subject to Licensee’s compliance with all terms and conditions of this EULA, LANDESK hereby grants Licensee a non-exclusive, non-transferable, restricted, license to use the Licensed Software in accordance with the type of license and subject to the quantity of Nodes paid for by Licensee.  Licensee may make a copy of the Licensed Software only as needed for archival and backup purposes.  Licensee may permit third party consultants and contractors (such as third-party supplier(s) of information services) to use the Licensed Software on Licensee’s behalf provided that (a) all such use is in accordance with the terms and conditions of this EULA, and (b) Licensee assumes full responsibility and liability for any use of the Licensed Software by such third parties in any violation of this EULA, including without limitation use in excess of the licensed number of Nodes. Licensee agrees not to override or bypass the activation process or any security feature, authorization, activation, or reactivation of the Licensed Software or to assist others in doing the same.

     

    4.  NODE COUNT VERIFICATION AND AUDIT.  Licensee agrees that LANDESK may periodically verify that Licensee’s usage of the Licensed Software does not exceed the quantity of Nodes or User-Based Licenses purchased.  Periodically, the Licensed Software on each server will generate Node Count Data.  Each time the Licensed Software generates Node Count Data on a server, Licensee agrees to send, within thirty (30) days of generation, the Node Count Data to LANDESK either automatically by the Internet or manually by email.  If Licensee fails to provide such Node Count Data within thirty (30) days, LANDESK has the right to render the Licensed Software inoperative or reduce the Licensed Software’s functionality until Licensee provides LANDESK with the Node Count Data.  If the node count verification process shows that Licensee, including its third party consultants or contractors using the Licensed Software for Licensee, is using more than the number of Nodes or other Licensed Software for which licenses have  been purchased, Licensee shall pay LANDESK for such additional Nodes and/or Licensed Software no later than thirty (30) days following Licensee’s receipt of an invoice from LANDESK, with such fees being the license fees as per LANDESK’s then-current price list. Licensee agrees not to override or bypass this node count verification process or assist others to do the same.  With respect to User-Based Licenses, Licensee agrees to provide LANDESK with documentation evidencing the total number of Users within thirty (30) days of LANDESK’s request. Licensee shall permit LANDESK to conduct audits to verify Licensee’s compliance with this EULA.  Such audits shall be conducted during normal business hours and after reasonable advance notice to Licensee by LANDESK. The cost of such audits will be borne by LANDESK; provided, however, that if such audit determines that Licensee has failed to pay fees amounting to five percent (5%) or more of that annual period’s fees due hereunder, then Licensee shall reimburse LANDESK for the cost of such audit in addition to payment of any identified delinquent fees.

     

    5.  USE RESTRICTIONS.  LANDESK reserves all rights not expressly granted to Licensee herein.  Without limiting the generality of the foregoing, Licensee shall not and shall not allow others to: (a) copy, modify, adapt, rent, lease, sell, distribute, export, re-export, assign, sublicense, translate, transfer, or reprogram the Licensed Software or any portion thereof except as provided in this EULA; (b) use the Licensed Software in a service bureau, facility management, service provider, timeshare, or other similar type of environment, (c) reverse engineer, decompile, translate, merge, or disassemble the Licensed Software; (d) create derivative works based upon the Licensed Software; (e) use the Licensed Software to perform any activity which is or may be, directly or indirectly, unlawful, harmful, threatening, abusive, harassing, tortious, or defamatory, or to perform any activity which breaches the rights of any third party; (f) take any actions that would cause the Licensed Software to become subject to any open source or quasi-open source license agreement not otherwise applicable; or (g) transfer any Licensed Software or Licensee’s license rights under this EULA, in whole or in part without LANDESK’s prior written consent, which consent shall not be unreasonably withheld or denied.

     

    THE LICENSED SOFTWARE IS NOT INTENDED OR LICENSED FOR AND LANDESK SPECIFICALLY DISCLAIMS LIABILITY FOR USE OF THE LICENSED SOFTWARE IN ANY ENVIRONMENT IN WHICH FAILURE OF THE SOFTWARE COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE.  LICENSEE AGREES TO DEFEND, INDEMNIFY, AND HOLD LANDESK HARMLESS FROM AND AGAINST ANY AND ALL CLAIMS ARISING OUT OF LICENSEE’S UNAUTHORIZED USE OF THE LICENSED SOFTWARE.

     

    6.  OWNERSHIP OF LICENSED SOFTWARE.  The Licensed Software is the proprietary property of LANDESK or its licensors.  No title to or ownership of any Licensed Software is transferred to Licensee.  The Licensed Software is licensed to Licensee, not sold.  All rights, title and interest in and to the Licensed Software (including any Update or Upgrade thereto), including all worldwide intellectual property rights, shall remain with LANDESK, its licensors, vendors and/or suppliers, as the case may be.  LANDESK may make changes to the Licensed Software at any time and without notice.  Except as otherwise expressly provided, LANDESK grants no express or implied right under any LANDESK patent, copyright, trademark, or other intellectual property right.

     

    7.  COPYRIGHTS, TRADEMARKS, AND PATENTS.  The Licensed Software is copyrighted and protected by the laws of the United States and other countries, and by international treaty provisions combined with patents and trademarks.  In no circumstance may Licensee remove or alter the copyright notice, trademark notice, or other proprietary notices from the Licensed Software.  Licensee agrees to faithfully reproduce and include all copyrights, trademarks, and other proprietary notices on any authorized copy of any Licensed Software.  LANDESK is either a registered trademark or trademark of LANDESK Software, Inc. or its affiliates in the United States and/or other countries. One or more patents, as well as other patent pending technology, may apply to Licensed Software.

     

    8.  maintenance and support SERVICES.  Nothing in this Agreement entitles Licensee to any Support Services and/or Maintenance of the Licensed Software without the required payment for such Support Services and/or Maintenance.

     

    (A) MAINTENANCE:  During the term for which Licensee has paid the applicable Maintenance or subscription fees for the Licensed Software, Licensee is entitled to Updates and Upgrades as and when they are made generally available to LANDESK’s end users.

     

    (B) Support services:  During the term for which Licensee has paid the applicable support fees, Licensee is entitled to support in accordance with LANDESK’s points-based support programs.  Points expire at the end of each Support Services period and new points are calculated each renewal period.  Support levels may be adjusted any time Licensee purchases additional Support Services.  For more information on the LANDESK support programs, see the LANDESK service portal at http://www.landesk.com/support/terms/.

    (C)  NO OBLIGATION. LANDESK shall be under no obligation to furnish Maintenance and/or Support Services for the Licensed Software to the extent that such Maintenance and/or Support Services are necessary or desired as a result of: (i) the operation of the Licensed Software in environmental conditions or configurations outside those prescribed in the Documentation; (ii) Licensee’s failure to upgrade and update the Licensed Software to the currently supported versions of the Licensed Software or to maintain the Licensed Software in accordance with the standards of Maintenance prescribed in the Documentation or as specified in Maintenance or Support Services received by Licensee from LANDESK; (iii) actions of any third party other than LANDESK or a third party authorized by LANDESK; and (iv) causes unrelated to the Licensed Software as delivered to Licensee by LANDESK, including without limitation, modifications to the Licensed Software made by Licensee or on Licensee’s behalf.

    (D) TERMINATION OF MAINTENANCE OR SUPPORT SERVICES. Without limiting any other remedies available under this EULA, at law, or in equity, LANDESK shall have the right to terminate Licensee’s right to receive Maintenance and/or Support Services with prior notice to Licensee for Licensee’s breach hereunder if such breach remains uncured for a period of thirty (30) days after receipt of notice thereof from LANDESK.

    9.  THIRD-PARTY SOFTWARE.  The Licensed Software may be bundled with non-integrated hardware or other software programs licensed or sold by a licensor other than LANDESK. LANDESK DOES NOT WARRANT SUCH THIRD-PARTY PRODUCTS.  Any and all such third-party products (e.g., drivers, utilities, operating system components, etc.) which may be distributed with the Licensed Software are provided "AS IS" without warranty of any kind, whether express or implied, and Licensee’s use and installation thereof, and any related warranty service, is subject to the third-party licenses supplied with such products or the applicable manufacturer’s warranty.  Use of Microsoft's DCOM software, distributed with the Licensed Software, is conditioned upon Licensee having a valid licensed copy of the applicable Microsoft operating system software on the computer on which the DCOM software is installed.  LANDESK expressly disclaims liability of any kind with respect to Licensee’s installation or use of third-party products.  Nothing in this EULA shall restrict, limit or otherwise affect any rights or obligations Licensee may have, or conditions to which Licensee may be subject, under any applicable open source licenses to any open source code contained in any Licensed Software.  LANDESK may cease to provide access to third-party databases and content, such as patch content, used with some licensed software, in its sole discretion, at any time, and makes no warranty that third-party software which Licensee seeks to access using the licensed software shall be available for downloading to Licensee’s system.

     

    10.  LIMITED WARRANTY.  LANDESK WARRANTS THAT FOR A PERIOD OF NINETY (90) DAYS FROM LICENSEE’S INITIAL ACQUISITION OF A LICENSE TO USE THE LICENSED SOFTWARE, THE LICENSED SOFTWARE WILL FUNCTION SUBSTANTIALLY IN CONFORMANCE WITH THE DOCUMENTATION ACCOMPANYING SUCH LICENSED SOFTWARE WHEN USED IN ACCORDANCE WITH THE ACCOMPANYING DOCUMENTATION.  LICENSEE’S SOLE REMEDY FOR A BREACH OF THIS WARRANTY SHALL BE THAT LANDESK, IN ITS REASONABLE DISCRETION, WILL EITHER: (i) RESOLVE THE NONCONFORMITY, (ii) REPLACE THE LICENSED SOFTWARE WITH SOFTWARE OF SUBSTANTIALLY THE SAME FUNCTIONALITY, OR (iii) REFUND THE LICENSE FEES PAID BY LICENSEE FOR THE APPLICABLE LICENSED SOFTWARE. THIS LIMITED WARRANTY SHALL NOT APPLY TO UPDATES AND UPGRADES (IF ANY) TO THE LICENSED SOFTWARE OR IF LICENSEE HAS OBTAINED A TRIAL-USE LICENSE.

     

    11.  NO OTHER WARRANTIES.  EXCEPT FOR THE FOREGOING LIMITED WARRANTY, THE LICENSED SOFTWARE, MAINTENANCE AND SUPPORT SERVICES ARE PROVIDED “AS IS”, WITHOUT WARRANTY OR REPRESENTATION OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. ANY EXPRESS WARRANTY MADE OUTSIDE OF THIS EULA IS EXCLUDED AND SUPERSEDED.  NEITHER LANDESK NOR ITS LICENSORS REPRESENT OR WARRANT THAT THE LICENSED SOFTWARE WILL SATISFY LICENSEE’S REQUIREMENTS OR THAT THE LICENSED SOFTWARE IS WITHOUT DEFECT OR ERROR OR THAT OPERATION THEREOF WILL BE UNINTERRUPTED OR ERROR FREE.  LICENSEE MAY HAVE OTHER WARRANTY RIGHTS PROVIDED BY LOCAL LAW.

     

    12.  LIMITATION OF LIABILITY AND DIRECT DAMAGES.  IN NO EVENT SHALL LANDESK OR ITS LICENSORS, VENDORS, AFFILIATES, SUBSIDIARIES, PARENTS, EMPLOYEES AND/OR SUPPLIERS BE LIABLE UNDER THIS EULA OR IN CONNECTION WITH THE LICENSED SOFTWARE, MAINTENANCE, OR SUPPORT SERVICES FOR ANY INCIDENTAL, INDIRECT, CONSEQUENTIAL, EXEMPLARY, PUNITIVE OR SPECIAL DAMAGES, OR FOR ANY LOSS OF PROFITS OR REVENUES, BUSINESS INTERRUPTION, LOSS OF INFORMATION, LOSS OF COMPUTER PROGRAMS, OR INABILITY TO USE THE LICENSED SOFTWARE (REGARDLESS OF THE FORM OF ACTION OR CLAIM), EVEN IF LANDESK HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  LANDESK’S ENTIRE LIABILITY UNDER THIS EULA SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES AND THE AGGREGATE LIABILITY OF LANDESK ARISING FROM OR RELATING TO THIS EULA, THE USE OF THE LICENSED SOFTWARE, MAINTENANCE, AND SUPPORT SERVICES SHALL NOT EXCEED THE AMOUNT OF THE LICENSE FEES RECEIVED BY LANDESK FROM LICENSEE UNDER THIS EULA FOR THE LICENSED SOFTWARE OUT OF WHICH SUCH LIABILITY AROSE (EXCEPT WITH RESPECT TO INDEMNIFICATION UNDER SECTION 13 OF THIS EULA WHICH SHALL NOT BE LIMITED).  some jurisdictions do not allow certain disclaimers or limitations of warranties, so some of these provisions may not apply to licensee.

     

    13.  INDEMNIFICATION.

     

    (A) INDEMNIFICATION BY LANDESK: LANDESK will, at its own expense, defend or settle any Infringement Claim and indemnify Licensee for any damages finally awarded against Licensee, but only if: (i) Licensee promptly notifies LANDESK of any Infringement Claim; (ii) LANDESK retains sole control of the defense, negotiations, settlement, or compromise of any Infringement Claim; and (iii) Licensee provides LANDESK with all necessary authority, information, and reasonable assistance (at LANDESK’s expense). LANDESK will not be responsible for any costs, expenses or compromise incurred or made by Licensee without LANDESK’s prior written consent. If use of Licensed Software is permanently enjoined as the result of an Infringement Claim, LANDESK will, in its sole discretion and expense, procure for Licensee the right to continue using such Licensed Software, replace such Licensed Software with non-infringing product, modify such Licensed Software so that it is no longer infringing, or, if each of the foregoing is commercially unreasonable or unduly burdensome, LANDESK may elect to refund to Licensee the fees, less depreciation, received by LANDESK for such enjoined Licensed Software. Depreciation shall be determined using a straight line basis over thirty-six (36) months, commencing on the effective date for LANDESK Licensed Software and on the date of first delivery to Licensee of any Licensed Software or Support Services.

    (B) EXCLUSIONS: LANDESK shall not have any indemnification obligations, other responsibility or liability for any costs, expenses, or damages, settlement, or otherwise resulting from: (i) LANDESK’s compliance with Licensee’s designs, specifications or instructions; (ii) Licensee’s modification (whether authorized or not) of Licensed Software; (iii) any Infringement Claim arising from Licensee’s combined use of Licensed Software (or any part thereof) with any Licensee or other third party product; or (iv) Licensee’s direct or contributory infringement of any business method patent.

    (C) ENTIRE OBLIGATION AND EXCLUSIVE REMEDY: The foregoing states the entire obligation and exclusive remedy of each of the parties hereto with respect to any LANDESK indemnification obligation.

    (D) INDEMNIFICATION BY LICENSEE: Licensee agrees to defend, indemnify, and hold LANDESK harmless from and against any and all actions, claims, damages, expenses (including attorneys’ fees and out-of-pocket expenses) and liabilities arising out of (i) Licensee’s unauthorized use of Licensed Software; (ii) for any material breach of this EULA by Licensee (or Licensee’s affiliates, contractors, consultants); (iii) LANDESK’s compliance with Licensee’s designs, specifications or instructions; and (iv) Licensee’s modification (whether authorized or not) of Licensed Software.

     

    14. PAYMENT AND TAXES.  In the event that Licensee is purchasing directly from LANDESK and payment is required from Licensee directly to LANDESK (as opposed to purchase through or payment to an authorized LANDESK reseller or distributor), Licensee shall pay LANDESK all amounts due in U.S. Dollars no later than thirty (30) days following Licensee’s receipt of an invoice from LANDESK.  For the purchase of any annual renewal of the then-current annual Subscription Fee and annual Support Services Fees (if any), Licensee shall make payment to LANDESK within thirty (30) days of such annual renewal. If Licensee fails to make a payment to LANDESK when due, LANDESK may charge Licensee interest at the lesser of a rate of one and one half percent (1.5%) per month or the maximum rate allowed by applicable law, which interest will accumulate on the outstanding balance on a daily basis until paid in full.  Licensee shall reimburse LANDESK for all reasonable costs, including legal fees and related costs, LANDESK incurs in collecting any late payments and interest from Licensee.  LANDESK shall be entitled to terminate all licenses, services and Support Services provided hereunder upon thirty (30) days prior written notice to Licensee if Licensee fails to pay any required fees when due.  In the event that any withholding, sales, value-added, use or other taxes or government fees, assessments or charges are payable because of this EULA, the license of the Licensed Software to Licensee, or because of any payment by Licensee, then Licensee shall pay all such taxes, fees, assessments and charges in addition to all other payments.  If LANDESK is required to make any such payments, Licensee agrees to reimburse LANDESK for such payments promptly upon notice from LANDESK.

     

    15.  TERMINATION OF THIS EULA.  If Licensee is using the Licensed Software under any time-limited license, including without limitation a Trial-Use License or Subscription License, this EULA shall terminate with regard to such Licensed Software without notice to Licensee on the last day of the specified time period. Any other license granted hereunder shall automatically terminate if Licensee breaches this EULA.  Upon expiration or termination of this EULA, Licensee shall immediately cease all use of the Licensed Software and uninstall and delete all of the Licensed Software.  The foregoing shall not limit or affect any remedy available to LANDESK as a result of any breach of this EULA by Licensee.

     

    16.  EXPORT COMPLIANCE.  Licensee acknowledges that the Licensed Software is exported from the United States in accordance with the Export Administration Regulations.  The Licensed Software, and any product or technical information provided by LANDESK, are subject to applicable import and export regulations of the United States and/or other countries.  Diversion contrary to U.S. law is prohibited. Licensee agrees to comply with all applicable import and export regulations as they may be amended from time to time. Regardless of any disclosure made by Licensee to LANDESK of an ultimate destination of the Licensed Software or any product or technical information, Licensee agrees that it will not export, re-export or disclose (directly or indirectly) any of the Licensed Software, any product or technical information provided by LANDESK, or any portion thereof, to any country, entity or person in violation of U.S. export laws or regulations or any other law, regulation, or government order.  Note that Licensed Software containing encryption may be subject to additional restrictions with which Licensee also agrees to comply.

     

    17.  GOVERNING LAW. If Licensee has its primary office in North America, Central America, South America, or any other area not expressly identified below in this section, this EULA is governed by the laws of the State of Utah, United States of America. If Licensee has its primary office in a member state of the European Union or the European Free Trade Association, the Middle East or Africa, this EULA is governed by the laws of England.  If Licensee has its primary office in Japan, this EULA is governed by the laws of Japan.  If Licensee has its primary office in the People’s Republic of China, this EULA is governed by the laws of the People’s Republic of China.  Such governing laws are effective without regard to the principles of conflict or choice of law and are exclusive of any provisions of the United Nations Convention on Contracts for Sale of Goods.  In any action or suit to enforce any right or remedy under this EULA, the prevailing party will be entitled to recover its fees and costs, including reasonable attorney’s fees.

     

    18.  U.S. GOVERNMENT RESTRICTED RIGHTS.  The Licensed Software is provided with “RESTRICTED RIGHTS” and is deemed “commercial computer software” and “commercial computer software documentation” within the meaning of applicable civilian and military Federal acquisition regulations and any supplement thereto.  Use, modification, duplication, or disclosure by the United States Government is subject to restrictions as set forth in DFARS 252.227-7014(a)(1) (JUN 1995) (DOD commercial computer software definition), DFARS 227.7202-1 (DOD policy on commercial computer software), FAR 52.227-19 (DEC 2007) (commercial computer software clause for civilian agencies), DFARS 252.227-7015 (NOV 1995) (DOD technical data - commercial items clause); FAR 52.227-14, including Alternates I, II, and III (DEC 2007) (civilian agency technical data and noncommercial computer software clause); and/or FAR 12.211 and FAR 12.212 (commercial item acquisitions), and any successor provisions . Use of the Company Products by the U.S. Government constitutes acknowledgment of LANDESK's proprietary rights therein.  The Contractor or Manufacturer is LANDESK Software, Inc. (or its subsidiaries or affiliates), with an office at 698 West 10000 South, Suite 500, South Jordan, UT 84095, USA.

     

    19.  SEVERABILITY.  If any provision in this EULA shall be found or be held to be invalid, unenforceable, or in conflict with applicable law in any jurisdiction in which this EULA is being performed, such provision shall be construed, limited, or altered, as necessary, to eliminate the invalidity, unenforceability, or conflict, and all other provisions of this EULA shall remain unaffected.

     

    20.  FORCE MAJEURE.  LANDESK shall not be liable for its failure to perform due to unforeseen circumstances or any causes beyond LANDESK’s reasonable control (“Force Majeure”).  In the event of Force Majeure, LANDESK’s performance will be extended for a period equal to the duration of the delay caused thereby.

     

    21.  WAIVER.  No action taken pursuant to this EULA, including any investigation by or on behalf of any party, shall be deemed to constitute a waiver by such party of any representation, warranty, covenant or agreement contained herein.  The waiver by any party hereto of a breach of any provision of this EULA or failure to perform by the other party shall not operate or be construed as a further or continuing waiver of such breach or failure to perform or as a waiver of any other or subsequent breach or failure to perform.  No failure on the part of any party to exercise, and no delay in exercising, any right, power or remedy hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of such right, power or remedy by such party preclude any other or further exercise thereof or the exercise of any other right, power or remedy.  All remedies hereunder are cumulative and are not exclusive of any other remedies provided by applicable law.

     

    22.  ASSIGNMENT; SUB-LICENSE.  Licensee may not assign, sublicense, or transfer this EULA, the Licensed Software, any right to Support Services, or any rights or obligations hereunder without prior written consent of LANDESK. LANDESK may assign this EULA and any rights or obligations hereunder at any time and without consent.

     

    23.  NOTICES. All notices required or permitted to be given hereunder shall be in writing, shall make reference to this EULA, and shall be delivered by hand, or dispatched by prepaid courier or by registered or certified mail, postage prepaid.  Notices to LANDESK shall be sent to the following address:

     

        LANDESK Software, Inc.

    698 West 10000 South, Suite 500

    South Jordan, Utah 84095

    Attn: Legal Dept.

     

    Notices shall be deemed served when received by addressee or, if delivery fails by reason of some fault or action of the addressee, when tendered for delivery.

     

    24.  ENTIRE AGREEMENT; AMENDMENT.  This EULA sets forth the entire understanding and agreement between Licensee and LANDESK relating to the subject matter herein.  This EULA may be amended only in a writing signed by authorized representatives of both parties.  No vendor, distributor, dealer, retailer, reseller, salesperson, employee or any other person is authorized to modify this EULA or to make any representations different from, or in addition to, the terms of this EULA and Licensee hereby confirms that it has not entered into this EULA in reliance on any statement or representation not expressly set forth herein.  Any terms and conditions of any purchase order or other document that is submitted by Licensee in connection with the LANDESK Licensed Software that are different from or in addition to the terms and conditions of this EULA are not binding on LANDESK and are ineffective.

     

    EULA - Version:  March 2014

     

    Affected Product(s)

    Shavlik Protect All

    Scan results show 1 or 2 missing patches where many more patches should be missing

    $
    0
    0

    Symptoms

     

    Scan results will show a limited number of missing patches, generally Microsoft Visual C++ or Studio Shell.  Additionally, the scan results will not show Patches Installed or Service Packs Missing


    Results will show similar to this:

    BadScanResults.PNG

     

    The expected results:

    ExpectedScanResults.PNG

     

    Cause

     

     

    You are running in an unlicensed limited mode and  you are very limited in the actions you are allowed to perform.

     

    Resolution


    Activate Shavlik Protect with a valid license, you can do this online or manually.


    Information about the behavior of patching Adobe and Mozilla products with Protect

    $
    0
    0
    Purpose

     

    This article is meant to provide information about how Protect provides security updates for Adobe and Mozilla products incrementally.

     

    Description

     

    When a vendor supports multiple branches or versions of a product Protect does not support moving to the latest version until the previous branch has been end of life (EOL).

     

    Example:

    For Adobe Flash, if versions 10 and 11 are still supported (Flash 9 & below are EOL) Protect offers all flash 5, 6, 7, 8, 9 and 10 to the latest version of 10 as a security update. Protect only offers the latest Flash 11-14  security patches to older versions of 11-14 that are currently installed. This behavior is in place because not all customers wish to move to the latest version.

     

    In this instance if you currently had Flash 10 installed you would need to use the "Software Distribution" scanning and deployment option within Protect to update directly to the latest version of Flash 14.

     

    This behavior can apply to all Adobe and Mozilla products that are supported for security patching within Protect.

     

    Additional Information

     

    If you need instructions for a software distribution scan and deployment please refer to the  Software Distribution Best Practices and Informational Guide

     

    Affected Products

     

    Shavlik Protect 9.x

    vCenter Protect 8.x

    Shavlik Protect Agent 9.0 Java 7 Update 65 Bug

    $
    0
    0

    Hello Forum Users/Support, We use the Shavlik Protect Agent to patch user laptops that are not connected to the network 24/7 and everything was working until the latest version of Java 7 update 65 was included. When Shavlik protect agent downloads and installs Java 7 Update 65 it is not silent and requites user to supply Administrative credentials then they have to click through several installation prompts. I believe this is a bug or incorrect shavlik agent xml file as this is the first time the Shavlik Agent has prompted users for credentials and installation prompts.  We have several hundred laptops now prompting users to for Administrative credentials to install Java 7 update 65 and is unrealistic to have to go to each laptop to install the Java update.  Until now the shavlik agent installed all software silently without requiring user credentials. Is there anyone that is having this problem with Shavlik Protect Agent and the new Java update 65 and what is the fix for this. Thanks, Tom

    Error when Scheduling Scan with Auto-deploy: Failed to schedule operation: 'Unkown error (0x84000005)'

    $
    0
    0

    Symptoms


    When attempting to set up a scheduled scan with auto-deployment, you receive a pop up error stating:

    Schedule: Failed to schedule operation: 'Unkown error (0x84000005)'

    error.JPG


    Within the ST.Protect.managed.log you may see the following type of error message:

    2014-07-07T17:47:38.0155053Z 0005 E OperationPresenter.cs:120|System.ComponentModel.Win32Exception (0x80004005): Unknown error (0x84000005)

      at ST.Deployment.Distribution.STScheduler.ScheduleJob(String machine, Int32 schedulerPort, X509Certificate consoleCertificate, String jobName, String command, String parameters, String workingDirectory, STScheduleRunAccount runAs, String userName, String domain, Byte[] encryptedPassword, STSchedule schedule)

      at ST.UI.Controllers.Scheduling.ScheduleConsoleTask.<ScheduleJobWithShavlikSchedulerAsync>d__5.MoveNext()

    --- End of stack trace from previous location where exception was thrown ---

      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

      at ST.UI.Controllers.Scheduling.ScheduleConsoleTask.<ScheduleJobAsync>d__2.MoveNext()

    --- End of stack trace from previous location where exception was thrown ---

      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

      at ST.UI.Controllers.Scheduling.PatchScan.<ScheduleConsoleTaskAsync>d__0.MoveNext()

    --- End of stack trace from previous location where exception was thrown ---

      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

      at ST.Protect.Forms.Workflow.OperationPresenter.<TryScheduleConsoleTaskAsync>d__0.MoveNext()



    Cause


    The reason this error occurs is due to too many characters within the job name [1.Name this operation (optional)]. The limitation is currently 53 characters. If you use 54 or more characters in this field it will cause the above error message to occur.


    jobName.jpg


    Resolution


    This issue has been marked as a defect by Shavlik engineering and should be fixed in a future version.


    The current workaround is to only use 53 characters or less when setting the job name.


    Affected Product(s)


    Shavlik Protect 9.x

    Shavlik Console Service

    $
    0
    0

    Hello,

     

    I have recently began experiencing issues with the Shavlik Console Service stopping unexpectedly which causes the scanning to freeze up. I have included both the errors that I receive each time this happens.

     

    Any help will be greatly appreciated...thanks,

     

    Paul

     

    Log Name:      Application

    Source:        Application Error

    Date:          7/21/2014 3:40:27 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      test.windsorfamily.com

    Description:

    Faulting application name: ST.ServiceHost.exe, version: 9.1.1012.0, time stamp: 0x533eec9d

    Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c

    Exception code: 0xc0000005

    Fault offset: 0x000000000002f3d6

    Faulting process id: 0x83c

    Faulting application start time: 0x01cfa51a67ae5baf

    Faulting application path: E:\Program Files\LANDESK\Shavlik Protect\ST.ServiceHost.exe

    Faulting module path: C:\Windows\system32\ole32.dll

    Report Id: dd5eca45-110e-11e4-9cf4-005056a96cdb

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>

        <Level>2</Level>

        <Task>100</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2014-07-21T19:40:27.000000000Z" />

        <EventRecordID>112254</EventRecordID>

        <Channel>Application</Channel>

        <Computer>test.windsorfamily.com</Computer>

        <Security />

      </System>

      <EventData>

        <Data>ST.ServiceHost.exe</Data>

        <Data>9.1.1012.0</Data>

        <Data>533eec9d</Data>

        <Data>ole32.dll</Data>

        <Data>6.1.7601.17514</Data>

        <Data>4ce7c92c</Data>

        <Data>c0000005</Data>

        <Data>000000000002f3d6</Data>

        <Data>83c</Data>

        <Data>01cfa51a67ae5baf</Data>

        <Data>E:\Program Files\LANDESK\Shavlik Protect\ST.ServiceHost.exe</Data>

        <Data>C:\Windows\system32\ole32.dll</Data>

        <Data>dd5eca45-110e-11e4-9cf4-005056a96cdb</Data>

      </EventData>

    </Event>

     

     

    Log Name:      Application

    Source:        .NET Runtime

    Date:          7/21/2014 3:40:26 PM

    Event ID:      1026

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      test.windsorfamily.com

    Description:

    Application: ST.ServiceHost.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: System.AccessViolationException

    Stack:

       at System.Management.IWbemServices.ExecMethod_(System.String, System.String, Int32, System.Management.IWbemContext, IntPtr, System.Management.IWbemClassObjectFreeThreaded ByRef, IntPtr)

       at System.Management.IWbemServices.ExecMethod_(System.String, System.String, Int32, System.Management.IWbemContext, IntPtr, System.Management.IWbemClassObjectFreeThreaded ByRef, IntPtr)

       at System.Management.SecuredIWbemServicesHandler.ExecMethod_(System.String, System.String, Int32, System.Management.IWbemContext, System.Management.IWbemClassObjectFreeThreaded, System.Management.IWbemClassObjectFreeThreaded ByRef, IntPtr)

       at System.Management.ManagementObject.InvokeMethod(System.String, System.Management.ManagementBaseObject, System.Management.InvokeMethodOptions)

       at System.Management.Automation.ManagementClassApdapter.InvokeManagementMethod(System.Management.ManagementObject, System.String, System.Management.ManagementBaseObject)

       at System.Management.Automation.BaseWMIAdapter.AuxillaryInvokeMethod(System.Management.ManagementObject, WMIMethodCacheEntry, System.Object[])

       at System.Management.Automation.Adapter.BaseMethodInvoke(System.Management.Automation.PSMethod, System.Management.Automation.PSMethodInvocationConstraints, System.Object[])

       at System.Dynamic.UpdateDelegates.UpdateAndExecute4[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Int64, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Runtime.CompilerServices.CallSite, System.__Canon, Int64, System.__Canon, System.__Canon)

       at System.Management.Automation.Interpreter.DynamicInstruction`5[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Int64, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.Interpreter.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.LightLambda.RunVoid1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)

       at System.Management.Automation.DlrScriptCommandProcessor.RunClause(System.Action`1<System.Management.Automation.Language.FunctionContext>, System.Object, System.Object)

       at System.Management.Automation.CommandProcessorBase.DoComplete()

       at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(System.Management.Automation.CommandProcessorBase)

       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(System.Object, System.Collections.Hashtable, Boolean)

       at System.Management.Automation.PipelineOps.InvokePipeline(System.Object, Boolean, System.Management.Automation.CommandParameterInternal[][], System.Management.Automation.Language.CommandBaseAst[], System.Management.Automation.CommandRedirection[][], System.Management.Automation.Language.FunctionContext)

       at System.Management.Automation.Interpreter.ActionCallInstruction`6[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.Interpreter.Run(System.Management.Automation.Interpreter.InterpretedFrame)

       at System.Management.Automation.Interpreter.LightLambda.RunVoid1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)

       at System.Management.Automation.DlrScriptCommandProcessor.RunClause(System.Action`1<System.Management.Automation.Language.FunctionContext>, System.Object, System.Object)

       at System.Management.Automation.CommandProcessorBase.DoComplete()

       at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore

    Scanning a remote machine using Protect fails with Error 452: Unable to connect to the remote machine

    $
    0
    0
    Symptoms

     

    • Cannot scan a remote machine with Protect 
    • Scanning a remote machine in Protect fails with the following error: 
      Error 452: Unable to connect to the remote machine

     

    Cause

     

    This issue occurs if one or more scanning prerequisites are not met, usually due to a configuration issue.
      

    Resolution

     

    To resolve this issue:

    1. Reboot the Protect console machine. 
    2. Verify if the Server and Remote Registry services are enabled on the remote machine and that you can remotely log in to this machine.

      To test the remote registry connection:
      1. Click Start> Run, type regedit, and click OK. The Registry Editor window opens. 
      2. Click File> Connect Network Registry.
    3. Ensure that the Workstation service is running on the machine performing the scan. 
    4. Check if there is already a connection between the server and scanned device and that this connection is using a different set of credentials than the Protect patch server. In this case,the Protect patch server cannot establish the connection. If the target machine being scanned is already connected to the scanning server via a drive mapping, the scan fails 
    5. Try scanning the target machine using both IP and Name. 
    6. Test the admin share using this command:

      net use\\machine_name\IPC$/user:domain\ username password

      Note: Provide the actual name of the machine you are trying to scan, along with the same credentials that you are attempting to scan with. You can substitute machine_name with domain if you are using local credentials.
    7. Check the Local Area Connection properties on the target machine to ensure that File and Printer sharing is enabled. 
    8. Try lowering your thread count for simultaneous machines scanned in the scan template to see if this eliminates the error. To do this, navigate to Scan template> General tab.

      For more information on scanning prerequisites, see this article: http://community.shavlik.com/docs/DOC-23019

    Additional Information

     

    Microsoft provides a patch to resolve this issue in a specific scenario. To verify if this is applicable, open a command prompt and run these commands:

     

    sc.exe \\Target_Computer_Namequery
    sc.exe
    \\Target_IP_Addressquery

     

    If sc.exe using Target_Computer_Name works, but sc.exe using Target_IP_Ad does not work, you must apply these patches: In the console machine:

    • For Windows Server 2008, 2008 R2 and 7, apply either SP1 or the patch described in the Microsoft Knowledge Base article 2194664
    • For Windows Server 2003 and 2003 R2, apply the patches described in the Microsoft Knowledge Base articles 975467 and 968389.

    In the target machine:

    • For Windows Server 2008, 2008 R2 and 7, there are no available patches and this issue is not seen to occur in these target operating systems. 
    • For Windows Server 2003 and 2003 R2, apply the patches described in the Microsoft Knowledge Base articles 975467 and 968389.

    Affected Products

     

    Shavlik Protect 9.x

    vCenter Protect 8.x

    Viewing all 2126 articles
    Browse latest View live


    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>