Leopard Server / Windows / ACL Problem

We have this problem that came up sense we upgraded our servers to Leopard. When Windows users are accessing files (over SMB), the POSIX permissions seem to override the ACLs. This is a problem because applications like Excel will change the permissions.
This worked perfectly in Tiger. The windows user would modify the POSIX permissions all they want, but it wouldn't matter because the ACLs were what mattered.
Does anyone know of a solution. This is a real problem.

Since your issue is caused by OS X Server, you may want to post your question over in the OS X Server forums:
http://discussions.apple.com/category.jspa?categoryID=96

Similar Messages

OS X 10.5.8 Leopard Server & SMB authentication problems

Hi all,
I am in charge of a OSX Leopard server. The platform has Windows XP /Windows Vista / OSX computers and as the server has a high capacity NAS it seemed logical to share it using SMB.
The initial set up was done having in mind just the MACs, and they have no issues connecting to the SMB shares. The problem is on Windows side.
Windows machines are supposed to use the SMB shares with Open Directory Accounts. But whenever we create an SMB share, there is a strange behaviour: files could be uploaded to the server, but once copied, they can't be copied back to windows machines, triggering the error (more or less, as the error text is in spanish): "File operation could not be completed, source file could not be found"
For debugging purposes, we have just created a share, step by step , identify which the problem is:
1 - Create a user from Workgroup manager, no admin capabilities.
2 - Create a folder under "Shared Items" Folder.
3 - Disable "Enable Spotlight Search"
4 - Disable AFP, FTP, NFS (leaving just SMB as sharing protocol)
5 - SMB protocol options: Disable "Allow guest access", Asign permmissions as follows: Owner: RW, Group R, Everyone R.
6 - We then go to permissions and choose user created at step 1, set him ACL permissions as RW.
7 - Save changes.
After that, we reboot our Windows test machine, flushing its dns cache previously.
Then when trying to connect to the share,an error message on our XP box says that we have no permissions to connect to the sahre (using our test user credentials). SMB log displays the following:
+setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.+
+[2009/10/23 12:05:20, 2, pid=29029] /SourceCache/samba/samba-187.9/samba/source/auth/auth.c:checkntlmpassword(319)+
+checkntlmpassword: Authentication for user [] -> [] FAILED with error NTSTATUS_NO_SUCHUSER+
Thanks in advance and best regards.
Message was edited by: javierspn

Edit:
I can now connect with the new user. Something to do with DNS cache and opened sessions on the SMB server that I manually closed.
However, same problem: I can upload files but whenever I try to copy one from the server to any XP workstation:
http://yfrog.com/3oerrorjkj
Basically meaning in plain English that the source file could not be found.
Regards.

File Sharing Speed with Leopard Server/ Windows XP

Went from Panther Server to Leopard Server. Panther worked fine. Leopard Server we've had a lot of problems with Windows XP clients. We run data files from the server. Using Panther the file sharing speed was comparable to putting the data file on the PC itself. When we moved to Leopard the speed went through the floor. 8 seconds on the PC and 4.5 minutes on the Server. The server is a substantially stronger machine with a lot more resources - but we've had to stop using it for it's intended purpose.
Help?

Same problem but almost the reverse. 10.5.2 server, windows clients file browsing, opening and saving speed is great, but our 4 iMac clients (Leopard also) really, really slow to generate thumbnail views of files and open them. Happens across several shares, seems to be a problem with AFP, although now after disabling AFP on some of the shares, it is happening on SMB as well. I have read several other discussions on this forum that attempt to deal with AFP performance issues, but none provide a real solution. Now that it is also happening with the SMB protocol as well I am getting a bit concerned.
Any advice or even a link to more info would be greatly appreciated.

IWork09 + Mac Os X Server Snow Leopard 10.6 - ACL problem

