We have a centralized location that connects our remote offices where 95% of our workstations reside. The MSIs are put on a share at this location. Most of our offices are connected via T1s. While it may take a few minutes for a package to be installed, it beats a tech having to visit each station. And, if your project allows, you can push the GPO to a few locations a day (or whatever schedule you choose) so as to not inundate the network at one time.
You would not want to push anything large, such as an MS Office package or a Windows service pack, this way though. Don Guyer Systems Engineer - Information Services Prudential, Fox & Roach/Trident Group 431 W. Lancaster Avenue Devon, PA 19333 Direct: (610) 993-3299 Fax: (610) 650-5306 [email protected] -----Original Message----- From: David W. McSpadden [mailto:[email protected]] Sent: Friday, October 16, 2009 9:45 AM To: NT System Admin Issues Subject: Re: Deploying things with Group Policy Ok that is a start. Now I have a WAN with 28 MPLS T1 LANs. Do I put the MSI package on the DC and have it pulled across the T1's or where does this mythical beast need to reside so as not choke my WAN?? -------------------------------------------------- From: "Ben Scott" <[email protected]> Sent: Friday, October 16, 2009 9:41 AM To: "NT System Admin Issues" <[email protected]> Subject: Re: Deploying things with Group Policy > On Fri, Oct 16, 2009 at 9:12 AM, David W. McSpadden <[email protected]> > wrote: >> I want to make sure everyone is on the same version of say UltraVNC. How >> do >> I set up Group Policy to deploy UltraVnc ... to every >> authenticated computer??? > > Is there an MSI package available to install UltraVNC? If so, then > create a GPO. Go to Computer Config -> Software Settings -> Software > Install -> right-click -> New -> Package. Pick the MSI file using a > UNC path that's available and readable by all machine accounts. The > next time they reboot, it should get installed. > > If there's no MSI, you have to either script something around the > SETUP.EXE-style installer and call the script as a Computer Startup > script, or build a .ZAP file. The .ZAP files are basically really > limited scripts, so I've never bothered. > >> ... with all my settings ... > > If you want settings via Group Policy, the program (UltraVNC) has to > expose those settings to Group Policy. That will mean it looks under > the various "Policies" subkeys in the registry, and honors settings > there. In other words, the program has to be written to support Group > Policy. The publisher will typically provide an .ADM or .ADMX file to > manage those GP settings. > > You can technically hack together an .ADM file that writes to other > areas of the registry, but then the changes won't be backed out when > the GPO no longer applies. (Sometimes called "tattooing the > registry".) > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
