App Layering: Advice for layering Solidworks, and other applications with prerequisite libraries and modules

This problem has been seen specifically with SolidWorks, which wants to install a .NET update and six different Runtime DLLs during the software install, but could easily apply to any complicated application, including some broker agents (VDAs) like the XenDesktop or XenApp agents.

For instance, this is the list of the specific prerequisites that SolidWorks was installing in the app layer:

Required system components will be installed (217 MB): Check For Updates, Microsoft C++ 2005 Redistributable (x64), Microsoft C++ 2005 Redistributable, Microsoft C++ 2008 Redistributable, Microsoft C++ 2010 Redistributable (x64), Microsoft C++ 2010 Redistributable, Microsoft Office 2003 Web Components, Visual Studio Tools, VBA 7.1, VBA 7.1 (English), VBA 7.1 (KB 2783832), Bonjour, Microsoft SQL Native Client, swactwiz and Visual Studio Remote Debugger.

All those Redistributable packages really need to be in the OS layer, not the app layer. So install them in the OS, and then create a new app layer based on the new OS, and it should work. OS-like software installations are a problem in app layers, especially if there might be conflicting versions in multiple layers. Make sure all OS-like software is installed in the OS before creating the app layer.

Related:

App Layering: How to specify or disable SSL protocols and ciphers in the ELM

The Apache SSL configuration is contained in /etc/httpd/config.d/ssl.conf. This file can be edited manually while logged in as the root account. The ELM contains VI, EMACS and Nano as text editors. If you’re not already familiar with EMACS and VI, we recommend Nano as the most user friendly editor.

  1. Edit ssl.conf with a command like this:

    nano /etc/httpd/conf.d/ssl.conf

  2. Scroll down to this section:

    ##

    ## SSL Virtual Host Context

    ##

  3. Edit or add these three lines in that section as necessary:

    SSLProtocol TLSv1.2 -SSLv3

    SSLHonorCipherOrder On

    SSLCipherSuite ALL:!EXP:!NULL:!ADH:!LOW:!SSLv2:!SSLv3:!MD5:!RC4

  4. Save the file and reboot the ELM.

Beware that this may invalidate any imported certificates, so be careful. It is worth creating a VM snapshot before performing this edit, so you can revert if it breaks your ability to login to the ELM.

Related:

App Layering: Advice for layering JAWS, ZoomText, and other software with WDM/mirror drivers

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

How to script removing and rescanning “Ghost NIC” devices in Windows

Download the Microsoft WDK so you can get a single stand-alone program called devcon.exe. Start here:

https://developer.microsoft.com/en-us/windows/hardware/windows-driver-kit

Jump right to “(2) Install WDK for Windows 10, version 1709”. It’s not specific to Windows 10, it covers every Windows build up to W10 1709. Install that on any machine, and find C:Program Files (x86)Windows Kits10Tools.

In the “x64” directory, grab devcon.exe. That is the only file you need from that distribution for this exercise.

Let’s assume we need to remove and recsan all VMware VMXNet3 network devices. These are VEN_15AD&DEV_07B0, but it should be sufficient to search just for the device ID number. To remove any present and nonpresent devices whose identifiers contain “dev_07b0”, run these two commands:

foreach /f “delims=:” %x in (‘devcon findall *dev_07B0*’) do devcon remove “@%x”

devcon rescan

The first command runs “devcon findall *dev_07b0*”, which returns every device, present or nonpresent, which contains that string in the registry identifier. And it then runs “devcon remove” on the identifiers returned, to remove them. The second command triggers a device rescan/reinstall.

If you want to put whose in a script instead of running them manually, change each %x to %%x. If it works from a CMD prompt, it’s possible to set it up as a script to run on every boot, or any other circumstance where you might need to do this.

Related:

App Layering: ELM will not boot, Operating System Not Found because boot disk is on the wrong SCSI port

On every ELM are at least two SCSI disks, and potentially more if the layer repository has been expanded. Initially, though, there is a 30GB disk on SCSI 0:0 and a 300GB disk on SCSI 0:1. The boot disk is the 30GB one, and the initial Layer Repository disk is the other. You can add additional disks and append them to the Layer Repository volume, and/or expand the initial 300GB disk, creating more disks or differently-sized ones.

