Re: troubles distributing packages

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




Here is what I have...

for my package 'CWShredder' I have my access accounts as administrators,
full control and users with read control, my Distribution point is my site
server \\SPARE, my program is cwshredder.

The properties of my program are on the general tab name: cwshredder, the
command line: cwshredder.exe which is located within my local C: on my site
server within its own folder cwshredder. Start is set to nothing, run:
normal, after running: no action required.

The requirements are estimated disk space unknown, max allowed run time 120
minutes, and this program can run on any platform

The environment is program can only run when a user is logged on and run
mode with administrative rights.

The advertisement general tab: name: cwshredder, package: CWShredder,
program: cwshredder, collection: System: POLICYTEST

The schedule is set correctly and the distribution point is set to download
content from distribution point and run locally, and when a client is
connected within a slow or unreliable network boundary download content from
distribution point and run locally.

My main question is does the folder where my exe resides have to be shared?
and do I need to put the path to the file in anywhere?

thanks



"sherrylkissinger@xxxxxxxxx" wrote:

Lots of good blogcasts on SMS here: http://www.blogcastrepository.com/blogcasts/folders/sms/default.aspx
for example, 'Software Deployment with SMS 2003'
http://www.blogcastrepository.com/blogcasts/folders/sms/entry351.aspx

If you're interested in a book: http://astore.amazon.com/buzzmanagement/detail/1932577238/104-1024113-9643119

Regarding your specific questions; Check the package source folder;
make sure it exists, and that the SMS server account has rights to
read the source.

As to 'where does it run from', in general unless you specifically
change the program line to do something different, if the source
folder contains the file "widget.msi", and you put 'widget.msi /qn'
on the program line, the client will run the command widget.msi /qn
from the UNC path corresponding to the Distribution point folder.

In general, unless you have some very unique circumstances, you should
not 'hard code' a path into the program line. You normally wouldn't
put in c:\widget.msi /qn doing so (in my humble opinion) negates
the benefits of having distro points , Windows installer source
management, some of the things I like best about sms...

On Sep 5, 12:44 pm, ryan <r...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,

I've tried many times to get a program distributed with my package, but
having no luck. In the command line part when you're setting up the program,
is that the path to the executable? Also, does this need to be on the root of
the C: drive or in its own folder

It keeps telling me

SMS distribution manager failed to process package "ahaview" Solution:
review the previous messages for further clarification about this problem.
Possible cause: The package source directory contains files with long
names........, etc.

any ideas, or is there a tutorial or webinar which I can look at to help
with this?

thanks



.



Relevant Pages

  • Re: troubles distributing packages
    ... On your SMS Server, create a folder called \Sources. ... In your SMS Admin Console, Find the Package 'CWShredder', and right- ...
    (microsoft.public.sms.setup)
  • Re: Distribution Manager error 2324
    ... >From the logs NAL is failing to create AV00000D folder under ... > The best drive for installing package on the distribution point ... > Failed to create the package directory AV00000D\ under the export. ... The log will give you exact error code>> as why the copy of package is failing. ...
    (microsoft.public.sms.swdist)
  • Re: SMSPKGC$ share missing
    ... Sorry Sathish. ... when you add a package with source as you said, ... > I assume this machine is a Distribution point. ... >> SMSPKGC$ Share / Folder is missing? ...
    (microsoft.public.sms.admin)
  • Re: SMSPKGC$ share missing
    ... Sorry Sathish. ... when you add a package with source as you said, ... > I assume this machine is a Distribution point. ... >> SMSPKGC$ Share / Folder is missing? ...
    (microsoft.public.sms.swdist)
  • Re: SMSPKGC$ share missing
    ... Sorry Sathish. ... when you add a package with source as you said, ... > I assume this machine is a Distribution point. ... >> SMSPKGC$ Share / Folder is missing? ...
    (microsoft.public.sms.setup)