Require Windows 98 Clients to Logon to the Domain
How can I require Windows 98 clients to logon to the domain instead of pressing “cancel” at the welcome screen?
By default Windows 9x doesn’t require a valid network username and password combination for a user to bypass the logon and gain access to the local machine. This functionality can be changed to require validation by the network before allowing access.
Actually there are 2 ways in which you can do it:
You need to set a system policy by creating a CONFIG.POL file using POLEDIT.EXE which comes on the Win9x CD and put the file in the NETLOGON directory of the domain controller server (if you have more than one you need to manually copy the file to the same location on all DCs). The path is: %systemroot%\system32\repl\scripts\export
- Go to your Win98 CD and navigate to X:\tools\reskit\netadmin\poledit\poledit.exe
(where X is the drive letter of your CD). Run poledit.exe.
Note: Make sure you use the version found on the Win98 CD and NOT the one provided with W2K!
- From the Options menu go to Policy Templates and Add the Windows.adm template if it isn‘t showing already.
- Go to the File menu, then choose New Policy.
- Double click into Default Computer.
- Drill down through Win98 Network, Logon. Tick Require Validation from network to logon.
- You can also add a banner warning users not to attempt to logon if they dont have the correct username and password or a capital punishment warning…
- Click down to the Update entry. Check Remote Update. Set Update Mode to Automatic.
- Go to File | Save As CONFIG.POL and copy to the NETLOGON share which is actually the %systemroot%\system32\repl\scripts\export folder. Make sure you copy it to the same location on all DCs (PDC and BDC).
- Open your registry and find the key below:
- Create a new DWORD value, or modify the existing value called “MustBeValidated” and set it to equal “1” to require successful authentication.
- Restart Windows for the change to take effect.
- Your machine must be part of a Windows domain for this tweak to work, as the user must be authenticated by the network.
More in Active Directory
How to Fix the "An Active Directory Domain Controller for the Domain Could Not Be Contacted" Error
Jun 20, 2022 | Michael Reinders
How to Delete a Protected OU in Active Directory
Jun 8, 2022 | Michael Reinders
Learn How Organizations Are Using Semperis Purple Knight to Secure Active Directory
Jun 7, 2022 | Russell Smith
Microsoft Announces Entra, A New Identity and Access Management Suite
May 31, 2022 | Rabia Noureen
Microsoft Releases Out-Of-Band Patches to Fix Windows AD Authentication Issues
May 20, 2022 | Rabia Noureen
Cloud Conversations – Ståle Hansen on Digital Wellbeing and Viva Explorers
May 19, 2022 | Laurent Giret
Most popular on petri