ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Discrepancy in Powershell version reporting.

    Scheduled Pinned Locked Moved IT Discussion
    powershell
    17 Posts 9 Posters 783 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Might be as simple as PS5 not being in the normal path. Check its absolute path.

      J 1 Reply Last reply Reply Quote 0
      • J
        JasGot @scottalanmiller
        last edited by

        @scottalanmiller said in Discrepancy in Powershell version reporting.:

        Might be as simple as PS5 not being in the normal path. Check its absolute path.

        That would have been too easy 🙂
        There is only one powershell installation and it is at:
        C:\Windows\System32\WindowsPowerShell\v1.0\

        Which is right where it belongs. I'm running the stand alone gui installer now to see if that works.

        1 Reply Last reply Reply Quote 0
        • black3dynamiteB
          black3dynamite
          last edited by

          Do you have WMF 5.1 installed?

          J 1 Reply Last reply Reply Quote 0
          • J
            JasGot @black3dynamite
            last edited by

            @black3dynamite said in Discrepancy in Powershell version reporting.:

            Do you have WMF 5.1 installed?

            That's the gui installer I'm going to install to see if it works. If it does, I should then be able to install it again with -force, or use Chocolaty with the upgrade option and see it go smoothly.

            1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender
              last edited by

              what version of windows are you on?

              J 1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato
                last edited by

                You need to reboot however so it shows the correct powershell version after the install. Did you do that?

                J 1 Reply Last reply Reply Quote 0
                • J
                  JasGot @Dashrender
                  last edited by

                  @Dashrender said in Discrepancy in Powershell version reporting.:

                  what version of windows are you on?

                  Server 2012

                  1 Reply Last reply Reply Quote 0
                  • J
                    JasGot @dbeato
                    last edited by

                    @dbeato said in Discrepancy in Powershell version reporting.:

                    You need to reboot however so it shows the correct powershell version after the install. Did you do that?

                    Sadly. Several times.

                    Busy weekend. I'll have to get back to this next week.

                    The ignition for this was the desire to start using Chocolaty. It has been one obstacle after another to get it off the ground. And know this, my goal is to get Powershell updated, .Net updated, and Chocolaty installed all from scripts within a backstage connection through SC.

                    So there are tons of scenarios that have to be worked out, and handled, all through scripting. :anguished_face:

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @JasGot
                      last edited by

                      @JasGot chocolatey is the easy one.

                      1 Reply Last reply Reply Quote 1
                      • P
                        psophos
                        last edited by

                        What version of .net is installed on the server?

                        I'm failing to remember which version of Powershell had a hard but silent requirement for a particular version of .net.
                        If memory serves it would install successfully (no errors) but would actually fail to install if the correct ver of .net was not already installed.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post