Win 10 Pro - LO Client Lampe nicht an

Probleme oder Fragen zum Lights-Out Add-In unter Windows Home Server 2011 und Windows Server 2012 Essentials werden hier beantwortet
Antworten
nsc2001
Foren-Einsteiger
Beiträge: 21
Registriert: 5. Nov 2012, 18:25

Win 10 Pro - LO Client Lampe nicht an

Beitrag von nsc2001 » 5. Aug 2016, 10:41

Hallo,

habe bei einem meiner Clients das Problem, dass der Zustand des Servers nicht erkannt wird. Bei allen anderen klappt es aber.

Server: Windows Server 2012 R2 Essentials
Client: Windows 10 Pro
Verbunden: Server <-> Switch <-> Client (alles über Lankabel)

Hier die LOGs von LightsOut:

LightsOutClientService.2016-08-05

Code: Alles auswählen

2016-08-05 10:08:49:248 [   4] DEBUG   RequestAdditionalTime
2016-08-05 10:08:49:263 [   4] DEBUG ** Initialized ResolveAssemblies, using product dir C:\Windows\system32\Essentials **
2016-08-05 10:08:49:263 [   4] DEBUG ============================
2016-08-05 10:08:49:263 [   4] DEBUG > OnStart
2016-08-05 10:08:49:310 [   4] DEBUG ============================
2016-08-05 10:08:49:310 [   4] DEBUG > ClientCore Ctor
2016-08-05 10:08:49:310 [   4] DEBUG LightsOutClient Version : 1.6.1.2408
2016-08-05 10:08:49:310 [   4] DEBUG .NET Framework Version  : 4.0.30319.42000
2016-08-05 10:08:49:310 [   4] DEBUG Running on machine/OS   : SCHLAFZIMMER Windows 10 [Professional], 10.0.10586.0, CPU x64, OS x64, Program x64
2016-08-05 10:08:49:310 [   4] DEBUG < ClientCore Ctor
2016-08-05 10:08:49:310 [   4] DEBUG ============================
2016-08-05 10:08:49:326 [   4] DEBUG > ClientCore OnStart
2016-08-05 10:08:49:326 [   4] DEBUG WindowsServerSolutionsEnvironment.Initialize()
2016-08-05 10:08:49:373 [   4] DEBUG > ConstructObjects
2016-08-05 10:08:49:419 [   4] DEBUG Found new R2 event log Microsoft-Windows-ServerEssentials/Admin
2016-08-05 10:08:49:435 [   4] DEBUG Initialized a check every 00:30:00 for Check for requests
2016-08-05 10:08:49:435 [   4] DEBUG Initialized a daily check at start-up and midnight for Daily logging
2016-08-05 10:08:49:435 [   4] DEBUG > ClientConfig ctor isVistaOrLater=True
2016-08-05 10:08:49:435 [   4] DEBUG Found 2012 R2 Backup task folder
2016-08-05 10:08:49:435 [   4] DEBUG Using task folder C:\Windows\system32\tasks\Microsoft\Windows\Windows Server Essentials
2016-08-05 10:08:49:763 [   4] DEBUG ReadNextBackupTimeFromTaskScheduler: Start changed from 01.01.0001 00:00:00 to 05.08.2016 13:11:00, Window end 14
2016-08-05 10:08:49:763 [   4] DEBUG ClientConfig: NextLocalBackupTime set to 05.08.2016 13:11:00
2016-08-05 10:08:49:826 [   4] DEBUG ReadMacAndSettings
2016-08-05 10:08:49:826 [   4] DEBUG ReadUserMac
2016-08-05 10:08:49:826 [   4] DEBUG < ClientConfig
2016-08-05 10:08:49:826 [   4] DEBUG ClientConfig: SendWakeup set to True
2016-08-05 10:08:49:841 [   4] DEBUG PipeServer: Listener started True
2016-08-05 10:08:49:841 [   4] DEBUG InitPipe: PipeTransmissionTimer started
2016-08-05 10:08:49:841 [   4] DEBUG ClientConfig: Interval set to 10
2016-08-05 10:08:50:029 [   4] DEBUG < ConstructObjects
2016-08-05 10:08:50:029 [   4] DEBUG starting Eventlog processing 2012...
2016-08-05 10:08:50:045 [   4] DEBUG Eventlog processing 2012 started
2016-08-05 10:08:50:123 [   4] DEBUG ==>> Start-up not for scheduled backup
2016-08-05 10:08:50:123 [   4] DEBUG < ClientCore OnStart, PipeTranmissionTimer started
2016-08-05 10:08:50:123 [   4] DEBUG < OnStart
2016-08-05 10:08:50:123 [   4] DEBUG ============================
2016-08-05 10:08:52:935 [   6] DEBUG >> Network address has changed
2016-08-05 10:08:53:154 [   6] DEBUG   IP-Address            : 192.168.20.22
2016-08-05 10:08:53:170 [   6] DEBUG PrepareWakeUp...
2016-08-05 10:08:53:201 [   6] DEBUG ClientConfig: Interval set to 1
2016-08-05 10:08:53:201 [   6] DEBUG Timer changed from 10 to 1
2016-08-05 10:08:53:232 [   6] DEBUG SERVER IS DOWN
2016-08-05 10:08:53:248 [   6] DEBUG ClientConfig: Interval set to 10
2016-08-05 10:08:53:264 [   6] DEBUG Timer changed from 1 to 10
2016-08-05 10:08:53:561 [   9] DEBUG >> Network address has changed
2016-08-05 10:08:53:732 [   9] DEBUG   IP-Address            : 192.168.20.22
2016-08-05 10:08:53:764 [   9] DEBUG PrepareWakeUp...
2016-08-05 10:08:53:779 [   9] DEBUG ClientConfig: Interval set to 1
2016-08-05 10:08:53:795 [   9] DEBUG Timer changed from 10 to 1
2016-08-05 10:08:53:811 [   9] DEBUG SERVER IS DOWN
2016-08-05 10:08:53:811 [   9] DEBUG ClientConfig: Interval set to 10
2016-08-05 10:08:53:826 [   9] DEBUG Timer changed from 1 to 10
2016-08-05 10:09:03:858 [   4] DEBUG PeriodicCheckTimerElapsed 10
2016-08-05 10:09:03:921 [   4] ERROR WoL - No MAC
2016-08-05 10:09:03:921 [   4] DEBUG ClientConfig: Interval set to 20
2016-08-05 10:09:03:999 [   4] DEBUG Creating new TransportClient
2016-08-05 10:09:03:999 [   4] DEBUG >> Creating new instance of TransportClient
2016-08-05 10:09:04:062 [   4] DEBUG ** Trying to resolve WssgCommon.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:04:062 [   4] WARN  ** Failed to resolve WssgCommon.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:04:077 [   4] DEBUG ** Trying to resolve WssgCommon.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:04:077 [   4] WARN  ** Failed to resolve WssgCommon.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:04:108 [   4] DEBUG << New instance of TransportClient created
2016-08-05 10:09:04:124 [   4] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:09:04:124 [   4] DEBUG Daily logging: Daily check triggered
2016-08-05 10:09:04:140 [   4] DEBUG Log cleanup ClientUpdate.*.log:-4
2016-08-05 10:09:04:140 [   4] DEBUG LogDelete finished
2016-08-05 10:09:04:140 [   4] DEBUG Log cleanup LightsOutClientGui.2*.log:-15
2016-08-05 10:09:04:155 [   4] DEBUG LogDelete finished
2016-08-05 10:09:04:155 [   4] DEBUG Log cleanup LightsOutClientService.2*.log:-14
2016-08-05 10:09:04:155 [   4] DEBUG LogDelete finished
2016-08-05 10:09:04:171 [   4] DEBUG Log cleanup LightsOutClient.Commandline.2*.log:-15
2016-08-05 10:09:04:171 [   4] DEBUG LogDelete finished
2016-08-05 10:09:04:187 [   4] DEBUG -----------------------
2016-08-05 10:09:04:187 [   4] DEBUG   LightsOutClientService: 1.6.1.2408
2016-08-05 10:09:04:202 [   4] DEBUG   .NET Framework Version: 4.0.30319.42000
2016-08-05 10:09:04:202 [   4] DEBUG   Running on machine    : SCHLAFZIMMER
2016-08-05 10:09:04:202 [   4] DEBUG   Operating System      : Windows 10 [Professional], 10.0.10586.0, CPU x64, OS x64, Program x64
2016-08-05 10:09:04:202 [   4] DEBUG -----------------------
2016-08-05 10:09:04:218 [   4] DEBUG   IP-Address            : 192.168.20.22
2016-08-05 10:09:04:233 [   4] DEBUG -----------------------
2016-08-05 10:09:04:233 [   4] DEBUG   Server is             : DOWN
2016-08-05 10:09:04:233 [   4] DEBUG   Joined to Server      : SERVER
2016-08-05 10:09:04:249 [   4] DEBUG   System                : 2011/2012
2016-08-05 10:09:04:249 [   4] DEBUG   Monitoring enabled    : False
2016-08-05 10:09:04:265 [   4] DEBUG   Action after Backup   : DoNothing
2016-08-05 10:09:04:265 [   4] DEBUG   Automatic wake-up     : True
2016-08-05 10:09:04:265 [   4] DEBUG   Allow server suspend  : False
2016-08-05 10:09:04:280 [   4] DEBUG   Server controlled     : False
2016-08-05 10:09:04:280 [   4] DEBUG   Domain Wake-On-Wan    : 
2016-08-05 10:09:04:280 [   4] DEBUG   Next backup time      : 05.08.2016 13:11:00
2016-08-05 10:09:04:296 [   4] DEBUG   Next Lights-Out backup: <not set>
2016-08-05 10:09:04:296 [   4] DEBUG   Backup window start   : 13
2016-08-05 10:09:04:296 [   4] DEBUG   Backup window end     : 14
2016-08-05 10:09:04:312 [   4] DEBUG   Lights-Out wake-up    : <not set>
2016-08-05 10:09:04:312 [   4] DEBUG   Server Sku            : WhsV1
2016-08-05 10:09:04:327 [   4] DEBUG   Suspend supported     : True
2016-08-05 10:09:04:327 [   4] DEBUG   Hibernation supported : True
2016-08-05 10:09:04:327 [   4] DEBUG -----------------------
2016-08-05 10:09:04:343 [   4] DEBUG Check for requests: Check every 00:30:00 triggered
2016-08-05 10:09:04:343 [   4] DEBUG ShowRequests
2016-08-05 10:09:04:358 [   4] DEBUG Starting to run async: powercfg.exe -requests with delay 0
2016-08-05 10:09:04:358 [   4] DEBUG Timer changed from 10 to 20
2016-08-05 10:09:04:374 [   3] DEBUG ******** start powercfg.exe -requests ********
2016-08-05 10:09:05:359 [  11] DEBUG SendTimerElapsed: not connected
2016-08-05 10:09:05:390 [  11] DEBUG ** Trying to resolve SkuResources.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:05:390 [  11] WARN  ** Failed to resolve SkuResources.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:05:405 [  11] DEBUG ** Trying to resolve SkuResources.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:05:405 [  11] WARN  ** Failed to resolve SkuResources.resources, Version=10.0.0.0, Culture=de-DE, PublicKeyToken=31bf3856ad364e35 **
2016-08-05 10:09:05:421 [  11] DEBUG ** DISPLAY:
2016-08-05 10:09:05:421 [  11] DEBUG ** Keine.
2016-08-05 10:09:05:437 [  11] DEBUG ** SYSTEM:
2016-08-05 10:09:05:437 [  11] DEBUG ** Keine.
2016-08-05 10:09:05:437 [  11] DEBUG ** AWAYMODE:
2016-08-05 10:09:05:452 [  11] DEBUG ** Keine.
2016-08-05 10:09:05:452 [  11] DEBUG ** AUSFšHRUNG:
2016-08-05 10:09:05:452 [  11] DEBUG ** Keine.
2016-08-05 10:09:05:468 [  11] DEBUG ** PERFBOOST:
2016-08-05 10:09:05:468 [  11] DEBUG ** [DRIVER] Legacykernelaufrufer
2016-08-05 10:09:05:468 [   3] DEBUG ******** finished powercfg.exe -requests ********
2016-08-05 10:09:09:812 [   5] DEBUG PipeServer.ListenForClients: Client has connected, handle 1032
2016-08-05 10:09:09:812 [   5] DEBUG Connect: 1 pipe client(s) connected to service
2016-08-05 10:09:11:375 [   4] DEBUG Received EnableAutoWakeup 1
2016-08-05 10:09:11:390 [   4] DEBUG   Saved mode = 1
2016-08-05 10:09:24:360 [  11] DEBUG PeriodicCheckTimerElapsed 20
2016-08-05 10:09:24:423 [  11] ERROR WoL - No MAC
2016-08-05 10:09:24:423 [  11] DEBUG ClientConfig: Interval set to 40
2016-08-05 10:09:24:454 [  11] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:09:24:470 [  11] DEBUG Timer changed from 20 to 40
2016-08-05 10:09:25:470 [  11] DEBUG SendTimerElapsed: not connected
2016-08-05 10:09:54:346 [   4] DEBUG GUI detected user activity at 05.08.2016 10:09:54
2016-08-05 10:10:04:482 [  11] DEBUG PeriodicCheckTimerElapsed 40
2016-08-05 10:10:04:531 [  11] ERROR WoL - No MAC
2016-08-05 10:10:04:531 [  11] DEBUG ClientConfig: Interval set to 80
2016-08-05 10:10:04:563 [  11] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:10:04:563 [  11] DEBUG Timer changed from 40 to 80
2016-08-05 10:10:05:577 [  11] DEBUG SendTimerElapsed: not connected
2016-08-05 10:11:24:580 [  18] DEBUG PeriodicCheckTimerElapsed 80
2016-08-05 10:11:24:629 [  18] ERROR WoL - No MAC
2016-08-05 10:11:24:629 [  18] DEBUG ClientConfig: Interval set to 160
2016-08-05 10:11:24:641 [  18] DEBUG ClientConfig: SendWakeup set to False
2016-08-05 10:11:24:671 [  18] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:11:24:671 [  18] DEBUG Timer changed from 80 to 160
2016-08-05 10:11:25:674 [  11] DEBUG SendTimerElapsed: not connected
2016-08-05 10:14:04:688 [  16] DEBUG PeriodicCheckTimerElapsed 160
2016-08-05 10:14:04:703 [  16] DEBUG ClientConfig: Interval set to 320
2016-08-05 10:14:04:763 [  16] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:14:04:763 [  16] DEBUG Timer changed from 160 to 320
2016-08-05 10:14:05:765 [  16] DEBUG SendTimerElapsed: not connected
2016-08-05 10:19:24:794 [  18] DEBUG PeriodicCheckTimerElapsed 320
2016-08-05 10:19:24:876 [  18] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:19:25:877 [  18] DEBUG SendTimerElapsed: not connected
2016-08-05 10:24:44:990 [  18] DEBUG PeriodicCheckTimerElapsed 320
2016-08-05 10:24:45:038 [  18] DEBUG Send next backup time triggered after ConnectTransport[code]
2016-08-05 10:24:46:050 [ 18] DEBUG SendTimerElapsed: not connected
2016-08-05 10:30:05:622 [ 11] DEBUG PeriodicCheckTimerElapsed 320
2016-08-05 10:30:05:686 [ 11] DEBUG Send next backup time triggered after ConnectTransport
2016-08-05 10:30:06:688 [ 27] DEBUG SendTimerElapsed: not connected
[/code]

