How to Collect Diagnostic Bundle Files from a NetScaler Appliance

Complete the following procedure for MPX and VPX appliances:

Complete the following procedure for SDX appliances:

Running the Collector Script in NetScaler Software Release 9.2 and Later

To obtain the collector file by using the NetScaler GUI, complete the following procedure:

Note: In NetScaler software release 9.2 and later, you can run the showtechsupport script from the Graphical User Interface (GUI) and the Command Line Interface (CLI).

  1. Open the Configuration Utility with the NetScaler Management IP address from a web browser.

  2. Expand the System node.

  3. Select the Diagnostics node.

  4. Click the GenerateSupportFile link under the Technical Support Tools section.

To obtain the collector file by using the NetScaler CLI, complete the following procedure:

Download the file from the appliance using a Secure FTP (SFTP) or Secure Copy (SCP) utility, such as WinSCP, and upload it to Citrix Insight Services for analysis.

Note: In NetScaler software release earlier than 9.0, the collector script must be downloaded separately and executed.

Note: In case of Netscaler in Cluster deployment please use the following CLI command to generate the collector file:

> show techsupport -scope CLUSTER

This will collect show techsupport information from all nodes in the cluster and compress the files into a single archive.

In order to generate the collector file from Graphical User Interface (GUI) please select “Partition” option from the Scope

  • Click Run and wait for the script to generate the collector archive.

  • After the appliance generates the collector archive, download and save the file on your local computer before uploading it to Citrix Insight Services.

    1. To obtain the collector file by using the CLI, run the following command:

      show techsupport

      After the appliance generates the collector archive the location of the file is displayed as shown in the following screen shot:

      User-added image

      The file is stored in /var/tmp/support and you can verify this by logging in to NetScaler and running the following command from a shell prompt:

      root@NS# cd /var/tmp/support/

      root@NS# ls -l

      total 2drwxr-xr-x 7 root wheel 512 Sep 25 15:38 collector_P_10.10.1.1_25Sep2014_15_38root@NS#

Uploading and Running the Collector Script on a NetScaler Appliance

To upload and run the updated collector script on a NetScaler appliance, complete the following procedure:

  1. Copy the updated collector script showtechsupport.pl (attached with this article) to the /nsconfig directory of the NetScaler appliance. Use an SFTP or SCP utility, such as WinSCP, to copy the file to the NetScaler appliance.

  2. Run the following commands from the CLI of the appliance:

    > shell

    # cd /nsconfig

    # chmod +x showtechsupport.pl

    # ./showtechsupport.pl

  3. Switch to the CLI of the appliance.

  4. Run the following command to create log files for analysis:

    > show techsupport

    The collector_<NSIP>_<P/S>_<DateTime>.tgz file is created in the /var/tmp/support directory of the appliance.

    Note: You must then upload the .tgz file to Citrix Insight Services for analysis.

  5. If you must uninstall this script, run the following commands from the CLI of the appliance:

    > shell

    rm /nsconfig/showtechsupport.pl

Collecting a Full Diagnostics Bundle from NetScaler SDX

  1. Open the NetScaler SDX Configuration Utility with the NetScaler SDX Management IP address from a web browser.

  2. Expand the Diagnostics node.

  3. Select the Technical Support node.

  4. Click Generate Technical Support File.

  5. Select Appliance (Including Instances) from the drop-down menu.

  6. Click Add.

  7. Select one or more instances to add in.

  8. Click OK. Wait for the process to complete.

  9. Select the bundle name that was generated and then click Download.

  10. Upload the bundle file to Citrix Insight Services.

For information on collecting/deleting NetScaler SDX support bundle using CLI/serial console refer to Citrix Documentation.

Related:

  • No Related Posts

Windows 10 updates KB4487029, KB4487021, KB4487011 and KB4487006 released

Microsoft released several cumulative updates for different Windows 10 versions on February 19, 2019. The cumulative updates KB4487029, KB4487021, KB4487011 and KB4487006 update Windows 10 version 1803, 1709, 1703 and 1607 but not the current version 1809.

