Hi Everyone,
I have a maintenance plan to run my daily SQL backups. A local NT Service account runs my SQL Server and SQL Server Agent services. I tried switching this to a domain account yesterday but couldn't get it to switch due to SPN issues and had to back out. So being stuck with a local account running the services, I'm trying to use a proxy to run SSIS package so I can push the backups to a secure network location that the local NT Service accounts running my SQL services can not access.
The problem is, the SSIS package is not leveraging the proxy and tries to create the folders and save the backups using the domain account tied to the computer. I've tested this extensively and if I give access to the computer's account the job works (the computer account also shows up as the owner if File Explorer).
The same account used for the proxy runs my sql services on other instances that can save to this drive location.
Any ideas on what to do (other than trying to switch the services to run off of the domain account again), or why the job is using the computer's id?
Thanks for your help.