Mandatory advertisements that have a recurrence pattern run one hour late in Systems Management Server 2003

After you create a mandatory program advertisement in Microsoft Systems Management Server (SMS) 2003 and set a recurrence pattern for the advertisement, the advertisement runs one hour late.

This problem occurs when the following are true:

• Your SMS 2003 site server and client computers are in a time zone where daylight-saving time applies.
• You schedule the advertisement before daylight-saving time is in effect.
• A client runs the mandatory program after daylight-saving time is in effect.

To resolve this problem, obtain the latest service pack for Systems Management Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Note This problem is not fixed in a hotfix.

To work around this issue, modify the schedule for the advertisement so that the advertisement runs at the expected time. To do this, follow these steps:

1. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
2. Expand Site Database (SiteCode - SiteName), and then click Advertisements.
3. In the details pane, right-click the advertisement that you want to modify, and then click Properties.
4. On the Schedule tab, double-click the mandatory assignment that is running late.
5. In the Assignment Schedule dialog box, click Schedule.
6. In the Time box, type a start time that is one hour earlier, and then click OK three times.

Note If the advertisement does not expire before daylight-saving time is no longer in effect, follow similar steps at that time so that the advertisement continues to run at the expected time.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Systems Management Server 2003 Service Pack 2.

For more information about advertising programs to clients, click the following article numbers to view the articles in the Microsoft Knowledge Base: