After the upgrade to Pulse 5.0R3.1 we are getting users who have to wait 5 to 30 minutes on the login screen after pressing Alt+Ctrl+Del.
In the logs we are finding the a hung of 'Juniper Unified Network Service'
Bron: Service Control Manager
Datum: 13-5-2014 13:32:49
De Juniper Unified Network Service-service is bij het starten vastgelopen.
Solved! Go to Solution.
We are working on a fix for the issue,opening a JTAC case if possible would be preferable for tracking purposes.
Yeah, I was bit by that also. Normally a service could be launched in a delayed fashion by having dependencies. Unfortunately, under XP/Server 2003, common dependencies (tcpip, Netman, etc.) don't make any difference. Under Windows Vista and above, you can try changing the service startup type to Automatic (Delayed Start) in the Services snap-in.
For XP/Server 2003, you will need to have some way to run the commands as administrator. Either have the user be part of the administrators group or use a 3rd-party program like SuRun and issue
net start "Juniper Unified Network Service"
as a login Startup command. The startup could be a simple batch file in %USERPROFILE%\Start Menu\Programs\Startup or in the registry. Give some time for your network stack to be available by using a sleep command prior to net start.... XP/Server 2003 doesn't have the sleep command, but you can install it from the Windows Server 2003 Resource Kit Tools.
To resolve this issue, perform the following actions:
1. Upgrade the Junos Pulse client to 5.0R6.
This fix does not apply if Search device DNS only is set in the VPN Tunneling Connection Profile.
This fix does not require an upgrade of the SA-Series or MAG-Series Operating System.
When will 5.0R6 be availible?
I have the same question. I don't see 5.0R6 available for download yet. It was supposed to be mid-August according to a JTAC case that I had open over a month ago (and that they made me close because they couldn't do anything until the new version came out)