Disabling Manually Scheduled Tasks in PP2010

(Also sento to Project Server Forum)
Hi All.
Even if the new feature is cool and often useful, it is not always seen to be accepted in tightly controlled environments; I'm wondering if it's possible to disable the ability to create and/or manage manually scheduled tasks on Project 2010 by client or
Enterprise policy; I'm aware of 2010 SP1 Server settings related to client default mode, assignments publishing and warning at publishing but I'm looking for a way to disable the feature on clients or inhibit project save and publishing.
Any suggestion?
Many thanks.
Paolo
Paolo Ajani - KPNET

in PWA, under the Additonal Server settigns there is a "task mode setting" section that can be used to set the default and override capabilities, however while the default setting does appear to work, the "manaully scheduled tasks can be published" and
the "user can override" options do not. Pending gettgin our custom code in place, we created a custom ribbon task tab & group that didn't contain the "buttons" that allowed the user to change them
<input id="ctl00_ctl00_PlaceHolderMain_PWA_PlaceHolderMain__taskModeSection_ctl01__taskModeAllowManualPublish" name="ctl00$ctl00$PlaceHolderMain$PWA_PlaceHolderMain$_taskModeSection$ctl01$_taskModeAllowManualPublish" type="checkbox" value="on" /> Manually
Scheduled tasks can be published to team members
Default task mode in new projects:
<input id="ctl00_ctl00_PlaceHolderMain_PWA_PlaceHolderMain__taskModeSection_ctl01__taskModeDefaultManuallyScheduled" name="ctl00$ctl00$PlaceHolderMain$PWA_PlaceHolderMain$_taskModeSection$ctl01$taskModeDefault" type="radio" value="_taskModeDefaultManuallyScheduled"
/> Manually Scheduled <input CHECKED="checked" id="ctl00_ctl00_PlaceHolderMain_PWA_PlaceHolderMain__taskModeSection_ctl01__taskModeDefaultAutomaticallyScheduled" name="ctl00$ctl00$PlaceHolderMain$PWA_PlaceHolderMain$_taskModeSection$ctl01$taskModeDefault"
type="radio" value="_taskModeDefaultAutomaticallyScheduled" /> Automatically Scheduled
<input id="ctl00_ctl00_PlaceHolderMain_PWA_PlaceHolderMain__taskModeSection_ctl01__taskModeAllowDefaultOverride" name="ctl00$ctl00$PlaceHolderMain$PWA_PlaceHolderMain$_taskModeSection$ctl01$_taskModeAllowDefaultOverride" type="checkbox" value="on" /> Users
can override default in Project Professional

Similar Messages

Disable all scheduled tasks?

We have around 40 scheduled tasks, many running every 10 to 20 minutes. I want to import a CAR file of these scheduled tasks to a new server, but I don't want them to execute on the new server until I can disable the task on the old server. I would rather use a CAR file than create each one manually. Is there a way to disable all scheduled tasks on the new server?
Thanks,
Steve

Hi Florian,
Adobe Acrobat Reader DC is set up for continuous updating.
You can modify those settings via the Adobe Customization Wizard DC or the Windows Registry
For the Windows Registry setting please check: Windows Updates
Regards,
Rave

Can summary tasks be prevented from toggling to "Manual Scheduled" Task Mode?

Hi gang,
Can summary tasks be prevented from toggling to "Manual Scheduled" Task Mode? I am using MS Project 2013 Professional, and have the Task Mode defaulted to "Auto Scheduled" for new tasks, and noticed that if I "accidentally"
enter some text in the summary task's Duration field that the text gets accepted and the Task Mode for that Summary Task toggles to "Manual Scheduled".
Perhaps should be my 1st question, is this normal behaviour?
Thanks in advance
\Spiro Theopoulos, Montreal, QC (Canada)

Spiro,
I can confirm the same behavior you are seeing. I am not sure of the design decision based on this, and I do not think there is way to lock summary tasks to be always Autop Scheduled. Sorry!
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

How to disable scheduled task through database?

I would like to know to disable scheduled task without OIM running, preferably through the database.
OIM has out of the box schedule tasks that are set to run when OIM starts, and I would like to prevent that from happening.
Is is possible to disable these tasks when OIM is not running?
if possible I would like to know what I need to do, preferably through the database

