Mountain lion Server import accounts & mobile home folder

Hello,
I am new to OS X Server and I have two questions.
First here is the situation.
We are a small company with 10ish mac (Mini, iMac & MBP) running.
So far we had the client account on the machines.
I want them to be server hosted from now. I have a dedicated Mini 2012 for such a use. Everything Gigabit connected.
So here are my questions:
1. How can I Import the acconuts from the different machine including home folder to the server?
2. For some users, on specific machines i would like to creat mobile home folders.
Is this possible?
I created Mobile home folder and it works flawlessly but anytime a user login it creates a mobile folder.
I would like to specify on which machine the account is mobile. On the other machine i want it to be server based.
Thank you in advance for your Help.
G.

Additional info: it appears that certificates are not working either: setting up ical: "the certificate for this server was signed by an unknown certifying authority."...

Similar Messages

Mountain lion server network accounts are not mounting network home directory, rather its creating a blank local directory

I have set up a scratch mountain lion server with open directory. copied over old user account directories and added my users that match the directory ids. Currently if a networked user logs into a networked computer, instead of mounting the network home directory, its creating a local home directory. suggestions?
thanks,
Dave

Additional info: it appears that certificates are not working either: setting up ical: "the certificate for this server was signed by an unknown certifying authority."...

Mountain Lion Server - Folder names intermittently change between Upper and Lowercase names on some user's iMacs

Hi,
Sorry if I'm posting in the wrong group, but I couldn't find a Mountain Lion server specific group.
I have a new Mac Mini Server running 10.5.8 that serves Mac only users. The Mac Mini has a 4tb Promise Pegasus RAID attached via thunderbolt. Today, some of the users on the network reported that a folder on the RAID was quickly alternating displaying it's sub-folders as all capital letters then upper and lowercase - I witnessed this and it happened 2-3 times a second. I have run a propogate permissions fix on the folder, then the whole volume from within Server App and also copied the contents of this folder to my Mac, then I deleted the original from the server and created a brand new folder with the correct name and copied the contents back.
The problem still persists. Server App does not report any issues and other folders don't exhibit this behaviour. I've looked to see if there are any weird characters in folder names that would do this. The volume is shared via AFP only (SMB and WEBdav are off).
Any ideas as to what could be going on?
Thanks in advance!

Hi.
I solved this problem. I fixed permissions on the Mac's that the users were using to access the server and this has fixed the problem. The server folder giving the problems had many nested folders totalling over 5000 items inside and this seemed to corrupt the permissions on the user's macs.
Hope this helps anyone with similar issues.

How do I share a folder over the internet with Mountain Lion server?

I am new to using formal servers. In Snow Leopard I was able to use web sharing to serve a small website and if I wanted to share a folder with someone I would just provide the person I wanted to share a file with the path to the file inside the sites directory. With Mountain Lion this functionality was removed from the sharing section of system preferences.
I purchased mountain lion server and was able to restore the website serving ability, but I haven't been able to figure out how to share a folder. I am still looking over what documentation I can find, but for the most part it just tells me to set up the services without telling me how. Any assistance would be helpful. Networking is not my area of expertise.
Best Regards,
David Finell

I purchased server to assist with this as I am unfamiliar with the command line protocols for using apache. Because of the UNIX architechture of OSX and I presume apache, I am uncomfortable using the command line for fear of causing serious problems.
Unfortunately, the documentation that I have seen for mountain lion server is wanting in either its completeness or layout/functionability. To summarize the server instructions as I understand them. It just says to configure it and my system to meet my requirements without telling me how.
I am confident that both the apache command line and server are capable of accomplishing what I was able to do before under snow leopard. I just haven't figured out how.
I was able to provide a link to family and clients like http://ipaddress/~user/folder
This no longer works.

HT5678 What the important thing we need before we can setup The Mountain Lion Server application

I want to set up mountain lion server application on my mac osx 10.83 , may i have some suggestion before i set up it to my macBook .

