Jody,If you are using GMT for your advertisement, the system will use GMT as the time to wake up clients. This is an alternative you can use to schedule your recurring advertisements if you can get away with it... we can, for all systems are in the same time-zone; however, we still don't use GMT.IF your advertisements are using client-local-time, then you may want to check and see that their timezone offset is properly set according to their hardware inventory report. This is the value that is used by the server to send out wake-up packets to clients when the advert is not using GMT.a quick query in SQL will yield all of the different values you have for timezone offset. You can copy and paste the following into a report: select distinct timezoneoffset from v_gs_workstation_status Or, if you would like to see all of your systems AND their timezoneoffset: select sys.netbios_name0 , ws.timezoneoffset , ws.lasthwscan from v_r_system sys left join v_gs_workstation_status ws on ws.resourceID = sys.resourceID Also, if anyone is having issues with clients waking up and NOT running advertisements, feel free to contact me. We are about to deploy this hotfix as a solution to a similar problem, but not necessarily the problem described in the KB959257 article. PSS instructed us that there is more to the fix than listed in the KB article. nick