Upgrading from 7.1 > 7.21

[donmontalvo]

OK, we finally increased RAM on our JSS box. Now we want to upgrade it from 7.1 to 7.21. I wanted to check to see if anyone ran into any show stopping glitches when they upgraded.

I know every environment is different...we reviewed KB 267 (*). Was looking for actual experiences, hoping to avoid shedding any blood. :)

(*) Should update this KB, was told earlier we can run multiple JSS instances in one environment (as a way to segregate JSS - where MySQL would be hosted on a dedicated box)...the KB seems to imply using more than one license is agin' da law.

Don

[talkingmoose]

JSS 7.21 requires an Intel processor.
On 5/25/10 4:52 PM, "Don Montalvo" <donmontalvo at gmail.com> wrote:

Other than that, it's working smoothly for me other than a new set of issues
that already have open tickets with JAMF. The big one for me is Snow Leopard
Macs not automatically logging in during imaging to install Adobe software.
Another is Casper Admin not utilizing Mac OS custom settings when compiling
configurations. These may have already been in 7.1.

The JSS itself runs fine and 7.21 has some nice new features.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[talkingmoose]

No, it's still an open issue. My understanding is that something changed
On 5/25/10 7:05 PM, "Dagel, Rich" <Rich.Dagel at landor.com> wrote:
between 10.5 and 10.6 to cause this behavior. I'm guessing a change in
security.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[donmontalvo]

OK, so the imager just logs in as the hidden-admin-user when the (just imaged) computer boots up. Then the Adobe install kicks in? Just wanted to clarify, so we don't deploy workstations that'll start installing Adobe Creative Suite when the first user logs in. :) If so, I think the imaging guys can handle that.

Thanks,
Don

[talkingmoose]

Doesn't matter who logs in first. Doesn't matter if the account is local to
On 5/26/10 2:15 PM, "Don Montalvo" <donmontalvo at gmail.com> wrote:
the machine or a directory account.

The first login triggers the Adobe install process.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[bentoms]

This has pretty severely hit our re-imaging..

Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

[donmontalvo]

Hmmm....we have a team of people imaging new computers, they use a configuration we created for them that includes installation of Adobe CS4 suite. Does this mean these guys would only need to manually log on to the Mac for the installers to kick in? Or do we need to tweak our configuration for them to continue to be able to image and deploy new Macs?

Thanks,
Don

[bentoms]

Does this mean these guys would only need to manually log on to the Mac for the installers to kick in?

-- Yes (if you're using an install customized from a retail dmg)... but I was contacted of list by a Jamf employee whom mentioned a simple option is to write a script to login on reboot as another account, this then kicks off the adobe install process.

Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

[donmontalvo]

Hi Ben,

Thanks for the feedback. William, have you tried this?

We're hot to move to 7.21 so we can leverage extension attributes, but can't unless we don't break critical functions along the way.

Don

[talkingmoose]

I've opted to put up with the extra step of logging in rather than build a
multi-GB package for a workaround.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[#11]

I've been running 7.21 since it came out, and I haven't experienced any
show-stoppers. The only real problems I recall dealing with have had to do
with my migrating to a cluster from a single server (which really didn't
cause any issues with the JSS itself), and with subsequently upgrading a
server from 10.5 to 10.6 (because of the Tomcat changes).

KB 267

I see what you're saying there...but I'm under the impression that the
licensing is actually client-based, i.e. number of seats managed, and so
running another server is permissible. Of course, IANAL nor a Jamf employee,
so YMMV.

-- Christopher Kemp
CNN Central Engineering

[donmontalvo]

Hi Chris,

Thanks for your feedback. I'm not sure what JAMF's position is for providing support for more than one JSS per environment.

Thanks,
Don

[bentoms]

I wouldn't mind knowing this.. AND how the licensing works if say, you have
a JSS internally & in a DMZ (read: external) with the same clients reporting
to both...

[#14]

My best suggestion, assuming you don't get an answer here on the list, is to
contact your rep & ask them. ;)

Christopher

[jarednichols]

I asked this question about a year ago when I stood up a test JSS. The
explanation I got is that you're licensed per client seats. So, let's say
you're licensed for 500 seats. If you have 475 in production and 25 in a
test JSS, you're good.

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