Re: Enterprose Manager after user password change

From: Bruce Prang [MS] (bprang@online.microsoft.com)
Date: 11/20/02 

From: "Bruce Prang [MS]" <bprang@online.microsoft.com>
Date: Wed, 20 Nov 2002 14:44:53 -0800

The only time I've seen this problem is when the users are logging into the
XP client machines with a non-Domain account. It doesn't matter how the
server is registered, it matters how they log into the client machines.

Are the users logging into the XP client using a DOMAIN account? 

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tim_Kehoe" <Tim.Kehoe@aipso.com> wrote in message
news:utlj78NkCHA.2248@tkmsftngp10...
> This is from 3 previous posts, buT I have not found a solution yet:
>
>
>
> The XP client PCs on our network lose their MS SQL Enterprise Manager
> registered servers when the user's network password is changed.  As an
> initial attempt to fix, I installed XP SP1 to no avail.  The keys still
> exist in the PC's registry after the password change under:
>
> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\80\Tools\SQLEW\Registered Servers X]
> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\80\Tools\SQLEW\Registered Servers X\SQL Server Group]
> "(local)"=hex:01,00,...
> "SERVER1"=hex:01,00...
>
> However, the servers do not show in SEM.  Saving the keys and restoring
will
> not help, since they are already there.  The user's are using Windows
> Authentication to an NT domain to register, so it doesn't seem like the
> password should be written to the registry.  So far, each PC has had to
> re-register at password change time.
>
> Looking at the keys' values (not shown above) I can see that all the old
> keys have the same data in the first 108 bytes and then change, however
the
> old keys are different from the new keys starting in byte 25 for 16 bytes.
> Starting at byte 49 for about 48 bytes all the keys spell SQL Server
> Registration (with 2 bytes per character - unicode(?)).  Copying the new
16
> to the old keys bytes did not help.
>
>
>
> The databases are running on W2K and WNT servers with no problems.
> The problem occurs on all XP client PCs - up to 20 tried so far.
> Regmon seems   to indicate the keys listed in my first e-mail are
> accessed
>
>
>
> XP SP1 did not help.  I looked at KB article Q324720 and it's link at
>
http://support.microsoft.com/default.aspx?scid=/support/ServicePacks/Windows
> /XP/SP1FixList.asp and saw that Q316994 seems to be included, but not
> Q323280.  I have to guess that Q323280 is not really in SP1 and not
readily
> available yet.  Is there a separate fix that somehow slipped the SP1
> packaging.   Please help!
>
>
>
> Is there a way for these PCs to keep these SEM registered servers?
>
>

Relevant Pages

  • Re: Security
    ... If you set a DACL on the registry keys, you can prevent any user from ... In other words the GPO was still ... >>> I had set Group Policy on the domain controller so that the client ...
    (microsoft.public.win2000.group_policy)
  • Enterprose Manager after user password change
    ... registered servers when the user's network password is changed. ... [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL ... Saving the keys and restoring will ... password should be written to the registry. ...
    (microsoft.public.sqlserver.security)
  • Re: Security
    ... > homepage on the client was unavailable. ... > homepage AND clean out the registry entries that were changed. ... It cannot alter keys that the user has ... homepage setting was altered despite settings you have set in a GPO. ...
    (microsoft.public.win2000.group_policy)
  • Enterprise Manager after user password change
    ... The XP client PCs on our network lose their MS SQL Enterprise Manager ... registered servers when the user's network password is changed. ... Saving the keys and restoring will ... password should be written to the registry. ...
    (microsoft.public.sqlserver.security)
  • Re: Migrating to new domain
    ... > they had to reregister their servers in Enterprise manager. ... > the client had registered or at least be able to tell them where they ... The SQL Servers groups with registered servers lists are usually stored in ... But I am not sure whether you can just export/import the registry keys to ...
    (microsoft.public.sqlserver.server)