> 16 unix groups – server_param maxgroups – what are example valid OS ?

Some operating systems allow sending more than 16 groups.

VNX has a parameter called: maxgroups – which allows support for more than 16 groups (up to 128) but reboot is required.

[nasadmin@localhost ~]$ server_param server_2 -facility security -info maxgroups -v

server_2 : name = maxgroups

facility_name = security

default_value = 16

current_value = 16

configured_value = 16

user_action = reboot DataMover

change_effective = reboot DataMover range = (16,128)

description = Define the max number of extra group in Unix credential

[nasadmin@localhost ~]$ server_param server_2 -facility security -modify maxgroups -value 64

server_2 : done Warning 17716815750: server_2 : You must reboot server_2 for maxgroups changes to take effect.


does anyone have an example of OS ?


  • No Related Posts

AppLayering 4.x – OS layer creation fails with error “An error occurred. The required file ‘OSType.txt’ was not found on your OS disk. Please obtain the application layering OS machine tools, run ‘Setup_x64.exe’ on your OS image”

AppLayering only supports MBR and Hyper-V Generation 1 machines. It does not supports GPT and Generation 2 machines.

Capture ELM logs and in camlogfile we could see, if GPT is being used.

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: Device Boot Start End Blocks Id System

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: /dev/nbd1279p1 1 4294967295 2147483647+ ee GPT

Note: App Layering will only look at the first partition or two, so if we are running setup64.exe and it’s saving on a 3rd or 4th partition, it’ll never look at that partition by design, so it will never find ostype.txt there.


  • No Related Posts

Auto Deployment stuck at “Client Record Updated”

I need a solution

I’m not sure where to start, but I’m running a distribute disk image job against a machine.  PC reboots, connects to PXE, boots to WinPE, loads drivers successfully, and establishes a network connection.  Then it starts dagent.  Dagent displays “client record updated” but that is where it stops.  It shows the address for my server, it shows the address for the client, but it doesn’t display computer name or MAC address.

I’d like to troubleshoot why it hangs.  Are there logs I can create that can assist here?  Any advice or tips would be appreciated.  I’m running a trial version of GSS 3.2 trying to get a proof of concept going so we can evaluate this product.  



  • No Related Posts

VNX: Linux: Cannot boot from SAN. Install boot fails in BIOS with “Emulux driver not installed”

Article Number: 482969 Article Version: 3 Article Type: Break Fix

Symmetrix,PowerPath,VNX1 Series,VNX2 Series

On trying to boot from SAN, we can install the OS (Linux Red Hat) with a mounted Linux disk. After install, boot fails in BIOS with “Emulux driver not installed”.

When the host OS kernel resides on an external device, it will not be loaded during boot by the host system’s hard disk controller. The OS image can only be fetched by the HBA’s BIOS. To facilitate visibility of external boot device by the HBA, the HBA BIOS must be installed to register the external device as the boot source.

To boot from storage attached to the SAN environment, the host bus adapters Boot BIOS must be installed and enabled on the adapter. This can explain why the Boot fails from SAN, as the reported message after OS install : boot fails in BIOS with “Emulux driver not installed”.

Correctly configuring HBA BIOS

Issue was resolved by following the steps for installing and configuring HBA BIOS in Host connectivity guide for Linux, Page 168-173.

EMC Host connectivity guide for Linux is found on Dell EMC Online Support at https://support.emc.com/docu5128_Host-Connectivity-Guide-for-Linux.pdf?language=en_US

Dell EMC supports Emulex, QLogic, and Brocade HBAs to boot from SAN.

Visit the Dell EMC webpage of the Dell EMC supported HBA vendor for the latest BIOS and firmware download:

• For Emulex, go to http://www.emulex.com

• For QLogic, go to http://www.QLogic.com

• For Brocade, go to http://www.Brocade.com
Emulex and QLogic adopt slightly different approaches in distributions of latest BIOS and firmware.


  • No Related Posts

Citrix Provisioning Services Boot Process

Understanding the Boot process in PVS:


When a target device starts it needs to somehow be able to find and contact a provisioning server to eventually stream down the appropriate vDisk.This information is stored in a so-called Bootstrap file named ARDBP32.BIN. It contains everything that the target devcie needs to contact a pVS server so that streaming process can be initialized.

The boot strap file be delivered through a TFTP server, this also partly applies to the alternative BDM(Boot Device Manager)approach. There are some distinct differences between TFTP and BDM