I'd ask what requirements you're looking to fulfill by using OS X Server on a MacBook system, as that's not a typical hardware configuration for a server.
OS X Server and most other server operating systems expect static IP addresses and full-time availability, where a MacBook tends to be mobile and to thus have a variety of dynamic DHCP IP addresses and networks, and MacBook systems also tend to be closed and hibernating at random times.
It's certainly possible to use this hardware as a server (and it can be useful when you're learning how to manage a server and have a "scratch" MacBook available), but the hardware is not necessarily a good fit.
As you add services, you'll want to have DNS services established and verified, and — on a typical NAT'd local area network with no other LAN-local DNS services — that involves configuring DNS services on OS X Server itself. DNS is a prerequisite for various other OS X Server services.
But yes, do have a disk backup, either Time Machine, or as an external disk backup, or however you preserve your data. Skimming the OS X Server manuals can help save some time figuring out the platform, too.

Performance issues home sharing with Apple TV2 from Mountain Lion Server

I have a Mac Mini which I have just upgraded to Mountain Lion Server from Snow Leopard Server.
I have noticed that the performance of Streaming a film using Home Sharing to an Apple TV2 has degraded compared to the Snow Leopard setup. In fact the film halts a number of times during play back which is not ideal.
I have tested the network between the 2 devices and cannot find a fault.
Has anyone come across this problem before.
Are there any diagnostic tools I can use to measure the home sharing streaming service to the AppleTV2 device.
Any help much appreciated

Well, I tried a few other things and one worked but again just the first time I tried connecting to the desktop PC with iTunes. I flashed my router with the latest update and the ATV2 could see the iTunes library and I was able to play media. Later in the day I was going to show off to my daughter that I had fixed it and, to my dismay, no go. I tried opening the suggested ports but no luck.
I then tried loading iTunes on a Win7 laptop and it works perfectly with the ATV2. Both the laptop and the ATV2 are connected to the router wirelessly while the Desktop is connected to the router by Ethernet. Not sure if this is part of the issue as it sounds like this didn't work for others. The only other difference between the laptop and desktop is that the desktop has Win7 SP1 loaded while the laptop does not; now I'm scarred to load it though I don't think that's the issue. All in all, a very vexing situation. Hopefully Apple comes up with a solution soon.

Complications migrating from Snow Leopard Server to Mountain Lion Server.

I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
"Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
What are my options here ?
This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
Clear directions on how to procede would be VERY MUCH appreciated
Thank you.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

Mountain Lion Server with Network User

I have a Mountain Lion Server with a network user. The whole system has been redone from Lion Server and on top of that I moved location, ISP, hardware and a few other things. The way I used the setup on Lion was to bind my MBP to the server and login from the MBP login window with the network account. If for whatever reason I wanted to look at the network account on the server, I could fast user swtich and everything that was open ie Safari, Mail, etc would be the same as it was on the MBP.
Now if I'm logged into the network user on the MBP and then go to the server, it logs in as if I've just booted. They share the home folder and any new files/folders created on one shows on the other. But if Mail is open on the MBP it won't be open on the server.
Does anyone have any ideas or suggestions?

Thanks for your reply.
I believe I got it to work, but,... How do you get the network account users to show up on the login window of the client computer? The login window shows the name of the client computer and the local accounts on the client computer. When I select Other in the login list I can login using a network account user id and it logs in. The network account user names do not show up on the login window

Upgrading to Mountain Lion server and all services breaks down...

