Re: pushing software to non domain servers
From: Stuart James [MSFT] (sjames_at_online.microsoft.com)
Date: 01/10/05
- Next message: Joe Palmer: "Re: Install OS Deployment Feature Pack"
- Previous message: Berni: "Re: pushing software to non domain servers"
- In reply to: Berni: "Re: pushing software to non domain servers"
- Next in thread: Jeff Harbaugh [MSFT]: "Re: pushing software to non domain servers"
- Reply: Jeff Harbaugh [MSFT]: "Re: pushing software to non domain servers"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 Jan 2005 14:53:22 -0000
Enomagic, I read from your post that you already have the client installed.
If this is not the case then like Berni says, the only supported way to
install the client on workgroup machines is manually.
You say that you are experiencing problems with installing updates (which is
what makes me assume you have the client installed already).... Is
everything else working OK i.e. is the client talking to the MP OK and
receiving settings, returning inventory etc? If this is all OK but you are
not getting software installed then check that you have configured a network
access account, this is required for the client to connect to a DP.
Regards
Stuart
-- ======================= This posting is provided "AS IS" with no warranties, and confers no rights. "Berni" <btarillion@yahoo.com> wrote in message news:uv1NAiw9EHA.1392@tk2msftngp13.phx.gbl... > Hi, > Under the client push installation method you have a Tab called "Accounts" > there you can add all the accounts for the different Domains that you want > to use to push the client. Remember to use "Domain\user" format. > For systems in the workgroup you will need to install the agent manually. > > Cheers, > > Berni > > "Enomagic" <enomagic@hotmail.com> wrote in message > news:uTiWJcr9EHA.1264@TK2MSFTNGP12.phx.gbl... >> Thanks for this. >> The issues I am having is that of authentication. How/Where do I >> configure >> accounts for the adv client / server to be able to do their stuff? >> >> Cheers, >> Enomagic >> >> >> "Berni" <btarillion@yahoo.com> wrote in message >> news:uKdtNap9EHA.3980@TK2MSFTNGP11.phx.gbl... >>> Hi, >>> You can do that by using SMS 2003 SP1, however you will need to install >> the >>> SMS Adv. Client manually or by a script on your standalone servers, the >> push >>> mechanisms is not working at all, I already tried it :-( . >>> But when the client is installed and correctly assigned to the Site the >>> updates are installed as on any server in the domain. >>> Remember that, if you have the servers behind of a Firewall, you will >>> need >>> to open several IP ports in order that the clients can contact the Site >>> server and viceversa, here a link for that : >>> >>> http://support.microsoft.com/default.aspx?scid=kb;en-us;826852 >>> >>> Cheers, >>> >>> Berni >>> >>> "Enomagic" <enomagic@hotmail.com> wrote in message >>> news:usn7J5d9EHA.1084@TK2MSFTNGP15.phx.gbl... >>> > Hello, >>> > I have a requirement to push software updates to servers which are not >>> > domain members (i.e. standalone). >>> > The marketing material for SMS 2003 says this is possible, but there >>> > is >> no >>> > literature on how to do this. >>> > >>> > Can anyone advise or point me in the right direction? >>> > All servers are 2003 and using SMS 2003. >>> > >>> > Thanks >>> > Enomagic >>> > >>> > >>> >>> >> >> > >
- Next message: Joe Palmer: "Re: Install OS Deployment Feature Pack"
- Previous message: Berni: "Re: pushing software to non domain servers"
- In reply to: Berni: "Re: pushing software to non domain servers"
- Next in thread: Jeff Harbaugh [MSFT]: "Re: pushing software to non domain servers"
- Reply: Jeff Harbaugh [MSFT]: "Re: pushing software to non domain servers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|