[Kave]

I have just installed OS X Server 10.2 on a Xserve machine efter fighting with the horrible disk striping performance of 10.1.5, and the inability of saving from Photoshop to a server volume.

I must say that the new tools for administration of the server is even mor eirrational than ever before.
There are 5 different tools for this, Server Assistant, Server Monitor, server Settings, server status and Workgroup manager.
The workgroup manager is for managing users and groups , and it is extremely hard to work with. A 23" Cinema Display is needed to have all the different settings windows open.
I have tried enabling windows service but with various succes. If I create an account who belongs to a group which have full access to a folder, they can't connect to the server using smb. Apple's solution in the manual is to enable "guest" access. When that is enabled, no users with accounts on the server can still login, only "guests", or people who don't provide a login name or password at all.

[Deicide]

Tell me about it. How does Apple expect people to migrate from ASIP6.3 with crap like this? I turned on windows file sharing to see if it was working. At any windows box all I get is an access denied dialog as soon as I try to open the server. It doesn’t even work from a MacOS 10.2 box. It gives me the list of shares to choose and after typing in the username and password it gives a 5023 error. The Workgroup Manager is a joke. I created a user and wanted it to have a simple home directory. It makes all these shares by default and you have to login before it creates the users home folder. 10.2 client is better at serving files through samba and afp and doesn’t have a connection limit.

[Kave]

I get the same error msg here to, -5023. Tried from Windows 2000 and from various OS X clients.
Apple's support pages, although they are better then a year ago, are worthless. If I select support for Mac OS X Server and search for Windows Sharing, I only get replies regarding ASIP.
I fully agree with the extremely silly shares settings. Most people with a server is interested in making a directory on a filesystem, and then make that available to a group of users. Doing that in OSX server takes lot of administration, removing the various stupid share points allready defined by itself.
And the homedirectory setting is very stupid to. An entry can look like this:
Home Directory = afp://Mac OS X Server 1/Users/username/. And that is for a local account.
Apple, when setting up a server, most people will never set up a users home directory on another server. Maybe some like it, but it shouldn't be a "default" setting.

Another thing that annoys me is that the OS X Server Server Monitor sometime take 5 minutes of letting the admin know that a disk suddenly is unmounted.

And what the hell do we need a key to lock the server, if the disk's will be unavailable when touched anyway? I guess the lock is not for stopping people from stealing your drives, if so I guess they will bring their own insex "key" to unlock the drives and plug them out.

[Kave]

I have spent 6 hours trying to figure out how to get the damn 10.2 Server to listen to a Wondows 2000 servers Active Directory via LDAP v3. According to Apple this is very easy to do. I have not succeded in doing this, allthough I have had 2 Windows experts to my help, and myself as an old samba user.
I have also tried accessing the Active Directory using the Address Book of 10.2, nedless to say without success.
The only way I actually could get a Windows 2000 Client, or a OS X 10.2 Client to login using smb was to enable the "Password Server" in 10.2 server. This not very well documented in the manual, but there is a PDF with some screenshots att www.apple.com/macosxserver that led me in to how to do it. It involves yet another utility called Open Directory Assistant, and the PDF is called "Open Directory". Look at page 3 and you probably will be able to figure out how to do it as well. In short you have to enable LDAP services to other computers. Do yet another reboot and then it works, if you also modifies the User's password field from "Normal" to "Password Server".
I don't know if it is the Next people who came up with the "talk in circles about all the technology that we just found and installed and didn't have time to do ANY docs at all" idea, but it sure is frustrating.

[Deicide]

Kave:

I was about to post the same info. I have been working on it from home this weekend and only have one pc(winxp pro) and one Mac for testing. Anyway, now my pc can open any of the shares without even prompting for a username or password. I have gone into the windows file server settings and made sure that guest access was turned off. I also went into each share and made sure "allow smb guest" was unchecked. are you getting the same thing?

Hopefully www.afp548.com will post some articles on the proper setup of this. It's funny looking at the Apple discussion boards for server. Everyone is bitching about the same thing but Apple pulls most of the posts. How are people going to know or get anything fixed if Apple wont let them? In the mean time I will keep wrenching away

[Kave]

Thanks for the link, www.afp548.com.
I am too bitching about it att discussions.apple.com, but they are removing my posts that are a bit more "friendlier" than here at macnn.
I have talked to Apple's Partner support here in Sweden (I work at a Reseller as a Apple Service Engineer) but they (Apple partnet support) don't know anything as allways btw.
No I am actually not getting the same error as you do. Since I enabled password server I can login with the correct username/password.
And since it's an Apple changed samba, we can't go for help at the regular samba forums.