I have a client with 6 users who are having issues saving iWork files in our MacMiniServer running 10.6.6.
Users, in MacOsX server are setting inside a group "i.e. GROUP". GROUP, in ACL field, have Full Control of Folder, child foldes, child files, all discendants and I propagate permissions.
One client, member of GROUP, can save pages/numbers/preview files into server, but every time other client, member of same GROUP, try to modify that document in mainly, Numbers or Pages (and also Preview) it is giving errors, "I don't have the specific ones at this time". So we have to drag the documents to our Local Desktop, save and then drag drop back into the Server folder, we all have read and write access to these documents.
I have seen in Server Admin File Sharing that iWork and Preview files lose their ACL information, while Office files, Archicad files and other don't have any problem.
Anyone have any ideas?
Thanks

Hi Yvan!
Few minutes ago I resolve my problem and now I tell you how.
The problem isn't that several users may work simultaneously on a given document (iWork files), but my typical situation was:
A user (X) saves a new pages files into server shared folder. He closes file and Pages.
After time, other user (Y) goes to open that file but for him it is impossible resaving the file. Not simultaneously, but in different time. IWork files lost their ACL.
In my server user X and user Y are inside the same group (AAA) and, in the share folder, ACL permissions are Full Control for AAA Groups.
This morning I have generated a new Share Points, I propagate permissions (Group AAA Full Control) to This Folder, Child Folders & Files and then I have transfered all my files from older Share Points to newest Share Folder. All iWork file now are working without permission problems.

Leopard Server beta testers: Anyone have it actually working?

I am beta testing Leopard Server 10 client version for only $499.
Anyone have Leopard Server running without problems?
Just want to know if anyone out there has gotten server to work for them?
Thanks

I gave Leopard server a try today. Here's my experience:
I use SoftRaid 3.6.4 as the raid driver on my G4 XServe with 4 ATA drives in the server and two external FireWire drives. Two of the internal drives are one Raid 0 volume and the 10.4 boot drive.
I used SuperDuper to make a backup image of my OS X Server boot drive, which is one logical volume on two physical disks.... in a RAID 0 configuration internal drives on the XServe. The backup is a single disk in a firewire external Granite enclosure. I booted from the cloned copy and ran for a while just to make sure the clone was good. No problems yet.
I then booted the Leopard Server CD and was able to do an UPGRADE install on the external firewire drive image. This process went smoothly with no problems.
Unfortunately, Leopard server is another story. The upgraded system isn't doing well: I couldn't get Apple Remote desktop from my laptop to connect to Leopard nor was I able to get the IMAP email server to work. Client machines just sat and "spinned" trying to make a connection. Had to monkey around with permissions to get 10.5 web pages working using Safari running on the Server. These pages worked perfectly on 10.4 with the same permissions. When trying to access the web pages from a client on the same subnet, was unable to connect. Web services were running fine and the firewall settings seemed OK so I'm not sure what is going on. So I powered down the external drive and will wait a and think about trying the upgrade again. Kind of wasted 4 or 5 hours today hoping this upgrade would be smoother.
I'll probably start over and do a clean install and export and import settings to 10.5. Not a particularly fun prospect.....
Leopard client was a simple process to move from 10.4 to 10.5. Leopard Server looks like a lot of work and hassle to me at this time.

Does Running Boot Camp Solve Mavericks' Windows-Networking Problems?

Anyone running Mavericks in a Windows-server environment knows how agonizingly slow it is populating a window on the server if there are more than a few dozen files in it (we have 25-30 folders on our Windows server that have more than 10,000 files in each one, and they are all images files with sizes between 5 and 50 MBs each). When we open a folder that's on the server in Mavericks' Finder, it can take up to 30 minutes to populate that window. We have since reverted to Mountain Lion and although it's still slow to populate those windows, it's nowhere near as slow as Mavericks, and once the window populates, as long as we don't shut down the computer, the next time we open that window it populates within seconds (I'm guessing that some sort of cache file is created).
Does anyone know if running Windows in Boot Camp (or Parallels) would speed up the Windows-server window population problem? I'm guessing it might but I'm not sure if the computer is still connecting to the server using the Mac networking protocol. If I use my Windows 7 PC the server windows populate almost instantly.
Any help would be greatly appreciated.
Lloyd

