| On Windows servers after installation of Remote Desktop Services (Add-WindowsFeature RDS-RD-Server) the Puppet agent populates the system32 fact incorrectly with "C:\Users\username\WINDOWS\system32". Uninstalling RDS-RD-Server and rebooting the server returns the OS fact to "c:\windows\system32". With or without RDS-RD-Server installed the result of running the command:
wmic os get systemdirectory
is always "C:\Windows\system32" Example of the "facter os" command output: (`admwintert` - Domain user)
PS C:\Windows\system32> facter os
{
architecture => "x64",
family => "windows",
hardware => "x86_64",
name => "windows",
release => { full => "2016", major => "2016" },
windows => { system32 => "C:\Users\admwintert\WINDOWS\system32" }
}
Customer ran another test and was able to reproduce the behavior with a vanilla AWS AMI:
Windows_Server-2016-English-Full-Base-2019.10.09 (ami-0daaf340f2253cd6c)
Customer launched, renamed and domain-joined it and then installed puppet. Then installed the Remote Desktop Session Host and rebooted. 'dawintert' is also a domain account.
PS C:\Windows\system32> facter os
{
architecture => "x64",
family => "windows",
hardware => "x86_64",
name => "windows",
release => { full => "2016", major => "2016" } ,
windows => { system32 => "C:\Users\dawintert\WINDOWS\system32" }
} |
