Netware 6.5. SP5 environment, OUs broken down by geographical location. We have a large jobsite that is joining the WAN and will have a local Netware server, in a separate OU. The users that are going to the jobsite will bounce back and forth between the jobsite and other locations (OUs). Instead of creating multiple user objects for a user, it seems an alias object in the jobsite OU may be the way to go to simplify the password issue. When using the alias object, what is the best way to control login scripts so that the headquarter scripts don't run, but rather the scripts written on the jobsite OU? Perhaps a combination of detecting which subnet the user is logging in on? While at the jobsite, the user should map the local server. When back at HQ, map their traditional server. The user will manually change their context as needed, no problem there. What's the best way to accomplish this? Thanks!