Well I got some new hardware in. This has allowed me to play with some various configuration settings – settings that I wish I had known about some years earlier.
Above, you can see where I’ve got two members, ONR1, and ONR2 in differing RAID formats, connected (below) the same storage pool,
Below you can see the volumes setup on the storage pool.
After some time, you’ll see that the volumes redistributed across the two sans.
Pretty sweet eh?
Occasionally it is necessary to use Sysprep instead of Quickprep when creating a desktop pool with View. This usually is because of some legacy software requiring unique local computer identifiers (SIDs). I recently got asked about it because of some older antivirus software that needed it to centrally manage its in-OS agents.A comparison of the two customization techniques can be found in the View Administration Guide on pages 95 and 96. KB article 2003797 gives a quick table of the differences:
|Removing local accounts
|Changing Security Identifiers (SID)
|Removing parent from domain
|Changing computer name
|Joining the new instance to the domain
|Generating new SID
|Language, regional settings, date, and time customization
|Number of reboots
||1 (seal & mini-setup)
|Requires configuration file and Sysprep
To setup and deploy a pool using Sysprep the high-level steps are as follows:
- Copy the Sysprep files to the vCenter server (Note that this is only required for Windows XP as Windows 7 comes with sysprep). Full details on this are in KB article 1005593.
- Create a Guest Customization Specification in vCenter.
- Add a desktop pool and tell it to use sysprep and the guest customization spec you have created.
Create a Guest Customization Specification
- In vCenter from the Home page select the option for Customization Specification Manager.
- Add a New customization and on the Properties page enter a name. DO NOT use a custom sysprep answer file.
- Continue through the wizard until the Computer Name page. Set this to use the virtual machine name.
- Step through the wizard entering license keys, administrator password, time zone, etc until you get to the Network page.
- Make sure you leave the network at the default of typical settings. This will then use DHCP
- On the Workgroup or Domain page leave this as the default. Any domain / administrator information entered here is not used. Instead the VM is joined to the domain using the guest customization settings defined in the pool settings through View Manager.
- On the last page Operating System Options make sure that the Generate New Security ID (SID) is checked. After all the whole reason we are using Sysprep is because unique SIDs are required for our use case.
Add a desktop pool
- In View Manager add a desktop pool as you would normally. The only deviation from using Quickprep comes on the last page for Guest Customization.
- Select the Domain. This list (normally only one in most environments) is what you defined when you configured the vCenter server in View Administrator and defined the Domains for View Composer. This settings is what will control which domain is joined and which credentials are used when customizing the linked clones.
- Select the appropriate AD container as normal.
- Select the option to Use a customization specification (Sysprep) and select the spec you created earlier.
- When you complete the wizard your pool should deploy although provisioning can be a bit slower than using Quickprep especially as there is an additional reboot of the linked clone required.
So what are the steps that take place when View customizes with Sysprep?
- Once the linked clone disks have been created, View Manager puts the VM into the Customizing state.
- View Manager calls the vCenter API customizeVM_Task to customize the VM with the customization specifications.
- View Manager powers on the linked clone.
- Inside the Guest OS on the linked clone, the View Composer Agent sees that it is starting for the first time and calls NetJoinDomain with the machine password cached on the internal disk.
- The machine is now joined to the domain.
- Sysprep is now run on the linked clone from within the guest.
- The View Composer Agent waits for Sysprep to finish before notifying the View Agent that customization is complete. Then the View Agent sends a message to the View Manager server.
- The View Manager Server powers off the clone and takes a snapshot of the customized, powered off clone (to give us our refresh state).
- View Manager puts the linked clone into the Provisioned state. If the VM is then powered on, it moves into the Available state.
If you’ve intentionally – or unintentionally lost your primary drive in Windows 2003 Software RAID, here’s how you’d get it back.
Load up the 2k3 Install disk
Press “r” for recovery mode
Select your installation
Enter your password
While you can just create a pv out of raw block device I normally try to avoid it as it can cause confusion as to what the block device is being used for. It may also break some of the auto discover routines that LVM can use if it’s missing it’s configuration files.
Here’s an example of using parted to create a GPT with 1 partition that is the whole drive and set the partition flag to be lvm. The mkpart requires that you specify a file system but it doesn’t create the file system. Seems to be a long standing bug in parted. Also the start offset of 1M is to ensure that you get proper alignment.
mkpart primary ext2 1M 100%
set 1 lvm on
vgcreate vg_*name* /dev/sdb1 /dev/sdc1 /dev/sdd1
lvcreate –extents 100%FREE -n lv_*name* vg_*name*
mkfs.xfs -f /dev/mapper/vg_*name*-lv_*name*
paste in the below:
# ### begin forwarding rule ###
# The statement between the begin … end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
$WorkDirectory /var/lib/rsyslog # where to place spool files
$ActionQueueFileName fwdRule1 # unique name prefix for spool files
$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
$ActionQueueType LinkedList # run asynchronously
$ActionResumeRetryCount -1 # infinite retries if host is down
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
*.* @@your splunk server:514
# ### end of the forwarding rule ###
chkconfig rsyslog on
service rsyslog restart
So we were having this weird latency issue with our new R815’s and the Broadcomm nics utilizing iSCSI on a segregated lan.
Turns out we needed the BCM-NetXtremeII-5.0-offline_bundle-940344.zip driver imported into update manager, a reboot later, we were all happy!
This explains how to add a cron job to VMware in such a way that it will still be there after reboots.
Having enabled ssh access to your ESX/ESXi server, ssh in as root.
First, add the cron job to the root crontab:
1. Edit /var/spool/cron/crontabs/root
2. Add the line (all on one line)
5 0 * * * /full/path/to/script arguments/with/full/path > /full/path/to/logfile 2>&1
3. When you quit, use Esc, :wq! to override the read only attribute.
For details of the meaning of “5 0 * * *” (5 minutes past midnight every day) read the man page for crontab(5) on any Unix/Linux server, or else on the web.
Now, add a command to /etc/rc.local to re-generate the cron job when ESX/ESXi reboots
1. Edit /etc/rc.local, using a command such as “vi /etc/rc.local”.
2. At the end of the file, add 3 lines (using “G” then “O” in vi). The first kills crond, the second adds the new cron job to the root crontab file, ad the third restarts crond:
/bin/kill $(cat /var/run/crond.pid)
/bin/echo ’5 0 * * * /full/path/to/script arguments/with/full/path > /full/path/to/logfile 2>&1′ >> /var/spool/cron/crontabs/root
3. Save and exit the editor (Press the “Esc” key then “:wq” then press “Return” in vi)
4. Run the command “auto-backup.sh” so that the change to /etc/rc.local survives a reboot.
Every time you change the cron job, remember to update /etc/rc.local as well and run the “auto-backup.sh” command to backup the new /etc/rc.local file.
If you change from a multi-processor system to a uni-processor system you need to manually change the HAL on the Windows server after the conversion.
To do this go into Device Manager after the machine first boots and discovers it’s new hardware and then click on Computer then right-click on the processor and select Update Driver. Then select Install from specific location and then Don’t search I will choose the driver to install. Then select show All compatible hardware and select the appropriate processor.
For example, if you went from a dual cpu to a single cpu then select ACPI uni-processor PC instead of ACPI multi-processor PC. You will need to reboot once you change this. To verify what HAL you are using you right-click your hal.dll in c:\windows\system32 and select the Version tab and select Internal Name and it should say halmacpi.dll for multi-processor acpi and halacpi.dll for uni-processor acpi.
Next clean up all the non-present hardware after the P2V conversion. To do this go to a CMD prompt and type SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then DEVMGMT.MSC and then select Show Hidden Devices. Delete any old grayed out hardware. Next remove any vendor specific applications/drivers. For example on a HP server you should go to Add/Remove programs and remove any HP management agents, survey utility, array config utility, version control agent, etc.
Also check your NIC and make sure there are no vendor specific drivers there (ie. teaming). Check the Services to see if all there is anything vendor specific related there and disable any services that are.
Open the Apache configuration file located at /etc/httpd/conf/httpd.conf
Change AllowOverride None to AllowOverride All inside the DocumentRoot Directory Directive, normally
This is very important for wordpress post name permalinks!!!
Install MySQL and Apache
yum install mysql
yum install mysql-server
chkconfig mysqld on
service mysqld start
sudo yum install php-gd
yum install httpd
chkconfig httpd on
service httpd start
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 5340 to server version: 3.23.54
Type ‘help;’ or ‘h’ for help. Type ‘c’ to clear the buffer.
mysql> CREATE DATABASE databasename;
Query OK, 1 row affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON databasename.* TO “username”@”hostname”
-> IDENTIFIED BY “password”;
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.01 sec)