Any of the other disks can be placed on any other SCSI port,because the Linux Logical Volume Manager (LVM) recognizes disks by their data, not their port location. But the 30GB boot disk must remain on SCSI 0:0 so that the virtual machine will boot from it. It it somehow moves and any other disk is at SCSI 0:0, it will not boot.

Edit the VM and move the disks around so that the 30GB boot disk is back on SCI 0:0. Note that if you miss putting back any of the Layer Repository disks, you may be unable to locate or use any layers until you do put all the pieces back.

If you are using a hypervisor with VM BIOS settings that allow you to choose the disk to boot from, make sure it is also set to boot from SCSI 0:0.

Related:

Which NetScaler functions maybe affected by a full /var/ partition

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

XenDesktop 7.15 – “Tablet Input Service” getting enabled after installing VDA software

1. Why is the service “Tablet Input Service” set to automatic by the Citrix VDA install?

Answer :

Tablet input service is a windows service and helps optimize windows for tablet PC’s with touch screens.

It can be disabled on purpose via group policy to optimize performance on Thin clients / Normal Pc’s(Non-touch) where the service isn’t required.

https://www.windows-security.org/windows-service/tablet-pc-input-service.


2. Why is this service required ?

Answer :

We install Multi touch driver, device and service.

This is part of ICAWS installation ( Desktop VDA).

The MS service is required to avoid issues like: https://support.citrix.com/article/CTX220770

We are not sure if we actually enable the service or this is default Microsoft behavior when the touch device is detected.

(service depends on: PnP{Plug and Play})

Following behaviors is noticed :

  • Device disabled – service stopped:

User-added image

  • This is happens when you enable device:

User-added image

Related:

[XenDesktop 7.14.1] XD SQL Transaction log growing excessively

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

FAQ: SNMP on NetScaler Appliance

This article contains frequently asked questions about the Simple Network Management Protocol (SNMP) in the NetScaler appliance.

Q: Is the SET operation for SNMP supported on the NetScaler appliance?

A: No. By default, the NetScaler appliance does not support the SET operation for SNMP. However, if you want to enable the SET operation for SNMP on the NetScaler appliance, contact the Citrix Support team.

Q: What SNMP operations are supported when a community is GET on the NetScaler appliance?

A: When a community is GET, only the SNMP GET is supported. The SNMP GetNext or bulk operations are not supported on this community.

The following is an example for the operations supported on this community:

test# ./snmpget -c private <Host_Address> system.sysDescr.0SNMPv2-MIB::sysDescr.0 = STRING: NetScaler NS9.0: Build 69.5, Date: Jun 12 2009, 06:00:53test# ./snmpgetnext -c private <Host_Address> system.sysDescr.0Timeout: No Response from <host>

Q: What is the procedure to load a Management Base Information (MIB) file to the SNMP Manager on a NetScaler appliance?

A: The procedure to load an MIB file to the SNMP Manager depends on the type of the SNMP Manager. Use any of the following procedures to load an MIB file to the Net SNMP Manager:

To load the MIB file to a UNIX based server by copying it, complete the following procedure:

  1. Copy the MIB file to the /usr/local/share/snmp/mibs/ directory.

    Note that the mibs directory location might vary between different UNIX distributions.

  2. Open the snmp.conf file in a text editor, such as the vi editor.

  3. Add the following entries to the file:

    mibs +IF-MIB

    mibs +NS-ROOT-MIB

  4. Save and close the file.

  5. Run the following command:

    net-snmp-config –snmpconfpath

To load the MIB file by running the snmp command on a UNIX based server, run the following command:

./snmpget -m ./NS-MIB-smiv2.mib -c public <Host_Address> httpTotResponses.0

NS-ROOT-MIB::httpTotResponses.0 = Counter64: 368

Q: How can you identify the object values from the trap messages on the NetScaler appliance?

A: The SNMP Manager receives the netScalerConfigChange trap message when a virtual server is enabled or disabled. The following is the MIB definition for the trap message:

