I found the scheduled task and it shows that 10 times on 3/14/26: User "NETWORK SERVICE" disabled Task Scheduler task "\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask"
Then today at 3:30AM: User "Domain\Server$" updated Task Scheduler task "\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask" User "NETWORK SERVICE" updated Task Scheduler task "\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask" It shows as to run every day at 3:24AM but the next run time is 5/13/16 3:24AM and the last time it was run was 11/10/2015 at 1:30PM. [cid:image005.jpg@01D1A77C.BEB1ED50] [cid:image006.jpg@01D1A77C.BEB1ED50] I changed the date back to 5/6/16. I will monitor this now and see what happens. Thanks Webster From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Christopher Baio Sent: Friday, May 6, 2016 8:59 AM To: ntsys...@lists.myitforum.com Subject: RE: [NTSysADM] KMS Question >From a support forum: These are events associated with SPPSVC service startup (event id 900) and shutdown (event id 903). The service is designed to shut down when nobody is using it. An application may call SL API, which will cause the service to wake up. Here is some additional information that may help to investigate anomalies in SPPSVC wakeup-shutdown pattern (notice that starting up because some other app calls SL API is not an anomaly). First of all, before the service shuts down, it updates a Windows Task Scheduler task under Microsoft/Windows/SoftwareProtectionPlatform. This task is scheduled to wake up SPPSVC approximately <renewal interval> minutes after a successful SPPSVC renewal (typically seven days later). You may want to look at this entry to verify that the next wake up time is consistent with your KMS renewal interval. Pay attention to the "Next Run Time" and "Last Run Time" fields. (This task schedule entry is hidden, so you need to enable viewing hidden tasks from the View menu in the Task Scheduler). Secondly, another potential reason for SPPSVC to keep waking up is another service: SPPUINOTIFY. This normally (when the system is in the licensed state) should run during KMS renewal and should shut itself down after the renewal has succeeded. If both of the above are right (that is the task scheduler task is scheduled outside of 2 hours and sppuinotify service is stopped), then there can be only an external reason for SPPSVC to wake up. -- Christopher Baio Desktop Support Technician CSDNET, Inc csdnet.net ________________________________ From: webs...@carlwebster.com<mailto:webs...@carlwebster.com> To: ntsys...@lists.myitforum.com<mailto:ntsys...@lists.myitforum.com> Subject: [NTSysADM] KMS Question Date: Fri, 6 May 2016 13:20:20 +0000 I am no KMS expert by any means and have only setup one KMS server 5 years ago for Citrix PVS and Office 2010. At current project, they are testing Office 2013 running on a XenApp 7.6 2012 R2 server. It appears, every third morning that the first user who launches Outlook takes 60 to 100 seconds for Outlook to become usable. Today it took 100 seconds. When I look in the Application event log, I can see event 4101 that says the Window license was validated followed by Event 1000 from Citrix saying the user's session is created and ready for use. I see an Event 45 for Outlook loading: Outlook loaded the following add-in(s): Name: Microsoft Exchange Add-in Description: Exchange support for Unified Messaging, e-mail permission rules, and calendar availability. Name: Online Meeting Add-in for Microsoft Lync 2010 Description: Online Meeting Add-in for Microsoft Lync 2010 Name: Microsoft Outlook Social Connector Description: Connects to social networking sites and provides people, activity, and status information. Name: Conversation History Add-in for Microsoft Lync 2010 Description: Conversation History Add-in for Microsoft Lync 2010 Name: CVArchiverAddin Description: Enables an email user to recover archived mail messages from an Outlook client. Name: Business Connectivity Services Add-In Description: This Add-in is used by Business Connectivity Services. After that event, I see event 900 The Software Protection service is starting. Followed by 27 various event from Office Software Protection Platform Service ending with The Software Protection service has completed licensing status check 70 seconds later. There are four of these events: The client has sent an activation request to the key management service machine. Why does this happen apparently every 72 hours and why on the first user who uses an Office program? This user only tests Outlook and Excel. Is it "normal" for it to take such a long time to validate the license/product? Any other info you need just ask. Thanks Webster
