[jnelson]

Here is a visual update:

So this is what the user’s home folders permissions look like. This is home the foreced local home directory is created. The user’s name is ‘testuser’ and the domain is ‘XXXX’ where ‘XXXX\dom’ = ‘XXXX\domain users’. Only two of the users directories have those correct domain permissions….the others are assigned ‘root’ and ‘wheel’ which breaks everything…

localhost:/Users/testuser admin$ ls -al
total 24
drwxr-xr-x 12 testuser XXXX\dom 408 Aug 23 10:44 .
drwxrwxr-t 9 root admin 306 Aug 23 10:42 ..
-rw-r–r– 1 root wheel 3 Aug 23 10:42 .CFUserTextEncoding
-rw-r–r– 1 testuser XXXX\dom 6148 Aug 23 10:44 .DS_Store
drwx—— 3 root wheel 102 Aug 23 10:42 Desktop
drwx—— 3 root wheel 102 Aug 23 10:42 Documents
drwx—— 17 root wheel 578 Aug 23 10:42 Library
drwx—— 3 root wheel 102 Aug 23 10:42 Movies
drwx—— 3 root wheel 102 Aug 23 10:42 Music
drwx—— 4 root wheel 136 Aug 23 10:42 Pictures
drwxr-xr-x 4 root wheel 136 Aug 23 10:42 Public
drwxr-xr-x 5 root wheel 170 Aug 23 10:42 Sites

[jnelson]

I guess a good question is whether you will be able to buy the RAID card seperately or are forced to purchase it as a BTO option. I haven’t seen any mention of it being sold seperately…maybe through a repair shop as a replacement part?

[jnelson]

Not to be a complete bonehead about this, but could you maybe get a little more specific as to each field we need to populate in the Zones tab of 10.3 server DNS?

Basically I am trying to fix a server which was setup without DNS running as a PDC and OpenDirectory Master that is seriously acting up. It looks like the standalone>DNS>Windows Services>OpenDirectory Master should have been the root to install instead but hindsight is 20-20…

[jnelson]

We have the same or similar problem with our current 10.3.4 server install (was 10.3.3 and had same problem). We would get the message that the domain was not available when a user tried to change a password but as long as they went through all the motions up until it asked them again to enter the old password after the error message, the password would in fact be changed.

Instead of waiting for a fix, we deployed and did some user education to just ignore the domain not available warning when changing a password and all has worked fine since then. Not ideal, but it works.

[jnelson]

The solution we had to this problem was to log in once on the Windows machine as a roaming profile and then go to the User Profiles management screen in Windows and from there tell it to use a local profile for that user.

Not a perfect solution but did work for our notebook users.

[Author]

Posts