netScalerConfigChange NOTIFICATION-TYPE OBJECTS { nsUserName , configurationCmd , authorizationStatus , commandExecutionStatus , sysIpAddress } "This trap is sent when the configuration on the NetScaler is changed." ::= { netScalerEventsV2 25 } 

The following is the sample output of the trap message:

2009-08-19 22:02:05 10.102.14.230 [UDP: [0.0.0.0]->[10.102.14.230]:3000]:DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (111347565) 12 days, 21:17:55.65 SNMPv2-MIB::snmpTrapOID.0 = OID: NS-ROOT-MIB::netScalerConfigChangeNS-ROOT-MIB::nsUserName.0 = STRING: "nsroot" NS-ROOT-MIB::configurationCmd.0 = STRING: "disable lb vserver namivserver"NS-ROOT-MIB::authorizationStatus.0 = INTEGER: authorized(1) NS-ROOT-MIB::commandExecutionStatus.0 = INTEGER: successful(2) NS-ROOT-MIB::sysIpAddress.0 = IpAddress: 10.102.14.2302009-08-19 22:02:05 10.102.14.230 [UDP: [0.0.0.0]->[10.102.14.230]:3000]:

In the preceding sample, the authorizationStatus.0 object has the authorized(1) value. The entry in the output is highlighted in bold face for your reference.

Q: On a NetScaler appliance, is it possible to receive a trap message on the SNMP Manager by using a different port than the default port?

A: Yes. By default, the trap messages are received on port 162. You can run the following command to set another port to receive the trap messages on the SNMP Manager:

./snmptrapd -c /root/snmptrapd.conf -P udp:<New_Port_Number>

Q: Does the NetScaler appliance support the inform messages?

A: No. The NetScaler appliance does not support the inform messages.

Q: What are the commands to configure SNMP on a NetScaler appliance?

A: You can run the following commands to configure SNMP on a NetScaler appliance:

add snmp community <Community_Name> <Access>

add snmp trap generic <Manager_Address>

add snmp trap specific <Manager_Address>

You can also run the following command to enable threshold value related alarms:

set snmp alarm <Alarm_Name> -time <Threshold_Value>

Q: What is the location of the NetScaler MIB file?

A: The NetScaler MIB files, NS-MIB-smiv1.mib and NS-MIB-smiv2.mib, are available in the /netscaler/snmp directory of the NetScaler appliance or in the Downloads section in the GUI. All Object IDs (OIDs) are available in the mib.txt and trap.txt files available in the /netscaler/snmp directory.

Additional Resources

SNMP version 3 queries are now supported on the NetScaler SDX appliance. SNMPv3 enhances the basic architecture of SNMPv1 and SNMPv2 to incorporate administration and security capabilities, such as authentication, access control, data integrity check, data origin verification, message timeliness check, and data confidentiality.

NetScaler 12 OID Reference

Question:

Can we Disable SNMP v1 because Set “add snmp community citrix All” from NetScaler Device will enable both SNMP v1 and v2.


Answer: Deactivation of the a specific snmp version is not supported.

Question:

Does SNMP Monitoring work for Admin Partitions ?

Answer:

Yes, SNMP Monitoring is supported in NetScaler firmware 12.0-56.x and above.

The SNMP Get and Walk functionalities are now supported on a partitioned NetScaler appliance for monitoring resource utilization details such as bandwidth, memory, or connection resources.

This was worked under the enhancement request – ENH0676597

Question:

Can we Disable SNMP v1 because Set “add snmp community citrix All” from NetScaler Device will enable both SNMP v1 and v2.


Answer: Deactivation of the a specific snmp version is not supported.

Question : Customer needs to monitor the individual interface statics via SNMP. Does NetScaler have OIDs to gather information on per interface basis?

Answer : Currently NetScaler doesn’t have SNMP OIDs to monitor the traffic per interface level. Netscaler has option for cumulative values only.

An Enhancement 0695767 is raised to add this functionality to NetScaler

Related:

Error: “VirtualMachineSnapshotNotFound” When Updating Machine Catalog

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts