SMS 2.0 Client assignment problem
Tech-Archive recommends: Speed Up your PC by fixing your registry
I have a SMS 2.0 site with only one server and about 65 clients. Packages
and so forth are working fine.
The problem I am having is there are 2 computers (all workstations are the
same being Windows XP Pro SP2) that never get assigned a site code, never
get listed under the default query "All Client Systems" and never receive
any advertisments.
On both workstations, the SMS client is installed and appears to be working,
but it is like it does not communicate with the server.
.
Relevant Pages
- Re: After reinstallation
... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
(microsoft.public.sms.setup) - RE: Client machines randomly locking up when printing
... constant, it occurs every day but not on all workstations, seems like one day ... > is a server or client side issue. ... click the Copy button and paste the full content to the Newsgroup. ...
(microsoft.public.windows.server.sbs) - Re: Adv Client with Workgroup Computers
... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
(microsoft.public.sms.admin) - Re: After reinstallation
... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
(microsoft.public.sms.setup) - Re: 4912: Cannot update the already existing object. Need some he
... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
(microsoft.public.sms.admin) |
|