The QRTZ92_TRIGGERS table contains the trigger time of the schedule tasks. You can directly modify the START_TIME and the NEXT_FIRE_TIME columns to future dates in order to prevent the scheduled jobs from starting.
You can also stop the Scheduler, which is responsible for kicking off the scheduled jobs.
To manually stop the Scheduler go to http://OIM_HOST:OIM_PORT/SchedulerService-web/status
You can configure the oim-config.xml so that the Scheduler is not started when OIM starts.
Reference: Managing Scheduled Tasks
To disable a schedule task, you have to have OIM running. You can use the APIs, modify the schedule tasks metadata (<taskStatus>false</taskStatus>), or use the UI to disable the schedule tasks.

CcmEval Scheduled task not being created with "Access Denied" error 0x80070005 only on XP machines

Before coming on here I checked out http://social.technet.microsoft.com/Forums/en-US/ddbfe6c3-ee54-4b2a-a3a7-a6515d974f76/client-check-failed-on-xpserver-2003-systems-onlyccmeval-is-not-being-scheduled?forum=configmanagerdeployment (GPO
to allow scheduled tasks by users) and another thread about a hotfix that seems to be pre-XP SP3 and pre-CM 2012 R2.
That said, I'm having an issue many seem to have, but I can't find the answer. From what I understand SCCM uses the user context to create the CcmEval task, but in XP users cannot set a task to run as any other user (ie SYSTEM in this instance) so what is
the workaround? I can't just give users Administrator permissions to install the client.
The exact log entries are:
<![LOG[Client evaluation task doesn't exist.]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="2" thread="4356" file="ccmevalcheck.cpp:705">
<![LOG[Client evaluation task is not found or is disabled or is not compliant, perform remediation]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="2"
thread="4356" file="ccmevalcheck.cpp:341">
<![LOG[Attempting to recreate client evaluation task.]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="1" thread="4356" file="ccmevalcheck.cpp:833">
<![LOG[Task scheduler 2.0 is not supported, peform task registration with 1.0 API.]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="1" thread="4356"
file="ccmevaltask.cpp:345">
<![LOG[Failed to delete task Configuration Manager Health Evaluation (0x80070002).]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="2" thread="4356"
file="ccmevaltask.cpp:379">
<![LOG[Failed to create task item (0x80070005).]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="3" thread="4356" file="ccmevaltask.cpp:387">
<![LOG[Failed to create client evaluation task.]LOG]!><time="19:05:43.548+360" date="12-14-2013" component="CcmEvalTask" context="" type="2" thread="4356" file="ccmevalcheck.cpp:850">
The bolded section is what's telling me it's Access Denied, and manual creation of any program task set to run as SYSTEM tells me the same- users cannot do this; only admins can.
What can I do?

So after sifting through some RSOP results and GPO objects I found a policy that wasn't necessarily prohibiting creation of them. (Not where you think it would be - under
Administrative Templates > Windows Components > Task Scheduler > "Prohibit New Task Creation" -
this was set to allow them) but this one I found was a File Permissions policy that set SYSTEM permissions to READ and EXECUTE.
I've changed this to FULL CONTROL for SYSTEM. I'm unable to get on the machines to examine everything closely, but from what I can see at least one of them has remediated themselves and now has a successful client check in the console. Hopefully the rest
of them will come around as GP updates itself and the client does an evaluation to remediate the Scheduled Task.
Hopefully this helps someone in the future as well.

ColdFusion 11 Scheduled Task & IIS 7.5

I have a scheduled task registered in ColdFusion 11 Admin console. ColdFusion 11 is hosted over IIS 7.5. The schedule task is to run 1 perticular file from sub application of the main app. After upgrading application from ColdFusion 9 to ColdFusion 11, scheduled task stopped working.
Note that, on IIS, main App has "Anonymous Authentication - Disabled" and "Windows Authentication - Enabled" ...
While for sub app (which is being called by scheduled task) has "Anonymous Authentication - Enabled" and "Windows Authentication - Disabled".
Moreover, when I try to run the scheduled task manually, it shows "Authentication falure" error in log file as
HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.
Any help would be greatly appriciated.
Thank you.

I've been fighting the identical problem since upgrading from CF8 on Windows Server 2008R2 with SSL enabled. The main CF application's folder is set for Windows Authentication This is happening on two different test servers- one running CF10 and the other running CF11, both of which had been running CF8 tasks with no problems. IIS settings for the subfolder with the scheduled task have only Anonymous authentication enabled (which is set to use the Application Pool identity that the Application Pool's identity is set to). I've set the file system permissions to allow Everybody, as well as IUSR, on the .CFM in question, and have tried using both HTTP and HTTPS forms of the URL in the scheduled task settings.
I can use the same HTTP/HTTPS URL in a browser directly (without authenticating to the server's application first) and the .CFM runs flawlessly. The CF http.log file shows Status Code=401, and saving the scheduled task output shows "IIS 7.0 Detailed Error - 401.2 - Unauthorized". What has changed in CF10 and CF11 if the underlying IIS server settings that worked before haven't changed?
Thanks,
Myron

Windows 2008 R2 server Scheduled Task not working

I have a batch file that writes to a file, when I click it manually it works. However when I have it set in a scheduled task it will create the file but it will not write to the file.
How can I fix this?

Hi,
1.
Please try to make sure the
Task Scheduler: Service is running.
For details: run 'services.msc', Scroll down to the 'Task Scheduler' service, Check the 'Startup Type' column, The 'Startup Type' should be set to "Automatic",
Check the 'Status' column.
If the service is started, it will list 'Started' in the 'Status' column.
2.
Please try to make sure Group Policy preventing the user to run the task.
3.
Please try to make sure UAC has been disabled.
4.
Please try to enabled the
policy Inclusion list for moderate risk file types, and fill ‘.bat’ in the blank.
For details:
User Configuration -> Administrator Templates -> Windows Components -> Attachment Manager
In addition, please try to refer
this to troubleshoot.
If the issue persist, please try to collect more information for further analyze:
Event log
==============
1. Click "Start", click “Run”, input "eventvwr" and press Enter.
2. Expand the "Windows Logs" node on the left pane, right-click on "System" and click "Save All Events As"; in the pop-up window, click to choose the Desktop icon
on the left frame, input "sys" in the "File name" blank, and then click save.
3. Expand the “Applications and Services Logs”. Click the arrow next to Microsoft, and then Windows, and then TaskScheduler. Click Operational. Click
"Save All Events As"; in the pop-up window, click to choose the Desktop icon on the left frame, input "policy" in the "File name" blank, and then click save.
4. Locate the two saved log files on the Desktop and send them to us.
GPMC.log
==================
a.
On domain controller, click Start -> Run, type GPMC.MSC, it will load the GPMC console.
b.
Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper user in the wizard)
c.
Right click the resulting group policy result and click the "Save Report…" => save report to save the report to a HTML file and send it to me.
please contact me with my account:
[email protected] to get a workspace to upload the information.
Hope this helps!

Scheduled task won't run .bat file

Hi. On Windows Server 2008 I have a scheduled task that calls a .bat file. The fist step in the .bat file is write to a log file to the same directory in which the .bat file exists. This allows me to find out if it is ever run. When the .bat file is run from a command prompt it runs as expected writing to the log file and completing its actions. My problem is that when I run the scheduled task manually or allow it to run when scheduled it appears to run but the .bat file is never run. No log file is ever created. The History tab in the properties of the scheduled tasks shows the task being started and running then completing with an operation code of 2. I've disabled the UAC for the user account. I've set the task to run as the Administrator user and verified the permissions for that user. I know the password is correct for the task because I can make changes to the properties and save those changes with the username/password. I'm at a loss for further troubleshooting steps. Can anyone point me in the right direction to figure out why these .bat files are not being run?

So I had this problem, I double clicked on the .bat and notepad opened the .bat. I ran through this whole long and very absorbing thread of this forum.   I wanted to save the entries that were most helpful, so I copied and pasted into
a notepad document (.txt) I could not find a way to attach it here, so I copied and pasted that below. I called it a synopsis.... Did I spell that right?
As you can see, I added my experience at the top (A and B). The stuff I copied is noted with the original author. This is the first time I posted anything to these here microsoft forums, although I have been telling computers what to do for 40+ years.
So hope I did not break any social protocols here.
==================================== Begin ====================================
     Running A Dot Bat File in Windows Server 2008 Vista 7 etc and beyond V01
============================================================================
This was created as a synopsis of the entries at the following forum location:
http://social.technet.microsoft.com/Forums/en/winservermanager/thread/d47d116e-10b9-44f0-9a30-7406c86c2fbe
A) manually
     This is an opinion added by Thomas Rock
    1) Open a command window (that would be cmd.exe)
    2) In the command window navigate to the directory containing the .bat file and it's dependents
           ex... C:\Program Files (x86)\Bobs\Your\Uncle
    3) Run the .bat file by typing the name including the .bat extension (in the command window of course)
             TheBatFile.bat
       Note: Using this method, the .bat file will run in the current command window directory (the directory where the .bat file is located)
                         (this is the key for getting it to run in the task scheduler... Start in folder option)
B) The double click
            This is an opinion added by Thomas Rock
     1) Using Windows exlporer, find the .bat file
     2) use the mouse or other device to double click on the .bat file
     3) if it does not run (in my case the wordpad application opened the .bat file)
          a) make sure that the .bat file extension is associated with the program c:\windows\system32\cmd.exe
          b) make sure the profile you are using has rights to run the cmd.exe
          c) make sure the profile has the rights to the directories, the .bat and any other objects used or affected by the .bat file processing.
