Startup Script after Software Installation Fails Over VPN

  • Thread starter Thread starter Jodi Tippett
  • Start date Start date
J

Jodi Tippett

I am using a Computer Group Policy to remove a software
package and push (via Software Installation) an upgraded
software package (not originally installed via GPO), and a
startup script to clean up some icons and empty folders
after the software installation.

The policy works fine at our headquarters (linked to OU),
software is installed and scripts runs properly. However,
when linking the GPO to our regions' OU (same domain,
separate site connected via T-1 through VPN) the startup
script fails to delete the folders.

Does the startup script wait for the software installation
to be finished before running, or could it be trying to
delete the folders before the package is finished with
them?

Anybody have any idea?

Jodi Tippett, MSCE, CCNA, CCA
 
Computer Startup scripts cannot be made to run over a RAS connection (note
that access speed is NOT the issue). See article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q227369

Work-around ("what we did")
======================
Can't give you the code (sorry it belongs to the company), but I can tell
you what we did to give ourselve equivalent functionality. In fact, it's
probably better than what MS would have given us because we can determine
the "run over RAS behavior" on a script-by-script basis (theirs would only
have made all or none of the scripts be able to run).
======================
======================
We created a service to run the same GPO API calls
to return the list of Computer GPOs, search them for
any scripts, and then:

a) run all scripts "always" when the access speed
was faster than the default FAST speed as
defined for Group Policies or

b) run scripts "no m,atter what the access speed"
that have an added "ForceSlow" parameter
on the command line when the speed was
slower than the default FAST speed as defined
for Group Policies.

(Note: MS default setting for FAST = 500 kbps)

When the activities are completed, it stops itself (stops
as a service). All activities are logged either in a local file
(time, date, accessing what DC, GPOs with scripts found,
which scripts were launched, etc.) or in the Event log
(service start, service stop, etc.).

The service wakes up on device booting and checks for
connectivity to a Domain Controller.

o If it determines that the device is running on a domain
LAN FAST connection (non-VPN), it just shuts down
and allows normal GPO processing to run the scripts.

o If it determines that no connection is available, then it goes
to sleep for one minute. At the end of the minute, it again
checks for access. If it finds access, then it does the things
noted above, otherwise it goes back to sleep for another
minute. It follows this process for up to one hour. At the
end of an hour, it just stops itself as a service (after all, we
don't want it to run forever).

Good luck!
 
Back
Top