From the Boot Camp System Requirements page: http://support.apple.com/kb/HT5634
Mac model
Windows 8
64-bit
Windows 7
64-bit
Windows 7
32-bit
Windows Vista
64-bit
Windows Vista
32-bit
Windows XP
32-bit
MacBook (13-inch, Mid 2010)
4
4
DVD
DVD
DVD
MacBook (13-inch, Late 2009)
4
4
DVD
DVD
DVD
MacBook (13-inch, Mid 2009)
4
DVD
DVD
MacBook (13-inch, Early 2009)
4
DVD
DVD
MacBook (13-inch, Aluminum, Late 2008)
4
DVD
DVD
MacBook (13-inch, Early 2008)
4
DVD
DVD
MacBook (13-inch, Late 2007)
4
DVD
DVD
MacBook (13-inch, Mid 2007)
4
DVD
DVD
MacBook (13-inch, Late 2006)
4
DVD
DVD
MacBook (13-inch, Mid 2006)
4
DVD
DVD
Your computer supports Windows 7 32bit with Boot Camp 4.

Leopard Server 10.5.4 + SMB + Windows XP Clients

Hello!
I got quite some interesting problems with my Xserv under Leopard Server 10.5.4 with Windows XP Clients.
The server runs as an open directory master and a standalone server for smb.
Shares are setup for AFP and SMB clients, ACLs are set up with read+write access for the user's group. So far everything works, users can connect from their Macs (OS X 10.3.x - 10.5.4) without problems.
My problem are the windows clients.
Connecting works fine, and apart from one permission bug (more on that later) they can access all files and do everything the macs can do.
Problem 1:
Users cannot rename files if they don't have write permission at the POSIX-level as either owner or group on the enclosing folder. ACLs do not matter at this point, if the user connects through SMB he cannot rename files or folders.
No big problem, I just put all users into one group and set this group as the POSIX-group and do a chmod -R g+w on all shares.
Inheritate this settings for SMB-connections works.
But not for AFP-connections. Every new folder a mac-client creates comes with permissions 755. So I changed UMasks on the clients to 002, and at least folders created by the finder now have the right permissions of 775.
Folders created by "new folder" on most applications load/save dialogs still come as 755 which screws up renaming for windows-clients.
Folders created when expanding a zip-file also behave this way.
The only solution I found for this was to make a cronjob that does a chmod -R g+w on the shares. Not that great.
Another "fun" feature with POSIX-permissions and SMB:
Files inside a folder. Files+Folder have an ACL set up that specifically denies deleting files+folders for a user. This users group has POSIX-permissions with write access to the enclosing folder. Window's explorer will let that user delete files and folders without any complaint about missing permissions to do so. They even disappear from the explorer-window, but are not actually deleted.
If you refresh the view, the files+folders are there again.
If the user instead has no POSIX-permission that grants him write-access, but an ACL that grants him delete, explorer happily deletes the files the user wishes to. And these files actually get deleted.
If the user has no write POSIX-permission and no ACL-permission to delete files, explorer complains about missing rights to delete files/folders.
I tried adding "acl check permissions = no" to smb.conf, but that didn't change this behaviour.
Problem 2:
Sometimes, when copying "large" files to a server share with windows explorer (from 50 MB upto 3 GB), the user immidiately gets an error message: "Cannot copy. The specified network name is no longer available."
The copied file shows up at once in the destination directory and has the correct file size, but only contains "garbage". Half a second later the same copy works and the file is actually copied successfully.
Sometimes this error shows up while a large file is copied and if you browse through other shared folders while the copy takes place.
Most often it will show up when you copy&paste with explorer.
I am stomped and have no idea where to search for a solution to this one.
I tried changing ethernet cables (premade and selfmade), the network switch, ethernet port of the Xserv ... connected a workstation directly to the Xserv - no change.
DNS works, all clients+Xserv have static IPs and the same settings for DNS-Server. Name resolution works, as does reverse resolution.
I even tried using a windows server 2003 as a WINS-Server without success for this problem.
There are no event log entries on the clients when this happens, and smbd.log on the server shows
read failure for 4 bytes to client 192.168.1.137. Error Connection reset by peer
I used wireshark to monitor what exactly happens when this shows up, but it just happens out of nowhere ... the clients just sends a TCP_RST. No unusual things before or after the TCP_RST.
I ran some tests with samba 3.0.32 and samba 3.2.x under linux 2.6.x - no such errors at all.
I tried installing Leopard Server on my Mac Pro, same behaviour.
I ran some batch-scripts that would copy large and small files in excess from/to the server from 4 different windows xp clients for a whole weekend 24 hours - not a single error. As soon as I use windows explorer to copy a file this error has a chance of showing itself.
Problem 3, more of an application bug:
Adobe InDesign CS2 (Windows again ;)) cannot export a PDF to a shared folder if the filename is longer than 8 characters. It starts exporting and after reaching 100% it just stops with the error "PDF cannot be exported." If the filename is shorter than 8 characters, all works fine. Exporting locally or to other samba servers (linux) or windows servers (2003) works fine. Copying this files to the share works, too.
Exporting any other filetype from IDCS2 (eps, inx, jpeg ...) works regardless of filename length. So does saving InDesign-files.
InDesign CS1 and CS3 do not show this, so I guess it's safe to assume this one is Adobe's problem
Did anyone experience similar problems or even better has a solution to some of these?
The real showstopper is problem #2, at least for us.
Thanks in advance and excuse my poor english skills!

