Re: Distributing App to Workgroup Client


Plot thickens...

If I move a machine that has the advances client installed from a domain to
a workgroup, I can install the advertised software. However, with a pure
workgroup client, I still can’t install the advertised programs. When I do
properties of the server within the collection section of the SMS console, I
notice ADSiteName = <null>. Could this be my problem? Is there a way of
changing this value?

In the properties of the workgroup client that worked, the ADSiteName was
populated...

RAW



"RAW" wrote:

> Rune,
>
> I've added a domain administrator account in the "Advanced Client Network
> Access Account" field under Under Site Hierarchy, Component Configuration,
> Software Distribution and still no luck.
>
> RAW
>
> "Rune Norberg" wrote:
>
> > Most likely you get this error because you haven't configured the network
> > access account (pt.3):
> > http://myitforum.techtarget.com/articles/8/view.asp?id=7747
> > /Rune
> >
> > "RAW" <RAW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:CC999B88-BE0F-4F7A-BDDE-2708170D1424@xxxxxxxxxxxxxxxx
> > > I'm trying to distribute software to workgroup servers running the
> > > advanced
> > > client. The application shows up in "Run Advertised Program", but when I
> > > try
> > > to install the application I get an error message "This program can not be
> > > run because the program files are inaccessible". The error message for
> > > the
> > > package under Advertisement Status is:
> > >
> > > An error occurred while preparing to run the program for advertisement
> > > "10020016" ("10000001" - "Software Install"). The operating system
> > > reported
> > > error 2147944602: The specified username is invalid. Additional program
> > > properties:
> > > Command line: Setup.exe
> > > Working directory:
> > > Drive letter (? = any):
> > >
> > > Possible cause: This message most commonly occurs when the program's
> > > command-line executable file could not be found, when a required drive
> > > letter
> > > connection to a distribution point could not be established, or when the
> > > program is configured to use the SMS Software Installation Account but the
> > > account is not specified, could not be found, or does not have the
> > > appropriate permissions.
> > > Solution: Check each of the items listed above.
> > >
> > > Additional Info:
> > > The subnet that this machine is on is listed in the Site Boundary.
> > > The client points to the correct SMS Site
> > > I don't have any problems distributing to domain clients.
> > >
> > >
> > > Any help would be greatly appreciated
> > >
> > > RAW
> > >
> >
> >
> >
.

Relevant Pages

  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: pushing software to non domain servers
    ... access to the machine to push the client. ... network access account defined. ... >> For systems in the workgroup you will need to install the agent manually. ...
    (microsoft.public.sms.misc)
  • RE: sbsb2003 premium and ISA
    ... another account. ... Run setup - install on IIS is generally the only selection available. ... Accept the client installation for the SBS (installs the Officescan ... settings for the server versus the clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: RE:RE:Client Install Issue!
    ... Check the Push installation account to verify the account. ... an SLP installed? ... I then proceeded to install the client ... When i initialize the client install through the SMS console, ...
    (microsoft.public.sms.setup)