if you're using the script from the DOC-4602, then everything should be fine. The script is aware of name changes (the "Name" in Service Desk is the login name) and thus it should set all network logins in the correct way. So for everything to work in order, you have to ensure that:
- Either users are being imported regularly OR that all name changes also happen in Service Desk. The script uses the attribute Name (tps_name) from the user to build the network login.
- The sp_SetNetworkLogin es being executed regularly (preferably daily over night). To do so, use a Maintenance Plan on your SQL Server and let the SQL Server run this stored procedure ("exec sp_SetNetworkLogin").
So if you're running both actions regularly, then all network logins should match the users.
Sometimes it happens, that Service Desk needs the tps_is_primary to be set for the primary network login. If you have more than one network login per user, that will be mandatory. If there is only one network login per user, then it is a good idea to set the value but it should work anyways. If you do not see the attribute on the Network Login window, just open the Console and go to the Designers - Window Manager - System - User Network Login and add the attribute to the window.
If you've got only one network login per user, then you can amend the script (in the original script that you can download these will be lines 43 and 44):
insert into tps_user_network_login (tps_guid,tps_user_guid,tps_network_login,tps_is_primary) values (newid(),@guid,@networkLogin,1)
That will ensure, that the one networklogin, you have per user, is marked as primary network login.
Hope that helps!