I tried several new approaches, but nothing worked so far.
The update to 10.5.5 made things worse. Connections are dropping all over the place, when saving from Adobe programs in particular.
Printing from clients to a Xerox Phaser 5500 works, but choosing a different paper size than the default chosen in the cups admin interface goes all wrong and either prints on the default paper size, but down/upscaled to the chosen paper size or prints on the chosen paper size and down/upscaled as if you were printing to the default paper size. (e.g. default paper size is A4, you choose A3 with an A3 document. Document prints on A4 and is downscaled to A4, or prints on A3 and is downscaled to A4.)
There is no way I can keep this thing in production much longer. I tried reinstalling again, but that did not change any behaviour. Another nice "feature": InDesign disables "edit original" when the path to the linked file contains any directoryname with more than 8 characters in length.
Coupled with a sometimes disappearing "dirserv" (it just stops working until I reboot the whole computer) the decision stands to move away from the Xserve.
Leopard Server 10.5.x just does not seem to work well with windows clients.
We will migrate to a windows server 2003 running ExtremZ-IP for the macintosh clients this weekend. Too bad that Apple does not allow Bootcamp to work on Xserves, at least the hardware would have been useful then.
(As a nice finishing touch, the harddisk partition where all data resides did become corrupt over the weekend. "The volume Daten could not be repaired."
Disk Utility and first aid did show nothing on friday ... saturday after no work being done on the partition this error shows up. The only solution I could find was to reformat the partition and restore from a previous backup. Another weekend down the drain. Sorry for the rant, but 6 weekends in a row is enough.)

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

Migration from Windows Small Business Server 2003 to Snow Leopard Server

Hello,
I'm going to migrate a Windows Small Business Server 2003 Standard to a Mac Mini Snow Leopard Server 10.6.x in a few weeks.
I have 2 questions :
Is there an official process to migrate my Exchange server datas ?
Snow Leopard Server has it Wizards to help me to muigrate datas to proper services ?
Thanx
Regards,
Gil DERENNE aka --( dB )--

