Creating Installation Package for Linux-Clients

I need a solution

Hey Guys

I just started testing / working with Symantec Endpoint Protection Version 14.2.1. I’d like to install a Linux Client, but I can’t really figure out how. Regarding to some tutorials you should create an installation package manually, but I’m not able to find the default Package-Path to create a new Package (I already searched my drive for *.info and *.zip Files, but I can’t find the default files).

Can you guys explain to me what I exactly have to do to create a linux installation package?

Thanks for your help.

Kind regards

Gabe

0

Related:

  • No Related Posts

Client push error.

I need a solution

Unable to client push SEP on other machines. it is possible when i take RDP of the machine and copy the setup and install the endpoint protection.

machine is already in domain. But not able to client push SEP. The error is like “Failed to download and/or install the remote Installation Service. A logon request contained an invalid type value.”

Error: -2   ApiError: 0  Message: Failed to download and/or install the remote Installation Service. A logon request contained an invalid logon type value.

0

Related:

  • No Related Posts

Citrix Hypervisor – Paravirtualized VM won't boot after upgrade to Hypervisor 7.0

Updated the following files that are used to boot the XS installer to match the current version being installed, on this particular case, files on the TFTP server were from previous Hypervisor version 6.x

mboot.c32

pxelinux.0

These files are needed on a TFTP server according to the Network Boot Installation process described here:

https://docs.citrix.com/en-us/xenserver/7-1/install/network-boot.html

Related:

  • No Related Posts

Policy and Managed Software Delivery

I need a solution

Up until now, we hvae not worked with a software policy or managed software delivery.

In going through the process for each, they appear to be the same to me- both use a software package to install and  remediate if not found on the client pc.  Is there a difference between the two?

Is one more appropriate for a software delivery, installation and remediation than the other?

0

Related:

  • No Related Posts

Client Installation for Linux

I need a solution

I have downloaded the SEP 14.2 trialware to install on our integration and test system, however I am unable to find the Linux client installation package, most of the clients are CentOS.  Is it possible that I can be provided with the software?  Both auto-compile and manual compile (if they are different) thanks.

I tried the online chat for support, they sent me here. 🙂

0

Related:

  • No Related Posts

Anti tampering featurer is not being installed properly for unified agent

I need a solution

Hi;

When I install the MSI using the command:

bcuaXX-setup.msi /qn CM_URL=https://proxysgip:8084 SUP=123456 FORCEREBOOT=no, the installation succeedes but the anti-tampering feature does not work. So when the user tries to uninstall the unified agent, she/he does not get asked for the anti-tampering password.

Kindly

Wasfi

0

1559623199

Related:

  • No Related Posts

Trying to install Symantec Endpoint Protection on my new Laptop. Get error message 0x80070002

I need a solution

Hi I just got a new laptop. It’s running Windows 10 Home Version 1809, 64-bit operating system, x64-based processor. When I try to install Symantec Endpoint Protection I get the follow message:

“The installer integrity check failed with error code 0x80070002. Common causes for this failure inslude an incomplete download, damaged media, or problems with the trusted Root certificate store.”

Can any one help me? I have deleted and redownloaded the installation files multiple times, and I always get the same mesage.

0

Related:

  • No Related Posts

How to Troubleshoot XenApp and XenDesktop MSI Installation or Upgrade Errors

Table of Contents

Pre-requisites

You need Administrator rights on your account to perform the steps listed in this article. Check User Accounts to see if you have Administrator rights or contact your Network Administrator to gain permissions.

Back to top

Troubleshooting Steps

Rectify Incomplete Installation which could interrupt any future installations

When an installation does not complete or roll back successfully, some files may remain in the system. Windows Installer considers the incomplete installation to be active and does not install new products or re-install existing products until the installation is resolved. Follow the instructions in this article to resolve this issue: Error: When Trying to Install or Remove XenApp Software, a 1603 Error Message is Displayed

Back to top

Troubleshoot/Resolve issues using Citrix MSI Log Analyzer

Citrix MSI Log Analyzer is a tool that troubleshoots install issues or upgrade issues and enables customers to resolve common issues by pointing them to a specific support article.

Note. You may skip this step if you were pointed to this article by the MSI Log Analyzer tool or the XenApp Xendesktop 7.16 Metainstaller, which has been integrated with the MSI Log Analyzer.

  1. Follow instructions in CTX229734 to download the latest version of the tool on the target machine where the installation failed occurred. Citrix recommends that you obtain the latest version of the tool.

Review these additional troubleshooting steps, in cases where steps above did not resolve the issue

Back to top

Resolve issues which could be due to corruption

Though the exact cause may vary from case to case, there could be a sign of corruption in registry, Performance counters, WMI providers, C++ Runtimes or or .NET Installation.

