Set static IP in Bitnami Wordpress

If you need to set a static IP on a Bitnami Wordpress VM stack, follow this procedure:

• Log into the VM
• Copy the existing eth0 configuration to a backup file:

sudo mv /etc/sysconfig/network/ifcfg-eth0 /root/ifcfg-eth0

• Edit the network config file

sudo vi /etc/sysconfig/network/ifcfg-eth0

• Change the following:

BOOTPROTO=STATIC
IPADDR=192.168.1.10      < Your static IP address
NETMASK=255.255.255.0

• Save the file
• Using vi create the following file:

/etc/sysconfig/network/routes

• with the following content:

default 192.168.2.1 - -(where 192.x.x.x is your default gateway)

• Edit the following file:

/etc/sysconfig/network/config

• and change:

NETCONFIG_DNS_STATIC_SERVERS=""

• to

NETCONFIG_DNS_STATIC_SERVERS="X.X.X.X"(where X.X.X.X is your DNS server)

• Restart networking

sudo /etc/init.d/network restart

Fix mouse in Vmware opensuse

Go to:
/lib/udev/rules.d

and edit

69-xorg-vmmouse.rules

to be

ACTION==”add|change”, ENV==”?”, ATTRS==”i8042 AUX port”, KERNEL==”event[0-9]“, PROGRAM=”/usr/bin/vmmouse_detect”, ENV{ID_INPUT.tags}=”vmmouse”

Renew Windows Server 2008 R2 self signed RDP certificate

• Go into control panel/admin tools/iisclick on root of IIS site
• Double click server certficates
• Locate the expired cert and right click/ export to desktop
• Right click and delete the expired cert
• Right click and ‘create new self signed certficate ‘Make sure the ‘friendly name’ is the external DNS name
• go into control panel/admin tools/Remote Desktop Services
• Select ‘remote app manager’
• Click to change digital signature settings and choose your newly created cert
• Recreate and redistribute .RDP files for individual apps

More Linux Permissions

If you need to set folders to 755 and files to 644

sudo chmod -R 644 * ; sudo chmod -R ugo+X *

Vmware - eth0 removed after cloning or moving from Workstation to Esxi

I recently setup a Bitnami WordPress on a local copy of Vmware workstation. This was fine for testing, but I then needed to deploy in a production environment, specifically on Esxi 4.x. The convert ran fine and the VM moved over, but when booting eth0 was not available and hence the stack was inaccessible.
It appears that something happens to the net rules during the conversion process. In order to remove saved rules, just rename the following file and reboot to restore eth0:

sudo mv /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.old

Then perform a reboot:

sudo shutdown -r now

and all should be fine....