Merging .REG files in NT4

Lmhost should be enabled by default unless something was previously done. If you want lmhosts read first, its a matter of changing the mode the workstations use and thus what order.

The reason your having problems getting your reg to insert via alogon script is because when a user executes a logon script, its in his/her contex. The Token they logged on with is the permission the logon script has at execution, remember a logon script is nothing more then a batch file running under a users security context. The end user doesnt have the permissions to execute the insertion of the registry file your trying to deploy.
Im curious why your deploying Lmhosts instead of using a WINS server? If you want to deploy this reg hack, the persona executing the command has to have administrative rights on the local Windows NT system and then your script should execute.

Hope I helped! Good luck!

Pete

I second what NTOz said, but with one thing to add. If its just a matter of the .reg not even launching, enclose that line of the batch file in double quotes. This especially applies with long file names, but I've seen it effect short names to. You should have a line in your logon script like this:

"\\PDC\netlogon\lmhostreg.reg"

That should fire it off, although if your users don't have the right permissions, it may not work properly. Good luck

This question was closed by the author