chore(deps): bump windows 11 to 22h2 september 2022

[tenthirtyam]

Summary of Pull Request

Bumps Windows 11 to the 22H2 September 2022 release.

In addition, in Windows 11 22H2 the value for the OS image has changed from Windows 10 Pro to Windows 11 Pro.

        <ImageInstall>
            <OSImage>
               <InstallFrom>
                  <MetaData wcm:action="add">
                     <Key>/IMAGE/NAME</Key>
                     <Value>${vm_inst_os_image}</Value>
                  </MetaData>
               </InstallFrom>
               <InstallTo>
                  <DiskID>0</DiskID>
                  <PartitionID>4</PartitionID>
               </InstallTo>
            </OSImage>
         </ImageInstall>

Signed-off-by: Ryan Johnson johnsonryan@vmware.com

Type of Pull Request

• This is a bugfix. type/bug
• This is an enhancement or feature. type/feature or type/enhancement
• This is a documentation update. type/docs
• This is a refactoring update. type/refactor
• This is a chore. type/chore
• This is something else.
  Please describe:

Related to Existing Issues

Issue Number: N/A

Test and Documentation Coverage

• Tests have been completed.
• Documentation has been added or updated.

Breaking Changes?

• Yes, there are breaking changes.
• No, there are no breaking changes.

[tenthirtyam]

Blocked.

Update to 22H2 results in a WinRM issue:

==> vsphere-iso.windows-desktop: IP address: 172.16.14.110
==> vsphere-iso.windows-desktop: Using WinRM communicator to connect: 172.16.14.110
==> vsphere-iso.windows-desktop: Waiting for WinRM to become available...

[tenthirtyam]

Error:

Solution: Recoding the windows-init.ps script.

[tenthirtyam]

LGTM! 🚀

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.