rgrundma Absent Member.
Absent Member.
1978 views

device shutdown no user logged in

I have been looking for the solution to what should be a simple procedure, but I have yet to find it.

Using ZCM11 on SLES server. I want to shutdown WinXP SP3 machines down at a set time each evening. I have tried a bundle with a Shutdown action. I have tried a bundle to launch the shutdown.exe /s command. My issue is that if a user is logged in, the machine will shutdown. If no user is logged in, the machine will sit until a user does log in, then the machine shuts down.

I tried enabling the CTRL-ALT-DEL policy, no go.

I really don't understand. Zen for Desktops 7 worked beautifully for this. What is different in ZCM11? Why does the logged-in or not logged-in user make any difference?

Can someone help?
Labels (2)
0 Likes
9 Replies
Knowledge Partner
Knowledge Partner

Re: device shutdown no user logged in

rgrundma;2135030 wrote:
I have been looking for the solution to what should be a simple procedure, but I have yet to find it.

Using ZCM11 on SLES server. I want to shutdown WinXP SP3 machines down at a set time each evening. I have tried a bundle with a Shutdown action. I have tried a bundle to launch the shutdown.exe /s command. My issue is that if a user is logged in, the machine will shutdown. If no user is logged in, the machine will sit until a user does log in, then the machine shuts down.

I tried enabling the CTRL-ALT-DEL policy, no go.

I really don't understand. Zen for Desktops 7 worked beautifully for this. What is different in ZCM11? Why does the logged-in or not logged-in user make any difference?

Can someone help?


And your bundle is assigned to device? Does the bundle launch as user or system or what?

Thomas
0 Likes
rgrundma Absent Member.
Absent Member.

Re: device shutdown no user logged in

thsundel;2135317 wrote:
And your bundle is assigned to device? Does the bundle launch as user or system or what?

Thomas


I assigned the bundle to a device group, consisting of 4 workstations. I don't know how to tell if a bundle launches as a user or system.

I did some further experimenting. I had 2 stations set to disable the CTRl-ALT-DEL policy. I read about this in other forum posts. 2 stations had the policy enabled. No users were logged in. The bundle kicked in before the screensavers could start, and all the machines shutdown!

It seems that the problem lies in the fact that no user is logged in and the screensaver has started. I suppose I could disable the screensaver, but we are trying to reduce energy costs as much as possible.

Any thoughts?
0 Likes
Knowledge Partner
Knowledge Partner

Re: device shutdown no user logged in

rgrundma;2135371 wrote:
I assigned the bundle to a device group, consisting of 4 workstations. I don't know how to tell if a bundle launches as a user or system.

I did some further experimenting. I had 2 stations set to disable the CTRl-ALT-DEL policy. I read about this in other forum posts. 2 stations had the policy enabled. No users were logged in. The bundle kicked in before the screensavers could start, and all the machines shutdown!

It seems that the problem lies in the fact that no user is logged in and the screensaver has started. I suppose I could disable the screensaver, but we are trying to reduce energy costs as much as possible.

Any thoughts?


This information might be of interest: Deployment will not reboot XP workstation at logon prompt if screensaver is running

Thomas
0 Likes
shaunpond Absent Member.
Absent Member.

Re: device shutdown no user logged in

Thsundel,

good TID, that one 🙂

--

Shaun Pond


0 Likes
Knowledge Partner
Knowledge Partner

Re: device shutdown no user logged in

Although one would think if that were the case, it would have affected ZFD as well and not just ZCM

In *my* experience, we have the same problem with ZFD/XP and of course, MS limits my choices as to how to fix it. (basically don't password-protect your computer if you're not there and don't do a CTRL-ALT-DEL which is how we display our security message).

ffffttt

on Microsoft, I say

Of course, when we get to Windows 7, we'll not have the ability to display the security message anymore via the Novell Client (at least not that I'm aware)

But maybe I'll win the lotto by then.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: device shutdown no user logged in

What I have found is the issue is really the ScreenSaver Settings for
the Not-Logged-On User. So your logged on users can have screen savers.
The Reg Below will clear out the settings for the Not-Logged-On Files.
In fact, I think that removing just the "ScreenSaverIsSecure" will
resolve the issue. Since there is not any password when nobody is
logged on, that key has no real function so removing just that is a good
place to start. If removing the one key is not enough, do both.


