The 2nd script reads a value from HKCU\Software and writes it to  file
 
I need to read a value from it but I can only access it when the current user is logged on.
 
I don't know how else to gain access to that key since i don't know the user's sid, so i put it into a user logon script via GPO so i can read it when the user logs on and that key is loaded.
 
should i run scripts sycncronously to get this key or is there a way to read it without the user logged on?
thanks

 
On 12/7/05, Jeff Salisbury <[EMAIL PROTECTED]> wrote:
We had this happen by accident for a short time. The old logon script specied in the user account properties was running as well as the desired logon script, which we tie to AD Sites. Both were running, and if I remember right the drive mappings in the legacy script were winning - which would mean that it was running after the script that was triggered by group policy. I don't think there is any harm provided there aren't conflicting drive mappings or other settings where script timing would need to be verified and accounted for.

Jeff


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Tom Kern
Sent: Wednesday, December 07, 2005 12:58 PM
To: activedirectory
Subject: [ActiveDir] logon scripts

 
What happends if you have 2 different logon scripts for users-
one in the legacy location and one in a domain GPO?
 
how do they execute?
does one start sooner?
are there any issues with doing things this way for a short time period?
 
Both scripts do completley different things.
 
Thanks
Confidential
This e-mail and any files transmitted with it are the property
of Belkin Corporation and/or its affiliates, are confidential,
and are intended solely for the use of the individual or
entity to whom this e-mail is addressed.  If you are not one
of the named recipients or otherwise have reason to believe
that you have received this e-mail in error, please notify the
sender and delete this message immediately from your computer.
Any other use, retention, dissemination, forwarding, printing
or copying of this e-mail is strictly prohibited.

Reply via email to