mmay1 Absent Member.
Absent Member.
1535 views

OES Client Login Script not Displaying, nor Fire Phasers

OES Client 2 SP4 IR11 for Windows
OES 2015 SP1
Windows 10 Pro, ver 1809
AMD Radeon R5 430 Dual Monitor video card
Dell OptiPlex 7050

New computer, right out of the box.
Installed OES Client.
Have never been able to get Login Script results window to display.
Nor have ever been able to get Fire Phasers sound to work.
Login Script does work as drives are mapped, etc.

Computer startup sequence:
Windows Lock screen
Notice to Users screen
Windows Login screen with OES Network login
Enter user name/password
Logs in to network
Local Windows user account is automatically displayed and logged in
Windows Desktop

Never see Login Script or hear phasers.
OES Client properties for Default System Login Profile on Script tab has all boxes checked.
Unchecking the Close Automatically does show the Login Script Results screen on a screen just before the Windows Desktop is displayed.
But this requires User interaction, i.e. click the Continue button to finish the login to the computer.
Previously the Login Script Results screen would be displayed, only for a short period of time, even when the Close Automatically box was checked.

PHASERS.WAV file is located in the C:\Windows\media directory.

I've done numerous searches on Internet and found nothing.

Thanks
Labels (1)
0 Likes
21 Replies
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

mmay wrote:

> Never see Login Script or hear phasers.


I haven't experienced this behaviour myself. Perhaps some additional
information will help with the diagnosis.

After you have logged on to Windows, can see your desktop, and things
have settled down, will the results window appear if you login (again)
from the icon in the systems tray?

If you pause the login script for perhaps 10 seconds, does that allow
sufficient time for the results window to appear?

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
mmay1 Absent Member.
Absent Member.

Re: OES Client Login Script not Displaying, nor Fire Phasers

After you have logged on to Windows, can see your desktop, and things
have settled down, will the results window appear if you login (again)
from the icon in the systems tray?

Yes, if login from icon in systems tray, the results window will appear.

If you pause the login script for perhaps 10 seconds, does that allow
sufficient time for the results window to appear?

