I believe, there was NetApp knowledge base and the problem definitely was discussed here already. IIRC this won’t work, account needs to be proper user account, not the machine one. Unfortunately I can’t find references right now, try to search kb/communities.
If you want to create a CIFS share that is meant to be accessed only by a machine account, you can map the IP address of the server to a local account on the filer in usermap.cfg and then add that user with useradmin and finally add full control for that user on the share. You may want to add other rights to the share for administration of files. I found it helpful to make the shares hidden to reduce the chance of others accessing the file.
We've done this for Notes storage on a set of filers for a lot of years. It seemed like a hack at the time, but it has been suprisingly stable.
10.10.10.10:"" => sccmuser (a backend storage IP subnet to limit access via IP spoofing can be a good idea)
useradmin user add sccmuser -g administrators -c "SCCM server" (or some other more limited group)
cifs access <sccm_share> sccmuser Full Controll
Something like this should get things rolling.
The documentation says that machine accounts should be able to access the data. Not sure if you've looked at that specifically or not.
we have the same problem with our new netapp to get access to a share with the computeraccount. We tried your way with the usermap.cfg. It seems to work half the way. We get an authenticaton message to input our credentials from the sccmuser. Should this not happen automatically and how can this be done?