GOT IT! Re: Legacy clients can't send back confirmation of install

From: Mark Morrell (morrellm_at_home.com)
Date: 02/17/05


Date: Thu, 17 Feb 2005 08:16:21 -0600

I got it to work finally!
I made the change last night and came in this morning to a bunch of NT
machines loaded with the client and ready to go.
All I did was add my own account to connection accounts/client.
I still have administrator in there, but I have less groups on my account
(yes, I am domain admin on the account I used). These are the groups I am
not part of that the administrator account is in: builtin administrators,
builtin backup operators, Enterprise admins, group policy creator owners,
and schema admins.

At this point I can only guess that one of those groups is somehow blocking
permissions somewhere that I haven't found yet. I would suspect enterprise
admins just because that seems to be the one the previous guy liked to mess
with for some reason.

Thanks to Kim, Kerwin and Jeff for pointing in the right direction.

"Mark Morrell" <morrellm@home.com> wrote in message
news:uTdmBJ3EFHA.2824@tk2msftngp13.phx.gbl...
> Hey Johan
> Nothing yet. I found some other problems that needed fixing more than
this
> one....so I have only spent a little time on it. I did get one NT machine
> to show up with the site code, but still not showing as a client.
> "When" I figure it out, I'll post the fix back here.
>
> Mark
>
> "Johan" <Johan@discussions.microsoft.com> wrote in message
> news:CE87AFF2-8D27-40B6-9F8D-D5D37F054597@microsoft.com...
> > Hi Mark!
> > I have the same problem....the push install to XP and win 2k works just
> fine
> > but my NT4 clients cant /will not "pop up" as clients in the SMS Admin
> > Console.
> > The CCM.LOG says: "Moving request to retry queue for verification"
> > Im sure that my connection account has right on my client.....
> > Any idees?
> >
> >
> > "Mark Morrell" wrote:
> >
> > > Good morning!
> > > I have finally installed SMS 2003 on a mixed (2000+2003) domain
> (advanced
> > > security). We have XP (SP1+SP2), W2K and NT4 workstations. The
install
> > > went great (I spent a LOT of time in these groups). I let it do
> discovery
> > > for a little over a week and it found most of the systems (another of
> the
> > > problems I should be able to fix from what I read here). I even
pushed
> out
> > > a couple packages to the XP and 2K clients.
> > >
> > > So a very big THANK YOU to all you people that spend time in here
> helping
> > > us.
> > >
> > > Now the problem: The NT4 boxes can't seem to answer back to SMS that
> they
> > > got installed. The client is showing up in control panel, but no
> components
> > > get installed. All of these boxes have the same problem - they can't
> even
> > > browse (Network neighborhood) to the SMS server even though they can
get
> to
> > > all the others. The weird part is that they can still go get updates
> from
> > > the Epolicy on the same server. I forced a few EPO updates from the
> > > workstations and they found the server.
> > > I have one of them here in the back room for testing. It just
happened
> to
> > > pick up an IP address one number off of my 2K machine that works fine
(I
> > > thought it might have been something with sites and subnets).
> > >
> > > Any ideas?
> > >
> > > Thanks
> > > Mark
> > >
> > >
> > >
>
>



Relevant Pages

  • Re: Login as local admin
    ... So if i basically ensure that my domain administrator account is a member of ... the schema admins, and enterprise admins, and login using these credentials, ... The article does not reference "local" administrator (as far as I ... If you choose to use an account other than the built-in administrator ...
    (microsoft.public.windows.server.sbs)
  • Re: Login as local admin
    ... schema admins, enterprise admins and the other groups mentioned, but the ... installing SBS SP1. ... So if i basically ensure that my domain administrator account is a member ... The article does not reference "local" administrator (as far as I ...
    (microsoft.public.windows.server.sbs)
  • Re: Advanced Client install nightmare
    ... I can succesfully connect to the remote registry using the account. ... Domain Admins and now Enterprise Admins. ... MVP Windows Server System - SMS ... I have deleted and re-created the client install account and the client ...
    (microsoft.public.sms.admin)
  • Re: Login as local admin
    ... schema admins, enterprise admins and the other groups mentioned, but the ... So if i basically ensure that my domain administrator account is a member ... The article does not reference "local" administrator (as far as I ... As i am trying to install SBS SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrade SBS2000 to SBS2003
    ... Specify an account with Enterprise Administrator prrivileges to the ... The domain Administrator account should be a member of the Enterprise ... Enterprise Admins" error when you run the Windows Small Business ...
    (microsoft.public.backoffice.smallbiz2000)