This guide begins with the least intrusive methods to help troubleshoot these issues. It is not intended to be an exhaustive guide, but it should be able to provide solution for the majority of these issues.

  1. Fix problems that block programs from being installed or removed

    Refer to this article for more information.

  2. Repair Missing or corrupted System files

    Run ‘sfc /scannow’ both in online and offline mode. Refer to this link for more details.

  3. C++ RunTime

Occasionally, the C++ redistributable packages are corrupted or inconsistent which may cause installations and upgrades to fail.

  1. Each XA/XD release comes with the system requirements. For example: 7.15 requirements are available here.

    Note: For your case open the link specific to the XA/XD release version being installed

  2. In the page, refer to the section on Virtual Delivery Agent(VDA) for Desktop OS and Server OS which provides details on the specific Microsoft Visual C++ runtimes.

    User-added image
    For example: As shown above VDA 7.15 on Desktop OS needs VC++ 2013 and 2015 runtimes. Depending on the version you are installing the runtime versions for those VDA may be different.

  3. The version mention in the documentation list the year. Follow the below steps to note down the File Versions of the actual msi of the VC++ runtime. Open/Mount the XenApp/Xendesktop ISO layout and browse to the Support folder. For each VC++ runtimes noted in step ii above browse to that sub-folder within the Support folder. For each of those, Right click the vcredist msi file under the respective VCRedist folder, Click Properties and Note down the File Version under Details tab. Make a note of all the 4 parts separated by dot for each vcredist msi file.

    User-added image

  4. Launch Control Panel and under Installed Program list note down all the VC++ runtime versions with the dots. If any of the version noted in step above is missing then one should install the specific version from the support folder under the Layout. On a 64 bit machine, both 32 bit and 64 bit versions are required to be installed. If all versions are present in the control panel then there might be some corruption in which case it is recommended to uninstall and reinstall those specific versions.

Test to install again and see if the problem persists.

  1. .NET Repair

    1. Follow steps here https://support.microsoft.com/en-us/help/2698555/microsoft–net-framework-repair-tool-is-available to repair .NET
    2. Test to install again and see if the problem persists.
  • Performance Counters

    Verify that the Performance Counters can be reloaded by opening an elevated CMD shell and type the following commands ( hit [ENTER] after each line) :

    cd c:windowssystem32

    lodctr /R

    cd c:windowssysWOW64

    lodctr /R

    Resync the counters with Windows Management Instrumentation (WMI):

    WINMGMT.EXE /RESYNCPERF

    Stop and restart the Performance Logs and Alerts service.

    Stop and restart the Windows Management Instrumentation service.

    Check the event viewer for any errors.

  • WMI Repository Corruption

    If failures happen due to WMI corruption, for example, “RegisterEventManifest” or any other failure related to WMI, in the MSI failing log, please see Telemetry or CDF MSI fails to install or upgrade due to WMI repository Corruption.

Test to install again and see if the problem persists.

Back to top

Issues caused due to permissions or access issues

  1. Citrix MSI Log Analyzer output may point to the file/registry location where one should assess the permissions and ensure the administrator installing the VDA has necessary permissions. If not grant permission and try the installer again
  2. Try to temporarily move the VDA out of the OU enabled GPO and try installation once again, then move the VDA back to previous OU post the successful installation.

Back to top

Other causes to check

  1. You may receive this error message if any one of the following conditions is true:
  2. Windows Installer is attempting to install an app that is already installed on your PC.
  3. The folder that you are trying to install the Windows Installer package to is encrypted.
  4. The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
  5. The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.
  6. Sometimes AntiVirus may interfere with the installations. Disable the anti-virus software and attempt the installation.
  7. In some cases it is observed running in as a domain instead of a local Administrator or vice versa may help resolve the issue.

Back to top

What Next?

This really boils down to an OS based problem in most cases. Here are some solutions that have worked in other support cases.

  1. There is a deeper fix that can rebuild the performance counters from scratch. See links below.
  2. Admins can re-register the Windows installer service and look at other general Windows MSI repair options.
  3. Admins can attempt a repair install of Windows.
  4. If none of these steps delivers a resolution, further data can be captured by collecting MSI logs and running CDF Control on the machine while the installer runs.
  5. Links provided in the Additional Resources section.

Back to top

  1. Use the VDA Cleanup Utility

As a last resort, Download the utility from here and execute it as an administrator on the target machine. Try the installation again to see if it works.

Back to top

Related:

SEPC Installation Package Refresh

I need a solution

Hello all,

First time poster on this forum. I have a question regarding the latest 22.17 Windows upgrade. The upgrade news article states the following:

    Action Required

    Windows device restart
    All users with Windows devices will be prompted to restart their devices after the update. Even if they delay the restart, their Windows clients remain protected.

    Windows installation package refresh
    Administrators who created a Windows installation package before April 3 should create and distribute a new one after April 3 to use for new Windows package deployments.

    As a hub with multiple sites (and multiple installation packages) does this mean we will need to recreate all the installation packages?

    0

    1554209202

    Related:

    • No Related Posts