C) As a task using task scheduler
     Proposed As Answer by Brian Vandemark Wednesday, September 02, 2009 9:36 PM
1) Make sure that the task is set to "configure for Windows Vista or Windows 2008" on the first page of the task properties (under the "general" tab)
2) Make sure that the task is set to "start in" the folder that contains the batch file:
      a) open the task properties
      b) click on the "actions" tab
      c) click on the action and then the "edit" button at the bottom.
      d) In the "Edit Action" Window there is a field for "start in (optional)" that you set to the path to the batch file.
      e) be sure to include an end backslash for the start in path "C:\dir1\dir2\"    (the last backslash is not optional)
3) Make sure that the task is running as an account that has explicit "Full access" permissions to all these things:
      a) the .bat file itself
      b) the folder containing the .bat file
      c) the target files/folders that are affected by the .bat script.
           Note: Inherited permissions did not seem to work.
4) Make sure that the account running the task is a member of the local "administrators" group for this machine
5) Make sure that the task is set to "run whether logged on or not"
6) Tick the box "Run with highest privileges".
       Note: Point 6 here was from Edson F. Lima Wednesday June 30 2010 1:35 PM
                  The original point 6 was moved to point 7.
7) The Task should run successfully with expected output when you right-click on the task and select "run"
        If it does that then it will run successfully when you are logged off.
