Looks like there are a couple of unexpected changes on the latest release of Pulse. This biggest is that the user agent string changed. We use this string to determine what roles to offer. After the Pulse client upgrade our check of user agent string (Roles/General/Restrictions/Browser) does not match so upgraded users are not offered a Pulse compatible role. I have to step through each Pulse role and change the acceptable user agent strings and add these new values. (5 done - 61 to go). Looks like there is now a user license agreement that has to be accepted. Most users will figure out they need to accept to use the software. The log in screen now includes a window pane to log on to NetMeeting. We don't use this so I'm hoping this does not cause too many user complaints/questions. We use a single URL log in screen for many purposse and user must select a realm. The realm Pulse users have to select doesn't show up when selected, nor is it remembered in subsequent sessions. I think these are bugs that will need to be fixed. To select the correct realm the user must first select a different realm, then select the Pulse realm. This is going to cause user problems. ... View more

The version of ESAP is at the very bottom of the Endpoint Security page. ... View more

Not seeing any errors, but Juniper's published compatibility table indicates that the newest/current version of Pulse is not compatible with older Version 7 releases. We did have a problem when the latest version of Pulse came out. The user agent string for the iPad client was previously *JunosPulseiPhone* but changed to *JunosPulseiPad*. Bob D ... View more

After another test it has been determined that the router arp table has some NC IP pool addresses pointing to the NIC on the active box and some point to the NIC on the standby box. Since the arp table eventually times out, this would fix itself over time. Now we know to do a manual clear arp table in the router should there be a fail over for any reason. There might also be some problem with the active box not issuing arp or garp to set the table correctly. ... View more

I think we finally got this resolved. There were a number of quite large system snapshots that we deleted. I think most of these snapshots were taken automatically by the system when some unexpected event occurred so we where not aware of them and the disk space they were taking. the event/access/admin logs were not what was causing the problem. We will need to periodically check for the existence of unwanted snapshots and deleted them. Bob D ... View more

We started getting those messages earlier this year. Changed the interval to copy off access logs from once a day to every hour. Still get these error messages/traps at times. JTAC was not helpful in explaining why we get the messages or how to find how much disk space is being used and how much disk space remains available. ... View more

Thanks for the response. We've been using Web re-write and are contemplating the user community reaction if we start to change to WSAM/JSAM or Network Connect. Do you offer Web re-write access? Did you have to convert users to Network Connect from a different access product? Did you consider xSAM rather than Network Connect? I'm leaning towards xSAM because it seems more granular in that I can configure to tunnel only 80 and 443 from a specific application (common browsers). I don't want to run Network Connect without a split tunnel because who knows what else is running on their home PCs that I don't want top deal with. (file sharing, home banking, streaming, etc).. Some secure destinations might also get cranky if they see a user arriving from an unexpected IP address (investment Web sites want extra authentication if they see a connection from a different IP). ... View more

We are using multiple OR checks for each version of Windows 7 Key/Subkey: SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName String; Windows 7 Enterprise and so on for the different version. Not very elegant but it works for now. Bob D ... View more

We use HC to make sure users have a current version of Windows so we are using registry checks for the different versions of Windows 7 - Key/Subkey: SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName String; Windows 7 Enterprise and so on for the different versions of Windows 7. Am looking forward to V6.5R2 that, I am told, will have the Juniper pre-defined option for Windows 7. Bob D ... View more