I have a sql server (2012) running on MSServer2008. I created a new SSISW package (took me forever...newb) that references a network share drive. The package works fine running under my creds, but when I let it loose under the agent's creds, it fails (can't see the folder.) I assume it's an authentication issue, but now my quandry.... What account should I use for Agent so it can get the job done?
It makes more sense that it's an authentication issue. You should use an agent account for the agent. If the server is on a domain, preferably one that has domain access.
My client runs AD, the server is in a domain (WINNTDOM), as are my creds. I tried using an account called WINNTDOM\sqlserveragent, but I couldn't add that account to the AD group to give it access to the network share.
If you're not familiar with AD permissions or the network share permissions setup, have the SA's make the account for "WINNTDOM\sqlserveragent" It may need to have permissions similar to what you have to work correctly. It's easier if they use groups for access.
Mirroring your account permissions may be the easiest way to get it going if they use groups, if not you'll need them to give the service account access to those same locations.
I'm so confused... What's the standard practice here? Is there a way to run the job under different creds?
You can run the job under what ever credentials you want, but they will need the access they need regardless. I would create a service account, give it the permissions it needs to the file share and anywhere else it needs to go, and work out from there.
My client runs AD
Are you a consultant? If you're there to fix a SQL problem, you can still get them to help you with network permissions. I would want my account name as far away from their data as possible moving forward. If they remove your account, you have to know it won't break anything.
.