Only the Enterprise editions of Windows 10 version 1607 and 1703 are supported. Home and Pro editions of these versions of Windows 10 are no longer supported; in other words: you need to upgrade the operating system to a supported version to receive continued support with updates.

Note: These are not security updates; they fix stability and other issues only. It is recommended that you back up your system before you install the updates or wait if you are not affected by any of the listed issues.

And Windows 10 version 1809? Microsoft pushes cumulative updates for the current version of Windows 10 to the Release Preview ring first before release. It is likely that an update will be released in the coming days / week.

KB4487029 for Windows 10 version 1803

KB4487029

Windows 10 version 1803 is the most used edition of Windows 10. Microsoft launched Windows 10 version 1809 last year but bugsforced the company to stop the distribution of the operating system for weeks.

The update increases the build of the operating system to 17134.619. The following changes are listed in the changelog:

  • Media Content can play e-learning content with USB adapter cables on Microsoft Edge.
  • Windows ActiveX content in iframes scrolls with other content in Internet Explorer 11.
  • Fixed an issue that caused Registry keys that are app-specific to be deleted after updates.
  • Time Zone information for Chile updated.
  • Fixed an audio compatibility issue of games with 3D Spatial Audio modes.
  • Fixed an issue that prevented users from pinning web links to Start or the Taskbar.
  • Fixed an issue that prevented the lockscreen image from updating.
  • Improved the performance of case-sensitive string comparison functions.
  • Fixed an compatibility status evaluating issue.
  • Improved the reliability of the UE-VAppmonitor.
  • Fixed a user hive updating issue.
  • Fixed an issue that allowed protected files (by Windows Information Protection) to be transferred using Bluetooth.
  • Fixed an issue with Internet Explorer proxy settings that caused the initial logon to stop responding.
  • Fixed an issue that prevented the deletion of wireless network profiles.
  • Addressed the cause for error “STOP 0x1A”.
  • Fixed a Timeline issue that caused File Explorer to stop working.
  • Fixed an issue that caused the Photos app to stop working when used from within the Mail app.
  • Fixed a PLMDebug.exe tool issue that caused the losing of debug sessions.
  • Improved AOVPN (Always On VPN) reconnect and disconnect functionality.
  • Further Japanese era name issue fixues.
  • Fixed an issue that caused Internet Explorer to skip loading images that have a backslash character in their relative source path.
  • Fixed an issue that caused applications that use Microsoft Jet Databases with Microsoft Access 95 formats to stop working.

You can download the update manually from the Microsoft Update Catalog website.

KB4487021 for Windows 10 version 1709

KB4487021

The update includes some of the fixes found in the update for Windows 10 version 1803 but not all of them. It does include some fixes that are not included in the update for version 1803.

The update increases the build to 16299.1004.

The changelog lists the following fixes and improvements:

  • Time Zone information for Chile updated.
  • Improved the performance of case-sensitive string comparison functions.
  • Fixed an compatibility status evaluating issue.
  • Improved the reliability of the UE-VAppmonitor.
  • Fixed a user hive updating issue.
  • New Group Policy called “Policy Details” that disconnects any wireless connections immediately when a wired connection is detected and “Minimize simultaneous connections” is configured.
  • Additional Japanese era date and format fixes.
  • Fixed the Internet Explorer not loading images with backslash characters in path issue.
  • Fixed an issue that caused applications that use Microsoft Jet Databases with Microsoft Access 95 formats to stop working.

You can download the update manually from the Microsoft Update Catalog website.

KB4487011 for Windows 10 version 1703

KB4487011

The update is only for Windows 10 Enterprise and Education editions. The update brings the build to version 15063.1659.

It includes the same updates as KB4487021 with the exception of the following exclusive additions:

  • Fixed an issue that caused programs to stop responding if its threads share the same input queue.
  • Addressed an issue with a rooted pointer to an item identifier list (PIDL) in File Explorer

The update is available on the Microsoft Update Catalog website as a manual download.

KB4487006 for Windows 10 version 1607 and Windows Server 2016

