Skip to main content

I just upgraded our JSS yesterday to v7 and have been having a few issues
with v7. I'm almost certain it's user error so I figured I'd ask the
experts.

Managed Preferences: I went through and made some quick managed preference
settings just to test this out. I did one that would put the dock on the
left so it would be obvious if it worked. I can't seem to figure out when
the clients will get this preference enforced though. I have set up a group
with my test device. Does the client get it when the enforce management
framework runs on the machine? I'm anxious to see it work locally on the
test machine.

OS X Disk: I'm very excited about the feature in v7 that allows you to
create the OS package in Casper Admin from the Install Disk. I took my Snow
Leopard DVD from WWDC and made a dmg in Disk Utility. Then I put the dmg
into Casper Admin and checked the box for 'This is a Mac OS X Install Disk'.
Then when I imaged the test machine, it reboots to Macintosh HD but goes
through the setup wizard. Is there an easy way to supress this setup? I'm
hoping to get away from having a 'gold master' hard drive to pull the base
OS package from so hopefully I can get a fresh OS X install from the disk
and have Casper Imaging add the management account and bind it to AD and
everything for me.

AD Bind: I've noticed that since upgrading to v7, my imaged test device
doesn't use my AD bind to get the device on our domain. In the netboot
image with Casper Imaging (v6) I don't see any available AD binds in the
Accounts tab. Is it possible that I need to rebuild my netboot image to
have Casper Imaging v7. I know I'll have to do this eventually but I'm not
sure if that's why it's not pulling any AD Bindings from the JSS.

Thanks,
John Moore | System Engineer ­ End User Computing | Cerner Corporation |
816.201.1564 | 816.651.7599 | john.l.moore at cerner.com |
http://www.cerner.com

----------------------------------------------------------------------

Managed Prefs - Yes, it's applied when you enforce the framework. Of course, depending on how you set up the preference, it may also require a login to apply it, so I'd recommend a reboot to apply everything. We enforce our framework on bootup anyways, so this covers everything.

OS X Disk - I'll have to check back in the office but make sure that you don't have the 'run setup assistant' box checked. The rest is up to how you set up your environment. I'm writing a script to remove some of the extranious apps for student and staff installs and make some settings happen, etc. I had done this in my 'base' images previously.

AD Bind - Given the significant overhaul in this area, I would expect that the v6 client wouldn't recognize the settings. You'll want to replace it in your set with a v7 client anyways to take advantage of the new partitioning, etc.

John

--
John Wetter
Technology Support Administrator
Educational Technology, Media & Information Services
Hopkins Public Schools
952-988-5373

I think I figured that issue out as well. I couldn't get the bind to show
up in Imaging 7 so I created a new one that was identical but a different
name. Sure enough, the new one showed up fine in all my Casper apps. It
must be something in upgrading from JSS 6 to JSS 7 that got lost in the
database.

If it is lost in the Db, be sure to let support know so they can track down the bug.

Thanks,
John

--
John Wetter
Technology Support Administrator
Educational Technology, Media & Information Services
Hopkins Public Schools
952-988-5373

Terms & ConditionsCookie settingsAccessibility statement