Casper Remote vs Policy deployment

[#1]

Hi all,

Got a laptop running 10.6.6 jamf version 7.21 …

I tried to Casper Remote a pkg and Remote fails at Authentication and pops into the Error Occurred.

I can ssh into the machine from Terminal and run jamf recon and reports back to the JSS without errors.
I can deploy a package with a Policy without errors.

Just Casper Remote bombs out. Even if I try to Update Inventory, bombs out… Nothing in the Jamf logs except:
Authenticating…
Authenticating…
Authenticating…

I have seen this before (laptops, desktops, 10.5, 10.6) and my work around is to create Policies for such instances just to get it going.

Anyone seen this behavior or can shed light some light my way where/what I should be looking for?

Thanks in advance!!

-P@

DISCLAIMER 19-1-2011 13:26:17

This communication is intended only for use by casper at list.jamfsoftware.com. It may contain confidential or privileged information. If you receive this communication unintentionally, please inform us immediately. Thank you. 180 has registered companies in the United States and in the Netherlands. 180 Los Angeles LLC . (180) 1733 Ocean Avenue, Suite 400, Santa Monica, California 90401, is registered with the trade register in the US in Delaware under file number 4260284 and the corporation's FEIN is 20-5982098. 180 Amsterdam BV (180) Herengracht 506, 1017 CB, Amsterdam is registered with the trade register in the Netherlands under number 34253037 and VAT number NL8161.54.673.B.01. The content of this communications is not legally binding unless confirmed by letter or telefax. Please note that 180 is neither liable for the proper transmission nor for the complete transmission of the information contained in this communication or for any delay in its receipt. Also please note that the confidentiality of email communication is not warranted. All services and other work provided by 180 are subject to our general conditions (supplier terms and conditions). The conditions are available for inspection at Herengracht 506, Amsterdam and at the Chamber of Commerce in Amsterdam. If you wish to receive a hard copy of these conditions, please send an e-mail with your address to info at 180amsterdam.com <mailto:info at 180amsterdam.com>

In the event you send to 180 any unsolicited ideas and/or materials (whether consisting of texts, images, sounds, software, information or otherwise) ("Materials") by e-mail or otherwise, 180 shall be entitled to use, copy and/or commercially exploit such Materials to the fullest extent, free of charge and 180 will not be bound by any confidentiality obligation in respect thereof.

[ernstcs]

My guess is that the actual management account information (username and
password) in the JSS itself does not match for some reason. Can you
manually edit that information for that computer in the JSS and then try
remote again after you refresh Casper Remote data, or quit and restart.

Craig E

[jarednichols]

Hi-

Our machines spin our Casper admin account password daily. Sometimes it
gets out of sync and we'll get these errors.

Remember that all machine-initiated sessions will be fine (except for Self
Service installs, though that could technically be called
"user-initiated"). So, we set up a policy (any,once per computer) that
will reset our admin account password to a new (strong) password. Tier 1
places a machine in the static group the policy is set to run on and often
will have the user logout/login (or just sit if that's a pain). The
machine will check back in, set its admin account password, and then Tier
1 can do service-initiated connections (e.g. Remote). The next time the
Enforce Management Framework hits the machine (every15,daily) it gets
re-spun to the random passwords we typically use.

j
-- Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

[stevewood]

2011/1/19 Nichols, Jared - 1170 - MITLL <jared.nichols at ll.mit.edu>

Hi- Our machines spin our Casper admin account password daily. Sometimes it gets out of sync and we'll get these errors. Remember that all machine-initiated sessions will be fine (except for Self Service installs, though that could technically be called "user-initiated"). So, we set up a policy (any,once per computer) that will reset our admin account password to a new (strong) password. Tier 1 places a machine in the static group the policy is set to run on and often will have the user logout/login (or just sit if that's a pain). The machine will check back in, set its admin account password, and then Tier 1 can do service-initiated connections (e.g. Remote). The next time the Enforce Management Framework hits the machine (every15,daily) it gets re-spun to the random passwords we typically use. j -- Jared F. Nichols Desktop Engineer, Client Services Information Services Department MIT Lincoln Laboratory 244 Wood Street Lexington, Massachusetts 02420 781.981.5436

Anytime I've had this happen I just run Recon against the single machine I'm
having problems with. That generally fixes it.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475