Checkpoints

---

As we've seen, the process flows for package distribution and advertised programs are quite straightforward. Outside of normal network traffic issues that might interfere with the copying of source files to a distribution point or the copying of instruction files to a CAP or policy updates to a management point, not much can go wrong. The amount of network traffic generated by updating CAPs and management points with package and advertisement information is relatively small, as the files involved are generally no more than 1 KB to 2 KB in size.

The real traffic comes with the copying or refreshing of source files to the distribution points. Remember that distribution points receive their files in an uncompressed format. That 200 MB application is generating 200 MB worth of network traffic when the source files are copied to the distribution point, and this traffic increases proportionally to the number of distribution points you're targeting. Although you can schedule when the distribution points are refreshed, the initial copy will take place at the time you create the package and identify the distribution points.

Also, keep in mind that when a client accesses a distribution point to run a program, the installation might also generate a significant amount of traffic between the distribution point and the client. The more clients accessing the distribution point at the same time, the more traffic generated and the greater the performance hit taken by the distribution point. In general, if you're targeting large numbers of clients, you should consider distributing the package load across several distribution points, perhaps local to the clients in question.

This same issue of source file size is a reminder to be sure that the proposed distribution points have enough free disk space to host the source files. The client computer needs about 900 KB of space to install the Advertised Programs Client Agent and, of course, enough space to carry out the installation of the application. This concern is not true for the Advanced Client, however. Recall that when you install the Advanced Client software, all the client agents are installed, but not enabled, until you configure the agent at the site server.

If a program fails, start your troubleshooting with the status message system or the log files. Often, simply retracing your steps will be sufficient to spot the problem. Check the package and program parameters. Test the package yourself. Check the clients' system time to be sure that they're receiving the advertisements when you think they should. Check the Advertised Programs Client Agent polling cycle to be sure that the client agent is checking for new advertisements in a timely fashion. Check that the Legacy Client has a CAP available and the Advanced Client a management point. Remember, too, to monitor the Advanced Client download cache and modify it appropriately as well.

---