S
Scott M. Foster
I'm trying to run a program (C:\Program
Files\Netscreen\Netscreen-Remote\vpn.exe -deactivate) that is located
on a Windows 2000 Professional system during the shutdown process. I
created a GPO shutdown script in my AD that calls the program. Since
there technically is no script I didn't have anything to place on the
DCs.
When I log onto the desktop and run gpresult.exe I can see that the
GPO is applied, but when I run the Group Policy plug-in for the MMC, I
can't see that the policy has replicated (unlike other settings that
do appear to replicate and show this when looking at the Group Policy
plug-in). This is confirmed when I shutdown the machine and I can
determine that the program isn't launched based on the configuration
of the machine when I logon again.
If I configure the Group Policy shutdown script on the local machine,
the policy works great. So this is what is stumping me, the shutdown
script policy works just fine on the local machine as long as I
defined it there, but when I define it from AD it doesn't appear to
work. I'm a little confused as to why this would be the case. Can
someone help me out here?
Scott (Frost)
Files\Netscreen\Netscreen-Remote\vpn.exe -deactivate) that is located
on a Windows 2000 Professional system during the shutdown process. I
created a GPO shutdown script in my AD that calls the program. Since
there technically is no script I didn't have anything to place on the
DCs.
When I log onto the desktop and run gpresult.exe I can see that the
GPO is applied, but when I run the Group Policy plug-in for the MMC, I
can't see that the policy has replicated (unlike other settings that
do appear to replicate and show this when looking at the Group Policy
plug-in). This is confirmed when I shutdown the machine and I can
determine that the program isn't launched based on the configuration
of the machine when I logon again.
If I configure the Group Policy shutdown script on the local machine,
the policy works great. So this is what is stumping me, the shutdown
script policy works just fine on the local machine as long as I
defined it there, but when I define it from AD it doesn't appear to
work. I'm a little confused as to why this would be the case. Can
someone help me out here?
Scott (Frost)