10.8.1 Server do NOT update

[spookfx]

HELP!!!!

Just updated a ML Server to 10.8.1 and now when I launch the server app I get
"Server requires OS X 10.8. The server you’re trying to connect to is not running OS X 10.8. Install OS X 10.8 on the server and try again."

Oh dear Apple... Are you sleeping?

https://discussions.apple.com/message/19360708#19360708

 

[spookfx]

Messy Hack

Ok a messy temporary solution, if you are stuck and need to get the server app running:

Open a terminal

cd /System/Library/CoreServices/
sudo vi SystemVersion.plist ( I hope you know how to use vi/vim )
replace 12B19 with 12A239 ....

You also need to change The Product Version from 10.8.1 to 10.8

so it looks like:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ProductBuildVersion</key>
<string>12B19</string>
<key>ProductCopyright</key>
<string>1983-2012 Apple Inc.</string>
<key>ProductName</key>
<string>Mac OS X</string>
<key>ProductUserVisibleVersion</key>
<string>10.8.1</string>
<key>ProductVersion</key>
<string>10.8</string>
</dict>
</plist>

**** Thanks to pjp_1976 for pointing out you only need to change one of the 10.8.1's to 10.8 *****

You might need to reboot for it to work....

I'm going to keep looking for a better (patch the server app) fix...

But good luck...

 

[mwhities]

Thanks for the post. I had considered it last night but, was to tired to mess with it.

 

[spookfx]

Server Version

I have also realised, that I was running an old Developer version of the ML Server app GM... V 2.0.21, this has issues...

If you update to the current version, V 2.0.23 it works with 10.8.1...

 

[XoticMike]

I have also realised, that I was running an old Developer version of the ML Server app GM... V 2.0.21, this has issues...

If you update to the current version, V 2.0.23 it works with 10.8.1...

How does one do this ?

 

[Les Kern]

Unrelated and could be considered a rant, but a lot of what I do is with about 20 OS X servers, most on 10.5 or 10.6. There was a time when they were seriously looking at the enterprise, and those servers were getting pretty sophisticated. Now I get the impression that the server coding team works out of a 1974 Chevy Vega in the back parking lot. We know now that their enterprise plans are off the table, concentrating on consumer and pro-sumer markets, and frankly, we all know that in a very short time the server sw they DO offer will be gone forever.
Better be ready for it.

 

[binaryspiral]

Unrelated and could be considered a rant, but a lot of what I do is with about 20 OS X servers, most on 10.5 or 10.6. There was a time when they were seriously looking at the enterprise, and those servers were getting pretty sophisticated. Now I get the impression that the server coding team works out of a 1974 Chevy Vega in the back parking lot. We know now that their enterprise plans are off the table, concentrating on consumer and pro-sumer markets, and frankly, we all know that in a very short time the server sw they DO offer will be gone forever.
Better be ready for it.

If this is true - they better take their code monkeys and throw them at Active Directory, Exchange, SharePoint, and DFS integration into OS X.

 

[MacsRgr8]

Come on guys, it seems pretty obvious that Apple has changed their game regarding to "server".
A Mac "server" is no longer a System Administrator's tool used only by the IT department which should only run on Server-class hardware.
Apple axed the Xserve a long time ago. OS X Server Lion is already more or less "a nice and easy server for the rest of us." OS X Mountain Lion had eliminated Server Admin.app (which wasn't default in Lion either...). The app "Server" in 10.8 doesn't even have a DHCP admin anymore.

OS X Server is cheap, easy and is made for "everyone".

If you really need a heavy-duty server with enterprise level of support, you won't use OS X Server. You cannot use OS X Server in combination with hardware which belongs in a 19" rack.

Apple makes sure that the end-user products they make connect perfectly well to the servers already used by the enterprise. That is a far, far better way for Apple to do their business than to try to be a competitor on the server market.
A shame for Apple ICT enthusiasts, but it seems the reality.

Here, take a look

 

[kingtj]

re: Purpose of OS X Server

Well, sort of... I'd honestly say the major reason for the existence of OS X Server today, though, is its usefulness in an environment full of iOS mobile devices. The MDM (mobile device manager) is very useful, even in very large businesses, so such things as mail server settings and wi-fi settings can be pushed to all the iPhones and iPads centrally (while preventing the users from making accidental changes to those settings on their devices).

Our company is getting ready to use this functionality so the wi-fi settings get auto updated when one of our employees visits one of our offices in different cities. Instead of them having to know the wi-fi password used at a particular office and manually joining the proper network the first time, the proper settings will be automatically pushed to the device as soon as they're on site and it will just connect up.

This type of functionality easily justifies the cost of a Mac Mini dedicated to running OS X Server at a location, just to handle the device management. But it's clearly something you don't need "serious rack mount hardware" to accomplish.

Come on guys, it seems pretty obvious that Apple has changed their game regarding to "server".
A Mac "server" is no longer a System Administrator's tool used only by the IT department which should only run on Server-class hardware.
Apple axed the Xserve a long time ago. OS X Server Lion is already more or less "a nice and easy server for the rest of us." OS X Mountain Lion had eliminated Server Admin.app (which wasn't default in Lion either...). The app "Server" in 10.8 doesn't even have a DHCP admin anymore.

OS X Server is cheap, easy and is made for "everyone".

If you really need a heavy-duty server with enterprise level of support, you won't use OS X Server. You cannot use OS X Server in combination with hardware which belongs in a 19" rack.

Apple makes sure that the end-user products they make connect perfectly well to the servers already used by the enterprise. That is a far, far better way for Apple to do their business than to try to be a competitor on the server market.
A shame for Apple ICT enthusiasts, but it seems the reality.

Here, take a look

 

[Mattie Num Nums]

Well, sort of... I'd honestly say the major reason for the existence of OS X Server today, though, is its usefulness in an environment full of iOS mobile devices. The MDM (mobile device manager) is very useful, even in very large businesses, so such things as mail server settings and wi-fi settings can be pushed to all the iPhones and iPads centrally (while preventing the users from making accidental changes to those settings on their devices).

Our company is getting ready to use this functionality so the wi-fi settings get auto updated when one of our employees visits one of our offices in different cities. Instead of them having to know the wi-fi password used at a particular office and manually joining the proper network the first time, the proper settings will be automatically pushed to the device as soon as they're on site and it will just connect up.

This type of functionality easily justifies the cost of a Mac Mini dedicated to running OS X Server at a location, just to handle the device management. But it's clearly something you don't need "serious rack mount hardware" to accomplish.

MDM is useless because users can un-enroll themselves at any time.

 

[SuperPuppy]

MDM is useless because users can un-enroll themselves at any time.

Hmm, I have never used OSX Server, however, in an Enterprise environment, I seriously doubt many would want users being able to un-enroll themselves.

The cost of standards is that its just that, its a standard, and in general for good reason, support overhead, etc.

Just my $.02

 

[Mattie Num Nums]

Hmm, I have never used OSX Server, however, in an Enterprise environment, I seriously doubt many would want users being able to un-enroll themselves.

The cost of standards is that its just that, its a standard, and in general for good reason, support overhead, etc.

Just my $.02

Its one of the downfalls of MDM. We used to use JAMF for our MDM solution but got sick of dealing with users un enrolling themselves. When I got my CMA certificate one of the caveats was Apple makes it so that the un enroll by user is enabled.

 

[kingtj]

re: useless

I agree that's not ideal, but I'd hardly call it useless?
If you deploy it as an aid to make life easier for users, vs. a security measure FORCING settings on people -- it makes perfect sense.

MDM is useless because users can un-enroll themselves at any time.