As far as I can tell, enabling loopback processing in a seperate group policy seems to be cause our login script to run twice on login.
I have a seperate policy for running the login scripts (default domain one) and another where this is enabled (a screen saver policy).. IE: I thought i read somewhere that it is bad practice to modify the default policies.. so I try to to create seperate policies for different things (or combos where appropriate), except in this case where its just a batch file referenced in the def. domain policy, though I should probably move that one out.
I enabled loopback on the user portion of the screensaver policy (timeout and password options set here).. I did this so I could disable the policy on a machine basis, rather than user basis (I didnt see how it could be done without the loopback turned on, as the screen saver settings come from the user section, not the computer section).
Any thoughts on why this enabled in that policy would cause the scripts to run twice in the default domain one?
Thanks,
Mark
I have a seperate policy for running the login scripts (default domain one) and another where this is enabled (a screen saver policy).. IE: I thought i read somewhere that it is bad practice to modify the default policies.. so I try to to create seperate policies for different things (or combos where appropriate), except in this case where its just a batch file referenced in the def. domain policy, though I should probably move that one out.
I enabled loopback on the user portion of the screensaver policy (timeout and password options set here).. I did this so I could disable the policy on a machine basis, rather than user basis (I didnt see how it could be done without the loopback turned on, as the screen saver settings come from the user section, not the computer section).
Any thoughts on why this enabled in that policy would cause the scripts to run twice in the default domain one?
Thanks,
Mark
