Re: [Puppet Users] Re: Scheduled_task?

2017-05-18 Thread Jason McMahan 
Thank you for confirming my suspicion Josh.

On Wednesday, May 17, 2017 at 11:09:14 AM UTC-5, Josh Cooper wrote:
>
>
>
> On Wed, May 17, 2017 at 5:34 AM, Jason McMahan  > wrote:
>
>> The full error is 
>>
>> Error: Failed to call 
>> #::NewWorkItem 
>> with HRESULT: -214702489
>> 3.:  The system cannot find the path specified.
>> Error: 
>> /Stage[main]/Profile::Windows::Applications::Sysinfo::Base/Scheduled_task[Automation/Inventory]/ensure
>> : change from absent to present failed: Failed to call 
>> #::New
>> WorkItem with HRESULT: -2147024893.:  The system cannot find the path 
>> specified.
>>
>> The folder exists but the task is not created nor seen.
>>
>> I believe i may just need to create it in the root but would like 
>> verification.
>>
>> Thank you
>>
>>
>>
>> On Tuesday, May 16, 2017 at 6:59:17 PM UTC-5, Jason McMahan wrote:
>>>
>>> Good day, 
>>> We were using the scheduled_task resource to create a task. It creates 
>>> the task however we nwed to create the task in a folder under task 
>>> scheduler.
>>> \automation\inventory
>>>
>>> We tried name => '\automation\inventory\
>>> But at run says can not find path.
>>> We looked at working_dir but that didn't sound promising either. Any 
>>> suggestions would be greatly appreciated. Thank you 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/53648950-dc88-4188-b2e4-678a1a14dec0%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> Puppet only supports v1 of the Windows task scheduler API (which is 
> present in 2003 and up), so I'm inclined to think folders are a v2 API 
> feature, which is filed as https://tickets.puppetlabs.com/browse/PUP-6455.
>
> Josh
>
> -- 
> Josh Cooper | Software Engineer
> jo...@puppet.com  | @coopjn
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3fac12f3-1ebf-45af-9d04-4459bb0ffda4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Scheduled_task?

2017-05-17 Thread Josh Cooper 
On Wed, May 17, 2017 at 5:34 AM, Jason McMahan 
wrote:

> The full error is
>
> Error: Failed to call 
> #::NewWorkItem
> with HRESULT: -214702489
> 3.:  The system cannot find the path specified.
> Error: /Stage[main]/Profile::Windows::Applications::Sysinfo::Base/
> Scheduled_task[Automation/Inventory]/ensure
> : change from absent to present failed: Failed to call
> #::New
> WorkItem with HRESULT: -2147024893 <(214)%20702-4893>.:  The system
> cannot find the path specified.
>
> The folder exists but the task is not created nor seen.
>
> I believe i may just need to create it in the root but would like
> verification.
>
> Thank you
>
>
>
> On Tuesday, May 16, 2017 at 6:59:17 PM UTC-5, Jason McMahan wrote:
>>
>> Good day,
>> We were using the scheduled_task resource to create a task. It creates
>> the task however we nwed to create the task in a folder under task
>> scheduler.
>> \automation\inventory
>>
>> We tried name => '\automation\inventory\
>> But at run says can not find path.
>> We looked at working_dir but that didn't sound promising either. Any
>> suggestions would be greatly appreciated. Thank you
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/53648950-dc88-4188-b2e4-678a1a14dec0%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

Puppet only supports v1 of the Windows task scheduler API (which is present
in 2003 and up), so I'm inclined to think folders are a v2 API feature,
which is filed as https://tickets.puppetlabs.com/browse/PUP-6455.

Josh

-- 
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2Bu97ukAMKHZDLmD-G8TyPDKNGYdDJf9uaVPW1AVgBdHOs3t9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Scheduled_task?

2017-05-17 Thread Jason McMahan 
The full error is 

Error: Failed to call 
#::NewWorkItem 
with HRESULT: -214702489
3.:  The system cannot find the path specified.
Error: 
/Stage[main]/Profile::Windows::Applications::Sysinfo::Base/Scheduled_task[Automation/Inventory]/ensure
: change from absent to present failed: Failed to call 
#::New
WorkItem with HRESULT: -2147024893.:  The system cannot find the path 
specified.

The folder exists but the task is not created nor seen.

I believe i may just need to create it in the root but would like 
verification.

Thank you



On Tuesday, May 16, 2017 at 6:59:17 PM UTC-5, Jason McMahan wrote:
>
> Good day, 
> We were using the scheduled_task resource to create a task. It creates the 
> task however we nwed to create the task in a folder under task scheduler.
> \automation\inventory
>
> We tried name => '\automation\inventory\
> But at run says can not find path.
> We looked at working_dir but that didn't sound promising either. Any 
> suggestions would be greatly appreciated. Thank you 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/53648950-dc88-4188-b2e4-678a1a14dec0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: scheduled_task changes on every puppet run

2014-08-18 Thread Rob Reynolds 
On Wed, Aug 13, 2014 at 12:55 PM, aaronm  wrote:

> I am getting similar logs every day, but I am not using any scheduled
> tasks in my manifests...
>
> (**this is on PE 3.3 installed a week or two ago**)
> trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' =>
> '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' =>
> 'daily', 'start_time' => '13:00'}]'
>
>
> /Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger
>
> /opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp
>
> ---
>
> (**this is from a longrunning PE server running 3.2 installed many months
> ago**)
> trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' =>
> '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' =>
> 'daily', 'start_time' => '13:00'}]'
>
>
> /Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger
>
> /opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp
>


