Restoring VM's backed up from ghettoVCB to ESX(i) 3.5, 4.x & 5.x

Usage:

[root@himalaya ~]# ./ghettoVCB-restore.sh
###############################################################################
#
# ghettoVCB-restore for ESX/ESXi 3.5, 4.x and 5.x
# Author: William Lam
# http://www.virtuallyghetto.com/
# Created: 08/18/2009
# Last modified: 2011_11_19_1
#
###############################################################################

Usage: ./ghettoVCB-restore.sh -c [VM_BACKUP_UP_LIST] -l [LOG_FILE] -d [DRYRUN_DEBUG_INFO]

OPTIONS:
   -c     VM backup list
   -l     File ot output logging
   -d     Dryrun/Debug Info [1|2]

(e.g.)

Output will go to stdout
        ./ghettoVCB-restore.sh -c vms_to_restore

Output will log to /tmp/ghettoVCB-restore.log
        ./ghettoVCB-restore.sh -c vms_to_restore -l /tmp/ghettoVCB-restore.log

Dryrun/Debug Info (dryrun only)
        ./ghettoVCB-restore.sh -c vms_to_restore -d 1
        ./ghettoVCB-restore.sh -c vms_to_restore -d 2

Standard input for script is a file that contains:

1) Full path to the backed up VM

2) Full restore path

3) Restoration disk format

4) Restored VM Display Name (NEW!)

Reminder: When creating this file on a non-Linux/UNIX system, one may  introduce ^M characters that will cause the script to misbehave. To  ensure that this does not occur, please create the file on the ESX/ESXi  host.

Here is a sample of what the file should look like:

[root@himalaya ~]# cat vms_to_restore
#"<DIRECTORY or .TGZ>;<DATASTORE_TO_RESTORE_TO>;<DISK_FORMAT_TO_RESTORE>;<OPTIONAL_RESTORED_VM_DISPLAY_NAME>"
# DISK_FORMATS
# 1 = zeroedthick
# 2 = 2gbsparse
# 3 = thin
# 4 = eagerzeroedthick
# e.g.
# "/vmfs/volumes/dlgCore-NFS-bigboi.VM-Backups/WILLIAM_BACKUPS/VCAP/VCAP-2009-08-18--1;/vmfs/volumes/himalaya-local-SATA.RE4-GP:Storage;1""/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36;/vmfs/volumes/mini-local-datastore-1;3"
"/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36;/vmfs/volumes/mini-local-datastore-1;1;VCSA-RESTORE"

Comments in the input file is acceptable so long as the intended line is preceded by a #. The above sample VM restore file,

vms_to_restore, describes the following backup:

VM to restore	Datastore to restore to	VMDK format	Restore VM Name
/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36	/vmfs/volumes/mini-local-datastore-1	thin	VCSA-5.1
/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36	/vmfs/volumes/mini-local-datastore-	zeroedthick	VCSA-RESTORE

---

Sample Execution:

Perform a dryrun by displaying debug information ( restore will not take place)

Display debug information level 1:

# ./ghettoVCB-restore.sh -c vms_to_restore -d 1
################ DEBUG MODE ##############
Virtual Machine: "VCSA-5.1"
VM_ORIG_VMX: "VCSA-5.1.vmx"
VM_ORG_FOLDER: "VCSA-5.1-2012-12-25_01-30-36"
VM_RESTORE_VMX: "VCSA-5.1.vmx"
VM_RESTORE_FOLDER: "VCSA-5.1"
VMDK_LIST_TO_MODIFY:
scsi0:0.fileName = "VCSA-5.1.vmdk"
scsi0:0.fileName  = "VCSA-5.1-0.vmdk"
scsi0:1.fileName = "VCSA-5.1_1.vmdk"
scsi0:1.fileName  = "VCSA-5.1-1.vmdk"
##########################################


################ DEBUG MODE ##############
Virtual Machine: "VCSA-RESTORE"
VM_ORIG_VMX: "VCSA-5.1.vmx"
VM_ORG_FOLDER: "VCSA-5.1-2012-12-25_01-30-36"
VM_RESTORE_VMX: "VCSA-RESTORE.vmx"
VM_RESTORE_FOLDER: "VCSA-RESTORE"
VMDK_LIST_TO_MODIFY:
scsi0:0.fileName = "VCSA-5.1.vmdk"
scsi0:0.fileName  = "VCSA-RESTORE-0.vmdk"
scsi0:1.fileName = "VCSA-5.1_1.vmdk"
scsi0:1.fileName  = "VCSA-RESTORE-1.vmdk"
##########################################