Windows Registry Editor Version 5.00
-------------------------------------
[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"SCRNSAVE.EXE"=-
"ScreenSaverIsSecure"=-



On 9/9/2011 3:16 PM, kjhurni wrote:
>
> Although one would think if that were the case, it would have affected
> ZFD as well and not just ZCM
>
> In *my* experience, we have the same problem with ZFD/XP and of course,
> MS limits my choices as to how to fix it. (basically don't
> password-protect your computer if you're not there and don't do a
> CTRL-ALT-DEL which is how we display our security message).
>
> ffffttt
>
> on Microsoft, I say
>
> Of course, when we get to Windows 7, we'll not have the ability to
> display the security message anymore via the Novell Client (at least not
> that I'm aware)
>
> But maybe I'll win the lotto by then.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
rgrundma Absent Member.
Absent Member.

Re: device shutdown no user logged in

craig_wilson;2136085 wrote:
What I have found is the issue is really the ScreenSaver Settings for
the Not-Logged-On User. So your logged on users can have screen savers.
The Reg Below will clear out the settings for the Not-Logged-On Files.
In fact, I think that removing just the "ScreenSaverIsSecure" will
resolve the issue. Since there is not any password when nobody is
logged on, that key has no real function so removing just that is a good
place to start. If removing the one key is not enough, do both.


Windows Registry Editor Version 5.00
-------------------------------------
[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"SCRNSAVE.EXE"=-
"ScreenSaverIsSecure"=-



This reg setting did the trick. Machines shut down with no problem. Thanks very much. One interesting occurrence, however. They all turned back on approximately 15 minutes later! I do have a Wake-On-LAN bundle for these machines, but it is set to distribute and launch at 7:00 AM, not the 4:00 PM time when machines shutdown.

Oh well, one issue at a time, I guess.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: device shutdown no user logged in

Good to hear.
Also let me clarify for some lurkers on the thread.

The Keys below do not impact any users who logon to the device nor does
it impact the profiles of newly created users. The portion of the
registry is used by Windows for the "User" when Nobody is logged onto
the PC. Settings value under \.DEFAULT\ is what is Windows uses while
sitting at the Ctrl-Alt-Del Screen.

To Modify Default Profile for new users, the User.DAT file needs to be
loaded and modified from the "default" user profile in the profiles
directory.

On 9/13/2011 8:26 AM, rgrundma wrote:
>
> craig_wilson;2136085 Wrote:
>> What I have found is the issue is really the ScreenSaver Settings for
>> the Not-Logged-On User. So your logged on users can have screen
>> savers.
>> The Reg Below will clear out the settings for the Not-Logged-On Files.
>> In fact, I think that removing just the "ScreenSaverIsSecure" will
>> resolve the issue. Since there is not any password when nobody is
>> logged on, that key has no real function so removing just that is a
>> good
>> place to start. If removing the one key is not enough, do both.
>>
>>
>> Windows Registry Editor Version 5.00
>> -------------------------------------
>> [HKEY_USERS\.DEFAULT\Control Panel\Desktop]
>> "SCRNSAVE.EXE"=-
>> "ScreenSaverIsSecure"=-
>>
>>
>>
>> This reg setting did the trick. Machines shut down with no problem.
>> Thanks very much. One interesting occurrence, however. They all turned
>> back on approximately 15 minutes later! I do have a Wake-On-LAN bundle
>> for these machines, but it is set to distribute and launch at 7:00 AM,
>> not the 4:00 PM time when machines shutdown.
>>
>> Oh well, one issue at a time, I guess.

>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
Knowledge Partner
Knowledge Partner

Re: device shutdown no user logged in

craig_wilson;2136085 wrote:
What I have found is the issue is really the ScreenSaver Settings for
the Not-Logged-On User. So your logged on users can have screen savers.
The Reg Below will clear out the settings for the Not-Logged-On Files.
In fact, I think that removing just the "ScreenSaverIsSecure" will
resolve the issue. Since there is not any password when nobody is
logged on, that key has no real function so removing just that is a good
place to start. If removing the one key is not enough, do both.


Windows Registry Editor Version 5.00
-------------------------------------
[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"SCRNSAVE.EXE"=-
"ScreenSaverIsSecure"=-



On 9/9/2011 3:16 PM, kjhurni wrote:
>
> Although one would think if that were the case, it would have affected
> ZFD as well and not just ZCM
>
> In *my* experience, we have the same problem with ZFD/XP and of course,
> MS limits my choices as to how to fix it. (basically don't
> password-protect your computer if you're not there and don't do a
> CTRL-ALT-DEL which is how we display our security message).
>
> ffffttt
>
> on Microsoft, I say
>
> Of course, when we get to Windows 7, we'll not have the ability to
> display the security message anymore via the Novell Client (at least not
> that I'm aware)
>
> But maybe I'll win the lotto by then.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


Thank you Craig, I will give it a try.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.