SCCM Distribution Point Server share
Carsten Cramer
I want to set up a remote Server Share as Distribution Point on a NetApp Filer.
A share exists and I granted share-level an Filesystem ACLs to the Computername$
Account of the sccm Management-Point Machine.
Acctually the 'SMS Site System Status Summarizer' logs errors due to 'access
denied' and it's not possible to send packages to that distribution point.
What has to be configured, so that a remote server share can be successfully
used. All Hosts are within the same Domain?
Could it be, that a NetApp based cifs Filer-share cannot be used as Software
Distribution Point?
BTW:
BITS / HTTP / HTTPS are not enabled for that distribution point, because it's a
Netapp Filer, where IIS cannot be installed of cource ;-)
The Main sccm Roles resides on a single Host.
Thanks so far.
Torsten [MVP]
you granted permissions for the MP? That would work if the MP is also the
siteserver (because the siteserver will be sending the packages, not the
MP).
I haven't tried that configuration with SCCM yet, but with SMS 2003 you also
needed an admin$ share on the DP (even if SMS never put any files in it).
Maybe you should give that a try. This scenario will not be supported ...
Torsten
Microsoft MVP - SMS
"Carsten Cramer" <carsten...@lrz-muenchen.de> schrieb im Newsbeitrag
news:%23rpPJNh...@TK2MSFTNGP05.phx.gbl...
Carsten Cramer
Actually there is one site server with all roles, but we want to place the
distribution share (DS) Role on a seperate server.
Now, your advice creating an admin$ share was quite qood, because the 'SMS Site
System Status Summarizer' shows no more errors and logs the diskspace,so the
process sets the status of the storage object to OK in the Site System Status
summary.
So far so good, but it's still not possible to place a packages on the
Netapp-share by SMS Distribution Manager (DM).
You said, that this szenario is not supported, so what kind of architecture
works with storage who is not managed by Windows-OS like NetApp?
Actually we don't want to use block based protocols like iSCSI which should work
of course, but we need to access the packages and other files from different
clients. Therefor a common Fileprotocol like cifs is needed.
How about setting up an IIS based Windows Server for BITS/http/https usages as a
DS and using the Netapp shares as virtual directories? Well, this probably
doesn't not close the gap to place packages on the Netapp server share, but the
IIS can connect the files on the remote Netapp share and reach them out to the
clients by http/https.
Could we place the packages on the Netapp-share by a different process than DM,
(Filecopy,sync,robocopy,a.s.o) and the manage them within site-server console?
What is your advice, the sccm documantation does not tell anything about the
dependencies and precautions for similar scenarios?
Torsten [MVP] schrieb:
Torsten [MVP]
see inline ...
"Carsten Cramer" <carsten...@lrz-muenchen.de> schrieb im Newsbeitrag
news:efnJTmsf...@TK2MSFTNGP02.phx.gbl...
>
> So far so good, but it's still not possible to place a packages on the
> Netapp-share by SMS Distribution Manager (DM).
Why? Which errors? Check distmgr.log for details.
> You said, that this szenario is not supported, so what kind of
> architecture works with storage who is not managed by Windows-OS like
> NetApp?
That's a really good question. I cannot image that other technologies than
MS ones are supported. I would contact your TAM or whatever MS contact to
make really sure that you scenario is supported.
> How about setting up an IIS based Windows Server for BITS/http/https
> usages as a DS and using the Netapp shares as virtual directories? Well,
> this probably doesn't not close the gap to place packages on the Netapp
> server share, but the IIS can connect the files on the remote Netapp share
> and reach them out to the clients by http/https.
You're leaving the supported path further ...
> Could we place the packages on the Netapp-share by a different process
> than DM, (Filecopy,sync,robocopy,a.s.o) and the manage them within
> site-server console?
I don't think so.
> What is your advice, the sccm documantation does not tell anything about
> the dependencies and precautions for similar scenarios?
My advice would be: check the documentation and search the chapter that's
covering the supported scenarios. I'll check if I can find out anything that
might help on that topic.
Torsten
Carsten Cramer
distmgr.log:
...
~The distribution point doesn't support drive enumeration or a valid drive could
not be found. $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 10:34:44.624 2008 W.
Europe Standard Time><thread=4660 (0x1234)>
~Failed to find valid drive on distribution point path
MSWNET:["SMS_SITE=MWN"]\\badwlrz-fnnas\SMSSIG$\
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 10:34:44.624 2008 W. Europe Standard
Time><thread=4660 (0x1234)>
Error occurred. $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 10:34:44.624 2008 W.
Europe Standard Time><thread=4660 (0x1234)>
...
So DM tries to enumerate drives on the Netapp Host, which will not work of course.
The 'Data Access' Option of the Package is configured to 'share the dirtibution
folder' by specified name. Therefore DM tries to create a share on the Host,
which is not possible because it's not a MS-Fileserver. I reconfigured it to
'Access distribution folder through common ConfigMgr package share' , created
shares named 'SMSPKGc$','SMSSIG$' an put necessary ACLs.
Still having Problems:
...
~Successfully made an accessible connection, got a NOS path, and, if requested,
got the number of free bytes at this location. $$<SMS_DISTRIBUTION_MANAGER><Fri
Mar 07 12:56:31.266 2008 W. Europe Standard Time><thread=4288 (0x10C0)>
~Successfully set access security on
MSWNET:["SMS_SITE=MWN"]\\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\ for package
MWN00003 $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.297 2008 W. Europe
Standard Time><thread=4288 (0x10C0)>
GetPackageSignature() called for package MWN00003 with version 5.
UnpackedSignature = 0~ $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.297
2008 W. Europe Standard Time><thread=4288 (0x10C0)>
~RDC:Binary update DP \\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\ using DP version
3, Source version: 5, Source: D:\tmp\SP0\ $$<SMS_DISTRIBUTION_MANAGER><Fri Mar
07 12:56:31.297 2008 W. Europe Standard Time><thread=4288 (0x10C0)>
RegisterSignatureUsage() called with for Package MWN00003, Version 5 with
Targetpath as \\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\~
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.297 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
RegisterSignatureUsage() called with for Package MWN00003, Version 3 with
Targetpath as \\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\~
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
C:\SMSPKGSIG\MWN00003.3.tar could not be found~
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
Could not register signatures for package MWN00003, version 3 and TargetPath
\\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\. Will do full file deltas for updated
files.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008 W. Europe
Standard Time><thread=4288 (0x10C0)>
FindFirstFile failed on \\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\*.*~
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
UpdateStagedFolderDeletedRdc failed; 0x80070005~
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
UpdateStagedFolderRdcW failed; 0x80070005~ $$<SMS_DISTRIBUTION_MANAGER><Fri Mar
07 12:56:31.360 2008 W. Europe Standard Time><thread=4288 (0x10C0)>
~Cannot copy package MWN00003 from D:\tmp\SP0\ to
\\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\, Win32 Error = 0
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
~Failed to copy package MWN00003 from D:\tmp\SP0\ to
MSWNET:["SMS_SITE=MWN"]\\BADWLRZ-FNNAS\DSKMGMT$\SMSPKG\MWN00003\
$$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe Standard
Time><thread=4288 (0x10C0)>
...
I stop here further investigations. Architecture of SCCM is not designed to work
with non MS-Filers. Thanks a lot so far.
fraetrain
> Hi Torsten,
>
> distmgr.log:
> ...
> ~The distribution point doesn't support drive enumeration or a valid drive
> could
> 2008 W.
> Europe Standard Time><threadF60 (0x1234)>
> ~Failed to find valid drive on distribution point path
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 10:34:44.624 2008 W. Europe
> Standard
> Time><threadF60 (0x1234)>
> Error occurred. $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07
10:34:44.624
> 2008 W.
> ...
>
> So DM tries to enumerate drives on the Netapp Host, which will not work of
> course.
>
> The 'Data Access' Option of the Package is configured to 'share the
dirtibution
> folder' by specified name. Therefore DM tries to create a share on the Host,
> which is not possible because it's not a MS-Fileserver. I reconfigured it to
> 'Access distribution folder through common ConfigMgr package share' , created
> shares named 'SMSPKGc$','SMSSIG$' an put necessary ACLs.
>
> Still having Problems:
> ...
> ~Successfully made an accessible connection, got a NOS path, and, if
requested,
> got the number of free bytes at this location.
> Mar 07 12:56:31.266 2008 W. Europe Standard Time><threadB88
(0x10C0)>
> ~Successfully set access security on
> package
> MWN00003 $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.297 2008
W.
> Europe
> Standard Time><threadB88 (0x10C0)>
> GetPackageSignature() called for package MWN00003 with version 5.
> 12:56:31.297
> 2008 W. Europe Standard Time><threadB88 (0x10C0)>
> ~RDC:Binary update DP BADWLRZ-FNNASDSKMGMT$SMSPKGMWN00003 using DP
> version
> 3, Source version: 5, Source: D:tmpSP0
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar
> 07 12:56:31.297 2008 W. Europe Standard Time><threadB88 (0x10C0)>
> RegisterSignatureUsage() called with for Package MWN00003, Version 5 with
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.297 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> RegisterSignatureUsage() called with for Package MWN00003, Version 3 with
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> C:SMSPKGSIGMWN00003.3.tar could not be found~
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> Could not register signatures for package MWN00003, version 3 and TargetPath
> files.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.344 2008
W.
> Europe
> Standard Time><threadB88 (0x10C0)>
> FindFirstFile failed on BADWLRZ-FNNASDSKMGMT$SMSPKGMWN00003*.*~
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> UpdateStagedFolderDeletedRdc failed; 0x80070005~
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> UpdateStagedFolderRdcW failed; 0x80070005~
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar
> 07 12:56:31.360 2008 W. Europe Standard Time><threadB88 (0x10C0)>
> ~Cannot copy package MWN00003 from D:tmpSP0 to
> BADWLRZ-FNNASDSKMGMT$SMSPKGMWN00003, Win32 Error = 0
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> ~Failed to copy package MWN00003 from D:tmpSP0 to
> MSWNET:["SMS_SITE=MWN"]BADWLRZ-FNNASDSKMGMT$SMSPKGMWN00003
> $$<SMS_DISTRIBUTION_MANAGER><Fri Mar 07 12:56:31.360 2008 W. Europe
> Standard
> Time><threadB88 (0x10C0)>
> ...
>
> I stop here further investigations. Architecture of SCCM is not designed to
> work
> with non MS-Filers. Thanks a lot so far.
>
> Torsten [MVP] schrieb:
>> Hi Carsten,
>>
>> see inline ...
>>
>> Newsbeitrag
>> news:
>>>> Newsbeitrag news:%
>>>>> Hi,
>>>>> I want to set up a remote Server Share as Distribution Point on a
>>>>> NetApp Filer.
>>>>>
>>>>> A share exists and I granted share-level an Filesystem ACLs to the
>>>>> Computername$ Account of the sccm Management-Point Machine.
>>>>>
>>>>> Acctually the 'SMS Site System Status Summarizer' logs errors due to
>>>>> 'access denied' and it's not possible to send packages to that
>>>>> distribution point.
>>>>>
>>>>> What has to be configured, so that a remote server share can be
>>>>> successfully used. All Hosts are within the same Domain?
>>>>>
>>>>> Could it be, that a NetApp based cifs Filer-share cannot be used as
>>>>> Software Distribution Point?
>>>>>
>>>>> BTW:
>>>>> BITS / HTTP / HTTPS are not enabled for that distribution point,
>>>>> because it's a Netapp Filer, where IIS cannot be installed of cource
>>>>> ;-)
>>>>> The Main sccm Roles resides on a single Host.
>>>>>
>>>>> Thanks so far.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
work
around works in SMS flawlessly.
That being said, any organization with Netapp filers is strong-armed into
deploying MS-file servers.