The PE catalog includes a scheduled task. Would you mind following up on
the pe-users group?



>
> On Thursday, August 7, 2014 7:36:18 AM UTC-4, cko wrote:
>>
>> Hi,
>>
>> I'm using the following scheduled_task on one of my windows server 2008
>> r2 boxes:
>>
>> scheduled_task { 'reboot':
>>>   command   => 'C:\WINDOWS\System32\shutdown.exe',
>>>   arguments => "-r -f -t 01",
>>>   user  => 'SYSTEM',
>>>   trigger   => {
>>> schedule=> weekly,
>>> start_time  => '06:00',
>>> every   => 1,
>>> day_of_week => sun,
>>>   }
>>> }
>>
>>
>> Puppet creates the task and works just fine.
>>
>> However, on every single puppet run the trigger changes (even though I
>> didn't change the puppet code).
>>
>> The report shows the following output:
>>
>>
>>> *Notice: /Stage[main]/Main/Node[NODE]/Scheduled_task[reboot]/trigger:
>>> trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly',
>>> 'start_date' => '2014-8-7', 'start_time' => '06:00'}' to '[{'day_of_week'
>>> => ['sun'], ' every' => '1', 'schedule' => 'weekly', 'start_time' =>
>>> '06:00'}]' Notice: Finished catalog run in 6.55 seconds*
>>
>>
>> Is there anything I can do to achieve idempotence with this scheduled
>> task?
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e7823a79-676c-4c6e-a985-378d264e91f0%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2014 , September
20-24 in San Francisco*
*Register by September 8th to take advantage of the Final Countdown

*
*--**save $149!*

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMJiBK7Qhv3dfBCGi8Va9%2Bo07oC0s-EiJw-e_o%3DFvERAQtvWdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: scheduled_task changes on every puppet run

2014-08-13 Thread aaronm 
I am getting similar logs every day, but I am not using any scheduled tasks 
in my manifests...

(**this is on PE 3.3 installed a week or two ago**)
trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => 
'2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 
'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp

---

(**this is from a longrunning PE server running 3.2 installed many months 
ago**)
trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => 
'2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 
'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp 

On Thursday, August 7, 2014 7:36:18 AM UTC-4, cko wrote:
>
> Hi,
>
> I'm using the following scheduled_task on one of my windows server 2008 r2 
> boxes:
>
> scheduled_task { 'reboot':
>>   command   => 'C:\WINDOWS\System32\shutdown.exe',
>>   arguments => "-r -f -t 01",
>>   user  => 'SYSTEM',
>>   trigger   => {
>> schedule=> weekly,
>> start_time  => '06:00',
>> every   => 1,
>> day_of_week => sun,
>>   }
>> }
>
>
> Puppet creates the task and works just fine.
>
> However, on every single puppet run the trigger changes (even though I 
> didn't change the puppet code).
>
> The report shows the following output:
>  
>
>> *Notice: /Stage[main]/Main/Node[NODE]/Scheduled_task[reboot]/trigger: 
>> trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly', 
>> 'start_date' => '2014-8-7', 'start_time' => '06:00'}' to '[{'day_of_week' 
>> => ['sun'], ' every' => '1', 'schedule' => 'weekly', 'start_time' => 
>> '06:00'}]' Notice: Finished catalog run in 6.55 seconds*
>
>  
> Is there anything I can do to achieve idempotence with this scheduled task?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e7823a79-676c-4c6e-a985-378d264e91f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: scheduled_task created but didn't see task under 'Task Scheduler' GUI

2013-04-25 Thread beyonddc . storage 
Nevermind, please ignore my post.  I was looking at the wrong place, the 
task did added successfully.  It was under the "Task Scheduler Library".

Thanks...

On Thursday, April 25, 2013 10:00:52 AM UTC-4, beyonddc...@gmail.com wrote:
>
> Hi All,
>
> I created a scheduled_task resource and applied it.  Puppet claimed that 
> it did added successfully but when I go into the 'Task Scheduler' GUI, no 
> such task exist.  When I delete the same scheduled_task, Puppet found it 
> and deleted it.  Deleting the same scheduled_task twice, Puppet would do 
> nothing.  That seems to me that the task did created at the first place, 
> then how come I couldn't see it in the 'Task Scheduler' GUI (I did press 
> the refresh button in the Task Scheduler GUI).
>
> Here's the output from Puppet
> C:\ism_test>puppet apply scheduled_task.pp
> Warning: Could not retrieve fact fqdn
> Notice: /Stage[main]//Scheduled_task[scheduled_task_test]/ensure: created
> Notice: Finished catalog run in 0.88 seconds
>
> C:\ism_test>puppet apply scheduled_task.pp
> Warning: Could not retrieve fact fqdn
> Notice: /Stage[main]//Scheduled_task[scheduled_task_test]/ensure: removed
> Notice: Finished catalog run in 0.20 seconds
>
> C:\ism_test>puppet apply scheduled_task.pp
> Warning: Could not retrieve fact fqdn
> Notice: Finished catalog run in 0.17 seconds
>
> Here's the scheduled_task resource
> scheduled_task { 'scheduled_task_test' :
> name => "DavidTest123",
> command => 'C:\windows\system32\notepad.exe',
> ensure => present,
> enabled => true,
> trigger => {
> schedule => daily,
> start_time => '23:00',
> }
> }
>
> Thanks!
>
> David
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.