When using TFTP , target device needs to know how and where it can find the TFTP server to download the bootstrap file before connecting PVS server. TFTP can be configure in HA through Netscaler to avoid single point of failure. Provisoning services has its own built-in TFTP server. However, we are free to use whatever you prefer.

One of the most popular approach in delivering TFTP server address to your target devices is through DHCP, but there are other option as well..

BDM(Boot Device Manager)

There are actually two different methods to make use of the Boot Device Manager.

Let start with PVS, PVS offers a quick wizard which will generate a relatively small .ISO(around 300KB). Next , you configure your Target devices to boot from this .ISO file, using their CDROM/DVD players. This method uses a two-stage process where the PVS server location will be hardcoded into the bootstrap generated by BDM. The rest of the information like the (PVS device drivers) is downloaded from the PVS server using a TFTP protocol (UDP port 6969), here TFTP will still be used.

As of XenDesktop version 7.x, when using XenDesktop setup wizard we can create and assign a small BDM hard disk partition, which will be attached to the virtual machine as a separate virtual disk. Using this method the above mentioned two-stage approach is no longer needed because partition already contains all the PVS drivers. This way all the information needed will be directly available without the need of PXE,TFTP & DHCP.


As and added advantage using the BDM method will also decrease the boot time by around 5 to 10 sec since we don’t have to wait for PXE and TFTP

Provisioning Services Boot Process Diagram



  • No Related Posts

Time out error when accessing application server via NetScaler LB

executing below command on the NS shell,

# nsapimgr_wr.sh -ys expect_nonhttp_response=1 (Execute this command only the advise from the support engineer)

What it does is it will abort transaction tracking on receiving binary data, which will allow the NS to forward the response packet received from server to the client.

Since it is an nsapimgr command it will not persist on reboot, hence it will have to be added to rc.netscaler file manually.


  • No Related Posts

The Citrix PVS Two-Stage Boot (TSB) service is not running

The Citrix PVS Two-Stage Boot (TSB) service is not running. This service is used for ISO booting. If Provisioning Services is using Boot Device Management and this service is not running, target devices might not be able to start up as expected.

Note: If Boot Device Management is not currently used, this service is not required and you can hide this alert.

For more information on the PVS boot process, see https://support.citrix.com/article/CTX227725


  • No Related Posts

The Tftp service is not running on the PVS server

To resolve this issue:

1. Launch the Services console: Click **Start** and then type **Services**.

2. Verify the TFTP Service is present and restart the service: From the Services console, right-click **Citrix PVS TFTP Service** and select **Start**.

3. Check the Event Log for any errors.

For more information, see Starting, stopping, or restarting Provisioning Services in the product documentation

Note: If you are not using the Boot Device Manager boot partition, this service is not required. Click **Hide Alert** to prevent this alert from appearing. You can show this alert again by clicking **Site Options > Show Hidden Alerts**. For more information, see Manage Smart Check alerts and notifications in the product doumentation.


  • No Related Posts

How to recover data after PGP encrypted disk crashed ?

I need a solution


I created a recovery disk image using bootg.iso, and booted with it on the computer with the problem hard drive. The recovery program comes up and when I choose the problem disk in the “Enter a choice” field, it says “No boot disk found. Cannot Continue.Press any key to halt the system  ” Error screen is attached.

Is there anything else I can do? I would appreciate your support.




  • No Related Posts

7018748: Command “zypper ref” returns an HTTP 400 error in SUSE Manager 3.0 or 3.1 client.

Optionally instead of the above steps the following workaround can be used, which is to set http to unsafe by running:

echo “HttpProtocolOptions Unsafe” > /etc/apache2/conf.d/zypp-fix.conf

rcapache2 restart

Further information can be found here:


Quoting an excerpt from the above link:

> Security risks of Unsafe


> Users are strongly cautioned against toggling the Unsafe mode of operation,

> particularly on outward-facing, publicly accessible server deployments.

> If an interface is required for faulty monitoring or other custom service

> consumers running on an intranet, users should toggle the Unsafe option only

> on a specific virtual host configured to service their internal private

> network

NOTE: The explained procedure will not help for clients that are not registered with SUSE Manager yet. Any such clients will need an update of zypper/yum, but that will not be possible as the clients don’t have any way to get updates.

In order to bypass this problem, recreate bootstrap repository with command “mgr-create-bootstrap-repo”. The command “mgr-bootstrap” (after another maintenance update) now makes sure of that when it generates the bootstrap script. However, it means that all the bootstrap scripts will need to be regenerated to include this change (after the package spacewalk-cert-tools has been updated to version or higher).


  • No Related Posts