Hibernate while not logged in

[Alfred]

I can't get Hibernator to function properly at the logon screen.
The logon screen saver is something else than the regular screen saver, and its parameters can be found in HK_USERS\.DEFAULT\Control Panel\Desktop.
Among others (like timeout), I changed the reg. value of SCRNSAVE.EXE from logon.scr to c:\windows\hibernator.scr, but after reboot, and after the screensaver timeout, hibernator seems to kick in and, unfortunately, out, back to the logon screen, starting the infinite loop again.

Is it possible to make Hibernator work without an already logged-on user?
Can someone confirm this behaviour?

[arkay]

I can't see why it would be kicking out again. It's just a screensaver. As long as it's called with a /s switch it whould work. Given that the other screensaver works this should be no problem.

The only thing I can think of is that the system doesn't grant access to the perfmon data until an authenticated user is logged in.

You should be able to tell by viewing the log c:\windows\hibernator.log.

It should mention errors like "Unable to connect to computer <XXXXX> to set up metrics"...

Take a look and we'll go from there..

I do have to ask though why you would have multiple user accounts on an MCE box and therefore require the login screen at all?

Cheers,
Arkay.

[Alfred]

Excuse me, I have this problem on a Windows Server 2003 SP1 standard edition which I would like to use as ftp and http server. I don't remember any strange entries in hibernator.log but I will look into it again. I wonder if someone can reproduce this behaviour. Sorry that I don't use MCE at this moment, but Hibernator seems like a true gem.

[arkay]

Alfred,

No problems.. I'm glad it's useful for more than just MCE machines That's partly why I did it this way.

It you can attach your log file I can take a look for you. It might give me some indications as to what isn't working.

Cheers,
Arkay.

[Alfred]

Enclosed are the .ini and .log files.
The kick-out of Hibernator back to the logon screen takes place after the countdown, at the moment it should have gone to hibernation.
However, the countdown seems to be missing in the log.
(the logged countdowns are with logged-on user)

I tried forced hibernation and the /s switch in the SCRSAVE.EXE registry value and in the ARGS==/s ini-entry, but that didn't help. Are you able to reproduce this with MCE?
Hibernation with logged-on user is no problem at all.

Regards,

Alfred

[arkay]

Ok.. Just tried this on my machine and it appears to be what I expected.

No Priviledge to run the PowerProf dll stuff to actually put it into standby or Hibernate.

Open to suggestion on how to fix that but at present I have no clue..

Here's the contents of my log... These values and the log itself were all written running it from the log-in screen.

Cheers,
Arkay.

