Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-783

Puppet Windows Agent cannot be installed with a domain user on locales where the Administrators group has a different name / spelling

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • puppet-agent 5.0.0
    • None

    • Master Setup: Puppet 4.8.1, Puppet 3.8.1
      Nodes: Windows Server 2012R2 (German) , Windows Server 2016 (German)

    • Hide

      The Puppet agent installer, when specifying a domain account, should properly add the domain account to the local Administrators account, even when Administrators is named / spelled differently as a result of running on a non-US English locale.

      Show
      The Puppet agent installer, when specifying a domain account, should properly add the domain account to the local Administrators account, even when Administrators is named / spelled differently as a result of running on a non-US English locale.
    • Agent
    • 3
    • Agent 2017-06-14, Agent 2017-06-28
    • Hide
      Affects all localised Windows installation.

      Should add the Administrator user to to the localised "Administrators" group and the {{facts.d}} directory with localised "Everyone" permissions.
      E.g. on a localised French Windows, the permissions are now set to:
      {noformat}
      C:\Users\Administrator\Documents>icacls C:\ProgramData\PuppetLabs\facter\facts.d
      C:\ProgramData\PuppetLabs\facter\facts.d Tout le monde:(OI)(CI)(RX)
                                               BUILTIN\Administrateurs:(OI)(CI)(F)
                                               AUTORITE NT\Système:(OI)(CI)(F)
      {noformat}
      Show
      Affects all localised Windows installation. Should add the Administrator user to to the localised "Administrators" group and the {{facts.d}} directory with localised "Everyone" permissions. E.g. on a localised French Windows, the permissions are now set to: {noformat} C:\Users\Administrator\Documents>icacls C:\ProgramData\PuppetLabs\facter\facts.d C:\ProgramData\PuppetLabs\facter\facts.d Tout le monde:(OI)(CI)(RX)                                          BUILTIN\Administrateurs:(OI)(CI)(F)                                          AUTORITE NT\Système:(OI)(CI)(F) {noformat}
    • Manual
    • We should verify this change

    Description

      Hello together,

      i try to install the Puppet Agent on Windows under a Windows Domain User like this:

      msiexec /norestart /i puppet-agent-1.8.1-x64.msi PUPPET_AGENT_ACCOUNT_DOMAIN=my-domain.de PUPPET_AGENT_ACCOUNT_USER=username PUPPET_AGENT_ACCOUNT_PASSWORD=userpw

      if i do this, the puppet installer raise an error with the message:

      Failed to add user to group (-2147022676 username Administrators)

      from this message, iam confused. Because the group "Administrators" does exists (the most time) only on english operating systems. In German for example, the group is named "Administratoren" instead of "Administrators".

      I dont know if its a problem with my infrastructure, but i guess from this message, that the puppet agent just cant handle other operating system languages. That meens, that the Puppet Agent can run only as the normal local Administrator.

      What you think?

      Best Regards

      Attachments

        Issue Links

          relates to

          CI Blocker - An issue that is preventing (a) CI job(s) from running successfully PA-1189 facter acceptance external facts failing on win10 failed to create process: Access is denied

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          links to

          Web Link Associated PR

          Activity

            People

              Unassigned Unassigned
              Andoreasu Andoreasu Pek
              Eric Delaney Eric Delaney
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support