|
|
|||||||
I have, what I hope is a very simple problem. First the background. We have recently migrated to an Active Directory Domain (WIN2K), from NT. We also have a large installed Novell base. We are currently only running Novell login scripts. We have a mix of NT/W2K/XP workstations. I have begun testing KIXTART in the Active Directory Domain, because Novell as well as the remaining NT domain will be going away in the next couple of months. I have created a very simple script that only maps one drive based on group membership. I have added this via the Group Policy at the root of the domain. The script runs and maps the drive on all of the Win2K and XP workstations. The login script does not run on any of the NT workstations tested. There are no error messages in the Event Viewer. But if I run the script manually after I login, it will run and it does map the drive. Any ideas? Thanks, LES |
||||||||
|
|
|||||||
I'm not positive, but i don't think GPOs apply to NT machines. |
||||||||
|
|
|||||||
I AM positive! GPOs will NOT run on NT4. |
||||||||
|
|
|||||||
Additionally, it's better to implement the loginscript via the user acount and not via GPOs, IMHO. |
||||||||
|
|
|||||||
FYI one thing that i have done for the last few sites that i have put in a kixlogon script, is just to call kix32.exe and name the logon script kixtart.kix (non GPO Loginscript). This has worked 100% for all MS platforms and no bat file was needed. |
||||||||
|
|
|||||||
This will not work for Windows 9x as Windows 9x does require a batch file in order to run the login script. |
||||||||
|
|
|||||||
you sure about that... i know i have win9x systems just launching kix32.exe and they are running the logon script.... |
||||||||
|
|
|||||||
Well... GPO logon script is the only way for my users. I simply don't support Wintendos and NT4! |
||||||||
|
|
|||||||
Ok, I understand that GPO's do not apply to NT workstations. But I can't imagine doing the login script via user account, perhaps it is my Novell background talking, but it has to be easier than that. We have over 6000 users that would have to be edited. And there is no hope of eliminating all of the NT machines quickly. There are over 750 of them left. At least I don't have to deal with Win 95. I am curious about Bryce's comment. "is just to call kix32.exe and name the logon script kixtart.kix (non GPO Loginscript)." I have placed kix32.exe in the logon script in the GPO. That doesn't work on NT. Where you talking about the user profile? Bare with we, I am just looking for a workable long term solution. Thanks for all the replies! LES |
||||||||
|
|
|||||||
Quote: ok i am SURE! that this works on win9x, i just tested it on a win98 computer. Created new user in 2003 AD, under user profile, run "logon.exe" (renamed kix32.exe) and the logon script name is kixtart.kix located in the NETLOGON share. It maped the drives, and installed some of the print tracking software that we use (geez... no one has touched this win98 computer in months!) Bryce |
||||||||
|
|
|||||||
Quote: Yes userprofile is what i was talking about. There are ways around having to edit 6000 user accounts by hand. You could run a quick kix script that would do it for you. an example.... to set the logonscript on ALL users in the @domain Code:
Bryce |
||||||||
|
|
|||||||
Quote: 6 or 6000 make little difference. A quick ADSI script can edit all of them in seconds. |
||||||||
|
|
|||||||
Thank you for the Code Bryce, If I decide I just go that route, it will come in very handy. However, I have just tested the script by placing it at the user profile level and it did not work on the NT workstation either. I will continue to test on that. Thanks |
||||||||
|
|
|||||||
That is an admin script that you would run against ALL of the users in your domain providing you have Domain Admin rights. BE CAREFULL accepting gifts from Greeks! |
||||||||
|
|
|||||||
I understand that it is a admin script and I do have full rights. and I thank you for your advice. I will be careful. Thanks, LES |
||||||||
|
|
|||||||
If you check each users' profile, you should see that they have KiX32.exe assigned to them as a legacy logon script. If you have both KiX32.exe and a script called KiXtart.kix in the \Netlogon share then it should work for ALL of your users. |
||||||||
|
|
|||||||
Quote: don't you mean geeks? that is why i commented out the "dangerous" stuff how many domain controllers you have? did you give file replication time to happen? check "%logonserver%\netlogon" share and make sure your stuff is in there. Bryce |
||||||||
|
|
|||||||
Forgot to mention that if you are still running a mixed shop, you need to make sure to optimize your bindings and provider order. Do not bind IPX to the Microsoft Client and put Microsoft at the top of the provider order. |
||||||||
|
|
|||||||
Make sure that the NT4 machines have the DSClient installed to make them site aware. |
||||||||
|
|
|||||||
This test machine does have the DSClient on it. I was hoping that would not be necessary. Just another thing to push out. Let see, what other questions were asked. We have 3 Domain controllers. I know that the replication is complete now. All KIXTART files are in the Netlogon. Thanks for your help. Have a great weekend. I will be back at this on Monday! LES |
||||||||
|
|
|||||||
OK Guys. I have only had a little time to play with this today, but here is where I am. I have added the profile login script information to my account, which has full admin rights and magically the script runs on my NT workstation and it maps my drive based on Group membership. Now my test user. It only has basic domain user rights. I added the same information to the profile login script on this user. The user is a member of the test mapping group. The Group does give rights the the share we are mapping. When the test user logins into the NT workstation script does not run. Any ideas? suggestions? Thanks for all of you assistance. LES |
||||||||
|
|
|||||||
Can you execute it manually from the comand line? Does the user have read/execute access to the DCs NETLOGON share? |
||||||||
|
|
|||||||
Yes, I left that one out. I can see and run it manually and it does map the drive. |
||||||||
|
|
|||||||
If playing with test groups, you need to remember to flush the cache. Better to do a simpler test with just a messagebox() without InGroup conditionals. |
||||||||
|
|
|||||||
After I flushed the cache, it worked! Thanks so much for all of your Help! LES |
||||||||
|
|
|||||||
Flushing the cache is described in the Kixtart Manual. Please read the introductory sections and appendices! |