Timeline for Download and delete documents using Powershell
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2010 at 16:33 | comment | added | James Love | Yep, you'd probably need not create a credential object like your sample code above, and Renzo's suggestion may work even better (he sits behind me in the office, I know his PowerShell is good :) ) | |
| Oct 25, 2010 at 14:44 | comment | added | Jonny | If the task is running through the context of the Windows Task Scheduler, would it not pass on those credentials and not require the username/password to be embedded into the script? | |
| Oct 25, 2010 at 13:45 | comment | added | James Love | The scheduling and management (enable/disabling) for Timer Jobs can easily be set up in a secure environment within Central Administration. With your business case for development of custom code, I'd suggest presenting the risk of having the entire SharePoint configuration username and password stored in a plain text file against having it locked away within the (tried and tested) security of SharePoint Central Administration. | |
| Oct 25, 2010 at 13:05 | comment | added | Jonny | Hello, the motivation to do this by script is for simple management and scheduling. There are also budget constraints associated with developing custom code. If this can't easily be achieved through powershell then I'll have to consider alternatives... | |
| Oct 25, 2010 at 12:58 | history | answered | James Love | CC BY-SA 2.5 |