D) Still another way as a task using task scheduler
      Proposed As Answer byDarren Wallace Thursday, July 15, 2010 1:41 AM
This has been bugging me for 6 or 7 months.
I don't have admin rights to the box and the guy who does is very busy...
so I've felt the range of emotions mentioned above.
I tried most everything above as well. But what seemed to get my processes processing, was ...
   • on the General tab, I clicked the Change User or Group button
   • in Select User or Group (first smaller dialog box) I clicked the Advanced... button
   • in the next Select User or Group (second bigger dialog box) I clicked the Find Now button
   • in the Search results I selected the Administrators (a group) and it returned SERVERname\Administrators into the "Enter the object name to select" entry in the previous dialog box
   • then I clicked OK and returned to the General tab above
   • the options to Run only when user is logged on and Run whether user is logged on or not are no longer available
   • then I made sure that the Run with highest privileges was checked
   • then I clicked OK and during the next scheduled time to run ... it ran
   Note: See note in A) Manually above.
E) Task scheduler recommendation
     Proposed As Answer byTamusJRoyceThursday, December 01, 2011 3:42 PM
I have found .bat and .cmd files do not run correctly either.
    My solution: Don't run the batch file directly.
       Have TaskScheduler run: cmd.exe
          with parameter: /C YourBatchFile.bat
         and start in: C:\SomePath\ (without quotes!) where C:\SomePath\YourBatchFile.bat exists.
        And then select the radio button for it to run regardless if you are logged in or not.
