I had the same problem with 6.2r1 and 6.2r2. Still had the same problem. I opened a case with JTAC, but just did not have the time to go thru troubleshooting with them (would not have done any good, it had worked before going to 6.2!!!). I had hoped others had the same problem and Juniper would fix it. Right now, if I have to modify multiple mappings, I remove all the mapped roles, save it and then add back the desired role mappings. It's a pain but it works. Hope it is fixed soon! ... View more

Browser pass-through? Where? I went to USER>USER ROLES>(my role>WEB>OPTIONS>ADVANCED OPTIONS. There is not "Browser pass-through" option. I see "Rewrite File:// URL's" and other options. Am I looking in the correct place? SA2000 and SA4000 (normal and FIPS), firmware 6.2R1. Thanks Joe ... View more

Why do it that way? If it is a true Active/Passive cluster, you can upgrade the firmware without shutting down the passive node. You connect to the Web GUI (with the VIP IP). Make sure you make a local backup of your configuration (Maintenance > Archiving > Local Backups). Then start the firmware upgrade (Maintenance > System > Upgrade/Downgrade). The cool thing is that all connections will be switched to the Passive node while the Active node is upgraded. Once that is complete, the connections will be switched back to the Active node and the Passive node will be upgraded. You can upgrade the cluster while users are connected! We do this on our SA4000 Active/Passive cluster and have never had a problem! ... View more

We have been using this since firmware 5.0 (and currently firmware 6.1R2) and it works with OWA 2003. This SSO setup is based on using HTTPS (443), if you use HTTP (80) just modify the entries. We use LDAP-S to Active Directory, but it should work for normal AD authention. OWA.YOURCOMPANY.COM = the URL for your OWA server Create (or edit) your RESOURCE PROFILES > WEB Scroll down and enable AUTOPOLICY: SINGLE SIGN-ON. Select REMOTE SSO Select POST THE FOLLOWING DATA RESOURCE: https://OWA.YOURCOMPANY.COM:443/* POST URL: https://OWA.YOURCOMPANY.COM:443/EXCHWEB/BIN/AUTH/OWAAUTH.DLL In the box just below these settings, make these parameters: LABEL = destination, NAME= destination, Value = https://OWA.YOURCOMPANY.com/EXCHANGE, Not modifiable LABEL = SubmitCreds, NAME= SubmitCreds, Value = Logon+On, Not modifiable LABEL = Username, NAME= username, Value = <USERNAME>, Not modifiable LABLE = Password, NAME= password, Value = <PASSWORD>, Not modifiable SAVE CHANGES ... View more

Go to: SYSTEM > NETWORK > NETWORK CONNECT. Make sure that the IP address you entered for "Network Connect Server IP Address" is NOT your IVE's internal IP address. The IP address must be different. ... View more

No, there is only some basic mention of Secure Meeting, the scheduler and sign-in pages. Sorry! ... View more

JW: I use NC and had no problems with firmware 5.5R4. Today I upgraded to 6.0R3.1, so far (fingers crossed) no problems with NC or Citrix. I had installed 6.0R1 on my SA4000 cluster and had numerous problems with Citrix connections. I had to back out back to 5.5 and it wrecked my cluster. I was luck that one member was still in fair shape. I have noticed that reverting back to a full version (6 to 5) is a real pain and may cause problems. Be careful and good luck! ... View more

I had the same problem, many of the checks in ESAP are bad. I have had numerous support cases opened. To see what is going on, on the User Roles > (one of the roles > General > Session Options, scroll down and select "Enable Upload Logs". Now go to System > Configuration > Client Logs. Select "Host Checker". Try to client that is failing the AV checks. Now on that workstation in Window Explorer go to: Documents and Settings\(user name)\Application Data\Juniper Networks\EPCheck and open the logs EPCheck.log. Scroll down and find the AV that is failing, you will see some reasons (pattern too old, etc.) If is shows the name is not recognized as it should the check was not made correctly (Juniper programmers) and you need to open a support case. ESAP 1.3.2 is the newest and the best so far, but still fails to recognize many antivirus packages correctly, even though they are listed as supported. And forget about Microsoft Live OneCare, I opened a case at ver 1.6 and when they finally got a check fixed for it the verision jumped to 2.0! Good Luck (you will need it!) ... View more