How to Install VMware Tools on Openfiler 2.99

openfiler logo

 

1. Shell into the Openfiler server

2. Make a directory to mount VMtools

mkdir -p /mnt/vmtools

3. Start the VMware installation from the vSphere client

4. Mount the VMware tools to the directory created in step 2

mount /dev/cdrom /mnt/vmtools

5. Copy the tar of the tools to the /tmp folder

cp /mnt/vmtools/*.tar.gz /tmp

6.  Extract the tar file

cd /tmp
tar xvf *.tar.gz

7. Execute the tools installer

cd vmware-tools-distrib
./vmware-install.pl

8. Keep answering “yes” to all questions

9. Reboot the system

shutdown -r now

Should you have any questions, comments or suggestions, please don’t hesitate to comment below. If you like what you have read, please share it on your favourite social media medium.

Allowing Citrix Receiver to use HTTP as well as HTTPS – PNagent

citrix-logo

 

I have just upgraded Citrix Receiver from version 3.0 to 3.1 and I found it only allows connections to HTTPS addresses, currently I am working on test servers so adding a certificate seemed a bit over the top!

Instructions

  • Open up registry editor
  • Navigate to HKLM/SOFTWARE/Citrx/Dazzle (32bit)
  • Navigate to HKLM/SOFTWARE/Wow6432Node/Citrix/Dazzle (64bit)
  • Modify “AllowAddStore” to “A”
Citrix Reciever Registry Screenshot

 

 

Should you have any questions, comments or suggestions, please don’t hesitate to comment below. If you like what you have read, please share it on your favourite social media medium.

Citrix Networking Ports

citrix-logo

On my travels installing and configuring Citrix XenApp 6.5 I had to allow certain ports open for all sorts of reasons. There are a lot of them so I thought I would write up a quick post on where to get the latest information regarding ports.

Citrix has kindly put up a list (document id CTX101810) or a link here.

Failing that, you can download the list that was latest updated in February of 2012 by Citrix.

Citrix Ports_by_Product_and_Port

Should you have any questions, comments or suggestions, please don’t hesitate to comment below. If you like what you have read, please share it on your favourite social media medium.

Expand LVM Volume on Linux

Linux logo

 

Overview

Logical Volume Manager (LVM) is a logical volume manager for the Linux Kernel; it manages disk drivers and similar mass-storage devices. The term “volume” refers to a disk drive or partition thereof.

Assumptions

This document assumes LVM is installed on the following Linux (LVM-aware) distributions:

  • Arch Linux
  • CrunchBang
  • CentOS
  • Debian
  • Fedora
  • Gentoo
  • Mandriva
  • MontaVista Linux
  • openSUSE
  • Pardus
  • Redhat Enterprise Linux
  • Slackware
  • SLED
  • SLES
  • Ubuntu

This document assumes the virtual machines is virtualised in VMware ESX.

Instructions

  1. Ensure backup is complete from the night before
  2. If any services are dependent on the volume, turn the services off
    1. eg: /etc/init.d/notes start
  3. shutdown –h now
  4. Increase hard disk in vSphereESX VM Hard Disk Increase Screenshot
  5. Power on virtual machine
  6. Stop services that have started automatically on start-up that depend on the volume
    1. eg: /etc/init.d/notes stop
  7. unmount <path>
    1. <path> = mount points to volume eg: /export
  8. pvresize –setphysicalvolumesize ###G /dev/sd#
    1. ###G = new size of disk in gigabytes
    2. /dev/sd# = disk
  9. lvresize –L +##G <path to logical volume>
    1. ##G = total capacity that has been added
    2. eg: lvresize +L +50G /dev/export/lvol0.
  10. e2fsck –f <path to logical volume>
    1. eg: e2fsck –f /dev/export/lvol0
  11. resize2fs <path to logical volume>
    1. eg: resize2fs /dev/export/lvol0
  12. mount –a
  13. Start any services stopped at point 6
  14. ps –aux | grep <service>
    1. Check service is started

Should you have any questions, comments or suggestions, please don’t hesitate to comment below. If you like what you have read, please share it on your favourite social media medium.

VMware ESXi 5.x Disable Shell Warning

vmware-logo

Cluster warning for ESXi shell and SSH appear on ESXi 5.x host

This is not something you should do unless you want to “hide” the error message when having the ESXi shell and SSH enabled for ESXi 5.x.

I removed the error messages in my test environment as I know no one is going to connect to the shell, this might be different in corporate enterprise environments.

References:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003637

To disable these warnings using vSphere Client:

  1. Select the ESXi host from the Inventory.
  2. Click the Configuration tab.
  3. Click Advanced Settings in the Software menu.
  4. Navigate to UserVars > UserVars.SuppressShellWarning.
  5. Set the value from 0 to 1.

Click OK

 

To disable these warnings using esxcli:

  1. Connect to the ESXi host through SSH using root credentials.
  2. Run this command:
esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 1

To enable these warnings using esxcli:

  1. Connect to the ESXi host through SSH using root credentials.
  2. Run this command:
esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 0

To disable SSH and warning using vSphere Web Client:

Disable remote access to the ESXi 5.x host

  1. From the vSphere Web Client, select vCenter from the Home menu.
  2. Select Hosts and Clusters under the Inventory Trees.
  3. Expand the tree in the left pane of the vSphere Web Client.
  4. Click the ESXi host with the yellow exclamation and click the Manage tab.
  5. Click Settings and highlight Security Profile.
  6. Scroll to Services and click Edit.
  7. Highlight ESXi Shell and click Stop.
  8. Repeat for SSH, then press OK.

Disable the Warning message

  1. From the vSphere Web Client, select vCenter from the Home menu.
  2. Select Hosts and Clusters under the Inventory Trees.
  3. Expand the tree in the left pane of the vSphere Web Client.
  4. Click the ESXi host with the yellow exclamation and click the Manage tab.
  5. Click Settings and highlight Advanced System Settings.
  6. Locate the parameter UserVars.SuppressShellWarning and click the pencil icon to edit.
  7. Change the value to 1 and press OK.

Should you have any questions, comments or suggestions, please don’t hesitate to comment below. If you like what you have read, please share it on your favourite social media medium.