locked
Permissions on Remote Source Folder RRS feed

  • Question

  • We're trying to using a remote NAS to store all of our sources for Applications, OSD Images, etc.  The file structure is essentially \\root\sources and we've created an AD Security Group named "SCCM Servers" which we've added our Primary (and only) Site Server, "SCCM-01" to. The root share is setup with "Everyone Full" permission, we then added the "SCCM Servers" Security Group with Full Permission to the \sources subdirectory, then rebooted SCCM-01 so it would pick up the new group membership. Now whenever we create a new application, point to where the .msi content is stored beneath the \sources folder, it creates the application successfully but when you go to deploy it the content status always shows as "The source folder for content does not exist."  Can someone guide me in the right direction? Thanks for any assistance.
    Saturday, August 4, 2012 1:15 PM

Answers

  • The NAS is an EMC Isilon, does SCCM 2012 not support this?  Any assistance would be greatly appreciated.

    This has nothing to do with ConfigMgr. It's your NAS device denying access and based on the above, it simply does not handle logins from computer accounts correctly.

    Probably time to either get EMC involved or move to plan B for storing source files.


    Jason | http://blog.configmgrftw.com

    Sunday, August 5, 2012 5:39 PM

All replies

  • Alright, we've tried two things:

    • We've captured the session with Wireshark and are getting "SMB2 131 TreeConnect Response, Error: STATUS_ACCESS_DENIED" once again I don't see what could be causing this issue as the Share is setup with Everyone Full and NTFS includes the SCCM-01 server with Full Permission.
    • Have tried using the FQDN of the NAS, with the same result.
    • Have tried opening a CMD prompt under the local system context and we can see the share when net view \\NAS is run but when we try to mount the share under the local system context we get "The password is invalid for \\NAS.  Enter the user name for 'NAS':  System error 1223 has occurred. The operation was canceled by the user."

    The NAS is an EMC Isilon, does SCCM 2012 not support this?  Any assistance would be greatly appreciated.

    Sunday, August 5, 2012 5:21 PM
  • The NAS is an EMC Isilon, does SCCM 2012 not support this?  Any assistance would be greatly appreciated.

    This has nothing to do with ConfigMgr. It's your NAS device denying access and based on the above, it simply does not handle logins from computer accounts correctly.

    Probably time to either get EMC involved or move to plan B for storing source files.


    Jason | http://blog.configmgrftw.com

    Sunday, August 5, 2012 5:39 PM
  • Did you find a resolution to this issue? I'm trying to use or NAS (also EMC Isilon) as a place to store our source files and have run into the exact same issue.
    Sunday, May 5, 2013 9:31 PM
  • For anyone else who has an issue with using an EMC Isilon NAS (or any NAS really) as a content store for Configuration manager, the computer object has to be granted at a minimum read permissions on the NAS share and the SMB share on the NAS. Our issue is that we gave the configmgr computer account read & execute permissions on the SMB share but not on the NAS itself.

    Also, if your content share is in a subfolder (i.e. NAS/Folder/Content-Store) the computer account has to have at a minimum read permissions on all directories between the root and the actual content store. To get around this, we just put our content store share on the root of our NAS and gave the computer account read permissions.

    Hope this helps.

    • Proposed as answer by Bryce17 Wednesday, May 8, 2013 9:38 PM
    Wednesday, May 8, 2013 9:38 PM