LightsOutClientGui.2016-08-05

Code: Alles auswählen

2016-08-05 10:09:08:171 [   1] DEBUG 
2016-08-05 10:09:08:187 [   1] DEBUG Mutex created, running...
2016-08-05 10:09:08:328 [   1] DEBUG ============================
2016-08-05 10:09:08:343 [   1] DEBUG Lights-Out Client Gui 1.6.1.2408 started
2016-08-05 10:09:08:343 [   1] DEBUG Running on SCHLAFZIMMER Windows 10 [Professional], 10.0.10586.0, CPU x64, OS x64, Program x64
2016-08-05 10:09:08:359 [   1] DEBUG UI Culture de-DE
2016-08-05 10:09:08:359 [   1] DEBUG Culture de-DE
2016-08-05 10:09:08:359 [   1] DEBUG Time and Tz : 05.08.2016 10:09:08 Local, Mitteleuropäische Zeit, offset 02:00:00, 05.08.2016 08:09:08/05.08.2016 08:09:08
2016-08-05 10:09:08:374 [   1] DEBUG ============================
2016-08-05 10:09:09:281 [   1] DEBUG Using hybrid shutdown on Windows 8 and later
2016-08-05 10:09:09:281 [   1] DEBUG Using Windows 8 icon set with size 16
2016-08-05 10:09:09:296 [   1] DEBUG Ctor, set tooltip to: Lights-Out Client: Server ist im Standby oder Heruntergefahren
2016-08-05 10:09:09:312 [   1] DEBUG >> MainFormLoad
2016-08-05 10:09:09:640 [   1] DEBUG << MainFormLoad
2016-08-05 10:09:09:812 [   1] DEBUG PipeClient: Connected to server, receive thread started, handle 916
2016-08-05 10:09:09:812 [   3] DEBUG PipeClient: receive thread entering read loop
2016-08-05 10:09:09:812 [   1] DEBUG Service pipe connected
2016-08-05 10:09:09:828 [   1] DEBUG Context menu enabled, connect/verify timer changed to 30s
2016-08-05 10:09:11:375 [   1] DEBUG Automatic wake check state clicked
Habe den LightsOut Client schon mehrfach neu installiert.
Mit ein- und ausgeschalteter Firewall.

