JSS 8.6 upgrade from v8.43

[Cem]

I am about to update our JSS to 8.6 from version 8.43.
Clients are running MacOS X 10.7.x, 10.6.x and few 10.5.x
JSS is on Xserve running MacOS X Server 10.6.8. Are there any known issues that I need to know?
Thanks for looking!

[ernstcs]

If you're not needing 8.6 to start using Mountain Lion I'm not sure you really need to. I went from version 8.43 to 8.6, but I'm also not using a Mac server anymore, now on a Windows VM.

My main issue, still troubleshooting, has been the computers not being named at imaging for 10.8.

Although I'm not sure where this issue lies, I could possibly be doing certificates wrong, but had issues with clients talking back to the server after imaging.

Another issue cropped up late last week where one of my logout policies says it can't access the share anymore, although other logout policies are just fine. Will start troubleshooting that this morning. That was on multiple OS versions. Not sure if it's the JSS/binary or the new Windows server.

Those are what I'm aware of.

[Cem]

@ernstcs
The reason I am updating is to use the latest features. Like SCEP Configuration Profile has a Dynamic Challenge option etc...

Regards to the CasperShare access issue. Was the log saying cannot mount?

[jhalvorson]

1 week ago, I upgraded from 8.52 to 8.6 on an Xserve with 10.6.8. I haven't started any Mountain Lion support yet. A few of our imaged computers take on "No Name" and fails when bound to AD, but I think it is something the one of the configuration centers are doing. Either they are using really old version of Casper Imaging or they are disconnecting the network adapters.

I recommend taking a screen snap shot of your tomcat and mysql settings as shown in the JSSDatabaseUtil. (It's located in /Library/JSS/bin.) Once that util is open, under the Utilities menu, choose either "Change MySQL Settings..." or "Change Tomcat Setting...". After the upgrade from 8.52 to 8.6, I believe the Min Memory for Tomcat got reset to the default. Unfortunately I didn't take snap shot prior to the upgrade and had to set them based on my own faulty memory.

[ernstcs]

True, Cem, there were other features added. People use that stuff? =D

Yeah, it's saying: Error: Could not mount a distribution point.

The share is working just fine for everything else. I can start a new discussion perhaps.

[Cem]

I recommend taking a screen snap shot of your tomcat and mysql settings as shown in the JSSDatabaseUtil. (It's located in /Library/JSS/bin.) Once that util is open, under the Utilities menu, choose either "Change MySQL Settings..." or "Change Tomcat Setting...". After the upgrade from 8.52 to 8.6, I believe the Min Memory for Tomcat got reset to the default. Unfortunately I didn't take snap shot prior to the upgrade and had to set them based on my own faulty memory.

good tip :)
this may help too:
https://jamfnation.jamfsoftware.com/discussion.html?id=53

For TomCat; If you wanted to you can increase the memory allotment past the 8GB limit by manually editing the file /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist. In this file, you will see this line:

<string>-Xmx1024m</string> (this is set to 1GB maximum, your settings may differ)

If you wish to bump up the allotted memory, you can edit the amount specified in that line. For example, if you wanted to bump up the memory to 2GB, you would edit the line to read:

<string>-Xmx2048m</string>

After making the change, you will need to restart Tomcat for the changes to take effect by running the following command from Terminal on the server:

sudo jssutil rt

The Max PermGen size is used to store class definitions, and shouldn't need to be increased unless we are running multiple web applications or are using a large amount of custom reports. I believe the default values for these fields are:

Minimum PermGen Size: 64 MB
Maximum PermGen Size: 128 MB

[Cem]

Yeah, it's saying: Error: Could not mount a distribution point. The share is working just fine for everything else. I can start a new discussion perhaps.

Yeah I see this in my environment on random Macs and policies... perhaps its a new disscussion.