Re: SCCM Distribution Point Server share

Hi Torsten,

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.

Torsten [MVP] schrieb:
Hi Carsten,

see inline ...

"Carsten Cramer" <carsten.cramer@xxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:efnJTmsfIHA.5088@xxxxxxxxxxxxxxxxxxxxxxx

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


Torsten [MVP] schrieb:
Hi Carsten,

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.cramer@xxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:%23rpPJNhfIHA.4144@xxxxxxxxxxxxxxxxxxxxxxx
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.


.

Relevant Pages

  • Re: Only Arskin
    ... are not prepared to sell a product that we can't support. ... the dependancies be inbuilt in that the VRPC package would ... A product for one particular version of one particular distribution ... that leaves the option of providing a complete Linux system ...
    (comp.sys.acorn.misc)
  • Getting Msg 2342 Followed by Error 2302 Every Hour, Distribution Manager Error
    ... are set as distribution points that I am trying to push this package ... SMS Distribution Manager failed to process package "Outlook Support ...
    (microsoft.public.sms.admin)
  • Re: package management
    ... I don't consider support in Librarian, ... - Every distribution has its own system for package management and one ... I develop Librarian to scratch my own itch, ...
    (comp.lang.lisp)
  • They are observing in connection with the cloud now, wont seek officers later.
    ... Do not document a distribution! ... grateful extremes cease in accordance with the modern compound. ... Fucking don't cause formally while you're ... playing in support of a definite director. ...
    (rec.music.christian)
  • Re: [announcement] SYSAPI and SYSSVC for Windows
    ... > hardware is supported. ... Then, Debian is for you. ... Use the stable distribution. ... I was referring to "package ...
    (comp.lang.ada)