Start time: Sun Jan 13 16:45:12 UTC 2013
End   time: Sun Jan 13 16:45:14 UTC 2013
Duration  : 2 Seconds

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

Display debug information level 2:

[root@himalaya ~]# ./ghettoVCB-restore.sh -c vms_to_restore -d 2

################## Restoring VM: VCSA-5.1  #####################
==========> DEBUG MODE LEVEL 2 ENABLED <==========
Start time: Sun Jan 13 16:45:35 UTC 2013
Restoring VM from: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36"
Restoring VM to Datastore: "/vmfs/volumes/mini-local-datastore-1" using Disk Format: "thin"
Creating VM directory: "/vmfs/volumes/mini-local-datastore-1/VCSA-5.1" ...
Copying "VCSA-5.1.vmx" file ...
Restoring VM's VMDK(s) ...
Updating VMDK entry in "VCSA-5.1.vmx" file ...

SOURCE: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1.vmdk"
    ORIGINAL_VMX_LINE: -->scsi0:0.fileName = "VCSA-5.1.vmdk"<--
DESTINATION: "/vmfs/volumes/mini-local-datastore-1/VCSA-5.1/VCSA-5.1-0.vmdk"
    MODIFIED_VMX_LINE: -->scsi0:0.fileName  = "VCSA-5.1-0.vmdk"<--
Updating VMDK entry in "VCSA-5.1.vmx" file ...

SOURCE: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1_1.vmdk"
    ORIGINAL_VMX_LINE: -->scsi0:1.fileName = "VCSA-5.1_1.vmdk"<--
DESTINATION: "/vmfs/volumes/mini-local-datastore-1/VCSA-5.1/VCSA-5.1-1.vmdk"
    MODIFIED_VMX_LINE: -->scsi0:1.fileName  = "VCSA-5.1-1.vmdk"<--
Registering VCSA-5.1 ...
End time: Sun Jan 13 16:45:35 UTC 2013
################## Completed restore for VCSA-5.1! #####################

################## Restoring VM: VCSA-RESTORE  #####################
==========> DEBUG MODE LEVEL 2 ENABLED <==========
Start time: Sun Jan 13 16:45:35 UTC 2013
Restoring VM from: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36"
Restoring VM to Datastore: "/vmfs/volumes/mini-local-datastore-1" using Disk Format: "zeroedthick"
Creating VM directory: "/vmfs/volumes/mini-local-datastore-1/VCSA-RESTORE" ...
Copying "VCSA-5.1.vmx" file ...
Restoring VM's VMDK(s) ...
Updating VMDK entry in "VCSA-RESTORE.vmx" file ...

SOURCE: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1.vmdk"
    ORIGINAL_VMX_LINE: -->scsi0:0.fileName = "VCSA-5.1.vmdk"<--
DESTINATION: "/vmfs/volumes/mini-local-datastore-1/VCSA-RESTORE/VCSA-RESTORE-0.vmdk"
    MODIFIED_VMX_LINE: -->scsi0:0.fileName  = "VCSA-RESTORE-0.vmdk"<--
Updating VMDK entry in "VCSA-RESTORE.vmx" file ...

SOURCE: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1_1.vmdk"
    ORIGINAL_VMX_LINE: -->scsi0:1.fileName = "VCSA-5.1_1.vmdk"<--
DESTINATION: "/vmfs/volumes/mini-local-datastore-1/VCSA-RESTORE/VCSA-RESTORE-1.vmdk"
    MODIFIED_VMX_LINE: -->scsi0:1.fileName  = "VCSA-RESTORE-1.vmdk"<--
Registering VCSA-RESTORE ...
End time: Sun Jan 13 16:45:35 UTC 2013
################## Completed restore for VCSA-RESTORE! #####################


Start time: Sun Jan 13 16:45:34 UTC 2013
End   time: Sun Jan 13 16:45:35 UTC 2013
Duration  : 1 Seconds

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

Execute restore with output going to stdout (restore the first two VMs listed from above):

Input file:

# cat vms_to_restore
"/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36;/vmfs/volumes/mini-local-datastore-1;3"
"/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36;/vmfs/volumes/mini-local-datastore-1;1;VCSA-RESTORE"

./ghettoVCB-restore.sh -c vms_to_restore