Exit errors may not be logged to the Event Log (they weren't when the .bat ran directly from Task Scheduler when I was logged in), so I find it best to manually log your own Event in case a error occurs and you want to send an email.
REM Logs an event which causes eventlog to send an email when it fails. Also, "/l application" needs to be lowercase.
eventcreate /t error /id 203 /l application /d "your logged description."
And then make a completely separate task with a trigger: On an event. Basic Selected. Log: Application. Source: EventCreate. Event ID: 203. And have the action on this task send an email (attaching any generated log files, if needed).
Hopefully helpful (took me 3 days to figure all this out...gar)
===================================== End ===================================
     Running A Dot Bat File in Windows Server 2008 Vista 7 etc and beyond V01
============================================================================

OIM - Understanding the scheduled-task User Operations

Hi,
Could anybody here explain what that task means?
The manual says:
This scheduled task performs the operation specified by the UserOperation attribute on the user account specified by the UserLogin attribute
Does anybody here have an example of a scenario that this task could be useful?
Regards
HH

Pretty simple. That scheduler is used to perform some actions on the OIM user account on a pre-defined schedule. That means you can perform ENABLE, DISABLE, or DELETE actions on any OIM user. And the attribute values could be:
UserLogin - OIM User Login
UserOperation - ENABLE
The above scheduler run will enable the user if its disabled. Now the utility part. Consider the following use cases:
*1)* You terminated any user, say User001 and you want to Disable this user and all its provisioned resources at 18:00 hours once he finishes all the office works, and if you directly Disable the user from Disable User button the User and all his resources would be gone immediately. So you can set this scheduler to run at 18:00 hours with the values User001 and DISABLE
*2)* You are an OIM help-desk guy and OIM administrator doesn't want you to have access to menu item Users because he doesn't want you to have a look at the OIM user personal details but he still want that you can actually perform enable-disable actions on OIM. In such case he will give you access to Manage Schedule Task menu-item so that you can perform the daily operations activity. This will be a solution to the use-case.
Thanks
Sunny

Scheduled Tasks Not working

Hi All,
I have an scheduled tasks on windows server 2008 standard, Which were working fine from couple of years.
Now we are facing the issue of skipping the tasks without any error in history tab.
" Next Run Time " is getting updated But the "Last Run Time" is in hold.
We had tried troubleshooting following steps:
1) Firstly, Windows update was cancelled & Restarted the server (Tasks started working fine with the End Result for 2 Days then Stopped)
2)Deleted all the tasks & scheduled the tasks again then restarted (Tasks started working again with the final outcome for few days then Stopped Issue started again)
Now we are confused and searched many Forums but we didn't find the solution.
We have 7 Tasks which triggers an .EXE File. It Runs Manually & do the process.
I have seen this System Task Running always "Certificate Services Client automatically manages digital identities such as Certificates, Keys and Credentials for the users and the machine, enabling enrollment,
roaming and other services" is this might be the reason..
Need the solution ASAP, I request all pro's to find me a solution.
Thanks

Hi,
Please check if there is a "CertificateServiceClient" in Task Scheduler.
As you suspect it is the cause, test to disable "Certificate Services Client service" in Services.msc to see if issue still exists.
If it is related, try to Increase the interval of SystemTask and UserTask under "CertificateServiceClient" in Task Scheduler to see if issue is affected.
If you have any feedback on our support, please send to [email protected]

Windows 2008 Server SFTP Scheduled Tasks fails to execute sftp commands

I have a scheduled task that pulls in Human Resources data using sftp public / private key combination. It was associated with user who has recently left the company and their account has been disabled. Everything I've read
so far leads me to believe that I need to establish the sftp connection and create a registry entry for another user... I don't want this application to be dependent on any particular user. I've stored the key set on a share that is
open to any system administrator on the server and created a batch job similar to:
Del oldFile.txt
"psftp.exe <user>@<server> -i <PrivateKeyLocation> -b <FtpComands>".
The old file gets deleted fine via scheduled task or manual, but the new file only gets pulled when running it directly from my account.
Any suggestions would be greatly appreciated.

The list of ftp commands that you are passing in to psftp.exe may need user specific resources (for example, a mapped drive). But it's difficult to say though without looking at what the psftp commands do. If the available commands for psftp.exe
are not flexible enough, you might want to look at other solutions like Sysax FTP Automation.

Windows Server Backup scheduled task run successfully but backup do not start (not running) on Windows Server 2012