Hi!
I have, after endless hours of scanning logs and .plist and other files' content and permission settings found why Mountain Lion Server.app in some cases doesn't seem to be able to take control over all service, stating it can't read or write its own setting files etc.
As a Swede I of course run a system set in the Swedish language. Mountain Lion can't upgrade a Swedish system, only fore languages are accepted !!!
See Migration Logs!
//Excerpt from the Mail Migration log:
Begin Mail Migration: Thu Aug 2 19:34:24 2012
purge: 0
sourceRoot: /Library/Server/Previous
sourceType: System
sourceVersion: 10.7.4
targetRoot: /
language: sv
Did not supply a valid language for the --language parameter, needs to be one of [en | fr | de | ja]
As you can see, it can only upgrade in English, French, German and Japanese system language. With no inital warnings the system crashes and causes a true mess half the way through its installation when you start Server.app.
Solution:
Throw Server.app in the trash or move it outside the Application folder, to force the computer to realized "its not a server". It can take half a minute or so for the system to realize it is no longer a server. You will see a sign.
Change the language setting to English in your system preferences and restart your computer. Move back Server.app from the trash (or where you put it) and start Server.app, thereby initiating a new Servers installation. I was happy to find that all mail accounts etc was found again. I thought for several hours they where lost.
The various sites hosted by the server did however not appear in their correct new location (when I tryed this). I had to manually move them from the "Previous" folder in /Library/Server/Previous/Library/Server/Web/Data/Sites/ to /Library/Server/Web/Data/Sites/
I hope this helps anyone out there....
Cheers!
Stefan

Please explain.... when are you stoped from upgrading?
I haven't actually had problems with the actual OS upgrade it is when you launch Server.app the first time everything goes to f-n h....
Server.app should reconfigure and move around a lot of files and it does, but not succeeding doing it correctly. Many services can't read their config files and have them in two places. I trying to figure out which ones are being used. Somethime both locations are used but only parts of the settings in the files !?!?
I am soon giving up...

Mountain Lion server VPN configuration problem

I'm having a problem connecting to my Mountain Lion server VPN even on my home local network. The configuration is so simple but I can't figure out what I need to do to get it to connect. Trying from my iphone and also ipad going directly to the ip address of the server and have the user account name, password and secret filled out as I have it set on the server but the connection fails. I was at first thinking it might be a DNS issue, but then dismissed that since it's happening on the local network. It seems to be an authentication issue, however I'm using the same settings as on the server. I have other services working such as file server, DNS and SUS so the product itself is fine, just the VPN service.
Any ideas?
- Chris

I had the same "No CHAP secret found for authenticating username" issue. I've been at this VPN thing for many many hours over many days. Desperately want OS X Server to work.
Finally I just bought iVPN to see if that would work somehow--- AND IT TOTALLY DID.
So, forget Mac OS X Server VPN. Just forget it. There are definitely many problems out there facing VPN access. But if you're at the point I was, where it's connecting just not authenticating, then forget Mac OS X Server.
http://macserve.org.uk/projects/ivpn/

Password problem after migrating to Mountain Lion Server

Hello everyone,
Yesterday, I migrated our Lion Server to Mountain Lion Server. Everything seemed to work fine. Except since this morning, none of the network user cannot connect to their calendar, reminders, and wiki. They can connect to their account and to their mails. The following line appears multiple times in ApplePasswordServer.Error.log:
Aug 16 2012 16:52:50 700250us client response doesn't match what we generated
It seems that only web services are concerned (vpn, mobile accounts, and mails are working). My initial guess is that the hash computed on the basis of the user password is not computed on the same way on the client machine (which is running Mountain Lion by the way) and on the server. On the other hand, this would be very surprising, since all this stuff is based on standards and unlikely to have changed since Lion.
I tried to create a new "Test" user. Even this new user, created after the migration, cannot connect to its calendar, etc. I also tried to reset my user password using the Server App. It makes no difference, the same lines appear in the logs.
Is anyone experiencing a similar problem ? Does anyone have a clue of what to try next ?
Thanks a lot !

