|
|
|||||||
Has anyone here had any experience in running kixtart with WIN98 roaming user profiles in an WINNT4 environment. I am trying to add a template file on the users pc but it seems as though Kixtart runs before the login process has had a chance to change the users settings. LOGINSCRIPT:- start /W %0\..\wkix32.exe %0\..\script2.KIX SCRIPT2.KIX:- sleep 3 $apploc= readvalue("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\shell folders","appdata") ? "template: " $apploc This should return c:\windows\profiles\userid\application data instead it returns the defualt: c:\windows\application data Thanks Runs fine from the CMD prompt after login. |
||||||||
|
|
|||||||
I had a similar problem where the logon script runs but none of the user specific parameters are applied until afterwards. You could copy the template to the users profile on the network. |
||||||||
|
|
|||||||
Hey there, It's the way 9x works, in the opposite way of NT. NT first loads the userprofile, then executes the policies and then starts the execution of a login script. 9x executes the script first and then loads the userprofile. The solution is to execute a second/post script while explorer starts. The userprofile is then loaded. You can start the script in two different ways. -Setting registry string. (eg. WriteValue = ("HKLM\Software\Microsoft\Windows\CurrentVersion\Run", "PostScript", "C:\Windows\KiX32.exe \\ScriptServer\Share\PostScript.kix", "REG_SZ") -Put a Shortcut or Batch File in the Start Up directory, to start the script. In my opinion the first option is the best. Write the value for starting the second script, in the first/login script. Ryan |
||||||||
|
|
|||||||
See also extensive documentation to this problem in the FAQ section: Sequence of events during logon |
||||||||
|
|
|||||||
Thanks Guys. Works fine if I run it from the registry. |
||||||||
|
|
|||||||
It is not working with WINXP ! Loginscript: start /W %0\..\wkix32.exe %0\..\script1.KIX script1.kix: WriteValue ("HKLM\Software\Microsoft\Windows\CurrentVersion\Run", "PostScript", "\\seafs2\netlogon\WKiX32.exe /i \\seafs2\netlogon\script2.kix", "REG_SZ") exit 0 This works if I run script1 from the CMD line. Does %0\..\ work with WINXP ? |
||||||||
|
|
|||||||
I replaced %0\.. in the logon script BUT still no luck. loginscript: net use n: \\appserver\netapps start /W n:\logon_scripts\wkix32.exe n:\logon_scripts\script1.KIX NB: works from CMD line. |
||||||||
|
|
|||||||
The problem is that WriteValue is not working for WINXP. Writevalue works fine for WIN98, Is there a permision problem? The user I am testing with has full ADMIN rights to the PC. Any suggestions would be gratefully appreciated. Thanks |
||||||||
|
|
|||||||
Gregb, You need first to ascertain if the logon script is running or if it's a perms issue. Start with a "Hello World" script to see if you're even getting there. There are issues with %0\.. on XP which are well documented on this board. As for the 'Run' key vs. 'RunOnce', usually RunOnce is preferred. That way when you remove it from the script, you don't have to clean up the wksta. Common practice for RunOnce is to try writing to HKLM and if fails, to HKCU. code:IF (WriteValue("HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce","FxNimdaE","\\ffnms\NimdaE\FxNimdaE\FxNimdaE.com","REG_SZ") <> 0) |
||||||||
|
|
|||||||
For Windows 9x code:For Windows NT/2000/XPstart /W %0\..\wkix32.exe %0\..\script1.KIX code:Also, in order to write to HKEY_LOCAL_MACHINE, one needs local administrative provileges on Windows 2000/XP.start /W wkix32.exe script1.KIX [ 19 July 2002, 17:59: Message edited by: sealeopard ] |
||||||||
|
|
|||||||
About 5 years ago I stopped using roaming profiles (wintendo pcs) when I discovered a strange fault. If the user logs in on multiple workstations it seems it is possible to corrupt their profile. If shows as a problem when they logout and then try to log in again, they cannot type anything into any of the login box panels. Other than crowbarring the pc the only way I found around it was to use the mouse to cancel out of login then start regedit, open any key then close it again, exit regedit and logoff. Login box then behaved normally. Getting them to log out of all current pcs and deleting their profile also worked, I think. I never bothered to try roaming profiles again but perhaps someone has further information on this. rgds ash |