################## Restoring VM: VCSA-5.1  #####################
Start time: Sun Jan 13 16:46:41 UTC 2013
Restoring VM from: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36"
Restoring VM to Datastore: "/vmfs/volumes/mini-local-datastore-1" using Disk Format: "thin"
Creating VM directory: "/vmfs/volumes/mini-local-datastore-1/VCSA-5.1" ...
Copying "VCSA-5.1.vmx" file ...
Restoring VM's VMDK(s) ...
Updating VMDK entry in "VCSA-5.1.vmx" file ...
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1.vmdk'...
Clone: 100% done.
Updating VMDK entry in "VCSA-5.1.vmx" file ...
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1_1.vmdk'...
Clone: 100% done.
Registering VCSA-5.1 ...
34
End time: Sun Jan 13 16:48:51 UTC 2013
################## Completed restore for VCSA-5.1! #####################

################## Restoring VM: VCSA-RESTORE  #####################
Start time: Sun Jan 13 16:48:52 UTC 2013
Restoring VM from: "/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36"
Restoring VM to Datastore: "/vmfs/volumes/mini-local-datastore-1" using Disk Format: "zeroedthick"
Creating VM directory: "/vmfs/volumes/mini-local-datastore-1/VCSA-RESTORE" ...
Copying "VCSA-5.1.vmx" file ...
Restoring VM's VMDK(s) ...
Updating VMDK entry in "VCSA-RESTORE.vmx" file ...
Destination disk format: VMFS zeroedthick
Cloning disk '/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1.vmdk'...
Clone: 100% done.
Updating VMDK entry in "VCSA-RESTORE.vmx" file ...
Failed to clone disk: There is not enough space on the file system for the selected operation (13).
Destination disk format: VMFS zeroedthick
Cloning disk '/vmfs/volumes/mini-local-datastore-2/backups/VCSA-5.1/VCSA-5.1-2012-12-25_01-30-36/VCSA-5.1_1.vmdk'...
Registering VCSA-RESTORE ...
35
End time: Sun Jan 13 16:50:19 UTC 2013
################## Completed restore for VCSA-RESTORE! #####################


Start time: Sun Jan 13 16:46:40 UTC 2013
End   time: Sun Jan 13 16:50:19 UTC 2013
Duration  : 3.65 Minutes


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

Execute restore with output going to log file

/tmp/ghettoVCB-restore.log (restore the last two VMs listed from above):

[root@himalaya ~]# ./ghettoVCB-restore.sh -c vms_to_restore -l /tmp/ghettoVCB-restore.log
Logging output to "/tmp/ghettoVCB-restore.log" ...

Synchronize time with external NTP server on Windows Server 2008 (R2)

Synchronize time with external NTP server on Windows Server 2008 (R2).

Time synchronization is an important aspect for all computers on the network. By default, the clients computers get their time from a Domain Controller and the Domain Controller gets his time from the domain’s PDC Operation Master. Therefore the PDC must synchronize his time from an external source. I usually use the servers listed at the NTP Pool Project website. Before you begin, don’t forget to open the default UDP 123 port (in- and outbound) on your (corporate) firewall.

1. First, locate your PDC Server. Open the command prompt and type: C:\>netdom /query fsmo
2. Log in to your PDC Server and open the command prompt.
3. Stop the W32Time service: C:\>net stop w32time
4. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org”
5. Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes
6. Start the w32time service: C:\>net start w32time
7. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
8. Check the Event Viewer for any errors.

Tested on Windows Server 2008 R2 (Build 7600).

Hong Kong — hk.pool.ntp.org

3.hk.pool.ntp.org
1.asia.pool.ntp.org
3.asia.pool.ntp.org
stdtime.gov.hk

Google App Engine - Picasa-Gallery installation & upload

My Picasa Gallery - http://picasa.kennymoody.net

by using : https://github.com/angryziber/picasa-gallery


installation:

0. download the picasa-gallery , unzip & config

1a. download JAVA SDK and install ( I am using SDK 1.6 )
1b.  Remeber to uninstall ALL JAVA JRE if you installed before

2. download GAE SDK and unzip ( Latest Version )

3. download Apache ANT and unzip to c:/ANT ( Latest Version )

4. in CMD ,
    type " set ANT_HOME=c:\ant "
             " set PATH=PATH;%ANT_HOME%\bin "
             " set JAVA_HOME=***path to JAVA SDK folder*** "

