azuercher Absent Member.
Absent Member.
711 views

Win 10 OES client sleep disconnects

We are rolling out a new Win10 image based on build 1803. Client OES2SP4 IR10 is being installed post image. We have a power management policy that sleeps the PC after a period of unuse. The policy does not hibernate the PC. We are having problems where the sleep seems to break authentication with the server and when the machines wakes up the user cannot access their network drives or send iprint jobs without relogging or rebooting. Are there client or windows settings that I can tweak to resolve this problem?
Thanks,
Aaron
Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Win 10 OES client sleep disconnects

On 22-01-19 22:06, azuercher wrote:
>
> We are rolling out a new Win10 image based on build 1803. Client
> OES2SP4 IR10 is being installed post image. We have a power management
> policy that sleeps the PC after a period of unuse. The policy does not
> hibernate the PC. We are having problems where the sleep seems to
> break authentication with the server and when the machines wakes up the
> user cannot access their network drives or send iprint jobs without
> relogging or rebooting. Are there client or windows settings that I
> can tweak to resolve this problem?
> Thanks,
> Aaron
>
>


Take a lan trace on the pc and see if when you awake the pc if there's
any ncp traffic. Depening on that answer:

1. Watchdog can help. See tid 7004848

2. you may be seeing something similar to tid7015928

3. Do not shut down the net interface in your policy
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win 10 OES client sleep disconnects

On Wed, 23 Jan 2019 12:58:21 GMT, Mysterious <Mysterious@heaven.com>
wrote:

>On 22-01-19 22:06, azuercher wrote:
>>
>> We are rolling out a new Win10 image based on build 1803. Client
>> OES2SP4 IR10 is being installed post image. We have a power management
>> policy that sleeps the PC after a period of unuse. The policy does not
>> hibernate the PC. We are having problems where the sleep seems to
>> break authentication with the server and when the machines wakes up the
>> user cannot access their network drives or send iprint jobs without
>> relogging or rebooting. Are there client or windows settings that I
>> can tweak to resolve this problem?
>> Thanks,
>> Aaron
>>
>>

>
>Take a lan trace on the pc and see if when you awake the pc if there's
>any ncp traffic. Depening on that answer:
>
>1. Watchdog can help. See tid 7004848
>
>2. you may be seeing something similar to tid7015928
>
>3. Do not shut down the net interface in your policy


Mysterious' item 3 is probably the issue. We have found that MS likes
to put the NIC to sleep and that causes this issue.

--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
azuercher Absent Member.
Absent Member.

Re: Win 10 OES client sleep disconnects

Mysterious;2494178 wrote:
On 22-01-19 22:06, azuercher wrote:
>
> We are rolling out a new Win10 image based on build 1803. Client
> OES2SP4 IR10 is being installed post image. We have a power management
> policy that sleeps the PC after a period of unuse. The policy does not
> hibernate the PC. We are having problems where the sleep seems to
> break authentication with the server and when the machines wakes up the
> user cannot access their network drives or send iprint jobs without
> relogging or rebooting. Are there client or windows settings that I
> can tweak to resolve this problem?
> Thanks,
> Aaron
>
>


Take a lan trace on the pc and see if when you awake the pc if there's
any ncp traffic. Depening on that answer:

1. Watchdog can help. See tid 7004848

2. you may be seeing something similar to tid7015928

3. Do not shut down the net interface in your policy



I'm investigating these suggestions. Right now I am testing some OES client settings that were recommened. I am using a ZCM device power policy and I don't see any way to specify network states in that policy.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win 10 OES client sleep disconnects

On Wed, 23 Jan 2019 15:34:01 GMT, azuercher
<azuercher@no-mx.forums.microfocus.com> wrote:

>
>Mysterious;2494178 Wrote:
>> On 22-01-19 22:06, azuercher wrote:
>> >
>> > We are rolling out a new Win10 image based on build 1803. Client
>> > OES2SP4 IR10 is being installed post image. We have a power

>> management
>> > policy that sleeps the PC after a period of unuse. The policy does

>> not
>> > hibernate the PC. We are having problems where the sleep seems to
>> > break authentication with the server and when the machines wakes up

>> the
>> > user cannot access their network drives or send iprint jobs without
>> > relogging or rebooting. Are there client or windows settings that I
>> > can tweak to resolve this problem?
>> > Thanks,
>> > Aaron
>> >
>> >

>>
>> Take a lan trace on the pc and see if when you awake the pc if there's
>> any ncp traffic. Depening on that answer:
>>
>> 1. Watchdog can help. See tid 7004848
>>
>> 2. you may be seeing something similar to tid7015928
>>
>> 3. Do not shut down the net interface in your policy

>
>
>I'm investigating these suggestions. Right now I am testing some OES
>client settings that were recommened. I am using a ZCM device power
>policy and I don't see any way to specify network states in that policy.


It appears that Microsoft for some reason did not make it easy to
manage the NIC power settings. I looked for solutions for quite a
while. Ended up pushing a powershell script in a bundle. But if you
find a better method, please share it.

--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
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.