Forum Replies Created
-
AuthorPosts
-
Damien
ParticipantI was posting this article to know more about the Apple support for enterprise.
The fact is, I read this blog from an old Apple employee saying that Apple’s enterprise support is bad. So I ask here about that as I am interested by Mac OS X Server.
I never said I will trust you more than him, I just want another (neutral if possible) opinions about that.
The best thing an administrator can do is to know the strength / weakness of each operating system. If a bad support is a weakness of Mac OS X Server, then I want to be aware of it 😀
Damien
ParticipantI am looking for a “real experience” feedback of Apple in the enterprise market. 😆
I mean this website is dedicated to Apple in enterprise environment, it is the best place to have some counter experiences 😁
Damien
ParticipantIf my entire basis for picking an operating system was a blog, I hadn’t post anything here 🙂
I posted this here because I want another opinions as I have no experience with Apple in the server market.
Damien
ParticipantHello,
I have spent some considerable time to get the following working with great success. Hopefully this helps.
My situation is:
W2K AD for authentication
OS X 10.3.3 Server – I just have to confirm this as it could be higher…
Windows Clients connecting to SMB Shares on XRaidthe steps I followed were:
1. Set up OpenDirectory to use AD plug in
2. Add for authentication and Address Book
3. Bind to AD – this needs to be done once you edit the smb.conf file
4. For Windows Services – set as member server
5. Edit smb.conf
– confirm workgroup is in uppercase and is correct domain name
– set use spngo = yes
– set security = ADS
– domain logons = yes *** this is the one that will let smb shares use AD security. if this is not set errors occur.
– verify that the REALM is correct and in uppercaseI did notice that occasionally the smb.conf file would reset the domain logon setting back to no so I changed the file to be immutable using
sudo chflags uchg /etc/smb.conf
If you ever need to change it again you’ll need to unlock it with:
sudo chflags nouchg /etc/smb.conf
After any edit of the smb.conf file you need to rebind to the AD.
Theory has it that this is all you need to do.
I use lookupd -d userWithName : userID to validate that I can talk to AD. Also another thing to note is the security on the directory needs to be set to give the AD user access.
Hope this helps.
I had a tough time getting where I am and hope this helps some others.
cheers Damien
-
AuthorPosts