Habt ihr noch Ideen, woran es liegen könnte?

Danke und Gruß

NSC2001

Benutzeravatar
larry
Moderator
Beiträge: 9905
Registriert: 22. Dez 2007, 16:13

Re: Win 10 Pro - LO Client Lampe nicht an

Beitrag von larry » 5. Aug 2016, 11:24

Wird denn der Client im Server korrekt als online erkannt und kannst du am Client über das Lauchpad die Warnungen anzeigen lassen.

Gruß
Larry
Hauptserver: Intel I3-2100, MSI H67MA-E45, WHS 2011
System: Corsair Force GT 90GB - Datenplatten: 2*Seagate 3TB + ext. WD 500 GB für Serversicherung(nur System),8 GB Ram, Fractal Design R3, be quiet! L7-300W, 2*Digital Devices cineS2(Mediaportal)
Archivserver: Intel Cel.G530, Intel DB65AL, WHS 2011, Drivebender
System: SamsF4 320GB - Datenplatten: 5*2TB SamsF4. + VHD für Serversicherung(nur System), 4 GB Ram, Lancool K-11X, be quiet! L7-300W
Backupserver: AMD Athl. X2 4850e, Gigabyte GA-MA780G-UD3H, 3*Asrock SATA3 + 1* DeLOCK 70154 SATA Controller, WHS 2011, Drivebender
System: SamsF4 320 GB - Datenplatten: 15 diverse Platten + VHD für Serversicherung(nur System) ,4 GB Ram, Seasonic ss 330 Watt
Router: AVM FRITZ!Box 7270, Kabel Deutschland
Clients: 2* HTPC, Win7 HP 32 Bit - 2*Arbeitsrechner Win7 HP 64 Bit - 1*Laptop Win7 HP 32-Bit