(ADD COUNTER) Adding counter : Processor::% Processor Time::_Total.
Thu Feb 2 12:16:22 2006 : (ADD COUNTER) Adding counter : Network Interface::Bytes Total/sec::Intel[R] PRO_100 VE Network Connection - Packet Scheduler Miniport.
Thu Feb 2 12:16:22 2006 : (ADD COUNTER) Adding counter : Network Interface::Bytes Total/sec::MS TCP Loopback interface.
Thu Feb 2 12:16:22 2006 : (ADD COUNTER) Adding counter : LogicalDisk:isk Bytes/sec::_Total.
Thu Feb 2 12:16:23 2006 : (SCREENSAVER) Starting Screensaver C:\WINDOWS\system32\ssbezier.scr.
Thu Feb 2 12:16:24 2006 : ( HIBERNATOR) Timeout in 0030 seconds. CPU avg (0.0000%) DISK avg (1.4429 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:25 2006 : ( HIBERNATOR) Timeout in 0029 seconds. CPU avg (0.0000%) DISK avg (1.7440 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:26 2006 : ( HIBERNATOR) Timeout in 0028 seconds. CPU avg (0.0000%) DISK avg (83.1644 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:27 2006 : ( HIBERNATOR) Timeout in 0027 seconds. CPU avg (0.0000%) DISK avg (93.1547 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:28 2006 : ( HIBERNATOR) Timeout in 0026 seconds. CPU avg (0.0000%) DISK avg (93.4559 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:29 2006 : ( HIBERNATOR) Timeout in 0025 seconds. CPU avg (0.0000%) DISK avg (93.8072 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:30 2006 : ( HIBERNATOR) Timeout in 0024 seconds. CPU avg (0.0000%) DISK avg (94.1584 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:31 2006 : ( HIBERNATOR) Timeout in 0023 seconds. CPU avg (0.0000%) DISK avg (97.3224 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:32 2006 : ( HIBERNATOR) Timeout in 0022 seconds. CPU avg (0.0000%) DISK avg (97.6737 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:33 2006 : ( HIBERNATOR) Timeout in 0021 seconds. CPU avg (0.0000%) DISK avg (99.8321 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:34 2006 : ( HIBERNATOR) Timeout in 0020 seconds. CPU avg (0.0000%) DISK avg (99.6441 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:35 2006 : ( HIBERNATOR) Timeout in 0019 seconds. CPU avg (0.0000%) DISK avg (99.7445 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:36 2006 : ( HIBERNATOR) Timeout in 0018 seconds. CPU avg (0.0000%) DISK avg (21.5369 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:37 2006 : ( HIBERNATOR) Timeout in 0017 seconds. CPU avg (0.0000%) DISK avg (11.9982 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:38 2006 : ( HIBERNATOR) Timeout in 0016 seconds. CPU avg (0.0000%) DISK avg (11.7473 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:39 2006 : ( HIBERNATOR) Timeout in 0015 seconds. CPU avg (0.0000%) DISK avg (15.0605 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:40 2006 : ( HIBERNATOR) Timeout in 0014 seconds. CPU avg (0.0000%) DISK avg (15.1611 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:41 2006 : ( HIBERNATOR) Timeout in 0013 seconds. CPU avg (0.0000%) DISK avg (15.2600 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:42 2006 : ( HIBERNATOR) Timeout in 0012 seconds. CPU avg (0.0000%) DISK avg (15.6615 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:43 2006 : ( HIBERNATOR) Timeout in 0011 seconds. CPU avg (0.0000%) DISK avg (14.7078 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:44 2006 : ( HIBERNATOR) Timeout in 0010 seconds. CPU avg (0.0000%) DISK avg (17.4685 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:45 2006 : ( HIBERNATOR) Timeout in 0009 seconds. CPU avg (0.0000%) DISK avg (17.4687 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:46 2006 : ( HIBERNATOR) Timeout in 0008 seconds. CPU avg (0.0000%) DISK avg (16.8160 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:47 2006 : ( HIBERNATOR) Timeout in 0007 seconds. CPU avg (0.0000%) DISK avg (16.5149 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:48 2006 : ( HIBERNATOR) Timeout in 0006 seconds. CPU avg (0.0000%) DISK avg (16.6655 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:49 2006 : ( HIBERNATOR) Timeout in 0005 seconds. CPU avg (0.0000%) DISK avg (13.2017 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:50 2006 : ( HIBERNATOR) Timeout in 0004 seconds. CPU avg (0.0000%) DISK avg (12.9507 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:51 2006 : ( HIBERNATOR) Timeout in 0003 seconds. CPU avg (0.0000%) DISK avg (12.2979 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:52 2006 : ( HIBERNATOR) Timeout in 0002 seconds. CPU avg (0.0000%) DISK avg (11.7960 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:53 2006 : ( HIBERNATOR) Timeout in 0001 seconds. CPU avg (0.0000%) DISK avg (10.8423 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:54 2006 : ( HIBERNATOR) Timeout in 0000 seconds. CPU avg (0.0000%) DISK avg (7.0777 kb/sec) NET avg (0.0000 kb/sec).
Thu Feb 2 12:16:54 2006 : ( TIMEOUT) CPU (0.0000 < 8.000, DISK (7.0777 < 19.297), NET (0.0000 < 5.000).
Thu Feb 2 12:16:54 2006 : ( HIBERNATOR) Standby (No Force).
Thu Feb 2 12:16:54 2006 : ( TIMEOUT) Attempt to enter standby failed : Not all privileges referenced are assigned to the caller.

[arkay]

This is the closest information I can find. It will be something similar. Just need to find which service needs access granted to allow a call to the powerprof dll from the login screen.. Unfortunately I can't find an exact example:

The Windows Time service may generate event ID 7023 after you upgrade to Windows Server 2003 Service Pack 1

View products that this article applies to.
Article ID:892501Last Review:September 14, 2005Revision:4.0
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry

On This Page

SYMPTOMSCAUSERESOLUTION Method 1: Grant "Change the system time" permissions to the LocalService account Method 2: Change the logon account of the Windows Time serviceSTATUSAPPLIES TO
SYMPTOMS

After you upgrade a Microsoft Windows Server 2003-based domain controller to Windows Server 2003 Service Pack 1 (SP1), the Windows Time service may not start. In this scenario, the following events may be logged in the Windows System log:Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Description:
The Windows Time service terminated with the following error:
Not all privileges referenced are assigned to the caller.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 46
Description:
The time service encountered an error and was forced to shut down. The error was: 0x80070700: An attempt was made to logon, but the network logon service was not started.

CAUSE

This issue may occur if the Local Service account has not been granted "Change the system time" permissions. Windows Server 2003 SP1 changes the startup configuration of the Windows Time service from LocalSystem to LocalService. Therefore, the startup account that the Windows Time service uses must have "Change the system time" permissions.

By default, the LocalService account is not a member of the Administrators group and does not have "Change the system time" permissions. Therefore, the Windows Time service does not start, and event 7023 is logged in the System log.

RESOLUTION

To resolve this issue, use one of the following methods:•Grant "Change the system time" permissions to the LocalService account.•Change the Windows Time service to use an account that has "Change the system time" permissions.
Method 1: Grant "Change the system time" permissions to the LocalService account

To grant "Change the system time" permissions to the LocalService account, follow these steps on the domain controller that is experiencing this issue:1.Click Start, point to Administrative Tools, and then click Domain Controller Security Policy.2.Double-click Local Policies, and then click User Rights Assignment.3.In the results pane, double-click Change the system time.4.Click Add User or Group, type Service, and then click OK.5.Restart the server. The Service account and the affected Svchost process are currently in use and will not see the new user until you restart the server.6. Log on to the server. 7.Click Start, point to Administrative Tools, and then click Services. Check to see if the Windows Time service is started.
Method 2: Change the logon account of the Windows Time service

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To change the logon account of the Windows Time service, you must modify the registry to separate the Windows Time service from the main Svchost process. To do this, follow these steps:1.Search and locate the Svchost.exe file.2.Make a copy of the Svchost.exe file and call it “Svchost_w32time.exe”.3.Click Start, click Run, type regedit, and then click OK to start Registry Editor. 4.Locate and then right-click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time
5.Modify the ImageName key so that the value is %systemroot%\System32\svchost_w32time.exe -k LocalService. (The default value is %SystemRoot%\System32\svchost.exe -k netsvcs.)6.Quit Registry Editor.7.Click Start, point to Administrative Tools, and then click Services.8.Right-click Windows Time, and then click Properties.9.On the Log On tab, click This account.10.Type the name of a user account that has "Change the system time" permissions, or click Browse to select an account.11.Type the password of the new account in the Password and Confirm password boxes, and then click OK.12.Right-click Windows Time, and then click Start.If these methods do not resolve the issue, incorrect permissions that are applied to the Net Logon service or the Windows Time service from Group Policy may cause the issue. You can use the Resultant Set of Policy tool to verify the permissions, as follows:1.Click Start, click Run, type rsop.msc in the Open box, and then click OK.2.Expand the Computer Configuration\Windows Settings\Security Settings\System Services folder. 3.In the Service Name list, double-click Net Logon. 4.If the policy setting is defined in the template, the Edit Security button is available. Click Edit Security.

View the list of accounts to make sure that the list is correct. Make sure that the Local Service account has Full Control permissions.5.Repeat step 3 and step 4 for the Windows Time service.
Cheers,
Arkay.

[Alfred]

Arkay,

That's a nice KB article. Thanks for digging this up. I agree it should be something similar. Happy to see the issue is reproducable. I will look further in this direction. Pity that our wake/sleep rhythms are 12 hrs out of sync. ;-)
If I make progress I will let you know.
Thanks.

Alfred

[arkay]

Alfred,

Thanks. Be interesting to know how to get around it if anyone else want's the same results. I had a quick look through the permission granted to various services but nothing immediately stood out as the one you'd need to modify.

Good luck

Cheers,
Arkay.

[Alfred]

As a test, I copied cmd.exe to hack.scr and made it the logon screen saver by editing the registry and rebooting. After timeout, without logging on, a command window was opened. This window appeared to be running under the restricted "Local Service" account and context. In the window I was unable to rename Hibernator.scr and access Hibernator.log, which explains why there was no logging of Hibernator when used as logon screen saver. After adding Local Service to the Administrators group, and a reboot, the log was written and it gave the same error you mentioned, about not enough privileges. So:
- The logon screen saver runs in restricted "Local Service" context (at least on Windows 2003).
- The "screen saver while logged on" runs in the context of the user.
This might be a very hard nut to crack, hmm.

Alfred