I am in the process of migrating a 80-100 user 'WORKGROUP' to a Windows 2003 R2 Active directory. I have to complete this in phases. The main issues right now is when I create the new users in AD they still need to connect to our FILESERVER in the 'WORKGROUP' until I migrate that data to the new domain and implement DFS. Wondering if anyone had any login script ideas or had a similar experience?I have tried using a general "net use z: \\fileserver\public /user:test password" batch file, but to get it to work I need to plug-in the users old usernname & password. I added the logon.bat to their AD account, but it won't run. Once logged into their PC and you manually launch the script, it works like a charm. I know there are issues around the UAC anddesign because there are actually two tokens in play here. What happens is the LSA recognized that you are admin at logon and creates two logons. The first with a "filtered" token or non-admin which is used to render your desktop andthe other containing your full token to be available after consent dialogs.I have even tried deploying via GPO using the "launchapp.wsf" and still no drive mappings. Like I said if I copy the logon.bat locally and run it works.ZT

Anyone have any suggestions?ZT