Solved

SCCM 2007 - NetApp Updated and issues with Compression and Distribution

Posted on 2014-03-11
4
286 Views
Last Modified: 2014-05-05
Originally we had a NetApp FAS3170 called tar10fs1 and all of our SCCM source packages were located on this NetApp.  Last weekend, we replaced this NetApp with a NetApp FAS3250 called tar10fs01.   The data was moved with SnapMirror and the shares recreated.  The DNS entry for tar10fs1 (previous NetApp) was changed to point to the same address as tar10fs01 (new NetApp).   The AD object for tar10fs1 was deleted.  On the Central Server (Window 2008 Standard -32 bit), I am able to successfully access anything on tar10fs01 with my sccm service account from the Central SCCM Server.

When I try to distribute packages with the original Source Directory of \\tar10fs1\...., I am getting Compression issues or Access Denied Error =5 issues.  When I update a Packages' Source Directory to \\tar10fs01\..., and distribute, I do not receive any compression or Access Denied errors.

What are your thoughts?
0
Comment
Question by:rmessing171
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 42

Expert Comment

by:paulsolov
ID: 39921415
you may need to re-run cifs config.  Since it was in AD there may be a SID attached to the old controller..or permissions issue.  Give Netapp a call and ask for the NAS team, you don't want to be stuck in Tier 1 hell..ask for duty manager if they ask you for mindless tasks such as perfstat.
0
 

Author Comment

by:rmessing171
ID: 39921519
Thank you for your quick response!

We don't believe it to be a permissions issue, because outside of SCCM on the same server we are able to access the new netapp locations \\tar10fs1 (old net app name) through windows explorer with the same username that SCCM uses to distribute packages.

The AD object for the original filer was deleted from AD.  CIFS was terminated on the filer without any change

Any other thoughts?
0
 
LVL 42

Accepted Solution

by:
paulsolov earned 500 total points
ID: 39922514
Can you access the new name and test with the new name?  Is the name you're using the actual name of the new filer or an alias?
0
 

Author Comment

by:rmessing171
ID: 39935219
Yes, I can access the new name or old name via Windows Explorer without any issues.  When SCCM 2007 tries to access using the old name, it provides me with Access denied Error 5.  When I update the Source Location with the new NetApp name I do not get any errors.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OfficeMate Freezes on login or does not load after login credentials are input.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
Suggested Courses

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question