Thank you for your reply
My network will be Apple only in a few time (1 server, 1 iMac and 1 Mac Pro).
Now, I want to replace server and all services installed on it :
- Active Directory (replaced by Open Directory)
- Users/Groups/machines
- NAT/Firewall and Backup (will be replaced by a Time Capsule)
- VPN for mobile access
- File and Printer sharing
- Fax Services with Fax/Modem 56K !oops! (replaced by a free service offer by my ISP)
- Mail/Calendar/Address book and notes with Exchange (replaced by each service to serv right thing : Mail, iCal, Address book...).
I know what to do with all things but not for replacing Exchange and transfer datas to each similar service in Snow Leopard.
In the network, Mail Server will be used by Outlook with IMAP protocol and other services by web interface (Windows computers are not a problem for me, it can be alone and only access web if necessary).
The number of clients inside the LAN :
- 2 iPhones
- 1 iPod Touch
- 1 PC Windows Vista (for a few time) with some VM (Linux and Windows)
- 1 iMac 27' with 1 VM (Windows)
- 1 LAN Printer HP Deskjet 6127 (RJ45 Static IP connection)
The number of clients outside the LAN :
- 3 PC Windows XP
- 2 PC Windows Vista
- 5 Nokia Smart Phones
When I'm going to by the Mac Mini Server with Snow Leopard Server, is there some support to help me to do it whith them and is it free or do I have to buy AppleCare to access to this service ?

Small problem: how using "Remote Desktop" on Snow Leopard Server

Hello,
How can I login to the Mac Mini Snow Leopard Server from 2 different Macs ?
Before I bought my Mac Mini Server in July, I asked the Apple Support if Snow Leopard Server has the equivalent of the Windows Remote Desktop functionality. He told me that it is possible. He did not tell me how, but I believed him.
I cannot find it in the documentation. Only 1 person can use screensharing. But I need more than 1 person working on the Mac OS X Server.
I moved our Photo library to the Mac OS X Server. With filesharing it takes 5 minutes to start iPhoto on our client iMac ( 1Gbps network). That is unworkable. So, from more iMacs users have to login to the server and start iPhoto on the server.
Thanks for the solution.
Hubert Anemaat

As per Jason's reply, there are two Terminal Server products available for Mac OS X. I have been testing both, both work in the same sort of way and will allow multiple simultaneous users to connect.
The typical approach is to (obviously) first to install one of these Terminal Server programs on your server. Then you (ideally) need another server hosting your Mac network home directories, and it needs to share the network home directories via NFS rather than AFP.
Note: Due to the way Mac OS X handles mounting AFP shares, you cannot have two users using the same share at the same time as the login defines the privileged's and the first logins privileged's would not be suitable for the second user, this is also why you cannot use "Fast User Switching" with two network login accounts when using AFP.
So, a client uses an RDC client (e.g. the free Microsoft Remote Desktop Client) to connect to the Terminal Server, this initiates a network login which access the users home directory via NFS.
RDC client (Mac or PC) ------> Mac Terminal Server <------ Mac network home directories
I have not tried iPhoto, but have tried various other applications, e.g. FileMaker, AppleScript, Microsoft Office 2004, etc. and the only problem I have hit so far is that Visual Basic in Office 2004 generates errors but Word and Excel otherwise work. Remember Office 2008 does not support Visual Basic (i.e. Macros).
I would actually expect iPhoto to work for multiple users as long as you use NFS. Using NFS for network home directories rather than AFP has actually 'fixed' a couple of badly written applications that had problems with AFP based network home directories, e.g. Adobe Acrobat 9.
I am using Mac OS X 10.6.4 Servers.

SNOW LEOPARD SERVER PROBLEMS REQUIRE CERTIFIED CONSULTANT TO HELP

I've had a pretty unstable Snow Leopard server install since it was upgraded from Leopard a few months ago. Some of the problems were said to be hardware related, but I've been unable to migrate it to a different computer (Mac Mini).
The current installation is running, albeit poorly.
We had a Mac consultant involved in these issues, but he has proven to be unstable and unreliable as well - so we're on a search for a new consultant to give us some paid assistance in straightening this thing out.
We're not on the US mainland, but can make the server accessible by ARD and/or SSH to someone.
Someone with Apple certification would be preferred.

