Fixes following errors when installing Office 2010
change from 'notrun' to ['0'] failed: '"\foo\bar\OFFICE14\Standard\x86\setup.exe" /modify Standardr /config "C:\Windows\Temp\office_config.xml"' returned 30066 instead of one of [0]
Failed to call refresh: '"\foo\bar\OFFICE14\Standard\x86\setup.exe" /modify Standardr /config "C:\Windows\Temp\office_config.xml"' returned 30066 instead of one of [0]
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
<!--
Fixes following errors when installing Office 2010
change from 'notrun' to ['0'] failed: '"\foo\bar\OFFICE14\Standard\x86\setup.exe" /modify Standardr /config "C:\Windows\Temp\office_config.xml"' returned 30066 instead of one of [0]
Failed to call refresh: '"\foo\bar\OFFICE14\Standard\x86\setup.exe" /modify Standardr /config "C:\Windows\Temp\office_config.xml"' returned 30066 instead of one of [0]
-->
This Pull Request (PR) fixes the following issues
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
Names of security objects built into Windows depend on the installation-time language. For example on a German system the "local administrators" group is called Administratoren rather than Administrators, causing puppet-msoffice to fail because being unable to set the correct owner group on office_config.xml. To make things worse, once set those names cannot be modified even when the default OS language is changed - if you want to rename Administratoren to Administrators you have to reinstall Windows.
Luckily, Puppet now understands Windows security identifiers and there is a well-known SID corresponding to Administrators regardless of the language used. Change group => 'Administrators' to group => 'S-1-5-32-544' and it will work regardless of whether your copy of Windows has been installed in English, German, Swahili, or Klingon.
Nb. Ideally the name of the built-in administrator user should be replaced by a SID too, especially given that in addition to language dependency that name can be changed by a certain Group Policy setting. Unfortunately that one is more tricky because its well-known SID is not fully static and I don't know if Puppet can be told to match user as S-1-5--500. On the other hand, I have yet to see this particular bit of puppet-msoffice fail even though the built-in administrator account isn't called Administrator on any of the machines I work with - so maybe Puppet handles this one internally.
<!--
Thank you for contributing to this project!
-->
