ConfigMgr Ticker App scheduled announcements not working as expected

James_Jankowski

Users of machines that are not logged in when a scheduled announcement becomes active, never get the announcement after they logon, even if the announcement has not expired.

User of machines that are not logged on when an immediate announcement is sent out do get the announcement when a user logs on if the announcement has not expired.  Seems like there is also a problem with scheduled announcements. 

Is this a known issue or documented somewhere that we might have missed?

We are running the latest ConfigMgr Ticker App on ConfigMgr 1706.

Any help would be greatly appreciated!

Matt_Medley

James_Jankowski said:

Users of machines that are not logged in when a scheduled announcement becomes active, never get the announcement after they logon, even if the announcement has not expired.

User of machines that are not logged on when an immediate announcement is sent out do get the announcement when a user logs on if the announcement has not expired.  Seems like there is also a problem with scheduled announcements. 

Is this a known issue or documented somewhere that we might have missed?

We are running the latest ConfigMgr Ticker App on ConfigMgr 1706.

Any help would be greatly appreciated!

Hey James, have you seen this Knowledge article? 

https://support.cireson.com/KnowledgeBase/View/1289#/

F_Christiansen

Hi James,

The Ticker announcement is stored in a WMI class and pushed down to clients as part of the policy.

When created from the Ticker Admin, a "Download Client Policy" request is pushed down to online clients while other clients will download the policy according to the Client Policy Polling Interval in your environment.
This is by default every 60 minutes. 
But as I recall, "Download Client Policy" requests on a collection will still be triggered on clients after logon, but keep in mind that the Notification Channel worker has a 10 minutes delay after the ConfigMgr Agent service start until it processes any request.

One more thing to be aware of is that the current Ticker is working with schedules based on the local time of the server, so if you have clients spread across time zones, announcements will not start simultaneously. 

Best regards
Flemming Appelon Christiansen

James_Jankowski

Thanks for the reply Flemming!  In our test environment where we have the ConfigMgr TickerApp installed, what we are seeing is none of our clients that are not logged on at the time of the scheduled announcement ever receive the announcement no matter when a users logs on or for how long they stay logged on (all of our clients are in the same time zone as our test SCCM 1710 server).  The only users to receive the announcement are the users that are logged on at the time of the scheduled announcement. 

I assume this is not expected behavior for the TickerApp for scheduled announcements?

SCCM seems to be functioning fine so I don't think its an issue with SCCM.