Skip to content

Hybrid powershell script release issues #8

@ggvaro

Description

@ggvaro

Hi CF,

At least in my latest node enrole for On-premises hybrid setup (windows 2019 10.0.17763 N/A Build 17763) I found that the powershell script is stuck twice here, in comments what I did to resolve it

[string[]]$supportedReleases = @(
    1809
    1903
    1909
    2004
    2009
    21H2 
)
  • It is complaining that 21H2 cannot be found, because was not a release in my scope deleting was enough to meke the script process, maybe '21H2' need to be escaped or something else

$release_id = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').DisplayVersion

  • Powershell registry command above returns null, I used instead ".ReleaseId" and worked

hope this helps others with the same issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions