Re: [Puppet Users] Scheduled_task + ad user

235 views
Skip to first unread message

Josh Cooper

unread,
Jul 2, 2012, 1:27:33 PM7/2/12
to puppet...@googlegroups.com
Hi,

On Sat, Jun 30, 2012 at 4:30 PM, fpommier <fpomm...@gmail.com> wrote:
Hi,
When a want to  use scheduled_task for create a windows task and when i give a AD user, i have this message :
err: /Stage[main]/Mirnas/Scheduled_task[test]/ensure: change from absent to present failed: Invalid user: DOMAIN\oper

My user domain and the password are correct.
I have the same error if i change DOMAIN\oper by op...@domain.com or DOMAIN/oper
With a local user,  is working, but i need a AD user for my batch to work.
Is it a bug , a limitation or i miss something ? 
Thank for any help

   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
       }
    }

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/P1hXwgGE2CoJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

It is definitely a bug. I've filed this as http://projects.puppetlabs.com/issues/15326. You can probably just remove the `LocalAccount = True` condition from the WMI queries in `Puppet::Util::ADSI#sid_for_account` at lines 56-58.

Josh

--
Josh Cooper
Developer, Puppet Labs

fpommier

unread,
Jul 3, 2012, 12:19:46 AM7/3/12
to puppet...@googlegroups.com
Hi Josh,
Thank for your quick and good reply.
I remove "and LocalAccount = True' at line 56 and 58.
It now work perfectly.
Thanks again.
Fred
Hi,

To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Jeff Sussna

unread,
Aug 21, 2012, 6:18:12 PM8/21/12
to puppet...@googlegroups.com
Stupid question: where is the source file for this hack?
Hi,

To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Josh Cooper

unread,
Aug 21, 2012, 8:31:01 PM8/21/12
to puppet...@googlegroups.com, puppet...@googlegroups.com
Hi Jeff,

It should be lib/puppet/util/adsi.rb

Also please add yourself as a watcher to the ticket.

Josh

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ily02pJOJqsJ.

Jeff Sussna

unread,
Aug 22, 2012, 12:17:31 PM8/22/12
to puppet...@googlegroups.com
The patch is working on XP but failing on Server 2003. Same domain/user on both. Can manually set the task to the user in question so I know it's a valid user/pw known to the 2003 machine.

Jeff Sussna

unread,
Aug 23, 2012, 6:14:37 PM8/23/12
to puppet...@googlegroups.com
Also, it doesn't look like scheduled_task supports setting "only run when logged on".



On Tuesday, August 21, 2012 7:31:01 PM UTC-5, Josh Cooper wrote:
Reply all
Reply to author
Forward
0 new messages