5. compile the file in CMD
    type " ant -Dsdk.dir =***path to GAE SDK folder*** compile "

6. in CMD , go to GAE SDK folder \ bin
    type " appcfg update ***path to picasa-gallery WAR folder*** "
   

all the files should be uploaded to GAE server now ...


   

Control USB Drive letter

The USBDLM is a freeware for personal use Windows service that gives control over Window's drive letter assignment for USB drives. Running as service makes it independent of the logged on user's privileges, so there is no need to give the users the privilege to change drive letters.It automatically solves conflicts between USB drives and network drives of the currently logged on user. Furthermore you can define new default letters for USB drives and much more.


USB drive letter manager - USBDLM http://www.uwe-sieber.de/usbdlm_e.html


What can USBDLM do for newly attached USB drives?
Check if the letter is used by a network share of the currently logged on user and assign the next letter that is really available
Reserve letters, so they are not used for local drives
Assign a letter from a list of new default letters, also dependent on many different criteria as the active user, drive type, connection (USB, FireWire), USB port, volume label, size and others
Assign letters for a specific USB drive by putting an INI file on the drive
Remove the drive letters of card readers until a card is inserted
Show a balloon tip with the assigned drive letter(s)
Define autorun events depending on many different criteria
Many other things, see help file, available online as HTML version too


All functions are applied to USB drives at the moment they are being attached, when the USBDLM service starts up and when a user logs on.
Usage


Instructions can be found on the author's site, so you'd better read them from there.


Running without a configuration USBDLM only prevents that an USB drive gets the letter of a network share drive of the currently logged on user. It remounts then to the next letter that is really available.


However it is worth noting that USBDLM is configured thru a text file, the USBDLM.INI. The USBDLM.INI is read from the folder of the USBDLM.EXE.


New default letters for new USB drives (flash or hard drive)
[DriveLetters] Letter1=U Letter2=Y Letter3=Z



USBDLM can have up to 9 'LetterX' entries in each section. They don't have to be continuous.


For Card readers, the typical 20-in-1 card reader eats one drive letter for each of its slots - if we have a card for or not. USBDLM can remove the reader's drive letter until a media is inserted.
[Settings] NoMediaNoLetter=1



USBDLM assings then a drive letter as configured. If you need different drive letters for a multislot cardreader, then use the criterion 'DeviceType' in a DriveLetters section (MSCR is short for MultiSlotCardReaders which can be used too):
[DriveLetters1] DeviceType=MSCR Letter1=R Letter2=W Letter3=



You can prevent Windows mounting to certain letters by putting them into section ExcludedLetters. This is especially useful for letters of network shares which Windows may assign to USB drives while booting.[ExcludedLetters] Letter1=F Letter2= Letter3=



USBDLM can show a balloon tip with information about the drive letter(s) or mount points used for a just attached drive:
[BalloonTips] Enabled=1



I hope you found this article useful, and that it saves you time on the job!

Windows Map Drive System error 86 has occurred

Happen on Windows 7 when access file sharing or run bat file of map drive.

Solution (On PC problem):

1- Start > in Search box type gpedit.msc

2- Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

3- Find “Network Security: LAN Manager authentication level” double click on it

4- Set it to “Send LM & NTLM – use NTLMv2 session security id negotiated” click OK

5- Restart

OR

Check the System time , the system time should match TODAY !

RouterOS PPTP VPN 比較有用的連結

Mikrotik Wiki
http://wiki.mikrotik.com/wiki/Manual:Interface/PPTP


Mikrotik RouterOS Site-to-Site configuration for Peers with Dynamic IP
http://alsacecom.fr/blog/?p=117


MikroTik RouterOS 建置 PPTP VPN Server 連回公司、家中內部網路 (固定IP、Static IP 適用)
http://blog.cscworm.net/?p=2454


MikroTik RouterOS 建置 PPTP VPN Server 連回公司、家中內部網路 (PPPoE、撥接上網 適用)
http://blog.cscworm.net/?p=2480

How to Run Windows XP for Free in Windows 8

Microsoft gave Windows 7 users a way to run older applications via Windows XP Mode. With Windows 8, however, that mode is no longer officially supported, and if you want to run Windows XP in a virtual machine, you need the license for it. Lifehacker reader Miloš, however, has found a workaround.

He discovered that within the free WindowsXPMode_en-us.exe file, there's a VirtualXPVHD file containing the Windows XP virtual machine, which you can open in VirtualBox. Here are the steps to get this working:

