Highlighted
Absent Member.
Absent Member.
2538 views

Actiion "Prompt user" whne no user is logged creates error messages

Hello,

we are using ZCM 11.2.1MU1 and Windows 7 x64-Clients. I would like to
install a bundle with a "Prompt User"-action, because a process must be
stopped before installing the update. When the bundle runs on a
workstation where no user is logged in, the following error occurs:
"There is no user session available or user session cannot be determined."
I understand this message, because i cannot prompt a user when he isn't
logged in...
I found TID 7004828 which suggests to set a requirement like "Primary
user is logged in" or "Logged in to primary workstation" or run the
action as "System". But unfortunately we are using passive mode login
and the prompt action cannot run as System. So which requirement for the
prompt-action can be used to avoid this error?

Kind regards,
Thomas

Labels (2)
0 Likes
11 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Thomas Degenhardt;2258584 wrote:
Hello,

we are using ZCM 11.2.1MU1 and Windows 7 x64-Clients. I would like to
install a bundle with a "Prompt User"-action, because a process must be
stopped before installing the update. When the bundle runs on a
workstation where no user is logged in, the following error occurs:
"There is no user session available or user session cannot be determined."
I understand this message, because i cannot prompt a user when he isn't
logged in...
I found TID 7004828 which suggests to set a requirement like "Primary
user is logged in" or "Logged in to primary workstation" or run the
action as "System". But unfortunately we are using passive mode login
and the prompt action cannot run as System. So which requirement for the
prompt-action can be used to avoid this error?

Kind regards,
Thomas


Only thing I can think of off the top of my head:

Assign the bundle to the USER (not the device) and set to Launch on event: User Login
0 Likes
Highlighted
Absent Member.
Absent Member.

Am 19.04.2013 18:06, schrieb kjhurni:
>
> Only thing I can think of off the top of my head:
>
> Assign the bundle to the USER (not the device) and set to Launch on
> event: User Login
>
>


Unfortunately we are using passive mode login, so i cannot associate the
bundle to users.

Regards,
Thomas

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Thomas Degenhardt;2259219 wrote:
Am 19.04.2013 18:06, schrieb kjhurni:
>
> Only thing I can think of off the top of my head:
>
> Assign the bundle to the USER (not the device) and set to Launch on
> event: User Login
>
>


Unfortunately we are using passive mode login, so i cannot associate the
bundle to users.

Regards,
Thomas


I think you can assign to a device, on event user login as well.
0 Likes
Highlighted
Absent Member.
Absent Member.

Am 19.04.2013 22:26, schrieb kjhurni:
>
> I think you can assign to a device, on event user login as well.
>
>

Yes, you're right. But that's not my favourite solution. Using this
schedule the deployment works only when a user is logged in. IMHO the
deployment should work too, when nobody is logged in to the computer. In
this case the deployment works without interrupting the user in his
work. I'm searching for a requirement which lets the bundle deploy in
both cases.

Regards,
Thomas
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Thomas Degenhardt;2259263 wrote:
Am 19.04.2013 22:26, schrieb kjhurni:
>
> I think you can assign to a device, on event user login as well.
>
>

Yes, you're right. But that's not my favourite solution. Using this
schedule the deployment works only when a user is logged in. IMHO the
deployment should work too, when nobody is logged in to the computer. In
this case the deployment works without interrupting the user in his
work. I'm searching for a requirement which lets the bundle deploy in
both cases.

Regards,
Thomas


But if you want it to deploy when nobody is logged in, then why are you prompting the user at all?
0 Likes
Highlighted
Absent Member.
Absent Member.

Am 22.04.2013 16:06, schrieb kjhurni:
>
> But if you want it to deploy when nobody is logged in, then why are you
> prompting the user at all?
>
>

I would like to install the bundle in both cases, but prompt only when a
user is logged in. Thats imho the fastest way to deploy the bundle.

Regards,
Thomas
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Use a System Requirement on the Prompt Action that would only be valid
if a user is logged onto the PC such as "Username" <> "system"

You would need to fiddle around to find what worked for you.


On 4/17/2013 10:30 AM, Thomas Degenhardt wrote:
> Hello,
>
> we are using ZCM 11.2.1MU1 and Windows 7 x64-Clients. I would like to
> install a bundle with a "Prompt User"-action, because a process must be
> stopped before installing the update. When the bundle runs on a
> workstation where no user is logged in, the following error occurs:
> "There is no user session available or user session cannot be determined."
> I understand this message, because i cannot prompt a user when he isn't
> logged in...
> I found TID 7004828 which suggests to set a requirement like "Primary
> user is logged in" or "Logged in to primary workstation" or run the
> action as "System". But unfortunately we are using passive mode login
> and the prompt action cannot run as System. So which requirement for the
> prompt-action can be used to avoid this error?
>
> Kind regards,
> Thomas
>



--
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.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Highlighted
Absent Member.
Absent Member.

Am 23.04.2013 14:46, schrieb craig wilson:
> Use a System Requirement on the Prompt Action that would only be valid
> if a user is logged onto the PC such as "Username" <> "system"
>
> You would need to fiddle around to find what worked for you.
>
>



I tried to use the requirement "Environment variable value" with the
variable "username" "not equal to" "system" but i'm not sure if this
variable exists when nobody is logged in because it's a local variable.
I tested it and i'll get prompted when i login again and th ebundle
starts after the prompt. That should avoid the errors. I'll kep on testing.

Regards,
Thomas

0 Likes
Highlighted
Absent Member.
Absent Member.

> I tried to use the requirement "Environment variable value" with the
> variable "username" "not equal to" "system" but i'm not sure if this
> variable exists when nobody is logged in because it's a local variable.
> I tested it and i'll get prompted when i login again and th ebundle
> starts after the prompt. That should avoid the errors. I'll kep on testing.


This requirement does not help. I'm still getting the following error:

"[ERROR] [04/27/2013 09:30:16.502] [1408] [ZenworksWindowsService] [27]
[] [PromptAction] [ActionMan.UserSessionUnavailable] [Es ist keine
Benutzersitzung verfügbar bzw. die Benutzersitzung kann nicht ermittelt
werden.] [] [null]"
Any help would be appreciated.

Regards,
Thomas


0 Likes
Highlighted
Absent Member.
Absent Member.

Possibly the following late information might help somebody:

For actions "Prompt User" or "Display Message" I use a dedicated requirement: "Environment Variable Exists": "LOGONSERVER" "Yes"
So the message will only get displayed when a user is logged in. If no user it logged in (which means only SYSTEM user is logged in) that variable does not exist.


I might be wrong, but this requirement on "Reboot/Shutdown" die NOT work - but please test it I might be wrong.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

BachmannK;2393554 wrote:
Possibly the following late information might help somebody:

For actions "Prompt User" or "Display Message" I use a dedicated requirement: "Environment Variable Exists": "LOGONSERVER" "Yes"
So the message will only get displayed when a user is logged in. If no user it logged in (which means only SYSTEM user is logged in) that variable does not exist.


I might be wrong, but this requirement on "Reboot/Shutdown" die NOT work - but please test it I might be wrong.


What the action is should not matter, though there are some known issues especially with XP that reboots may not occur if nobody is logged on but the screen saver is active, depending on other OS settings.
The issue is not limited to ZENworks however.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
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.