The timezone value passed to sysprep is an index (i think the index in selection box of the installation screen)
the values are documented and taken from here
http://msdn.microsoft.com/en-us/library/ms912391(v=winembedded.11).aspx

so the value you see in the floppy is correct.
in 3.2 it worked for the same version of windows?

Takahashi-san,

easy way round this is to drop a file with an override value for win 2008 (or whatever OS you want to override its values)

/etc/ovirt-engine/osinfo.conf.d/10-windows-timezone-fix.properties

and restart the engine for the change to take effect.

10-windows-timezone-fix.properties:

os.windows_2008.isTimezoneTypeInteger.value = false
os.windows_2008x64.isTimezoneTypeInteger.value = false
os.windows_2008R2x64.isTimezoneTypeInteger.value = false

pending backport to 3.4

Verified in rhevm-3.4.0-0.13.beta3.el6ev.noarch (av6).

Verification steps:

1. Create new windows 2008 R2 VM
2. Install rhev-tools and seal the VM - do the "sysprep" procedure.
4. Create template from VM.
5. Create pool from the template with JST time zone "Tokyo Standard Time". **)
6. Run pool vm and then check its timezone setting
7. Check for <TimeZone> in file A:\sysprep.inf

**) Beware of bug 1088440, where the sysprep.inf file always contains the time zone set in VM dialog / System side-tab. It ignores time zone set in VM dialog / Initial Run side-tab as well as in the Run Once dialog.

Results:
6. The VM has time zone set to Tokyo Standard Time. In Windows the "Date and Time" dialog says: (UTC+09:00) Osaka, Sapporo, Tokyo
7. The time zone in sysprep.inf file is saved in plain text, not integer number.
   It contains: <TimeZone>Tokyo Standard Time</TimeZone>

This behavior is defined in the default OS info configuration file shipped with RHEVM:

# grep -r isTimezoneTypeInteger /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties
os.windows_xp.isTimezoneTypeInteger.value = true
os.windows_2003.isTimezoneTypeInteger.value = true
os.windows_2008.isTimezoneTypeInteger.value = false
os.windows_2003x64.isTimezoneTypeInteger.value = true
os.windows_7.isTimezoneTypeInteger.value = false
os.windows_2008x64.isTimezoneTypeInteger.value = false

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0506.html