1. Download WindowsXPMode_en-us.exe from Microsoft. You'll need to run the validation tool to prove your copy of Windows is valid.

http://www.microsoft.com/taiwan/windows/virtual-pc/download.aspx

1. Then use 7-Zip or another archive tool to open the EXE file as an archive.
2. Within that archive, find the "sources/xpm" file within it, and extract that folder to your hard drive.
3. Finally, in the extracted xpm file, you'll find a file called VirtualXPVHD. Rename it with a VHD extension.

In VirtualBox, open the VirtualXPVHD virtual machine, and voila! You've got Windows XP Mode (running Windows XP Professional) in Windows 8, no need for the XP license.

This might also be possible with Windows 8's built-in virtual machine manager, Hyper-V, but that's only available in Windows 8 Pro.

VMware ESXi 5 Update 更新 ( Command Line )

【安裝前的準備】
使用「esxcli software profile get」指令，查詢記錄更新前的版本及更新狀態，以便更新後驗證對照。

~ # esxcli software profile get    ESXi-5.0.0-469512-standard         Name: ESXi-5.0.0-469512-standard         Vendor: VMware, Inc.         ......

【開始系統更新】
開始更新 VMware ESXi 5.0 時，使用的「esxcli」指令是：

esxcli software vib install --depot 《更新檔路徑》

或是：

esxcli software vib install -d 《更新檔路徑》

順便加上進入「維護模式」的參數，一長串指令就像這樣：
esxcli software vib install --maintenance-mode -d /vmfs/volumes/datastore/update-from-esxi5.0-5.0_update01.zip 

【驗證更新結果】
再次使用「esxcli」指令查詢更新版本：

~ # esxcli software profile get

錯誤：Windows 無法連線到 System Event Notification Services 服務 (Error： Windows could not connect to the System Event Notification Service)

當你開機時，剛登入後，突然跳出一個氣球資訊-(Windows 無法連線到 System Event Notification Services服務...)，接著網路、側邊欄......等等都不能使用!

圖像 1:

如果您遇到上述的情況，請執行以下步驟解決問題：

1. 點擊左下角的 「Windows 圖示 」,然后點擊「所有程式」。
2. 點擊「附屬應用程式」, 然后右鍵點擊一下「命令提示字元」,再點擊「以系統管理員身分執行」，如下圖：

   圖像 2:

   
3. 在「命令提示字元」畫面中輸入指令 "netsh winsock reset catalog"，完成後按下鍵盤 Enter 鍵，如下圖：

   圖像 3:

   
4. 提示 "順利重設 Winsock Catalog " 後，關閉「命令提示字元」然後重新啓動電腦。

   圖像 4:

   

VMware KB: Creating snapshots in a different location than default virtual machine directory

VMware KB: Creating snapshots in a different location than default virtual machine directory

In ESX/ESXi 3.x and 4.x, all files comprising snapshots are created in the virtual machine's working directory. By default, the working directory is the same directory as the virtual machine's (.vmx) configuration file. Thus, if the virtual disk (.vmdk) file is located on different datastore than the virtual machine itself, virtual disk redolog (-delta.vmdk) files are created alongside the virtual machine's (.vmx) configuration file instead of beside the virtual disk (.vmdk) file.

You may want to change the location (new directory on the same or alternative datastore) where virtual disk redolog (-delta.vmdk) files are created, in order to:

• Create snapshots but do not have enough space on the VMFS volume.
• Power on a virtual machine when there is not enough space to create a swap file on the VMFS volume.

This article describes a method to change the default virtual machine working directory location used for snapshots on ESX/ESXi 3.x and 4.x.

Note: For information about this procedure in ESXi 5.0, see Changing the location of snapshot delta files for virtual machines in ESXi 5.0 (2007563)

To change the default virtual machine working directory location for snapshots (to a new directory on the same or alternative datastore):

1. Power off the virtual machine.
2. Open the virtual machine's .vmx configuration file in a text editor. For more information, see Tips for editing a .vmx file (1714).
3. Add a line to the .vmx configuration file for the virtual machine, specifying a full path to the directory on a datastore for theworkingDir option:
   
   workingDir = "new_path_location"
   
   Example:
   
   workingDir = "/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"
   
   This ensures that subsequently created snapshots will cause new virtual disk redolog (-delta.vmdk) files to be created in the defined directory.
   
