This is a tracker for the lower-level v2v bug: RHEl-49761

After a successful Windows 2022 server guest migration using MTV 2.6.1, the "qemu-guest-agent" is not completely installed. The Windows Scheduled task is being created, however it is being set to run 4 hours in the future instead of the intended 2 minutes in the future. 

Testing is done in Eastern Time Zone. All physical (host) nodes (both in source VMware environment, and target OCP-V environment) have time synced against valid NTP server. Time sync is not a problem.

The following is output from the Windows `schtasks /QUERY` command:

```ps

PS C:\Users\Administrator> schtasks.exe /QUERY

Folder: \
TaskName                                 Next Run Time          Status
======================================== ====================== ===============
Firstboot-qemu-ga                        5/10/2024 1:47:00 PM   Ready
MicrosoftEdgeUpdateTaskMachineCore       5/11/2024 10:26:32 AM  Ready
MicrosoftEdgeUpdateTaskMachineUA         5/10/2024 12:56:32 PM  Ready

```

NOTE that the WALL CLOCK time when the VM was started was ~9:44am.  So all timestamps in the windows logs that say 1:44pm is 4 hours ahead of wall clock.