Hi Brian,
I'm an IT consultant dealing with Mac OS Servers and Windows Servers as well as Linux. I can offer a few helpful suggestions since just recently I transferred data from a Mac OS 10.5.8 Server to a 10.6.2 Server.
My first question to you is what data are you immigrating from? example 10.5.8 Server Data to 10.6.2 server?
The reason why I ask this since IMAP data in 10.5.8 and before was using Cyrus and starting in 10.6 apple switched to Dovecot.
Initially, I did not realized that apple made the switch and had stalling problems using the apple migration tool. (Personally I don't think the tool works well since a lot of others are running into this problem when researching this issue).
In the end I decided it was best to important everything manually, mail and not use the apple immigration tool since I think it has some issues.
The first thing I would do is make sure the DNS is configure right so that the server can resolve it's name which is very important.
Hopefully you're been running Open Directory . Export the users from the old server and import it to the new 10.6.2 server.
Next transfer the IMAP mail from 10.5.8 server to the 10.6 server to the same locations.
Example in 10.5.8 server default location is
/var/imap
and
/var/spool/imap
note this is where cyrus stored imap data in 10.5.x and maybe before. I have to look at my old 10.4 server since I'll be upgrade my own server soon.
My clients Servers have been upgrade fine by doing the manual method.
anyway...
keep those two locations in mind of where you mail is stored.
next I would copy your old cyrus mail to the new server. Don't use the migration tool at all. Just setup the new server and get the DNS running so it can resolve itself before you do this.
also make sure mail server is not running and it's off.
open up a terminal window
copy and paste this but change the name of the volume/hard drive name (HD_name)
sudo /usr/libexec/dovecot/migratemaildata.pl --cyrusBin "/Volumes/HD_name/usr/bin/cyrus/bin" --database "/Volumes/HD_name/var/imap" --sourceSpool "/Volumes/HD_name/var/spool/imap" --targetSpool "/var/spool/imap/dovecot/mail"
ok do this will convert all of your cyrus mail to dovecot. Make sure you've already imported the users from Open Directory before doing this script.
after all of this
there's still one more step
for some reason the postfix "main.cf" file is configured to use cyrus in 10.6.2 update.
/etc/postfix/main.cf
you can use the pico editor if you like.
example
type in at terminal window
sudo pico /etc/postfix/main.cf
it should be near the end of the file
don't bother with anything that's in # which is ignored.
look for
mailbox_transport = cyrus
then change it to
mailbox_transport = dovecot
save the changes
edit settings in the mail server with server admin to what you had... I recommend don't importing the mail settings from the old server admin since some people reported that its better just to manually configure it.
however for other server admin settings you might try to export and import to the new server.
If you have any questions just let me know and I'm glad to help the mac community.

Leopard server and windows users

We run a mac + pc environment with some users on macs, many on pcs, and our office server is a windows exchange for email etc. As a multi-location consulting firm, we need to set up a good collaboration system that is hosted internally (to preserve confidentiality) and allows us to create a web-based knowledge creation, sharing and collaboration environment. We have looked at some of the new web services offers, but all are hosted by the providers.
We are considering buying a mac leopard server and have the following questions:
1/ will windows users be able to use the wiki, chat, calendaring and podcast facilities from their laptops without any problems, and will they have the same easy user interface?
2/ does the wiki server enable group collaboration like:
2a/ sending out email notifications on new posts (without changing our exchange server)
2b/ allowing groups to create project and team specific areas
3/ The problem we face is one of adoption. If we can make this as easy as facebook, then lots of people will migrate within 48 hours. But is this possible with the leopard server?
4/ finally, we are based in Singapore and our offices are all in Asia? Do we need a lot of experienced Apple-savvy technical people to create any of these applications, or is leopard server as easy to use as a mac is for a home user?
Any thoughts or inputs would help. FYI, alternatives we are evaluating are jive software's clearspace or basecamp or zoho's web based suites.
thanks / Suresh
Message was edited by: suresh Venugopalan Shankar
Message was edited by: suresh Venugopalan Shankar

suresh Venugopalan Shankar wrote:
1/ will windows users be able to use the wiki, chat, calendaring and podcast facilities from their laptops without any problems, and will they have the same easy user interface?
Yes, the web based interfaces work just fine for both OS's, the chat server is using jabber (clients on about every OS) and the calendaring is using the standards based iCalendar format.
2/ does the wiki server enable group collaboration like:
2a/ sending out email notifications on new posts (without changing our exchange server)
2b/ allowing groups to create project and team specific areas
I don't know of functionality to send out e-mail notifications on new posts, but you can subscribe to RSS feeds of things posted in the blog section of the wiki server. I'd need a little bit more information to understand what you're looking for as far as creating project and team specific areas.
3/ The problem we face is one of adoption. If we can make this as easy as facebook, then lots of people will migrate within 48 hours. But is this possible with the leopard server?
On the front end most of this stuff is very easy to use, and is in my opinion even simpler than facebook and such.
4/ finally, we are based in Singapore and our offices are all in Asia? Do we need a lot of experienced Apple-savvy technical people to create any of these applications, or is leopard server as easy to use as a mac is for a home user?
It's pretty easy to set the server up as long as you read the documentation. There's also a lot of resources online if you have problems (like this forum). It would probably be helpful to have someone familiar with LDAP systems and at least some command line usage on the server, but like I said, the documentation is pretty good. You can go read it to get an idea at http://www.apple.com/server/macosx/resources/
Hope that helps out some.

New Snow Leopard server problems -need advice.

hello everyone. I just setup a mac pro with Snow Leopard server to replace our G5 which was setup up for simple file sharing as a fake server and am having several challenges listed below:
*I've made sure the new computer running SL server has the same local name and IP address as the previous G5 (now off of the network)
- Our windows (Vista) computer cannot see the server on the network. This was not a problem with the G5 and SMB filesharing.
- I cannot access server preferences due to this error: "Unable to set node credentials for /LDAPv3/127.0.0.1 with the record name server.mydomain.com$ There may be a problem with the Open Directory service."
- server admin is treacherously slow both locally and remotely.
I cold really use some help on these folks. I'd sincerely appreciate it.

Thanks for your input everyone. I turned off DNS (just to see) and it's still slow. Frankly I am not sure if I even need it yet. My goal is only to setup local services and then open the server up to the WAN.
My provides the DNS I suppose. MY ISP points to my WAN IP and my router directs that to my server's internal IP. At least that's how things are setup now and left over from when i was using Snow Leopard client as a fake server (for filesharing and DayLite).
I did setup the initial DNS settings of Snow Leopard Server after the install to the computer's IP address which I assigned manually and left the rest to get from my router's DHCP server. I setup the zone (home.mydomain.com)
Any ideas for the sluggishness.

The Windows SMB feature has file locking if multiple users are accessing the same file. Does Snow Leopard Server File Sharing (AFP) provide similar features?

The Windows SMB feature has file locking if multiple users are accessing the same file. Does File Sharing (AFP) on Snow Leopard Server provide similar services?

Were you ever able to solve this problem. I'm having similar issues since upgrading to snow leopard. Four macs connect to a Windows Server 2003 for shared files. Each user has full permissions & when we "get info" it shows read & write permissions. Two of the computers were running 10.4, two were running 10.5. Everything worked properly until upgrading to snow leopard. Some files let me copy, move, delete. Others either just hang up or we get a "no permission" error. Also getting a "pdf is in use" error, even when the file/folder doesn't contain a pdf. We had our IT rep check the server who said everything is in working order. They don't represent macs any longer but feel that it's a mac problem. I would have to agree since this problem only started after the upgrade, and the one machine that was not upgraded (still running 10.5.8) is not dealing with these problems.
Lastly, I would install 10.5 back on all of the computers if I could, but the leopard disk that came with one of the computers wouldn't work with the 2 machines running 10.4 and I didn't see it available at the apple store. I'll buy it if it's still available, but why wouldn't the disks that I have work?
Thanks for any help

Leopard Server / Windows / ACL Problem

Similar Messages

Maybe you are looking for