Using the Registry to Change Settings in XP Home Ed.

[David Dickinson]

My client tried to do things on the cheap and bought nine
XP Home machines for their network before they called me.

It's a peer-to-peer network (no domain) with 2KPro and XPH
workstations only. I need to change the network
authentication method of the XPH machines to "Classic -
local users authenticate as themselves". Of course,
however, there's no gpedit.exe on XPH.

I thought I could change the value of forceguest at

HKLM\System\CurrentControlSet\Control\LSA

to "0" instead of the expected default "1" (authenticate
as guest), but it's already 0!

Does XP Home ignore these values or am I missing something?

I'll be grateful for any help.

David Dickinson
eveningstar at mvps dot org

 

[Doug Knox MS-MVP]

As far as I'm aware, XP Home ignores this setting, and all network access authenticates as Guest.

 

[Torgeir Bakken \(MVP\)]

As far as I'm aware, XP Home ignores this setting, and all network access authenticates as Guest.

Yes, you are correct, XP Home ignores the ForceGuest setting...

 

[GTS]

As others noted, you can't do that on XP Home. You may, however, be able
to work around it, depending on what you need to do. If it's an issue of
accessing shared resources without using the guest account, mapping shares
with individual user names and passwords is sometimes an option. See sample
batch files at
http://[Remove anti spam spaces]www. gtscomputerservice. com

(I've use this successfully for several clients with XP Home issues, buy if
you need the authentication for some reason other than simple shares, it
won't help.)

 

[Guest]

As others noted, you can't do that on XP Home.

Yep. They've said that XP Home ignores the registry
settings.

What I'm trying to do is to use MBSA to scan XP Home
systems on a peer-to-peer network. Unfortunately, it
can't unless it can authenticate as an administrator on
the remote machine.

Argh.

But thanks for your reply.