Fixing user with wrong Domain Logon Name

This is both a comment and question. When adding a new user I forgot to
preface his Domain Logon Name with the domain. Instead of typing
domain\username I simply typed username. There was warning message that was
generated but then the user got created. I opened the newly created user in
an attempt to fix my mistake but the Domain Logon Name field was greyed out.

I "fixed" the problem by modifying the users' record in the SystemUserBase
table in the CompanyName_MSCRM database. So far everything seems to be
working but if any of you see a problem with how I fixed this issue, please
let me know ASAP before I run into bigger problems.

Thanks.

Mathieu
Wed Jun 15 15:02:47 CDT 2005

As far as I know, modifying directly the DB is not supported by Microsoft
and should NEVER be done, for any reason. You are lucky if you don't get
into deep problems with this...

Mathieu.


"Guy Kerr" <GuyKerr@discussions.microsoft.com> a écrit dans le message de
news: F73EC0FB-6DA1-4CE2-A81C-C24D605BB827@microsoft.com...
> This is both a comment and question. When adding a new user I forgot to
> preface his Domain Logon Name with the domain. Instead of typing
> domain\username I simply typed username. There was warning message that
> was
> generated but then the user got created. I opened the newly created user
> in
> an attempt to fix my mistake but the Domain Logon Name field was greyed
> out.
>
> I "fixed" the problem by modifying the users' record in the SystemUserBase
> table in the CompanyName_MSCRM database. So far everything seems to be
> working but if any of you see a problem with how I fixed this issue,
> please
> let me know ASAP before I run into bigger problems.
>
> Thanks.

Matt
Wed Jun 15 23:06:17 CDT 2005

I have done this myself in the past without any problems. In general, updating
the dataase directly is not advised, but there are some cases where you have
to. But, you should never mess with the GUIDS as they may affect the
SecurityDescriptor which can cause major problems down the road.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On Wed, 15 Jun 2005 12:46:09 -0700, "Guy Kerr"
<GuyKerr@discussions.microsoft.com> wrote:

This is both a comment and question. When adding a new user I forgot to
preface his Domain Logon Name with the domain. Instead of typing
domain\username I simply typed username. There was warning message that was
generated but then the user got created. I opened the newly created user in
an attempt to fix my mistake but the Domain Logon Name field was greyed out.

I "fixed" the problem by modifying the users' record in the SystemUserBase
table in the CompanyName_MSCRM database. So far everything seems to be
working but if any of you see a problem with how I fixed this issue, please
let me know ASAP before I run into bigger problems.

Thanks.

John
Wed Jun 15 23:47:28 CDT 2005

also done this...in my case it was because the full domain name was entered
instead of the netbios domain name. Again no problems have been seen and in
fact MBS support recommended this approach

--
John O'Donnell
Microsoft CRM MVP
http://www.mscrmfaq.us


"Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
news:oju1b11okc8isiri5vlvd87odq0vk6ljqu@4ax.com...
> I have done this myself in the past without any problems. In general,
updating
> the dataase directly is not advised, but there are some cases where you
have
> to. But, you should never mess with the GUIDS as they may affect the
> SecurityDescriptor which can cause major problems down the road.
>
> Matt Parks
> MVP - Microsoft CRM
>
> ----------------------------------------
> ----------------------------------------
> On Wed, 15 Jun 2005 12:46:09 -0700, "Guy Kerr"
> <GuyKerr@discussions.microsoft.com> wrote:
>
> This is both a comment and question. When adding a new user I forgot to
> preface his Domain Logon Name with the domain. Instead of typing
> domain\username I simply typed username. There was warning message that
was
> generated but then the user got created. I opened the newly created user
in
> an attempt to fix my mistake but the Domain Logon Name field was greyed
out.
>
> I "fixed" the problem by modifying the users' record in the SystemUserBase
> table in the CompanyName_MSCRM database. So far everything seems to be
> working but if any of you see a problem with how I fixed this issue,
please
> let me know ASAP before I run into bigger problems.
>
> Thanks.
>

NathanWarner
Mon Jun 20 00:58:03 CDT 2005

good post thanks guys!

"John O'Donnell" wrote:

> also done this...in my case it was because the full domain name was entered
> instead of the netbios domain name. Again no problems have been seen and in
> fact MBS support recommended this approach
>
> --
> John O'Donnell
> Microsoft CRM MVP
> http://www.mscrmfaq.us
>
>
> "Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
> news:oju1b11okc8isiri5vlvd87odq0vk6ljqu@4ax.com...
> > I have done this myself in the past without any problems. In general,
> updating
> > the dataase directly is not advised, but there are some cases where you
> have
> > to. But, you should never mess with the GUIDS as they may affect the
> > SecurityDescriptor which can cause major problems down the road.
> >
> > Matt Parks
> > MVP - Microsoft CRM
> >
> > ----------------------------------------
> > ----------------------------------------
> > On Wed, 15 Jun 2005 12:46:09 -0700, "Guy Kerr"
> > <GuyKerr@discussions.microsoft.com> wrote:
> >
> > This is both a comment and question. When adding a new user I forgot to
> > preface his Domain Logon Name with the domain. Instead of typing
> > domain\username I simply typed username. There was warning message that
> was
> > generated but then the user got created. I opened the newly created user
> in
> > an attempt to fix my mistake but the Domain Logon Name field was greyed
> out.
> >
> > I "fixed" the problem by modifying the users' record in the SystemUserBase
> > table in the CompanyName_MSCRM database. So far everything seems to be
> > working but if any of you see a problem with how I fixed this issue,
> please
> > let me know ASAP before I run into bigger problems.
> >
> > Thanks.
> >
>
>
>