Thank you for answering.
Wow, I'm somewhat shocked this feature was neglected. I know now why my developers prefer buying VMWare instead of using Hyper-V. We often need to set the date on our application (12/31/xx, for example) to test what happens over a given time frame, especially as we develop point-of-sale applications which have time-based rules and we must test these in our VM's.
Okay, well I guess I'll buy VMWare and give another bit of money to EMC instead of using a MS product.
SMH
To anybody else who's seen this thread, here are some other relavant links.
https://technet.microsoft.com/en-us/library/hh848584%28v=wps.630%29.aspx?f=255&MSPPError=-2147217396
Here's what I see in my powershell when I try to find a date function in the BIOS.
PS C:\Users\Kai> get-vm
Name State CPUUsage(%) MemoryAssigned(M) Uptime Status
---- ----- ----------- ----------------- ------ ------
LUbuntu Off 0 0 00:00:00 Operating normally
WindowsPhone_WVGA Off 0 0 00:00:00 Operating normally
WindowsWhistler Off 0 0 00:00:00 Operating normally
PS C:\Users\Kai> get-vmbios WindowsWhistler
VMName StartupOrder NumLockEnabled
------ ------------ --------------
WindowsWhistler {CD, IDE, LegacyNetworkAdapter, Floppy} False
PS C:\Users\Kai> get-vmbios WindowsWhistler
VMName StartupOrder NumLockEnabled
------ ------------ --------------
WindowsWhistler {CD, IDE, LegacyNetworkAdapter, Floppy} False
PS C:\Users\Kai>