• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Powershell snapin and registry

Scheduled Pinned Locked Moved Solved
Windows Problems
6
16
3.0k
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.
  • A
    aruhuno @Joe Schmitt
    last edited by aruhuno Apr 16, 2018, 2:05 AM Apr 16, 2018, 7:47 AM

    My apologies for my absence.

    @Wayne-Workman
    I think you put your finger on the problem.

    @jbsclm
    AVG don’t remove this key.

    @joe-schmitt
    %WINDIR%\sysnative\windowspowershell\v1.0\powershell.exe does not exist.
    I test with %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe but not working…

    "Parce que la connaissance appartient à tout le monde", inios.fr

    T 1 Reply Last reply Apr 16, 2018, 12:10 PM Reply Quote 0
    • T
      Tom Elliott @aruhuno
      last edited by Tom Elliott Apr 16, 2018, 6:10 AM Apr 16, 2018, 12:10 PM

      @aruhuno the native path does exist, it’s just not tab accessible. Unless of course powershell isn’t installed I suppose.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 1
      • A
        aruhuno
        last edited by aruhuno Apr 19, 2018, 8:14 AM Apr 19, 2018, 2:11 PM

        It works with %WINDIR%\sysnative\windowspowershell\v1.0\powershell.exe!
        Why FOG don’t use by default this path?

        Thanks a lot for your help!

        edit: can you mark the post from Joe as solution please?

        "Parce que la connaissance appartient à tout le monde", inios.fr

        S 1 Reply Last reply Apr 20, 2018, 3:14 PM Reply Quote 0
        • S
          Szeraax @aruhuno
          last edited by Apr 20, 2018, 3:14 PM

          @aruhuno I think that the problem is that if we just always use that path, then all x86 installations would fail (I don’t believe that a 32bit machine has a sysnative folder). If we put in a check that will attempt to use the 64 bit powershell if its running on a 64 bit machine, I think that would be good. For now, I just plan to use that path instead of powershell.exe.

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Apr 20, 2018, 3:16 PM

            @Szeraax is correct. We do provide Snapin templates for both Powershell and Powershell 64 bit for this reason. Eventually when we allow the client to install as 64 bit on machines, then this problem won’t exist.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            S 1 Reply Last reply Apr 20, 2018, 3:17 PM Reply Quote 0
            • S
              Szeraax @Joe Schmitt
              last edited by Apr 20, 2018, 3:17 PM

              @joe-schmitt Good point. 32bit client is having to escape the normal system. 64 bit client would use powershell.exe and get the correct one by default. Anything us plebs can do to help get a 64bit client out?

              1 Reply Last reply Reply Quote 0
              • J
                Joe Schmitt Senior Developer
                last edited by Apr 25, 2018, 4:05 PM

                @Szeraax the client itself is actually already 64 bit compatible. It gets installed as 32 bit because the msi targets 32 bit. I suppose going forward I could either make 2 different installers (one for each architecture) or build a single installer that can target either.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                S 1 Reply Last reply Apr 25, 2018, 4:39 PM Reply Quote 0
                • S
                  Szeraax @Joe Schmitt
                  last edited by Apr 25, 2018, 4:39 PM

                  @joe-schmitt If you made it auto-target 64, would that potentially break people who use it to install 32bit programs?

                  T 1 Reply Last reply Apr 25, 2018, 5:19 PM Reply Quote 0
                  • T
                    Tom Elliott @Szeraax
                    last edited by Apr 25, 2018, 5:19 PM

                    @szeraax I doubt it. 32 bit installers usually have no issue installing in 64 bit systems, as you the the fog client installs and runs just fine, mostly, in 32 bit mode. You might run into issues using powershell or some scripts that might require a pure 32 bit mode but I can’t think of one that is that specific currently.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    S 1 Reply Last reply Apr 25, 2018, 5:59 PM Reply Quote 0
                    • S
                      Szeraax @Tom Elliott
                      last edited by Apr 25, 2018, 5:59 PM

                      @tom-elliott Powershell as of… a year or two ago VASTLY prefers to be run in the system native bitness. Hence, we had all those issues when I was trying to Import-Module for stuff that was on the system, but available only to the 64bit version of powershell. I doubt that you would have ANY problems from powershell if client were to auto-target either.

                      T 1 Reply Last reply Apr 25, 2018, 6:40 PM Reply Quote 0
                      • T
                        Tom Elliott @Szeraax
                        last edited by Apr 25, 2018, 6:40 PM

                        @szeraax I meant you wanting, for some reason, to run a 32 bit powershell script from a 64 bit instance.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        S 1 Reply Last reply Apr 25, 2018, 6:41 PM Reply Quote 0
                        • S
                          Szeraax @Tom Elliott
                          last edited by Apr 25, 2018, 6:41 PM

                          @tom-elliott Ah. I haven’t yet ever found a need to run x86 powershell on x64 machine.

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

                          200

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project