SolutionBase: Performing common administrative tasks with SMS 2003
Last screen
On this last screen before updates are downloaded (only the catalog was downloaded earlier), you can usually just take the defaults. The information on this screen defines a directory to which updates will be stored and sent to distribution points.
Each shot above corresponds to the bullet points below.
Each shot above corresponds to the bullet points below.
- After the updates are downloaded, you're provided with a summary window indicating whether updates are ready for use.
- After viewing the update summary, choose which distribution points should receive the updated package files. If you want to limit bandwidth, or update certain sites separately, this is a good way to accomplish these goals.
- Installation agent settings allow you to decide if you want to collect the client inventory immediately or create templates regarding system state. Further, you can opt to postpone system restarts so users are not adversely affected by updates.
- Also regarding the installation agent, you can tell SMS to perform an unattended installation of the updates and decide whether or not you want to notify users that an update is about to take place. In some situations, you can also allow the user to postpone the installation for a period of time.
- Finally, should this set of updates be advertised to a collection. This way, if you missed a client, you might be able to catch it during the next window. A patch won't be installed if a system doesn't need it.