KB4487006

The update bring the version of the operating system to 14393.2828. It is only available to Enterprise and Education editions.

The changelog lists the following improvements:

  • Chile Time Zone information update.
  • Fixed an issue that caused Remote Desktop Protocol client applications to display a black screen on login.
  • Improved the performance of case-sensitive string comparison functions.
  • Fixed an compatibility status evaluating issue.
  • Improved the reliability of the UE-VAppmonitor.
  • Fixed a user name display issue in the Routing and Remote Access Service (RRAS) servers.
  • Addressed an issue that caused updates to a relying party trust to fail when using PowerShell or the Active Directory Federation Services (AD FS) management console.
  • Fixed an issue that caused “specific error message for external complexity password changes” to display.
  • Fixed an issue that caused Microsoft Outlook to throw the error “The Operation Failed” when viewing Microsoft Exchange address books.
  • Fixed an issue that prevented the enabling of Storage Maintenance Mode.
  • Fixed a server stop working error when handling a compound client request that includes a rename.
  • Fixed error 0x165 when pausing a node and taking it down for maintenance.
  • Fixed a cause for Stop 24 error on a virtual Remote Desktop Service server.
  • Fixed an issue with Japanese era names.
  • Fixed a reliability issue with win32kfull.sys.
  • Fixed the Internet Explorer not loading images with backslash characters in path issue.
  • Fixed the Microsoft Jet database access issue.

Microsoft lists three known issues, all known already:

  1. For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.
  2. After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.
  3. After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.

The update can be downloaded manually from the Microsoft Update Catalog website.

Summary
Windows 10 updates KB4487029, KB4487021, KB4487011 and KB4487006 released
Article Name
Windows 10 updates KB4487029, KB4487021, KB4487011 and KB4487006 released
Description
Microsoft released several cumulative updates for different Windows 10 versions on February 19, 2019.
Author
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
Advertisement

Related:

  • No Related Posts

Open Enterprise Server 2018 SP1 – Now Available!

Nick Scholz

Micro Focus is pleased to announce the availability of Open Enterprise Server 2018 Service Pack 1, which includes plenty of exciting features and enhancements. Open Enterprise Server 2018 SP1 Highlights include: CIFS Performance/Specification Compliance – Folder Redirection allows users to redirect the path of a known folder to NSS AD network file share. Users can then …

+read more

The post Open Enterprise Server 2018 SP1 – Now Available! appeared first on Cool Solutions. Nick Scholz

Related:

  • No Related Posts

SEP 14 & VMWare Workstation 15 Player

I need a solution

I am using SEP 14.2 build 1031 on Windows 10 Pro 1809 build 17763.292 and VM Workstation 15 Player.

I have found that if I install the Network Intrusion Prevention / Firewall components of SEP that it inherently blocks incoming network access to any virtual machines.  I could see this if I used NAT configuration for the VM but I am using Bridged, which means that as far as the network and host machine are concerned this should behave like it’s own entity.

I have Googled the problem and the closest solution I have found is essentially put an allow all rule in the Symantec firewall, which seems to defeat the purpose entirely.  How do I configure SEP allow traffic into and out of a VM without haivng to effectively turn off the firewall on host machine?

0

Related:

  • No Related Posts

XenDesktop VDA Installation – Optional Components

The default Virtual Delivery Agent (VDA) software (Desktop OS) installation includes several optional components that some customers might not require depending on their specific use cases. This article provides instructions for excluding one or more of these optional components using command line, for example – Personal vDisk, Citrix User Profile Manager.

Requirements

Basic MSI installation scripting knowledge.

Background

Certain customer use cases might not require several optional components included with the default VDA software installation. For example, installing/upgrading the VDA software on virtual machine images not managed by Machine Creation Services will not require the Personal vDisk. Similarly, some customers might not require Citrix User Profile Management.

Refer to Citrix Documentation – Command line options for installing a VDA for more information.

Related:

  • No Related Posts

Can't create App Layering image for MCS in Azure, hangs during Windows Setup