Hi,
A backup job has been setup on Windows Server 2012 (Platform: Win32NT; ServicePack: ; Version: 6.2.9200.0; VersionString : Microsoft Windows NT 6.2.9200.0) via Windows Backup Software UI (Local Backup 1.0).
It is appearing as a scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup" belonging to user 'nt authority\system' in task scheduler.
The problem is that the Backup job never start despite the scheduled task running and completing successfully (when run automatically or manually)!
Would you be able to explain why and assist in resolving that issue?
Here is what we know:
When the backup is run manually via the Windows Backup Software UI, it works fine.
When the backup is run via command line (as set in schedule task) in a cmd command prompt (as local/domain 'administrator' or as 'nt authority\system' which is possible by running command prompt via 'PsExec.exe -i -s cmd'), something like "%windir%\System32\wbadmin.exe
start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet", it works fine.
If you manually run the preset scheduled task while logged in as administrator, the task run and complete successfully but the backup job does not start.
Idem if you schedule task is run automatically at scheduled time.
The schedule task run and complete successfully but the backup job does not start.
It is confirmed by running the following in a command prompt as 'nt authority\system':
schtasks /run /tn "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup"
SUCCESS: Attempted to run the scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup".
Despite success result, the Backup job does not start running...
No errors or warning appears anywhere in Event Logs (Microsoft > Windows > Backup or Task Scheduler) nor in the scheduled task History tab. The schedule task complete successfully but no Backup job is run...
If scheduled task automatically set by Windows Backup software is duplicated (copied) and set manually it runs fine as 'administrator' and as 'nt authority\system' (subject that 'nt authority\system' is added to the 'Backup Operators' AD group).
Here is an export of the current pre-set schedule task, is there any settings that need to be changed to make it works?
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
    <Author>MYDOMAIN\SERVER1</Author>
    <SecurityDescriptor>D:AR(A;OICI;GA;;;BA)(A;OICI;GR;;;BO)</SecurityDescriptor>
</RegistrationInfo>
<Triggers>
    <CalendarTrigger id="Trigger 1">
      <StartBoundary>2014-07-14T21:00:00</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByDay>
        <DaysInterval>1</DaysInterval>
      </ScheduleByDay>
    </CalendarTrigger>
</Triggers>
<Principals>
    <Principal id="Author">
      <UserId>S-1-5-18</UserId>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
</Principals>
<Settings>
    <MultipleInstancesPolicy>Parallel</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>true</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>false</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
    <UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>P3D</ExecutionTimeLimit>
    <Priority>7</Priority>
</Settings>
<Actions Context="Author">
    <Exec>
      <Command>%windir%\System32\wbadmin.exe</Command>
      <Arguments>start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet</Arguments>
    </Exec>
</Actions>
</Task>
Thank you in advance for your feedback.