4. Note: This step is optional. Adding the new file location ensures the swap file is created in the working directory.
   
   When virtual machine is powered on for the first time, a new swap file is created in the working directory of the virtual machine.  By default, the virtual machine writes the swap file in the same directory as the.vmx configuration file. If you would like to change this location, add the new location to the below line in the.vmx file:
   
   sched.swap.dir = "path_to_vm_directory"
   
5. Save the changes and close the virtual machine's .vmx configuration file.
6. Reload the virtual machine configuration by unregistering and re-registering it in the inventory. For more information, seeRegistering or adding a virtual machine to the inventory (1006160).
7. Power on the virtual machine.

Note: If you are performing a storage vMotion or storage migration of a virtual machine that has its working folder set to a location other than the virtual machine directory, this change is not maintained and you must reconfigure it as necessary.

VMware KB: Changing the location of snapshot delta files for virtual machines in ESXi 5.0

VMware KB: Changing the location of snapshot delta files for virtual machines in ESXi 5.0

In ESXi 5.0, the storage vMotion process has been improved to allow:

• Virtual machines can now be migrated to a new datastore while running on snapshots.
• Linked clone virtual machines are now supported with storage vMotion.

For further/related information see the following VMware blog post, vSphere 5.0 Storage Features Part 2 - Storage vMotion

The above link was correct as of March 13, 2012. If you find a link is broken, provide feedback and a VMware employee will correct the link.
To facilitate these improvements to storage vMotion and the new Storage DRS feature a change to the snapshot process was introduced to ESXi 5.0.

With previous versions of ESX/ESXi the delta disks were stored in the directory specified by the workingDir parameter.

This was typically the same directory as the configuration files for the virtual machine, but this could be changed by updating theworkingDir parameter.

With ESXi 5.0 storage vMotion will ignore the workingDir parameter and all the the snapshot delta disks are now stored in the same directory as the base disk.

For further/related information see the following VMware blog post, Storage vMotion, Storage DRS & Virtual Machine Snapshots Interoperability.

In ESXi 5.0 the workingDir parameter still exists but it is only used to specify the location of the snapshot .vmsn file.

To go back to the pre-ESXi 5.0 way of storing snapshots in the directory specified by the workingDir parameter there is a new parameter snapshot.redoNotWithParent which must be added to the virtual machine .vmx file.

Note: For the ESX/ESXi 3.x/4.x version of this article, see Creating snapshots in a different location than default virtual machine directory (1002929).

To specify that the snapshot delta files should be kept in the same directory as the location specified in the workingDirparameter then we need to add a new parameter snapshot.redoNotWithParent to the virtual machine configuration file.

To modify the snapshot storage location:

1. Ensure that the virtual machine is powered off.
2. Right-click the virtual machine and click Edit Settings.
3. Click the Options tab.
4. In the Advanced Options, click General.
5. Click Configuration Parameters.
6. Click Add Row.
7. In the Name field, type snapshot.redoNotWithParent.
8. In the Value field, type true.
9. The virtual machine can be powered on again.

For more information, see the VMware blog post Storage vMotion, Storage DRS & Virtual Machine Snapshots Interoperability.

Note: The preceding link was correct as of March 13, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

Note: The following additional behaviour are experienced with snapshots and Storage vMotion on ESXi 5.0:

• If you have a virtual machine running on snapshots and you move a VMDK from one datastore to another its associated snapshot files will move with the VMDK to the new datastore (even if they were created in the working directory initially).
• Newly created snapshots will be created in the working directory again though (as per the advanced setting).
• The working directory is located at /usr/lib/vmware/hostd/docroot/downloads.
• Snapshot files do not move if you move the configuration files to another datastore. The existing snapshot files continue to stay on the original datastore.

windows 7 出現MTP usb設備驅動安裝問題解決方法

因為一直以來都以為是驅動方面出問題!所以一直沒有找到解決方法!

這個設備是用來同步媒體的，windows media player 11是可以安裝的，可是12不行，而可惡的微軟綁定了wmp，不能卸載，所以windows 7中才會出現這個問題。不管你是什麽手機，解決方法如下！

今天無意中發現驅動裏的一個信息"由於其配置信息(註冊表中的)不完整或已損壞，Windows 無法啟動這個硬件設備。 (代碼 19)"
改變方向看是不是註冊表問題!結果真的成功了!