I put the external command (#) and used the Windows "timeout" command at the end of the login script. I had to pause the script for 40 secs for the results window to appear.

It seems to me that on older versions of Windows that the OES Client was able to determine when the Windows login had finished and would display the results script. The OES Client doesn't seem to be able to do that on Windows 10.

Mike
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

mmay wrote:

> It seems to me that on older versions of Windows that the OES Client
> was able to determine when the Windows login had finished and would
> display the results script. The OES Client doesn't seem to be able to
> do that on Windows 10.


Hi Mike,

Thanks for that feedback.

There have been issues with Windows 10... 😉

It sounds to me as if the computer is just too busy during boot-up.
What kind of computer is it? What resources are available (memory,
processor, HD/SSD)?

Perhaps Alan will jump in with some other ideas...


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

Kevin Boyle wrote:

> It sounds to me as if the computer is just too busy during boot-up.
> What kind of computer is it? What resources are available (memory,
> processor, HD/SSD)?


Hi Mike,

I see from your original post your computer is an Dell OptiPlex 7050.

Assuming it has sufficient resources, check the Power Options in the
Control Panel. Set the power plan to High Performance then go into the
advanced settings and set everything to maximum and see if it makes any
difference. I have found that the Balanced plan severely restricts the
performance on my own system.

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
mmay1 Absent Member.
Absent Member.

Re: OES Client Login Script not Displaying, nor Fire Phasers

Dell OptiPlex 7050
CPU Intel i7, 3.5GHz
Memory 8GB, 2400MHz
Hard Drive 500GB, 7200rpm, SATA 6Gbps

The power plan was Dell, I changed it to High Performance and maximized for performance all the individual plan settings.
Restarted.
No joy. No script results window. No phasers sound.

Mike
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

mmay wrote:

>
> Dell OptiPlex 7050
> CPU Intel i7, 3.5GHz
> Memory 8GB, 2400MHz
> Hard Drive 500GB, 7200rpm, SATA 6Gbps
>
> The power plan was Dell, I changed it to High Performance and
> maximized for performance all the individual plan settings.
> Restarted.
> No joy. No script results window. No phasers sound.
>
> Mike


You get the result screen when you login to OES via the Client icon in
the system tray.

You get the result screen when you login to OES from the Windows login
screen but only if you delay the termination of the login script by 40
seconds.

That certainly appears to me that your system is resource constrained
during Windows login.

You have confirmed that the power plan is set to High Performance and
those settings are all maximised.

The specs you present above are more than adequate to achieve a speedy
login.



At this point I still have no idea why this is happening but we may be
able to isolate the problem by trying a few more things...

To see if this issue is related somehow the the user account, you can
setup a new user account and see if the issue remains.

Make sure you install the latest BIOS, firmware, and drivers from the
Dell site in case there are system issues they may resolve.

If you have a diagnostic program that came with your workstation you
should run it to verify there are no hardware issues.

Check the Windows event logs to see what errors or warnings are
reported.

You can run Wiershark on your OES server and compare the packet
captures obtained from the Windows login and the login from the Client.



Does your workstation use a wired or wireless network connection?

Is your workstation a member of a Workgroup or a Windows domain?

Do you have other Windows 10 systems that do not exhibit this
behaviour? If so, what is different with them?

Is there anything unusual about your login script? Complex? Lots of
drive mappings? etc.

Does the issue remain if you use a very simple login script that, for
example, maps a single OES drive?

Is the issue still present if you install an older OES Client?
- OES Client 2 SP4 IR10 for Windows
- OES Client 2 SP4 IR18 for Windows



I'm throwing out a lot of ideas here, hoping that some additional
details might emerge. Start with the ones you feel are the most
promising. With the information gathered, someone is bound to provide
some insight!

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: OES Client Login Script not Displaying, nor Fire Phasers

You might try using the Windows "Run logon scripts synchronously" policy. Enable this Windows policy in the Group Policy Editor (GPEDIT.MSC) under Computer Configuration > Administrative Templates > System > Scripts > Run logon scripts synchronously. Note the same policy is also available as a User Configuration policy.

Earle Wells
0 Likes
mmay1 Absent Member.
Absent Member.

Re: OES Client Login Script not Displaying, nor Fire Phasers

Kevin,
You get the result screen when you login to OES from the Windows login
screen but only if you delay the termination of the login script by 40
seconds.

The result screen is displayed after the Windows login screen and before the Windows desktop when login from OES client, but only if termination of script is delayed 40 sec. Always login from OES client, not just Windows client login. There is a cmd prompt window with the rest of the time left in the 40 sec. counting down and the results window. A 30 sec. delay was not enough, and there is usually about 8 sec. left of the 40 sec.

Does your workstation use a wired or wireless network connection?

Wired, Gigabit

Is your workstation a member of a Workgroup or a Windows domain?

Workgroup, "RATCHFORD", and checked, it is a member.

Do you have other Windows 10 systems that do not exhibit this
behaviour? If so, what is different with them?

Have three Dell OptiPlex 9020:
CPU: Intel i7, 3.6GHz
Memory: 8GB, 1600MHz
Hard Disk: 500GB, 7200rpm, SATA 6Gbps
These were Windows 8.1 Pro and recently upgraded to Windows 10 Pro, version 1809
Come to think of it, these problems were also there with Windows 8.1 Pro and they are still there with Windows 10 Pro.

Is there anything unusual about your login script? Complex? Lots of
drive mappings? etc.

Nothing unusual about login script. Not complex. 5 drive mappings and 2 search mappings.

Is the issue still present if you install an older OES Client?
- OES Client 2 SP4 IR10 for Windows
- OES Client 2 SP4 IR18 for Windows

When upgrading the 3 Dell OptiPlex 9020 from Windows 8.1 Pro to Windows 10 Pro, also upgraded the OES client from OES Client 2 SP4 IR7a to OES Client 2 SP4 IR11. The problem was there with the IR7a client on Windows 8.1 Pro.

I am not on site now, but will gather the rest of the information requested the next time that I'm on site.
Mike.
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

mmay wrote:

> I am not on site now, but will gather the rest of the information
> requested the next time that I'm on site.
> Mike.


From the information you just provided it would appear that this issue
is not confined to:
- a specific workstation
- a specific version of the OES client
- a specific version of Windows e.g. Windows 10

Do you know if the issue was present on any Windows 7 systems?

The only thing that stands out so far is that your workgroup name is
not the default name but that shouldn't be an issue.

I'm anxious to here what else you might learn when you are back on
sight.

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

Kevin Boyle wrote:

> I'm anxious to here what else you might learn when you are back on
> sight.


I'm anxious to hear what else you might learn when you are back on
site. 😉

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
mmay1 Absent Member.
Absent Member.

Re: OES Client Login Script not Displaying, nor Fire Phasers

Earle,

good to communicate with you again. This is actually Henry Lucius for Mike. You helped us with a previous OES Client problem.

In doing some Internet searching on these problems, I came across the Windows "Run logon scripts synchronously" policy somewhere. I tried it and it didn't have any affect.

In searching TID-7016351 History of Patches and Fixes for Novell/OES Client, I came across this:

Login script results window hangs or never displays with multiple monitor configuration. (Bug 815964)

I wonder if this bug or it's fix is somehow related? The 3 Dell OptiPlex 9020 have AMD Radeon R5 240 dual monitor card and the Dell OptiPlex 7050 has AMD Radeon R5 430 Dual monitor card.

Henry
0 Likes
mmay1 Absent Member.
Absent Member.

Re: OES Client Login Script not Displaying, nor Fire Phasers

KBOYLE;2495728 wrote:
mmay wrote:

> Do you know if the issue was present on any Windows 7 systems?



Don't have any Windows 7 systems. Only have/had Windows XP, then right to Windows 8.1, which are all now Windows 10.

Henry for Mike
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES Client Login Script not Displaying, nor Fire Phasers

mmay wrote:

> Login script results window hangs or never displays with multiple
> monitor configuration. (Bug 815964)



The fix for this bug was included in:
Novell Client 2 SP3 for Windows (IR10)


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: OES Client Login Script not Displaying, nor Fire Phasers

> It seems to me that on older versions of Windows that the OES Client was
> able to determine when the Windows login had finished and would display
> the results script. The OES Client doesn't seem to be able to do that on
> Windows 10.


I suspect that this is largely the right answer. But it's not that
the Client for Open Enterprise Sever "tries to determine when the
right time to display the window will be".

Both the eDirectory login script command line -- and any other login
script command line(s) returned by other installed network clients for
Windows -- are being executed at the time and choosing of Microsoft's
USERINIT.EXE process. When those command lines are executed, and what
desktop is currently visible when those command lines are executed, is
being controlled from outside of the login script process command
line(s) themselves.

We're displaying the window "every time we run", but that doesn't
necessarily mean the window is actually visible to the user sitting in
front of the computer, if Windows is intentionally still showing you
the welcome screen instead of processes on the user's desktop.

Your observation that "it seems different now" is something we've
observed too, and also discussed in the recent "Windows 10 - Login
Hang - Failed Drive Map Screen" thread
(https://forums.novell.com/showthread.php?t=510418).

That thread describes how "now when you pause the login script
results, it's pausing a results window at a time when the window
doesn't appear to be actually visible yet to the interactive user".
It's as though later versions of Windows 10 are trying to make the
login process "more silent" or "pretty" and are keeping the login
script command line(s) "hidden" under the welcome screen background.

I think the main thing "absent" is that when this window is "hidden",
the fire phasers isn't allowed to make foreground sounds either. As
you confirmed, the login script /is/ running, and the drives /are/
being mapped. It's just happening "in the background", kind of
"underneath" the Windows welcome screen.

I don't think there is any existing configuration tweak that will
"solve" that issue immediately. Something like "Run logon scripts
synchronously" could end up creating delays rather than solving the
display issue. e.g. If you set that policy, and then put a "Pause" in
the login script, you're now left waiting for 120+ seconds until
Windows decides to time out and switch from the welcome screen to the
user's desktop. (At least we've seen that in the lab here.)

That's a bug we're working on (Bug 1105790), but solving that bug
isn't going to "force Windows to switch away from showing the welcome
screen". It can only make it so that "Run logon scripts
synchronously" doesn't remain "stuck waiting" behind a "Pause" or
similar "wait for input to continue" condition at a time when the user
cannot actually see the login script results window.

We do in fact want to continue running the login scripts "as soon as
possible" rather than delaying, since we want to start before or as
soon as USERINIT.EXE starts invoking the shell process (which it does
immediately after the login script command line(s)). For the benefit
of those mapped drives needing to be available for Windows Explorer
"Run" and "RunOnce" registry commands, "Startup" folder commands, or
environment variables that are established by the login script, etc.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
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.