Hyper-V Integration Services Shows VM Created in 1600
-
Here's a new one on me and google-fu is failing me.
I have a client with a Windows Server 2012 R2 running 1 VM in Hyper-V. Everything works perfectly on the server and the VM except that integration services shows the vm was created on Dec 31 1600. Checked dates on both server and vm and everything is accurate. I checked the version of integration services and it is already on the most current version. And all updates have been applied to both host and vm. This isn't affecting anything as far as functionality but really weird. Anyone else seen this before?
-
Never seen that.
You could try exporting the VM, them importing it... but I don't know if that'll change the created date.
Or you could create a new VM, configure it the same way, and reuse the VHD.
-
It looks like the creation time parameter is missing there. Check this https://www.altaro.com/hyper-v/restoring-virtual-machine-creation-time/ for a way to fix it.
Edited: added correct link. -
@darek-hamann That link points to this post.
-
@murpheous said in Hyper-V Integration Services Shows VM Created in 1600:
@darek-hamann That link points to this post.
Try this one: https://goo.gl/vgSLnQ
-
Sorry, guys. pasted the link to this thread. The correct one is https://www.altaro.com/hyper-v/restoring-virtual-machine-creation-time/
