Re: SMS 2.0 Client on Domain controller fails error 1069

From: Michael Poling [MSFT] (michpol_at_online.microsoft.com)
Date: 07/21/04 

Date: Wed, 21 Jul 2004 14:42:44 -0700

The error 1069 is "The service did not start due to a logon failure."

I have seen issues where the Default Domain Controller Security Policy has
been disabled and replaced by a custom policy, or modified where SMS is not
able to modify it.

If this is the case try adding SMSInternalCliGrp to the "Logon as a Service"
permission in your Domain Controller Security Policy or enable the Default
Domain Controller Security Policy.

This posting is provided "AS IS" with no warranties, and confers no rights.

"John Graham" <anonymous@discussions.microsoft.com> wrote in message
news:16dd01c46f45$84ea7140$a601280a@phx.gbl...
> Running SMS V2.0 sp5.
> Trying to install SMS client using NT Remote Client
> Installation method on a pair of AD Domain controllers.
> The first server installation succeeded without any
> problems. The second server fails with the following error
> in ccm.log
> ------
> $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21 08:16:55.725 2004
> Alaskan Daylight Time><thread=2808 (0xAF8)>
> ---> Sync part #1: Account is in the local administrators
> group (still need account properties sync locally)...
> $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21 08:17:54.864 2004
> Alaskan Daylight Time><thread=3456 (0xD80)>
> ---> Synced! User comment set to "SMS#_SOUTHGLENN
> PDC:\\NORTHGLENN Svr=SOUTHGLENN @ 07-21-2004, 08:16.54"
> locally $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21
> 08:17:54.880 2004 Alaskan Daylight Time><thread=3456
> (0xD80)>
> ---> Created service "CCMBoot" on machine "SOUTHGLENN".
> $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21 08:17:54.927 2004
> Alaskan Daylight Time><thread=3456 (0xD80)>
> ---> ERROR: Unable to start service "CCMBoot" on
> machine "SOUTHGLENN", error = 1069.
> $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21 08:17:54.943 2004
> Alaskan Daylight Time><thread=3456 (0xD80)>
> ---> Waiting for service to stop
> $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21 08:17:54.943 2004
> Alaskan Daylight Time><thread=3456 (0xD80)>
> ---> Service stopped $$<SMS_CLIENT_CONFIG_MANAGER><Wed
> Jul 21 08:17:59.942 2004 Alaskan Daylight
> Time><thread=3456 (0xD80)>
> ---> Failed to start the CCM Client Bootstrap service on
> SOUTHGLENN (1069) $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul
> 21 08:17:59.942 2004 Alaskan Daylight Time><thread=3456
> (0xD80)>
> ---> Service "CCMBoot" on machine "SOUTHGLENN"
> successfully deleted. $$<SMS_CLIENT_CONFIG_MANAGER><Wed
> Jul 21 08:17:59.989 2004 Alaskan Daylight
> Time><thread=3456 (0xD80)>
> ---> Failed to install CCM Client Bootstrap component on
> client (1069) $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jul 21
> 08:18:00.005 2004 Alaskan Daylight Time><thread=3456
> (0xD80)>
>
> -----
> Please note that these servers (Northglenn and Southglenn)
> are set up identically!

Relevant Pages

  • Re: Local Policy
    ... > In Administrative Tools, go to Domain Controller Security Policy. ... and then click User Rights Assignment. ...
    (microsoft.public.win2000.active_directory)
  • RE: Terminal Services to a W2K DC - problems
    ... Domain Controller Security Policy => Local Policies => User Right Assignment ... > group policy limitation I am missing, but the only way they are able to work ... > sessions to do on-call work on these machines. ...
    (microsoft.public.win2000.active_directory)
  • Re: local admin permissions on DC
    ... Domain Controller Security policy. ... ("Allow logon through Terminal Services" ... > This is for monitoring a branch office DC -- the IT person was the NT ...
    (microsoft.public.windows.server.general)
  • no "domain controller security policy" under administrative tools
    ... I am logged on as admin but cannot see "domain controller security policy", ... Have no problems on other DC's on the network. ... Steve ...
    (microsoft.public.win2000.active_directory)