From your previous post I don't think this is an issue of concurrent running. Were you not trying to write to the current user hive during logon. If so, I think the real issue is Win9x doesn't define the "Current User" hive in the registry until after logon completes. In Win9x you can not write to "Curent User" until logon completes.Does WinNT create this hive before the logon script starts up? We have no WinNT clients on our network so I have never tested this. I had always assumed NT & Win9x behave the same on this issue.
Fuse,
As a guess from his previous post, I assumed he was trying to set registry policies in the current user hive during the logon process.
SLM,
If you are trying to set policies during logon I recommend you turn all user policies off & then you can set very complex lock downs in by writing to the "default user key from your logon script.
If your network clients consists of a relatively homogenous mix of hardware/software then roaming policies might do the trick.
Poking these policies into the runonce key can be a catch-22 sometimes. Some of the policies might require rebooting to work.
Our strategy is turn polices off then lock down real tight during boot up and then relax constraints during logon.
[This message has been edited by JackLothian (edited 31 March 2001).]
