I have aset up a small workgroup LAN for my church that has several novis
users.

When these users have connection problems, they use the network connection
wizard to try to Fix things.

It be nice to disable this wizard entirely, but I'd settle for changing the
default workgroup to be the PC's defined workgroup for the PC instead of
MSHOME.

Derz wrote:

> I have aset up a small workgroup LAN for my church that has several
> novis users.
>
> When these users have connection problems, they use the network
> connection wizard to try to Fix things.
>
> It be nice to disable this wizard entirely, but I'd settle for
> changing the default workgroup to be the PC's defined workgroup for
> the PC instead of MSHOME.

I'm not sure why changing the workgroup would be useful. Why not set up
those users as Limited accounts and have the computer automatically log
in to a Limited account? You didn't say if you are using Pro or Home.
With Pro, you can set up very fine-grained user permissions and set the
machines up so users can't change anything. If you have Home, you can
try Doug Knox's Security Console program from http://www.dougknox.com.
I believe it's under Windows Utilities.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

"Malke" wrote:
> I'm not sure why changing the workgroup would be useful...

Because they keep changing the workgroup inadvertantly to MSHOME and can no
longer access the shared resources on the LAN established workgroup. This is
all I want to lock down.

I'd rather not go with restrictred accounts. I don't want to manage them.
They want to install their own software, create new accounts, etc. I don't
want to be an ADMIN. Just want to Idiot proof this MS oversight.

In article <77FB1FBC-5074-45D3-94AC-(E-Mail Removed)>,
"Derz" <(E-Mail Removed)> wrote:
>"Malke" wrote:
>> I'm not sure why changing the workgroup would be useful...
>
>Because they keep changing the workgroup inadvertantly to MSHOME and can no
>longer access the shared resources on the LAN established workgroup. This is
>all I want to lock down.
>
>I'd rather not go with restrictred accounts. I don't want to manage them.
>They want to install their own software, create new accounts, etc. I don't
>want to be an ADMIN. Just want to Idiot proof this MS oversight.

Changing the workgroup name doesn't prevent access to shared resources
on the LAN established workgroup. Windows networking supports
multiple workgroups, and a computer in any workgroup can access a
computer in any workgroup.

To see all of the workgroups on a network:

1. Click My Network Places.
2. Click "View workgroup computers".
3. Press the Backspace key.

To access another computer, regardless of what workgroup either
computer is in, type the other computer's name in the Start | Run box
in this format:

\\computer
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

"Steve Winograd [MVP]" wrote:
> Changing the workgroup name doesn't prevent access to shared resources
> on the LAN established workgroup. Windows networking supports
> multiple workgroups, and a computer in any workgroup can access a
> computer in any workgroup.

Interesting, I didn't know that.. Not sure why then the shared data folder
refuses to "auto-connect" on clients until I correct the workgroup on the
server..

Thanks for the info..

I also found a way to eliminate access to the network connection wizard for
all users. You can't rename or delete the file (Windows will recreate it on
the fly. But you can use security to Deny Execute access to everyone..
The file is..%SystemRoot%\System32\hnetwiz.dll