Microsoft Networking Domain

[Goethe]

This is my 2nd post on this subject, I haven't got any help the first time so I'll try again.
I need some utility or registry tweak that would hide domain field on microsoft networking login and I need it bad. it became daily problem with stupid people changing domain name and I am getting sick and tired of it. please help!!!!!!!!!!!!!!
http://sysopt.earthweb.com/forum/frown.gif

[Goethe]

It's more complicated then that, First Microsoft login comes up and when they login onto the domain it logs them into the novell also, then there is few software updates that run every time they log in.
Trust me I tried to tell them but it's not easy to tell 300 people same thing every day.
I just need something that will hide Domain field.

[Mntsnow]

LOL I know about "training" people sometimes http://sysopt.earthweb.com/forum/frown.gif At my work we also use Novell networking. Can you possibly change which Networking client that they sign into first? We actually have the Novell client as the primary log in and once they have logged into their machine once you can hide the "context/domain" that they authenticate to. Then within a script for Novell it will then log them into the Microsoft client as well.

[Mntsnow]

Why not create a script that they start that will then complete their login correctly? I'm sorry but I dont know of the "microsoft" tweak that will let you hide the domain name. Why not instruct the users to not change the domain name? or setup a DHCP server that will assign them to the correct workgroup and domain?

Sorry I didnt post before..I didnt know the answer so I didnt post http://sysopt.earthweb.com/forum/smile.gif

[ctaylor]

We do the same thing as MTNSNOW suggested here. The limitation with being primarilly a CLIENT FOR NETWARE NETWORKS first is that you then need to make sure that the field for the correct primary login server remains unchanged.

To me, this sounds like a variation of the NT Domain field problem. Perhaps newer versions of Netware avoid this problem......

[Goethe]

There is no problem, I was already aware of that solution but it's not eazy to change it on 300 + PC's. I was just thinking that I could find something and be able to push it through with the rest of the software updates.

[Mntsnow]

I will try and run it past a couple of our Admins at work and see if they can offer anyother Idea's