The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider (here's the code).
The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider ([here's|https://github.com/puppetlabs/puppet/blob/6.0.0/lib/puppet/provider/user/windows_adsi.rb#L111-L117] the code). The home property does not make sense on Windows, because the user's profile (which is the home's directory) will always be in C:\Users -- we already create/delete the user profile via. the managehome property. Furthermore, the HomeDirectory property does not seem to do anything useful in terms of implementing the home property of the User resource.
The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider ([here's|https://github.com/puppetlabs/puppet/blob/6.0.0/lib/puppet/provider/user/windows_adsi.rb#L111-L117] the code). The home property does not make sense on Windows, because the user's profile (which is the home's directory) will always be in C:\Users -- we already create/delete the user profile via. the managehome property. Furthermore, the HomeDirectory property does not seem to do anything useful from Puppet's perspective.
Thus, we should stop supporting the 'home' property for our Windows user provider. There are several paths we can take here: * Fail fast in terms of implementing the property validation code (i.e. the validate block) * Associate a feature with the home property of (e.g. sets_home_directory) and apply that feature to the current User resource providers that support the home property.