Search the Community

I am trying to set up a Windows 20012 Core server as Client running the WOL Proxy I have got it working on a different subnet using three Windows 7 computers and it works but when I install the Client on the server it loads the WOL proxy and it stays installed for about 2 hours then SCCM uninstalls it. Sample logs below any ideas why it would uninstall the Wol Proxy Sleep agent log ============ Start wakeup proxy service ============= SleepAgent 3/27/2014 2:45:31 PM 6 (0x0006) Initialize wakeup proxy service SleepAgent 3/27/2014 2:45:31 PM 6 (0x0006) Start to initialize all services SleepAgent 3/27/2014 2:45:41 PM 6 (0x0006) Processor Monitor INITIALIZED SleepAgent 3/27/2014 2:45:48 PM 6 (0x0006) Ping Service INITIALIZED SleepAgent 3/27/2014 2:45:48 PM 6 (0x0006) WOL Check: NeedWolTesting=False, WolSuspect=False SleepAgent 3/27/2014 2:45:48 PM 6 (0x0006) Create local machine instance SleepAgent 3/27/2014 2:45:48 PM 6 (0x0006) Detect and fill active IP/MAC addresses SleepAgent 3/27/2014 2:45:48 PM 6 (0x0006) SetWakeOnMagicPacketOnly: Setting Wake on Magic Packet only for all interfaces. SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) SetWakeOnMagicPacketOnly: Configuring adapter PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\FF5650000E57A6FE00_0 SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) EnableWakeOnMagicPacketOnly already true, no need to reconfigure SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Starting to determine the primary network adapter SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) .NET API reported "2" network interfaces. SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Examine adapter "Ethernet 3" SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) vmxnet3 Ethernet Adapter SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) DisableARPandNDOffload: PMARPOffload before: 0 SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) DisableARPandNDOffload: PMNDOffload before: 0 SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Examine adapter "Loopback Pseudo-Interface 1" SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Normal card in non Hyper-V environment: "Ethernet 3" SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) IP address is "205.121.139.9" SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Found a suitable network card at initialization SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) PowerPlatformRole: PlatformRoleDesktop SleepAgent 3/27/2014 2:45:49 PM 6 (0x0006) Scheduling roll call in 83650 seconds SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) State Manager INITIALIZED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Starting on UDP port 25536 SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Bind to local address "205.121.139.9" for message channel. SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Udp Service INITIALIZED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Register sleep event handler SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Registered for sleep events SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) WMI Event Prcessor INITIALIZED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Proxy Service INITIALIZED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Probe Manager INITIALIZED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Completed initialization SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Register network change handler SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Run the service SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Start all services SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Processor Monitor STARTED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Ping Service STARTED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Becoming a guardian ... SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Create Power Request: Your machine is currently acting as a network guardian SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Set Power Request SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) LastRollCallStart day: 1 (expected: 86) SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Cleared our list of machines. Reason: Missed roll call SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) State Manager STARTED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) Udp Service STARTED SleepAgent 3/27/2014 2:45:50 PM 6 (0x0006) WMI Event Prcessor STARTED SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) Start binding to a ssnps adapter. SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) #ParserCallback: StatusCode = 2197848070, Description = sparser.npb:001.000 Successfully unserialized NPL parser 'C:\Windows\CCM\NetMonParsers\Profiles\2D37DAAD-2AE1-42CF-B7CB-A4313A43F845\sparser.npb., MsgType = Information. SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) #Loaded Npl sets. SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) ssnps reported 2 adapters. SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) Successfully bound to a ssnps adapter 0 with the name "Ethernet 3" SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) End binding to a ssnps adapter. SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) Proxy Service STARTED SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) Probe Manager STARTED SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) All services STARTED SleepAgent 3/27/2014 2:45:51 PM 6 (0x0006) Stop requested SleepAgent 3/27/2014 2:48:43 PM 13 (0x000D) CCMExec.log Check and install Wakeup Proxy hotfix CcmExec 3/27/2014 3:15:46 PM 3872 (0x0F20) Retry Wakeup Proxy install/uninstall #1 CcmExec 3/27/2014 3:15:46 PM 3872 (0x0F20) Wakeup Proxy disabled, service installed -> Remove service CcmExec 3/27/2014 3:15:46 PM 3872 (0x0F20) CFirewallManager: Successfully deleted wake-up proxy firewall rule 'ConfigMgr Wake-up Proxy' CcmExec 3/27/2014 3:15:47 PM 3872 (0x0F20) Wakeup proxy service stopped successfully CcmExec 3/27/2014 3:16:02 PM 3872 (0x0F20) Uninstall wakeup proxy service "msiexec.exe /L* "C:\Windows\CCM\Logs\wakeprxy-uninstall.log" /quiet /uninstall {80E2D04F-30CE-47B7-8413-1EB00351B848}" CcmExec 3/27/2014 3:16:02 PM 3872 (0x0F20) Run command "C:\Windows\system32\msiexec.exe /L* "C:\Windows\CCM\Logs\wakeprxy-uninstall.log" /quiet /uninstall {80E2D04F-30CE-47B7-8413-1EB00351B848}" CcmExec 3/27/2014 3:16:02 PM 3872 (0x0F20) "C:\Windows\system32\msiexec.exe /L* "C:\Windows\CCM\Logs\wakeprxy-uninstall.log" /quiet /uninstall {80E2D04F-30CE-47B7-8413-1EB00351B848}" completed successfully CcmExec 3/27/2014 3:16:26 PM 3872 (0x0F20) Sending State Message with topic type = 2100, state id = 1, run state = 0, and error code = 0x00000000 CcmExec 3/27/2014 3:16:26 PM 3872 (0x0F20)