I found out the following:
After looking at the contents of the password server database using the slot numbers of several user accounts, it seems that all users where WEBDAV-DIGEST authentication is failing, have two entries for the digest method "*cmusaslsecretDIGEST". This is obviously wrong. All users who can authenticate successfully have only one such entry.
Deleting and recreating the user account has no effect. In fact, updating the password server with a new entry may actually trigger this error. It could be that all users where this is failing have changed their passwords after the server was updated to Mountain Lion.
It would be interesting to know if you also see duplicate entries for "*cmusaslsecretDIGEST" in the database. You can display a password server record via the user account's slot number (in your example, the 0xd6ace...) using the command
sudo mkpassdb -dump <slot-number>
At the end of the record dump, you should see 10 digest entries with their method identifiers.

Server admin is unable to login to server.app after upgrade to Mountain Lion Server?

After upgrade to Mountain Lion Server I am unable to login to the server tools. When I input the admin user name and password the dialog box just shakes indicating the wrong password. But it is the correct password. How do I reset the password or if necessary how do I rest the server and start over on Mountain Lion. I found info on how to reset the server on previous versions of the server which involved executing a plist in the LaunchDaemon folder. However that file does not exist on the server following upgrade to Mountain Lion.
Thanks, Howard

I upgraded today and had the same issue. I took following steps to fix my computer.
Boot into Recovery Partition (Hold Option Button while booting)
Open Terminal.
Type resetpassword
Select your hard drive
Select the user account (Administrator)
Enter a new password for the user
Reenter password
Save
Restart
Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
Restart
Everything should be working as expected

I'm trying to use Mountain Lion Server so my family can have separate logins via Screen Share to their iTunes.

Using Mountain Lion Server so my family can have separate logins and connect via Screen Share.
Works great, each has their own home directory and permissions are perfect.
Now setting up iTunes for each with their own Library (not shared), thus keeping multiple Libraries.
I get this;
This Computer is already associated with an Apple ID.
If you download past purchases with your Apple ID, you
cannot auto-download past purchases with a different
Apple ID for 90 days.
What!
So what it is on the same computer, they are completely separate Libraries never to be mixed.
If this works, I only need to keep one computer up and running, instead of three.
Each can do their syncing/backup and connect to the various Airplay/AppleTVs I have around the house.
How do I fix this.
Thanks

Bottom line is you can't - easily.
You need to make sure that you log out of the server each time otherwise the ID is running. To explain, if you had a laptop with different people using it, your solution works fine. Each time someone logs in, the iTunes ID is different so it works as you can only have one person using the laptop at any one time.
Now, turning your problem inside-out, you want people to be able to log into iTunes concurrently to use their own version of the program with their own library. This does not seem to work and you get the conflicted ID error message. Even though iTunes is running under their own login ident, I have never been able to get this working reliably and was told that iTunes is NOT a network-aware application as it is designed to be single user.
The way I got around this was to login as XYZ and to make sure that the ID was changed in iTunes accordingly. However, it did not always work so I gave up with the whole thing.

Configuring postfix on Mountain Lion Server

I'm trying to upgrade from Snow Leopard Server to Mountain Lion Server and did an install of Mountain Lion Server on top of a working instance of Snow Leopard Server. The "crippled" GUI on Mountain Lion Server is forcing me into using terminal to configure Postfix to handle incoming email.
I would like to configure Postfix to only accept email that is forwarded from a gmail business account. The public email address is [email protected] which is received by Google Mail, goes through their spam filters and then is auto-forwarded to [email protected]
The server WAN domain is nonpublic.com The ip address is 96.231.165.126
The server LAN is nonpublic.local The ip address is 10.6.18.201
The server is a MacMini running Mountain Lion Server 10.6.8 hostname server so the FQDN is server.public.com.
The network on the MacMini is configured to handle both LAN and WAN traffic through the 1GB physical ethernet port which plugs into a CISCO 3750 switch. The external traffic to the WAN flows through the switch as tagged packets. The LAN traffic is not tagged. The VLAN connection is running 802.1q
When an email is sent through the WAN to [email protected] the Postfix SMTP log shows:
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: connect from cisco.public.com[96.231.165.123]
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: disconnect from cisco.public.com[96.231.165.123]
I can send emails from a client on the LAN through this server with no problems. The incoming mail server can connect to the machine via the Cisco router/switch but Postfix just shows "cisco" as the connection (that's the router's DNS name) and provides no more info. I suspect Postfix possibly doesn't like the 802.1q connection and drops the SMTP request to connect on port 25.
I have turned on "debug" logging in Postfix, but that is all that appears in the SMTP log file
I've spent most of the week reading through everything I can find on how to install and configure postfix on Mountain Lion Server and work around the cripled GUI in the "server" application. I'm barely OK using Terminal and not familiar at all with configuring Postfix directling editing the config file.
What is the best approach to configure Postfix to allow SMTP connections from the outside to deliver incoming email that is forwarded from gmail.com?
I did find an "aliases" file in /etc/postfix/aliases but I'm not sure how to add the aliases and if adding aliases with a text editor is going to cause the "server" app problems and if the changes will be lost when the machine is restarted.
Any help would be appreciated.