To deploy an MCS image to Azure, you decide to use the Azure connector in App Layering. This produces a virtual disk that is primed to run through Windows Setup. You attach it to a VM, power it on, and find that Windows Setup never completes. If you look at the console screen shot in the debugging page in Azure, you see an image like this:


That is a black screen that says Getting Ready, with a CMD (command prompt) window titled ERROR HANDLER, at the path C:Windowssystem32oobe. This means Windows Setup failed. You can download the VHD and open it up to read Windowssetupact.log, Windowspanthersetupact.log, WindowslogsCBScbs.log, but that won’t help too much.

Related:

  • No Related Posts

Unified Endpoint Management with the Latest Release of ZENworks 2017

Gil Cattelain

As an organization grows, the often-fragmented endpoint management that worked in a smaller company starts to present a significant risk. Scaling requires a user-centric approach with a focus on security and self-service access to your organization’s most necessary applications. Cloud-based apps that offer universal access from any device are flexible, but legacy support is equally …

+read more

The post Unified Endpoint Management with the Latest Release of ZENworks 2017 appeared first on Cool Solutions. Gil Cattelain

Related:

  • No Related Posts

Can't edit App layer, boot error 0xC000000F; but OS and Platform Layers work OK

First, verify this is not https://support.citrix.com/article/CTX238440 . The error message is normally different, but that’s the most likely cause: language issues.

Second, Add Version to your OS layer, run CMD As Administrator, and do the following. This will trigger a new scan of critical OS system files to update our list of critical system files.

CD Program FilesUnideskUniservice

Uniservice.exe /B

<Reboot>

Then finalize that and test creating a new app layer again.

Otherwise, this is a system driver that has not been properly copied to the boot disk. This does not apply to OS and Platform layers because the boot disk is handled differently. But with App Layers, the boot disk is a thin disk that contains just enough Windows to get minifilter drivers running. 0xC000000F means we missed copying something to the boot disk.

Unfortunately, you can’t tell what we missed. What you need to do is version your OS layer to get a record of a successful boot. Login, run msinfo32, Boot, and enable Boot Logging. This will create a boot log file called C:Windowsntbtlog.txt that conatins, in order, every file loaded during boot. Reboot to generate the log, and copy it to a file share. Leave the packaging machine for the OS layer open, you will need it again in a minute.

On the packaging machine for the App Layer that fails to boot, attach your Windows installer ISO. Boot from that. When you get the the first Windows Setup dialog, type Shift-F10, which will bring up a command prompt window. In this machine, X: is the CD-ROM, C: is the mini boot disk, D: is the OS layer, and E: is the package disk. We care about C: and D:. Specifically, we care about what is in D: that is not in C: but should be.

Load up ntbtlog.txt in Notepad. In the command prompt window, type “C:” to get to the C drive, and then “CD Windowssystem32”. All of your important files will be in Windowssystem32 or windowssystem32drivers. Read through the ntbtlog.txt, and check that each file is on your C: drive. For any files which are not, copy them from the D: drive with a command like this:

XCOPY /CHOK D:Windowssystem32driversntosext.sys C:Windowssystem32drivers

The parameters to XCOPY ensure that the permissions and attributes are copied as well. Note every missing file. Once you have found and copied in the missing files, reboot from the hard drive, not the CD-ROM. Verify that your app layer now boots. Cancel the App Layer.

Back in the OS layer, edit C:Program FilesUnideskUniservicebootfile.txt. Add the correct path for the missing files to the bottom of bootfile.txt. Note that the directory separators are / instead of . So for instance, add the following line:

C:/Windows/system32/drivers/ntosext.sys

C:/Windows/system32/drivers/clipsp.sys

Save the file, finalize, and attempt to create a new app layer with the new OS version. If this works, please open a Support Case and let Citrix know about this file. Normally we would have picked it up with the Uniservice /B scan. We will likely ask for other information from your OS layer, including if you know what updates might have triggered this. However, with the modified bootfile.txt, you should be able to continue your deployment.

Related:

  • No Related Posts