方法：打開註冊表編輯器（開始--》運行--》regedit），依次展開HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{EEC5AD98-8080-425F-922A-DABF3DE3F69A}刪除“upperfilter”項或“lowerfilter”項，然後進入設備管理器中把通用串行總線控制器下面的所有帶嘆號的設備都刪除，重新掃描硬件安裝即可恢復。

How to get better resolution on your standard 10 inch netbook

Most of the 10 inch netbooks available right now on the market ship with a standard resolution of 1024 x 600 px. Only in the last months we’ve started to see more HD 10 inch display, with the higher 1366 x 768 px res.

I for one like the lower res on my Toshiba and wouldn’t trade it for the HD one in a million years. I’ve tested the HD and experienced some extreme headaches caused by reading the tiny text for a longer time. So big res 10 inch screens are a no no for me.

Still, I noticed that quite a few of you guys enjoy it, so here’s a quick tweak i found on forums that will help you get better res for your standard 10 inch display.

First, i’ll have to tell you that you are going to get 1024 x 768 and 1152 x 864 px res available for the 10 inch display . These are not HD resolutions as you might have reckon and will translate in text skews and compressed displayed content. In most cases, the result won’t be that great, but hey, if you want the increased resolution, you should give these tweaks a try. And one more thing. This only works on Windows 7 equipped netbooks.

Here’s what you have to do:

1) Run regedit
1a) If you are not on higest tree level, go to him (by click on “Computer” from key tree)
2) Search and modify all values “Display1_DownScalingSupported” from “0″ to “1″
3) Restart the system
4) Enjoy the two new resolutions: 1024×768 px and 1152×864 px

Now, when selecting a resolution in Windows you’ll get the extra methods above. However, be aware that these tweaks might not work on all netbooks (it was tested by users on the 1000H, 1005He or the 1005HA Asus devices) and might cause software instability when changing between options.

install X64 新倉頡 2010

1. Download the Pinyin installer.
2. Open the installer using 7 Zip (or any similar program).
3. Extract IME32.cab, IME32.msi and IME32.xml (if you're using a 64-bit version of Windows, extract the '64' files too).
4. Open IME32.msi using Orca (search for 'Orca MSI' if you don't have this program).
5. In 'Tables' > 'CustomActions' right-click and drop the entry 'AbortMsi' then save the file (optionally repeat this process for IME64.msi too).
6. Install IME32.msi (and IME64.msi, if necessary) as normal.

在Vista/Win7 的IE 中, 解決輸入法的「記憶體不足」問題

這是降低 IE 的保安程度, 這自然增加了被惡意程式入侵的機會, 所以用戶要衡量這
方面的風險。 這類利用記憶體漏洞來入侵電腦的病毒, 數量不多, 以前只有數個病毒例
子, 不過始終有這風險。
要取消這記憶體保護模式, 可開啟 IE, 在 [工具] 的選項內開啟 [洲際網路選項],
在 [安全性] 的標籤下, 取消 [啟用受保護模式] 的一項

Outlook 2003 can't open zip attachments on Windows 7

Problem: When using Outlook 2003 on Windows 7, users can't open zip attachments from a message - double clicking on the zip brings up the Open/Save dialog but clicking Open does not open it (the zip is saved in the securetemp folder each time you double click though). 

To open the zips, users need to save them to the hard drive then open if they want to use Windows Compressed folders feature. (If they install a zip program, there is no problem - zips open as expected.)

This is apparently "by design" and is related to the new Libraries file management feature. There is registry value that controls how the explorer handles certain file types for specific applications and this registry value can be edited as a workaround. 

However, because we don't know if editing this key might cause other problems it's highly recommended users install a 3rd party zip program instead. (There are a number of free and low cost zip programs available, many have more features than Compressed Folders.)

Open the registry editor and browse to this key:

Windows 32-bit versions:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows\CurrentVersion\ShellCompatibility\Applications\outlook.exe

Using 64-bit Windows, the key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Windows\CurrentVersion\ShellCompatibility\Applications\outlook.exe

String: STRIPFOLDERBIT
String: VERSION Original Data value: 11.*,10.*,9.*,8.*,7.*

Recommended fix:Edit the VERSION string value, removing 11.*; 
New VERSION string value: 10.*;9.*;8.*;7.*

Alternate fix: Delete (or rename) the STRIPFOLDERBIT value

Reboot Windows.

I tested both registry hacks and both allow me to open zip attachments.