Once again, the issue is not to run the backup manually from the command line but to have it run via the scheduled task setup by the Windows Backup software.
By default, the schedule task is to be run as NT Authority\System, and when run under this account, the backup does not start (even though account is member of Backup Operators) and job can manually be run via elevated command prompt. This is not a normal
behavior and constitute a major bug in Windows Server 2012.
From my understanding the NT Authority\System account is a built-in account from Windows that should by default be part of the Administrators group (built-in) even though it does not explicitly appears like it in AD by default.
This account shall have by default Administrators rights and Backup Operators rights (via the Administrators group) without being explicitly added to those groups (http://msdn.microsoft.com/en-gb/library/windows/desktop/ms684190%28v=vs.85%29.aspx). By design
it is supposed to be the most powerful account which has unrestricted access to all local system resources. If that is not the case (as it seems) then this would constitute a major bug in Windows Server 2012 edition.
As said previously and as you confirmed, currently by default NT Authority\System on Windows 2012 server cannot start backup manually via an elevated command prompt unless it is manually added to Backup Operators (or Administrators) group. But wouldn't that
constitute a bug of Windows Server 2012?
Our server has not yet been restarted since I added NT Authority\System account to the Administrators group explicitly manually so I cannot yet confirmed it would sort the issue. Indeed it is heavily in use so cannot easily be restarted. Will confirm when
done.
We also have an additional problem where after a while of last reboot, part of the Exchange ECP can no longer be properly loaded in the web browser due to compilation error (compilation is done via NT Authority\System account which seems to no longer have
sufficient right to compile .NET code). What is strange is that it works at first and then stop working at some point... I am hopeful that adding NT Authority\System to the Administrators group would sort this issue as well but once again, that shall not be
needed!!!
Could a Windows Server 2012 update introduced some security policy changes or else that prevent NT Authority\System to have full power?

Office 2013 C2R Update Scheduled Task does not work

Hi all.
I am having difficulty getting network deployed updates to work correctly. I installed and older version of Office 2013 with the ODT from a network share and set the update path. I then downloaded an update via ODT.
The issue is the scheduled task does not update office. If I trigger or manually run from a command prompt "C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe RUNMODE RERUNMODE modetorun updatedetection modeargs reschedulemode tasktrigger
scheduledtask updateuitype background” from Task Scheduler nothing seems to happen. Monitoring Task Manager it looks like integratedoffice is called albeit very briefly.
But, if I run "C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe RUNMODE RERUNMODE modetorun updatedetection background” from a command prompt Office updates, but if I edit the Scheduled Task to above Office does not update if the
task is triggered.
As Office can update if the right command is given it would appear that my config.xml etc is correct. Any ideas on why the Scheduled Task does not work?
Cheers
Jakes

What permissions are set on the location of the updates ? C2R currently needs permissions granted for machine accounts as it runs under that context. This will change at some point that C2R gets updated.

Modify Schedule Task - OIM 11g

Hello Experts,
I have created a custom schedule task and deployed it in OIM11g and it works. Now I want to modify the deployed schedule task (add some more scheduled task parameters). How to do that? Can you assist?
I tried the following but its not happening,
1.exported the schedule task
2.modified
3.Imported
Thanks and Regards
INIYA

835060 wrote:
Two ways
1.either create a new job with your attributes,deploy and disable the old one(better if its dev env)
2.Take the export of your metadata.Modify the attributes and import back the fileI guess he already has tried the 2nd option which is not working and I believe it should not work as well. The time you create a job, it reads your xml and sets the attributes and creates a instance of the task. Thus if you just change the xml it won't reflect in the previously created instance.
Hence create a new job and delete the previous one.
HTH,
BB

XLreporter scheduled tasks stopped running

Hi Experts,
We are experiencing problems on XLreporter scheduled tasks.
They worked properly with sending emails as daily routine. However for some reason they stopped running in windows Task Scheduler. We can still run the jobs thru manually in XLreporter Organizer with correct result and sucessful logs. In the mean time the service of Task Scheduler is ok for other tasks than XLreporter.
What we can see in Event Viewer is the error message with two other information message below for each run:
Error:
The VB Application identified by the event source logged this Application IXExecutor: Thread ID: 5904 ,Logged: An error occured while Initializing Job
Object variable or With block variable not set
Info:
The VB Application identified by the event source logged this Application IXExecutor: Thread ID: 5904 ,Logged: Before deleting mclsIFDSApp
Info:
The VB Application identified by the event source logged this Application IXExecutor: Thread ID: 5904 ,Logged: IXExecutorProxy - ExecuteJob: Before Exit Sub
The SBO version 8.8 PL14 on windows server 2003 R2 SP2 ,SQL Server 2005
Can you please advise? Many thanks Ryan
Edited by: Ryan Fu on Jun 22, 2011 3:55 AM

Just found this one too:
Note 855021
If you want scheduled report jobs in XL Reporter to be executed independently of the logon status of the user who defined the job, you must allow Microsoft Excel to be started by the scheduled job.
1. Choose Run from the Windows Start menu and type dcomcnfg.exe. A window called Component Services appears. Choose Component Services->Computers->My Computer->DCOM Config->Microsoft Excel Application from the list.
2. Right-click on Microsoft Excel and choose Properties. Choose the Security tab.
3. Choose Customize under Access Permissions and choose Edit...
4. Choose Add... and choose Users and/or User Groups that require access to Excel. Then choose OK.
5. Repeat the procedure for Customize under Launch Permissions.
6. Choose the Identity tab.
Choose This User.
Choose a user that is a member of the administrator group from the browse button and enter password.
This user will be the one that is given access to Microsoft Excel when executing scheduled jobs. Normally this would be the Administrator user.

Disabling Manually Scheduled Tasks in PP2010

Similar Messages

Maybe you are looking for