MrHoffman, thank you for your response to my challenge to get the new test server working. This is a migration from Snow Leopard Server to Mountain Lion Server.
Here is the "checkhostname" test results:
blue:~ admin$ sudo changeip -checkhostname
Password:
Primary address     = 96.231.165.211
Current HostName    = blue.pderby.com
DNS HostName        = blue.pderby.com
The names match. There is nothing to change.
dirserv:success = "success"
blue:~ admin$
Here is the response from postconf -n
blue:~ admin$ postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
dovecot_destination_recipient_limit = 1
html_directory = /usr/share/doc/postfix/html
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
inet_interfaces = loopback-only
inet_protocols = all
mail_owner = _postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
message_size_limit = 10485760
mydomain_fallback = localhost
newaliases_path = /usr/bin/newaliases
queue_directory = /Library/Server/Mail/Data/spool
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_tls_ciphers = medium
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
use_sacl_cache = yes
blue:~ admin$
I agree that I should change the LAN domain from .local to something like .internal or whatever.   I've been running with .local for 5 years on snow leopard server and never had any problems so that was a low priority.
I hope I'm just not seeing some obvious setting in main.cf

Smooth transition from Mountain Lion Server to Mavericks Server 3.0!!

After an new OS release that are always complaints about installation and configuration problems. First comers to using any new software tool provide valuable feedback we generally hope will help improve the new product. It's how things have worked since the first 6503 Apple II's and 8086 IBM PC's.
I've been using and upgrading PC's since THOSE DINOSAURS! And I can't remember EVER having an OS upgrade go as smoothly as my recent upgrade from Mountain Lion Server (OS X 10.8.5 w. Server 2.2.2) to Mavericks Server 3.0.
I chose to do a clean Mavericks install on a clean partition created on a 1 TB disk that was upgraded into my trusty MacBook. I used the DiskmakerX app to create a Mavericks installation USB drive. When the screen came up with the option to import users, programs & files (took a pass on email) from the Mountain Lion Server partition, I let it run overnight to transpose everything of value into the clean Mavericks installation.
The next morning the only program that wasn't PERFECTLY installed and configured on Mavericks was Server 2.2.2. I deleted it and bought/installed Server 3.0. After Server 3.0's setup ran that only thing I had to do manually was start Postgres! My domain setting, DNS, all my web applications that were set up on Mountain Lion Server were all GOOD TO GO again on Mavericks Server!
I'm disclosing this here, publicly because it was a BIG PAIN to install and deploy all my websites using Mountain Lion's server app. To say the easy transposition into Server 3.0 was an unexpected and pleasant surprise amounts to massive understatement.
Now I'm going to describe two small anomolies I've noticed in either Mavericks or Server 3.0 that other users might want to be on the lookout for. They're not fatal. But they might be "habringers" suggesting underlying problems in either the new OS or the new Server's internals.
The toolbar icon for TimeMachine doesn't "spin" when it backs up. It's not a big deal. But it's convenient to see the circle around the clock whirling so we know when TIme Machine is backing up.
Mavericks Server isn't reporting newly upgraded apps as available under the Updates Tab of the Server's Software Updates subsystem. It might be inconsequential. But with a new OS version it never hurts to let the developers know about the "little things" that don't apparently work.
Kudos to the Maverick's developers for releasing an OS X version that's THIS CLEAN. And hugs to Apple's management for making it a free download upgrade for developers!!!
Full disclosue: I don't now and never have worked for Apple. but I do own a few shares of Apple stock that we purchased many years ago at $14.00 / share. I'm not a big shareholder. But based on my recent seamless upgrades to Mavericks and iIOS 7, I'm a happy one who's not likely to sell any time soon.
If Apple can do for ALL THEIR HARDWARE AND SOFTWARE PRODUCTS what they seem to have done for OS X and iOS, they've got at least a fighting chance to recover from their losses after their stock peaked at about $700.00 /share.
Keep up the good work!
Dr. Bob Blomeyer

