![]() So if you were to query the task from CMD prompt, you would see the task listed 3 times but Granted, if you run this in a CMD prompt, you will see errors when deleting the task but that is because the task that it is trying to delete has multiple triggers. CMD file we created:įor /f "tokens=2 delims=\" %%x in ('schtasks /query /fo:list ^| findstr /c:"Microsoft Office 15 Sync Maintenance for"') do schtasks /Delete /TN "%%x" /F ![]() We had talked to MS about this and they highly discouraged us setting permissions on the EXE that creates the task or locking Was create a small bat file and using Task Scheduler, run the task on system startup to delete any of those tasks generated by users. We use Xenapp 6.5 with Office 2013 and although it does not seem to have an effect on server performance, it does cause clutter in the Task Scheduler. This looks like an old thread but I think I have a better/cleaner way of fixing this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |