Forced to make local users

I have some software that on some machines, I must create a local user with
the same ID as their Active Directory ID to get the program to work. We had
tested for file access, and other stuff, but ended up just creating this new
user and adding them to the Power Users group. Yes, we did try adding the
"real" user to the Power Users group. Now, the user would still log into the
Domain, but it's just that the program would now work.

Any ideas? These symptoms are sporadic and not applicable to any given
program or person. All workstations are XPSP2. This behavior happens very
infrequently however is frequent enough to be a pain. Especially since I
want to minimize the use/number of Local Users.


Carl

Carl Hilton wrote:
> I have some software that on some machines, I must create a local
> user with the same ID as their Active Directory ID to get the
> program to work. We had tested for file access, and other stuff,
> but ended up just creating this new user and adding them to the
> Power Users group. Yes, we did try adding the "real" user to the
> Power Users group. Now, the user would still log into the Domain,
> but it's just that the program would now work.
> Any ideas? These symptoms are sporadic and not applicable to any
> given program or person. All workstations are XPSP2. This behavior
> happens very infrequently however is frequent enough to be a pain.
> Especially since I want to minimize the use/number of Local Users.

Sounds more like something is terribly wrong with said machines.
A local account vs a domain account - if given the same local group
membership - should make no difference in the runnig of any applications
that reside solely on that local machine.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Carl Hilton wrote:
> I have some software that on some machines, I must create a local
> user with the same ID as their Active Directory ID to get the program
> to work. We had tested for file access, and other stuff, but ended up
> just creating this new user and adding them to the Power Users group.
> Yes, we did try adding the "real" user to the Power Users group. Now,
> the user would still log into the Domain, but it's just that the
> program would now work.
> Any ideas? These symptoms are sporadic and not applicable to any given
> program or person. All workstations are XPSP2. This behavior happens
> very infrequently however is frequent enough to be a pain. Especially
> since I want to minimize the use/number of Local Users.
>
>
> Carl

Are the computers joined to the domain properly? Are the affected machines
or users affected by a group policy that the others aren't?

Kerry

See if there are any errors/warnings in the logs seen via Event Viewer on
those computers that may indicate a problem with contacting the domain,
obtaining Group Policy, etc. I would also run the support tool netdiag on
those computers and make sure that their preferred dns servers are only
domain controllers and never ISP dns servers. --- Steve



"Carl Hilton" <someone@microsoft.com> wrote in message
news:%23Zx%235faBGHA.4076@TK2MSFTNGP14.phx.gbl...
>I have some software that on some machines, I must create a local user with
>the same ID as their Active Directory ID to get the program to work. We had
>tested for file access, and other stuff, but ended up just creating this
>new user and adding them to the Power Users group. Yes, we did try adding
>the "real" user to the Power Users group. Now, the user would still log
>into the Domain, but it's just that the program would now work.
>
> Any ideas? These symptoms are sporadic and not applicable to any given
> program or person. All workstations are XPSP2. This behavior happens very
> infrequently however is frequent enough to be a pain. Especially since I
> want to minimize the use/number of Local Users.
>
>
> Carl
>
>