Upgrade from 10.6.8 to 10.9

[Sheridan]

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.

Edited May 8, 2014 by Sheridan

[Brimstone]

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.

 

 

 

[Arthur]

the proxy issues will be a deal breaker though!

Our Macs authenticate to our Smoothwall proxy via Kerberos. We don't get any username & password popups any more.

 

And Auralia 4 and Musition 4 don't work either - this is pretty much going to kill off 10.9 here.

10.9 is listed as a supported OS for both apps? In what way do they not work?

 

• www.risingsoftware.com/auralia/system_requirements.php
  
• www.risingsoftware.com/musition/system_requirements.php
  

[Sheridan]

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!

[Sheridan]

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?

[Arthur]

Do the xserve (2009 era) take any sata drive, or do they have to be apple specific drives?

http://groups.google.com/forum/#!topic/macenterprise/w9mXSRhec1Q

[Sheridan]

Looks like a WD 250GB drive will probably work - only one way to find out!

[Arthur]

if the SMB thing is so dodgy I'm not keen on rolling this out now anyway!

The post below might be of interest.

 

www.edugeek.net/forums/mac/125854-os-x-mavericks-released-s-free-3.html#post1172067

[Brimstone]

The post below might be of interest.

 

www.edugeek.net/forums/mac/125854-os-x-mavericks-released-s-free-3.html#post1172067

 

Mac OS X 10.9.3 Client actually makes SMB connectivity to an AD Server worse!

[Sheridan]

This isn't looking very promising, I might be better off sticking with 10.6.8 at this rate.

[Arthur]

Mac OS X 10.9.3 Client actually makes SMB connectivity to an AD Server worse!

Worse in what way? Is it worth staying on 10.9.2?

[Mikee_Amsys]

Did you get my PM about some tweaks for SMB Sheridan?

 

Eseentially, Mavericks is SMB2, but laughably, XP, W7 and W8 have different troubles connecting to it. The most common problem is the protocol for connecting, or the number of times connecting. (rejecting the credentials, then accepting them the 2nd time around)

 

Most commonly, checking the log you'll see the username has included the domain as well (ex. 'domainname\username')

 

Here's the notes I've compiled to help me out so far:

 

XP Fix:

 

Here's the value we have the HKEYLOCALMACHINE\System\CurrentControlSet\Control\Lsa\LMCompatibilityLevel

set to:

Windows XP set to: 3

Windows Vista and Windows 7 set to: 1

 

Windows 7 Fix:

 

1. Enter “gpedit.msc” in the Start Search box.

 

2. Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.

 

3. In the right pane, enable the following policies:

 

Manager Authentication Level to "Send NTLMv2 response only"

 

WE MAY NEED TO UNDO THIS the previous setting is:

 

Send LM & NTLM - use NTLMv2 session security if negotiated

 

Mavericks Fix:

 

Force your Mavericks Mac to use SMB instead of SMB2.

 

To do this you'll need tocreate a nsmb.conf file in your home directory with the path ~/Library/Preferences/nsmb.conf.

 

There are several ways to do this. First, you can up a terminal from Utilities and paste in the following line from the shell prompt:

 

echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

 

The above must be entered as a single line with a return at the end. You can also create this configuration file with a text editor such as vi from the terminal. Do not, however, try to create this file with a word processor. You'll end up with formatting characters in the file that will ruin it for configuration purposes.

 

 

You can also try forcing Mavericks to use the older SMB variant,Common Internet File System (CIFS). To do this,simply edit your server connection URL so that it uses CIFS. Use the Finder to choose the "Go" menu and select "Connect to Server..." (or just use command-K) and type "cifs://YourServerName" and hit Return; the server should mount. If it doesn't, try entering the share's designation as well, e.g. "cifs://YourServerName/YourDriveName."

 

[Sheridan]

I did get your pm, sorry I haven't replied yet as I've been a bit distracted the last few days.

 

I'm in two minds about whether to stick with 10.6 or move to 10.9 now. Difficult to test unless I take a couple of Macs offline to set up a mini test environment.