After an new OS release that are always complaints about installation and configuration problems. First comers to using any new software tool provide valuable feedback we generally hope will help improve the new product. It's how things have worked since the first 6503 Apple II's and 8086 IBM PC's.
I've been using and upgrading PC's since THOSE DINOSAURS! And I can't remember EVER having an OS upgrade go as smoothly as my recent upgrade from Mountain Lion Server (OS X 10.8.5 w. Server 2.2.2) to Mavericks Server 3.0.
I chose to do a clean Mavericks install on a clean partition created on a 1 TB disk that was upgraded into my trusty MacBook. I used the DiskmakerX app to create a Mavericks installation USB drive. When the screen came up with the option to import users, programs & files (took a pass on email) from the Mountain Lion Server partition, I let it run overnight to transpose everything of value into the clean Mavericks installation.
The next morning the only program that wasn't PERFECTLY installed and configured on Mavericks was Server 2.2.2. I deleted it and bought/installed Server 3.0. After Server 3.0's setup ran that only thing I had to do manually was start Postgres! My domain setting, DNS, all my web applications that were set up on Mountain Lion Server were all GOOD TO GO again on Mavericks Server!
I'm disclosing this here, publicly because it was a BIG PAIN to install and deploy all my websites using Mountain Lion's server app. To say the easy transposition into Server 3.0 was an unexpected and pleasant surprise amounts to massive understatement.
Now I'm going to describe two small anomolies I've noticed in either Mavericks or Server 3.0 that other users might want to be on the lookout for. They're not fatal. But they might be "habringers" suggesting underlying problems in either the new OS or the new Server's internals.
The toolbar icon for TimeMachine doesn't "spin" when it backs up. It's not a big deal. But it's convenient to see the circle around the clock whirling so we know when TIme Machine is backing up.
Mavericks Server isn't reporting newly upgraded apps as available under the Updates Tab of the Server's Software Updates subsystem. It might be inconsequential. But with a new OS version it never hurts to let the developers know about the "little things" that don't apparently work.
Kudos to the Maverick's developers for releasing an OS X version that's THIS CLEAN. And hugs to Apple's management for making it a free download upgrade for developers!!!
Full disclosue: I don't now and never have worked for Apple. but I do own a few shares of Apple stock that we purchased many years ago at $14.00 / share. I'm not a big shareholder. But based on my recent seamless upgrades to Mavericks and iIOS 7, I'm a happy one who's not likely to sell any time soon.
If Apple can do for ALL THEIR HARDWARE AND SOFTWARE PRODUCTS what they seem to have done for OS X and iOS, they've got at least a fighting chance to recover from their losses after their stock peaked at about $700.00 /share.
Keep up the good work!
Dr. Bob Blomeyer

Mountain lion Server import accounts & mobile home folder

Similar Messages

Maybe you are looking for