Prev: Accessing files on Desktop from in network computers
Next: Home network puzzle -- things have fallen apart.
From: JClark on 3 Jan 2010 11:04
On Thu, 3 Dec 2009 17:51:28 -0600, VanguardLH <V(a)nguard.LH> wrote:

>JClark wrote:
>
>> John John wrote:
>>
>>> use a batch file then just create a .reg file
>>
>> Love that batch file idea. I've copied your post to refer to as I
>> create it.
>
>If you don't want it obvious in the normal startup locations (Startup folder
>and HKCU/HKLM Run keys) then make it a login script. For example, run
>"control.exe userpasswords2", Advanced tab, Advanced button, double-click a
>username to see the advanced properties, Profile tab, and enter the name of
>the .bat or .cmd file as the login script. This is how you do it for local
>security policies. In a domain, you get to push policies which include
>login scripts. Presumably you wouldn't bother saving the login script on
>the user's own host but use an UNC to point at a network resource to find
>the script file.
>
>Also, rather than use a .bat file that then loads load a .reg file (via
>"regedit.exe /s <regfile>"), you could eliminate the need for the .reg file
>altogether and just have the batch file do the registry changes. Have the
>batch file use reg.exe to make direct changes to registry (run "reg.exe /?"
>for help).
Thank you, Vanguard. I will peruse your post and try to learn from it.
Since I had so few persons to do it for, it made more sense just to
configure each profile.
Jack
 | 
Pages: 1
Prev: Accessing files on Desktop from in network computers
Next: Home network puzzle -- things have fallen apart.