edit logon locally, why can't I?

[Mike MacSween]

Windows XP Pro, SP2

I found I had a problem with an ASP site I run locally. The user of that
site couldn't logon. In local security policies, user rights assignment, the
'logon locally' option in uneditable, and has a different icon. What gives?
Why can't I edit logon locally. I've got full admin privileges.

Why did the anonymous user who once could logon on locally get changed. I
didn't do it.

Cheers, Mike MacSween

 

[george]

Windows XP Pro, SP2

I found I had a problem with an ASP site I run locally. The user of that
site couldn't logon. In local security policies, user rights assignment,
the 'logon locally' option in uneditable, and has a different icon. What
gives? Why can't I edit logon locally. I've got full admin privileges.

Why did the anonymous user who once could logon on locally get changed. I
didn't do it.

Cheers, Mike MacSween

Could it be that your machine happens to be (or has been in the past) part
of a Windows 2000/2003 domain?
In that case it is subject to Domain Group Policies. (The different icon is
a little group of 3 'machines', rather than the blue 0101, right?)
If so, place the machine in a workgroup to get out of the GPO being applied
or, alternatively, alter the GPO settings at the domain level to reflect
your goal.

hth

george

 

[Mike MacSween]

Thanks.

Everything you say is correct, I think. But I really couldn't find where to
edit the group policy for local logon on the server. Any clues?

Cheers, Mike

 

[george]

There are a few ways in which you can edit this.
In ADUC (Active Directory Users and Computers), Domain Properties, Group
Policy Tab, Default Domain Policy, Edit,
or On the Group Policy tab the button that takes you to GPMC (Group Policy
Management Console if you happen to have that installed)
or through Administrative Tools, Domain Security Policy (if you're running
Windows 2000 AD.
Or the equivalents of these when running Windows Server 2003.
Don't really know what you've got setup, so I hope this gets you started in
the right direction.
Incidentally, please keep in mind that notably this kind of security setting
is a domain-wide deal.

hth

george