Issue #15326 has been updated by Jeff Sussna.
It doesn't appear that the workaround (remove account = local constraint) works on Windows Server 2003. ---------------------------------------- Bug #15326: Scheduled_task does not accept domain user accounts https://projects.puppetlabs.com/issues/15326#change-69775 Author: Josh Cooper Status: Accepted Priority: Normal Assignee: Josh Cooper Category: windows Target version: 2.7.x Affected Puppet version: 2.7.17 Keywords: windows scheduled_task domain user Branch: >From ><https://groups.google.com/forum/?fromgroups#!topic/puppet-users/pkePgl72M6M> The `scheduled_task` resource type does not accept domain user accounts, though it should. <pre> scheduled_task { 'test': ensure => present, enabled => true, command => 'C:\test\test.bat', working_dir => 'C:\test', user => 'DOMAIN\oper', password => 'xxxxx', trigger => { schedule => daily, start_date => '2012-06-26', # Defaults to 'today' start_time => '09:05', # Must be specified } } </pre> The issue is that the logic for validating user/group accounts in `Puppet::Util::ADSI#sid_for_account` restricts the WMI query to local accounts. This is also an issue for files, e.g. setting the file owner to a domain user. We do need to be careful about WMI queries that can return a lot of data, e.g. get all users in the Administrators group. But I don't think that is a concern with `sid_for_account` method, since we're just looking up the SID for a particular user. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
