Re: SMS Client

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Stan White [MS] (stanwh_at_microsoft.com)
Date: 05/26/04 

Date: Wed, 26 May 2004 08:53:24 -0700

Are you sure the clients are not trying to go to the production site and
failing?
The lab site may not have discovered the machines and therefore no policy is
generated for them.
The site server is discovered using server discovery so that could explain
why it has policy. 

-- 
-- 
Stan [MSFT]
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
--
"ark" <sparkster@webmail.co.za> wrote in message 
news:be9bcaf1.0405240824.15b0cb1d@posting.google.com...
> Please Help
>
> I have just performed a restore of SMS 2003 from our production
> enviroment into a lab enviroment. To cut a long story short the
> problem i am currently experincing is as follows.
>
> All the Advance clients are not downloading any of the polcies which
> are advertised on the management point. Which means the compnenets are
> not being enabled and the all the actions are not being downloaded to
> the client. If i use the policy spy tool from the toolkit one can see
> them advertised. All the clients can successfully connect to the MP's
> . A distribution point has also been installed on the same server.
>
> The logs
>
> I have pasted what is currently shown in the client logs as erros.
>
> execmgr.log
> Software Distribution Site Settings for the client are missing from
> WMI.
> (The above error i believe to be the source of the problems)
>
> PolicyAgent.log (The following events are repeated one after the other
> all through the log)
> 1.Requesting Machine policy assignments
> 2.Requesting policy from authority 'SMS:PRD'
> 3.Raising event:
>
> instance of CCM_PolicyAgent_AssignmentsRequested
> {
> AuthorityName = "SMS:PRD";
> ClientID = "GUID:6E98F943-1C25-4548-8420-3D5B648187F7";
> DateTime = "20040524153723.094000+000";
> ProcessID = 2240;
> ResourceName = "PRDCS001";
> ResourceType = "Machine";
> ThreadID = 3292;
> 4.Requesting User policy assignments for
> 'S-1-5-21-4217281460-1848104915-2132370106-500'
>
>
> Please i have sat for three days with this problem with no luck yet.
>
> Oh by the way the Advance client whihc i have installed on the SMS
> Server itself did succesfully download the policies and enable the
> components. and has all the actions.
>
> Thanks
> Mark

Relevant Pages

  • Re: RWW and Remote desktop stopped working on all clients
    ... (was a policy issue, ... the RWW site with no trouble, select options, use OWA via RWW site, and I ... adminsitrator or another account with Domain Admin role; also the server ... The first client reported to have the ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Agent Push
    ... Have you configured the management points and Server Locator Points? ... Do you have a client connection account, ... There servers are configured to use> active directory sites as roaming boundaries. ... Client agent push is> configured to install platform dependant agents after the> discovery. ...
    (microsoft.public.sms.admin)
  • Re: Prevented from adding users
    ... Disabling the policy has not resolved the problem. ... setting I should configure my print server name? ... Without stepping through the debugger on this I am unsure why the client ...
    (microsoft.public.windowsxp.print_fax)
  • Re: GPO causing client security logs to fill?
    ... Enabled Small Business Server Remote Assistance Policy No ... titled "Client Logon Failure". ... So basically, the Account lockout threshold, account lockout ...
    (microsoft.public.windows.server.sbs)
  • Re: authentication problem
    ... I my domain computers already have the client/repond policy assigned to them ... > the problem is that you can only log on to the client ... What's the OS of the server you are logging on? ... >>session with a domain controller in this domain LABB ...
    (microsoft.public.win2000.security)