Reset Search
 

 

Article

KB44112 - Host Checker on Windows 10 Redstone 4 machines fails when the image is deployed using sysprep tool.

« Go Back

Information

 
Last Modified Date4/18/2019 9:08 AM
Synopsis
This article provides information on an issue that may impact Windows 10 Redstone 4 (1803) images deployed with sysprep and using Host Checker
Problem or Goal

This kb explains a potential issue with Windows 10 Redstone 4 (1803) images created using Microsoft built in Sysprep tool.                                                                                                                     
Windows 10 Redstone 4 (1803) is officially supported on the following Pulse versions:
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43655

This issue is reported on domain user accounts only. Admin accounts on the very same systems do not experience failure with Host Checker running and the VPN connects fine. Analysis of the affected devices logs show a privilege failure.

 
The error “ dsHostChecker.exe dsHostChecker p7704 t28D0 DspreauthCookieHelper.cpp:55 - 'SetDspreauthCookie' Error 0 writing cookie into the Windows store shows failure in writing the cookie into the Windows Store which usually happens due to permission issues.
 
This can be seen in client-side debug logs for process dsHostChecker.

Eg logs :

00159,09 2018/09/24 11:15:42.905 3 extksaj dsHostChecker.exe dsWinClient p10600 t28B8 dsThread.cpp:216 - 'DSThreadMonitor::release()' release thread 7109238, size = 1
00132,09 2018/09/24 11:15:42.906 3 extksaj dsHostChecker.exe dsWinClient p10600 t28B8 dsThread.cpp:225 - 'DSThreadMonitor::release()' ended
00218,09 2018/09/24 11:15:42.906 3 extksaj dsHostChecker.exe dsHostChecker p10600 t28B8 TnccLink.cpp:142 - 'NotifyConnectionChange' Host check finished, result for connection 0x1 on NAR 0xdd44e921, new state `Open': `Success'
00178,09 2018/09/24 11:15:42.907 1 extksaj dsHostChecker.exe dsHostChecker p10600 t28B8 Dspr
eauthCookieHelper.cpp:55 - 'SetDspreauthCookie' Error 0 writing cookie into the Windows store

 
Cause
Lack of user account permission to write cookies.
 
Solution
# Work around for fresh installation:
Install Pulse software into a Windows 10 1803 PC, then use SYSPREP to have it build an image, then install on the clients.
# Workaround for the user machine which are already affected by the problem:
Change the permissions on C:\USERS\<WDS account> to AUTHENTICATED USERS = FULL CONTROL. <WDS account> is whatever name you used to build the profile in before SYSPREPing it.


Note : Pulse Secure team is currently working to get a permanent fix on this. This kb will be updated with the latest findings on the issue.If you face similar issue please reach out to Pulse Secure Technical support team for any concerns.

 
Related Links
Attachment 1 
Created ByHarshdeep Singh

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255