G
Guest
Guest
Archived from groups: microsoft.public.win2000.group_policy (More info?)
I have created a login script that runs some updates to some software on the
150 workstations on my LAN.
The problem I'm running into is that several of my workstations are not
running the logon script.
I placed the logon script in the
\\mydomain.com\sysvol\bpc-financial.com\Policies\{31B2F340-016D-11D2-945F-00
C04FB984F9}\USER\Scripts\Logon
I have added the logon script to scripts list under the Default Domain
Policy:
User Configuration | Windows Settings | Scripts | Logon list.
Most of my workstations are running the script with no problem.
I will say this, when we setup several of these workstations, we created a
master workstation and ghosted the hard drive image to the new systems.
The new systems were disjoined from the domain, renamed, and rejoined the
domain once they were deployed.
I haven't found any way to really test this or test to see if a script has
run on a workstation other than to go to the workstation and see what
version of the software is on the actual PC.
Does anyone have any suggestions?
I have created a login script that runs some updates to some software on the
150 workstations on my LAN.
The problem I'm running into is that several of my workstations are not
running the logon script.
I placed the logon script in the
\\mydomain.com\sysvol\bpc-financial.com\Policies\{31B2F340-016D-11D2-945F-00
C04FB984F9}\USER\Scripts\Logon
I have added the logon script to scripts list under the Default Domain
Policy:
User Configuration | Windows Settings | Scripts | Logon list.
Most of my workstations are running the script with no problem.
I will say this, when we setup several of these workstations, we created a
master workstation and ghosted the hard drive image to the new systems.
The new systems were disjoined from the domain, renamed, and rejoined the
domain once they were deployed.
I haven't found any way to really test this or test to see if a script has
run on a workstation other than to go to the workstation and see what
version of the software is on the actual PC.
Does anyone have any suggestions?