Comments on: Juniper SSL VPN Secure Access 6.5R2 Available – Windows 7

By: Michael McNamara

Michael McNamara — Wed, 18 Aug 2010 16:55:09 +0000

Thanks for sharing that information!

By: Jascha

Jascha — Sat, 14 Aug 2010 09:21:45 +0000

Thank you both for your replies! I tried it and it doesn’t really care about any missing information.

By: Lord Edam

Lord Edam — Fri, 13 Aug 2010 18:08:15 +0000

it’s designed to go out effortlessly, so if you’re using central deployment (group policy etc.) it shouldn’t be a problem.

msiexec /i /qb junipersetupserviceinstaller.msi runs through the installation without input, provided it’s run with administrative credentials.

By: Michael McNamara

Michael McNamara — Thu, 12 Aug 2010 18:26:41 +0000

Hi Jascha,

Thankfully I don’t have to worry about packaging the client. I just let the client(s) automatically install whenever a user visits the Juniper SSL VPN Secure Access 4000 appliance.

You’ll need to repackage the MSI using an answer file or some other method. There are a number of ways to-do this but they revolve around how to automate a silent MSI install and not around the Juniper SSL VPN itself.

Good Luck!

By: Jascha

Jascha — Thu, 12 Aug 2010 16:47:39 +0000

Hi there,

I’m about to deploy the Juniper Installer Service ( 2.1.2.5973) as a base for the 6.5R3.1 NC on our clients using WPKG. I can easily make the msi available, but don’t know how to enter the required information (username/company) in silent mode.

Do you guys know, how to manage this?

Thanks in advance,
J

By: Mohammed Hughes

Mohammed Hughes — Wed, 28 Apr 2010 17:49:41 +0000

Internet Explorer 8 is very good because it is as stable as Opera. I hate the previous versions of IE like IE6 because it hangs frequently. `

By: Juniper Secure Access SSL VPN Software 6.5R2 is a winner | Michael McNamara

Juniper Secure Access SSL VPN Software 6.5R2 is a winner | Michael McNamara — Wed, 24 Feb 2010 04:44:17 +0000

[...] might recall that I wrote about software release 6.5R2 back in December 2009, detailing our troubles with the 6.5R1 software release and our hope that Juniper could save the [...]

By: DaveTheRave

DaveTheRave — Thu, 31 Dec 2009 09:10:27 +0000

I hear you on the hammering! It was a very disappointing release and one Juniper should get a hammering for. We use our appliances to create a split tunnel into our network for our laptop users. As the users have already logged on locally before they connect to the VPN we are using the NC to call a kix script. This script refreshes our ZenWorks application delivery window, map’s a bunch of drives, runs a couple of reg checks and copies a few small office templates. On previous releases of NC, if you had one small drop the whole script would run again. It looks like they have built tolerance into the software to stop this happening which is great. Keep us posted on how you get you.

By: Michael McNamara

Michael McNamara — Thu, 31 Dec 2009 05:44:17 +0000

Thanks for the feeback Dave. We literally got hammered by 6.5(R1). I was waiting until after the holidays to upgrade the system to 6.5R2. Although I do have a test system running 6.5R2 I have yet to really put it through it’s paces.

With respect to your comments about the NC script? What type of commands are you running in the script? Are you mapping drives, etc? Just curious.

Cheers!

By: DaveTheRave

DaveTheRave — Wed, 30 Dec 2009 14:20:17 +0000

6.5 for us was a dog… DNS issues, DHCP timeouts etc etc

Been running 6.5 R2 for a few weeks now and so far so good… Rock solid in fact. The fix for preventing the NC script to run each time the connection is dropped is most welcome!

Thumbs up