Software Deployment

Are you using ConsoleOne? If you are trying to push the files to the local workstations, it doesn't take anymore bandwidth to install them as that portion happens locally. If you want to stagger them, create additional OUs and associate them separately or, you can associate your software to the users using several different NAL groups. Are you familiar with NAL (Novell Application Launcher)? We have around 4000 workstations and we do all installs, state-wide, using NALs and never have a bandwidth problem. I will say this depends on the size of your pipe to remote locations (if any). Of course, you need to know how to create the NAL objects and package or repackage the installations. In addition, each workstation will need a NAL client installed. We use WPS to create or repackage our MSIs for other software. We are about to install Office 07 using this method on all our workstations but, we did the same thing with all our software including Office 03. With Office 07, you should create a network admin install point and use Microsoft's customization tool to decide how/what will be installed and create a NAL for the distribution from that location. It is unessessary to copy all the installation files to each workstation without installing them. I will say this a a deep rabbit hole if your environment (e-directory) hasn't been set up yet or you are unfamiliar with Novell's ConsoleOne. How many workstations and different locations are you dealing with?
Good Luck,
Pat