Casper Imaging 8.62 connection timeout after Java update

It's a defect...the temporary fix is to use port 9006 in Casper Imaging until the defect is fixed.

I've got the imaging techs force quitting Casper Imaging once NetBooted, and then holding Option key to bring up the Casper Imaging address field window...hoping for a fix, if not I will have to update the NetBoot images so they point to the right URL...

Hope this helps anyone who has the same problem.

Don

http://server.domain.com:9006/ <-- Note trailing slash!

Here is the defect acknowledgement:

From: JAMF Support support@jamfsoftware.com Date: Thursday, December 6, 2012 5:11 PM To: Don Montalvo xxxxxx@xxxxxx.xxx Subject: Connection Timeout while Netbooted [ ref:_00D80cOw4._500C0NfwKF:ref ] Don, Thanks for your time on the phone today. I'm glad we were able to get things smoothed out this afternoon and get things up and running. The details involved with the Netboot unable to launching Casper Imaging are included with Defect# D-003000 which includes the following steps to replicate. -From the server that hosts the Netboot, you can luanch any Casper app and it connect fine with no error 28 -Tried using the HTTP address via Netboot Casper Imaging and everything worked fine. Also backed up the public cert and replaced with the built-in CA and the HTTPS address worked fine. -Only when using a third -party trusted cert would we receive this error on 3 separate cases. With our current version 8.62 we have not fixed the defect yet but made the error message more informational then the previous: ERROR 28 Regards, xxxxxx xxxxxx Account Manager JAMF Software General Support: (612) 216-1296 ref:_00D80cOw4._500C0NfwKF:ref

Don this is what I do. SuperDuper to another physical hard disk called OS BackUp. Do my update, if something screwed I just boot from OS Back up and clone it back again using Super Duper. Many times Apple sting us with updates that mess stuff up

Yep, unplanned update (we were in final stages of testing), we addressed the issue so it won't happen again.

We use RAID1 so we just need to snap the mirror, perform the update and restore the mirror (current or original state). We've been doing this for years on OS X and other *nix platforms. Easier, and doesn't require using extra drives or apps.