Reply to thread

Message

<blockquote data-quote="Luca Brasi" data-source="post: 878890" data-attributes="member: 60220">Hi again Michael,&nbsp;this is what my tests bred:- The inspecting client feature is no more preventing the standby, cool! But...- There are no more entries in the log for this[CODE]2012-07-01 13:55:14.377024 [PS StandbyWakeup(15)]: PS: Inspecting RemoteClient: [/CODE]It will always be empty, regardless of the client is running on local machine or on the remote client.But I will have this entry in powercfg /requests instead[ATTACH]106463[/ATTACH]This is new to me. Is this by design? Thought the concept would be that the client forwards his request to stay alive to tvservice.exe and this would appear in the requests?Now, what happens if no local client is running and the remote client isn't watching tv, just navigating through the menues. The server will go to sleep then?Hm, maybe that would be intended because it will wake up over wol as soon the tv is triggered on the remote client?</blockquote>

[QUOTE="Luca Brasi, post: 878890, member: 60220"] Hi again Michael, this is what my tests bred: - The inspecting client feature is no more preventing the standby, cool! But... - There are no more entries in the log for this [CODE]2012-07-01 13:55:14.377024 [PS StandbyWakeup(15)]: PS: Inspecting RemoteClient: [/CODE] It will always be empty, regardless of the client is running on local machine or on the remote client. But I will have this entry in powercfg /requests instead [ATTACH]106463[/ATTACH] This is new to me. Is this by design? Thought the concept would be that the client forwards his request to stay alive to tvservice.exe and this would appear in the requests? Now, what happens if no local client is running and the remote client isn't watching tv, just navigating through the menues. The server will go to sleep then? Hm, maybe that would be intended because it will wake up over wol as soon the tv is triggered on the remote client? [/QUOTE]

Verification