Stripping a load of the plastic and fittings out saves a good bit of resources as well.

http://news.cnet.com/8301-1001_3-10209580-92.html?tag=rtcol;pop

The hostname command should do the trick, but you’ve got a couple of other places to look in as well.  This should all be so familiar to anyone used to Red Hat anyway.

Make sure it all matches up in:

/etc/sysconfig/network

/etc/hosts

You may also need to reboot, sometimes a service network restart is not enough.

HA should now work a treat!

Launch diskpart from the command line.

list volumes

select volume #

extend

Done!

[vSphere PowerCLI] C:Program FilesVMwareInfrastructurevSphere PowerCLI> get-datastore -name "*test*" | get-vm | wher

e { $_.Powerstate -eq "poweredoff" }

Name                 PowerState Num CPUs Memory (MB)

----                 ---------- -------- -----------

UPRINTXDM            PoweredOff 1        2048

Uprint8_test         PoweredOff 1        512

U-SANTEST-01         PoweredOff 1        512

U-SANTEST-02         PoweredOff 1        512

TestVM               PoweredOff 1        512

uclh-test-vm02       PoweredOff 1        3840

Get all hosts in a cluster to rescan for new storage:

Get-Cluster | get-vmhost | Get-VMHostStorage -RescanAllHBA

Go and install powershell on your windows machine, and then go to the vmware site to download their VI-plugin.

Once installed, you can launch from the vmware folder group, but you may get an error when launching due to the unsigned script.  You can ignore this but it may cause you further issues later.

If you get this you’ll see this:

File C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1 cannot be load
ed because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
At line:1 char:2
+ . <<<<  "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1"
PS C:\Program Files\VMware\Infrastructure\vSphere PowerCLI>

To resolve, you need to set the signing to allow the VMware bits to all run properly.  Most cmdlets will be fine, and I only ran into problems with this when I tried to use the AnswerVM class which didn’t exist.

Note: this will remove your security on running scripts, so only do this if you are comfortable with the implications - don’t let any code run you’re not happy with and understand fully.

set-executionpolicy unrestricted

Then exit the shell, and restart - it will now look like this:

VMware powershelll startup

Firstly, -t smbfs now appears to be deprecated, so -t cifs should be used instead.

Secondly, smbclient traffic is blocked by the firewall by default, and all you will get when trying to make the connection is:
mount error 111 = Connection refused

To resolve this, simply go into the configuration for the host, security profile and make sure to enable smbclient.

• general installation and configuration
• iSCSI & EqualLogic setup and performance tuning
• Alerting and management
• Troubleshooting

find . -name "whatever*" | xargs rm

Job done.

With instructors throughout the country, the site seems to be growing nicely.

Check them out at www.ignitiondrivingschool.com

We’re running a further workshop in London this time, more details and registration can be found at the NCC Website.