nsc2001
Foren-Einsteiger
Beiträge: 21
Registriert: 5. Nov 2012, 18:25

Re: Win 10 Pro - LO Client Lampe nicht an

Beitrag von nsc2001 » 5. Aug 2016, 11:58

Launchpad.PNG
Launchpad.PNG (20.69 KiB) 3282 mal betrachtet
Wo finde ich denn die Warnungen?

Im Dashboard gibt es keine anstehenden Warnungen...
LightsOut.PNG
LightsOut.PNG (16.28 KiB) 3282 mal betrachtet
Und der Client wird als Online angezeigt...

Benutzeravatar
larry
Moderator
Beiträge: 9905
Registriert: 22. Dez 2007, 16:13

Re: Win 10 Pro - LO Client Lampe nicht an

Beitrag von larry » 5. Aug 2016, 13:46

Das passt so. Wenn der Client korrekt im Server als Online angezeigt wird, sollte die Kommunikation zwischen der ConnectorSoftware auf dem Client und dem Server passen.
Ich verschiebe es dann mal ins LightsOut Forum. Vielleicht kann hier Martin etwas anhand der LightsOut Logfiles sagen.
Hauptserver: Intel I3-2100, MSI H67MA-E45, WHS 2011
System: Corsair Force GT 90GB - Datenplatten: 2*Seagate 3TB + ext. WD 500 GB für Serversicherung(nur System),8 GB Ram, Fractal Design R3, be quiet! L7-300W, 2*Digital Devices cineS2(Mediaportal)
Archivserver: Intel Cel.G530, Intel DB65AL, WHS 2011, Drivebender
System: SamsF4 320GB - Datenplatten: 5*2TB SamsF4. + VHD für Serversicherung(nur System), 4 GB Ram, Lancool K-11X, be quiet! L7-300W
Backupserver: AMD Athl. X2 4850e, Gigabyte GA-MA780G-UD3H, 3*Asrock SATA3 + 1* DeLOCK 70154 SATA Controller, WHS 2011, Drivebender
System: SamsF4 320 GB - Datenplatten: 15 diverse Platten + VHD für Serversicherung(nur System) ,4 GB Ram, Seasonic ss 330 Watt
Router: AVM FRITZ!Box 7270, Kabel Deutschland
Clients: 2* HTPC, Win7 HP 32 Bit - 2*Arbeitsrechner Win7 HP 64 Bit - 1*Laptop Win7 HP 32-Bit

nsc2001
Foren-Einsteiger
Beiträge: 21
Registriert: 5. Nov 2012, 18:25

Re: Win 10 Pro - LO Client Lampe nicht an

Beitrag von nsc2001 » 12. Aug 2016, 08:42

Nachdem ich den PC auf Win10 Update 1607 hochgezogen habe und den Connector neu installiert habe, funktioniert auch LO wieder...

Antworten