I have two servers. One is a W2K Server set as the primary domain controller (although I don’t use is as a PDC) and the other is a Windows NT4 Server setup as a standalone server which is a member of a workgroup that is a member of the domain. When a user logs in, he logs into a workgroup, not the domain. Then a .bat file is launched from their startup folder which runs KiXtart from the standalone NT4 Server which maps the network drives based upon their user name and group membership. This setup evolved over the years and although not perfect, it works fine for our 50 users.
I am transferring the NT4 setup to new server hardware. I have installed the same NT4 operating system on the new box and imported the SAM database from the old server to the new installation. But in this new setup, the KIX logon script does not recognize the user as being a member of local groups on the new NT4 Server when using the INGROUP statement in KIX. If I logon as that user on the actual server itself, KIX does work as expected, but when I logon as a user on a client workstation (W98 or W2K) the logon script runs, but the INGROUP statement does not recognize any of the group memberships. If I run a test script from a workstation using the ENUMLOCALGROUP statement in a DO loop, it only shows the first group on the server and stops. If I run the same test script from the server, it does show all the groups that the user is member of.
As far as I know, the new NT4 install is the same as the old one, but what worked fine in the old installation is not working in the new NT4 installation. Any idea why KiXtart is not assigning users to groups on the new NT4 installation?
I am transferring the NT4 setup to new server hardware. I have installed the same NT4 operating system on the new box and imported the SAM database from the old server to the new installation. But in this new setup, the KIX logon script does not recognize the user as being a member of local groups on the new NT4 Server when using the INGROUP statement in KIX. If I logon as that user on the actual server itself, KIX does work as expected, but when I logon as a user on a client workstation (W98 or W2K) the logon script runs, but the INGROUP statement does not recognize any of the group memberships. If I run a test script from a workstation using the ENUMLOCALGROUP statement in a DO loop, it only shows the first group on the server and stops. If I run the same test script from the server, it does show all the groups that the user is member of.
As far as I know, the new NT4 install is the same as the old one, but what worked fine in the old installation is not working in the new NT4 installation. Any idea why KiXtart is not assigning users to groups on the new NT4 installation?
