Q: Goodbye OS X Server- I tried, we tried.
Frustrated, not angry...
Well folks. I think this is goodbye to OS X Server - the server that I thought was much easier to use. I've followed instructions on this (https://discussions.apple.com/thread/5751873) forum and several others over the past 7 months. It's cost me so much time and headache.
- Migrating wikis from Mountain Lion Server to Mavericks server has yet to work
- Upgrading our Mountain Lion Server to Mavericks leaves us without wiki, calendar, and other services
- Apple support docs don't do the trick
- Phone calls with Apple support techs haven't provided any solutions and they really do try.
- Our current Mountain Lion Server suddenly lost all filesharing authentication capability and Apple enterprise solutions haven't been able to figure this one out.
- I'm stuck with a server with broken mountain lion server I have never been able to upgrade and/or migrate and ultimately would be left to copy/paste wikis to a fresh Mavericks server, export/import calendars from each client station, and contacts - I don't even know how that's going to work.
I believe in keeping IT folks employed, but...
The support from Apple seems so marginal (just for the server) and the plethora of problems with upgrading to Mavericks server and/or the manual fight to only potentially get it done seems very un-Apple like and just downright counter to what Apple represents.
So I'll think different...
Our server will be relegated to a client machine with simple file sharing. Perhaps We'll buy Daylite to assume some of the responsibilites. Truth is, even when things were working, it was always flaky in some way.
I really wanted to employ OS X Server in an efficient way, but it's been more trouble than I can accomodate.
Fortunately I am not an average client user nor a novice, so working in terminal is comfortable.
Perhaps in a few years or so, I'll reconsider, but my experience with OS X server on Mountain Lion and Mavericks has affected my trust.
Thanks for all of the help to those who provided instructions, workarounds, directions toward solutions, etc.
For those of you who had a successful migration - consider yourself lucky.
...by the way...after finishing the incredible instructions on this (https://discussions.apple.com/thread/5751873) page (and i sincerely mean that despite them not working for me) the result was a wiki page that looked like this
Caught exception "[<CSEntityPlaceholder 0x7fb2d15d5910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key externalID." [NSUnknownKeyException] executing route /app-context/wiki/:
(
0 CoreFoundation 0x00007fff8a0fe25c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff8da20e75 objc_exception_throw + 43
2 CSService 0x0000000104bc7957 -[CSLocalServiceProxy forwardInvocation:] + 1229
3 CoreFoundation 0x00007fff8a05c1c4 ___forwarding___ + 452
4 CoreFoundation 0x00007fff8a05bf78 _CF_forwarding_prep_0 + 120
5 CSService 0x0000000104bf9573 __27-[CSAppContextService init]_block_invoke240 + 180
6 CSService 0x0000000104bdf81a __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
7 CSService 0x0000000104be2d6c -[CSHTTPBackgroundResponse bounce:] + 286
8 Foundation 0x00007fff9073976b __NSThread__main__ + 1318
9 libsystem_pthread.dylib 0x00007fff8bc58899 _pthread_body + 138
10 libsystem_pthread.dylib 0x00007fff8bc5872a _pthread_struct_init + 0
11 libsystem_pthread.dylib 0x00007fff8bc5cfc9 thread_start + 13
)
Mac mini, OS X Server
Posted on May 9, 2014 8:07 PM