Re: Distributing App to Workgroup Client


I think I solved the problem. I don't know if this is the correct solution,
however, I am now able to advertise and install software on workgroup
machines.

Defined a client push account:
--> Connection Accounts --> Client --> %machinename%\std_account

Created a std_account on the workgroup machine with administrative privileges

"RAW" wrote:

>
> 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: User discovery doesnt show adv client
    ... I usually only advertise to users if everybody needs to get the ... >>> I installed the adv on a collection for windows xp computers. ... >>> Do i have to install the adv client on the for example all user collection, ... >>> because i cannot install it for a specific user. ...
    (microsoft.public.sms.admin)
  • Re: Pervasive WG and CS compatibility
    ... But if its a client install, ... I think maybe the best thing to do is purchase a workgroup PSQL 8 engine to ... install on the workstation, this will give you the 8 client automatically. ... > Both apps would be looking at central unique databases. ...
    (comp.databases.btrieve)
  • Re: Distributing App to Workgroup Client
    ... If I move a machine that has the advances client installed from a domain to ... a workgroup, I can install the advertised software. ... > Access Account" field under Under Site Hierarchy, Component Configuration, ...
    (microsoft.public.sms.swdist)
  • Re: How to change workgroup name?
    ... Go into the Control Panel->Network connections and right click your Local ... Click the Install button and select ... Then select Client for Microsoft Networks and have it installed. ... Workgroup name. ...
    (microsoft.public.windowsxp.basics)
  • Re: Managing Workgroup Clients with SMS 2003 SP1
    ... The process is the same for domain and workgroup machines. ... SMS needs the same permissions as a client that was part of the domain. ... You can install the client via push provided all admin accounts have the ...
    (microsoft.public.sms.admin)