on this page a try as a last resort.
Ahhh, I see. Tough spot to be in. Do you have a spare device to create your test build on even? The reason that caution is the best way, is because some people hit brick walls going from 10.8-10.9 - Mavericks has taken onboard driver signing more seriously, so shared printing might take a hit or need a review. The upgrade to SMB2 causes some problems for Windows devices if they look at the share, so consider that if you're having to dish out SMB to Windows users.
Cheers, I think I'll be going for the full fresh install of both server and clients - just to make a clean start! As long as the od/ad authentication and proxy authentication works (it does now, but with a login dialogue) then I'll be happy.
Just got to get a 10.9 installer on a usb pen now!
In my experience i went for a server upgrade from 10.7 to 10.9 and a started from scratch with a fresh install for the clients, although i now wish id have gone for a fresh install of both server and client. Too many niggles left with an upgrade.
I used this How to make a bootable Mavericks install drive | Macworld
and option 1.
Hope that helps, once id created one image i used DS to roll out.
Well - I finally got a 10.9 installer on a USB pen (using DiskmakerX) after several attempts. I've now got a nice clean client machine to image, but I see what you mean about 10.9 being a bit of a pain. Proxy authentication seems to be broken (constantly bringing up ntlm authentication for our smoothwall) and generally running very slow/timing out. I can't even access some smb shares (on 2008 server and also an old 2003 server) I'll do some more testing but if its going to be this bad then the next stage is to try 10.7, stick with 10.6.8 or even stick windows on them!
Sorry guys, too busy to read all the posts
@Sheridan I also have the same issues you describe, the most annoying one is, it will map those smb shares, but only after saying its been unsucessful, click ok to the error message, and then it maps. This is accessing shares on 2003 server
We'll only have the 2003 shares for a little while longer so thats not a major concern for us - the 2008 share issues and the proxy issues will be a deal breaker though!
And Auralia 4 and Musition 4 don't work either - this is pretty much going to kill off 10.9 here.
Last edited by Sheridan; 8th May 2014 at 01:10 PM.
Apart from the following as well...
Accessing home folders using the windows server smb protocol causes issues with permissions. This can lead to inaccessible data to the administrator on the server.
You can integrate a mavericks client fine, just any data created on a mavericks client or any data accessed on the windows server corrupts permissions.
Senior UK Engineers at Apple have said to me there is no fix in the pipeline for this issue.
Once you install and run Musition/Auralia, you should be prompted for activation and all that guff - it just bombs out saying it can't read the local database and that firebird.conf is missing. Usually I'd have to activate, then setup the connection to the database.
TBH - if the SMB thing is so dodgy I'm not keen on rolling this out now anyway!
I've decided to stick a new drive in the xserve and keep my old installation on the original drive as a fallback measure. Do the xserve (2009 era) take any sata drive, or do they have to be apple specific drives?
There are currently 1 users browsing this thread. (0 members and 1 guests)