Moving to Snow Leopard

Hi,
I did a clean install of Snow Leopard and then migrated from a clone the accounts, network setting and documents. I then reinstalled all of the applications. Everything works just fine but a good number of Color profiles for my printer (Epson Pro 3800) are missing. Does anyone know where these live so i can move them over to the new install?
thanks

I believe you would find them in the library in the colorsync folder.

Similar Messages

Just installed Lion on 2009 MacBook Pro moved from Snow Leopard - img. copies of movies will not play on DVD player

I have a MacBook Pro 2009. In order to get iCloud I have moved to Lion. Mountain Lion will slow machine too much. I now find that DVD player will not play the Disc Image .img movie files. When I open DVD player and click File and Open DVD Media, the Disc Image files are greyed out. The .dvdproj files are not greyed but if I click on them I get a message that "the media type is not supported". I could play the movies without any problem before I switched to Lion. The switch was done at the Apple store by an Apple Technician. Any idea what is happening?

Download and install VLC. http://www.videolan.org/vlc/index.html and get rid of DivX.

"Safari Can't Find the Server" is chronic in Safari under Snow Leopard...

Since moving to Snow Leopard (or perhaps it is just an updated Safari in SL and otherwise not related to SL??) when my Mac starts up from sleep with Safari being already open, I typically find a blank message with "Safari Can't Find the Server"... And just clicking on pages, I sometimes get that same message. Sometimes I get the spinning gear (for way too long) and I've learned to stop it and just click the same link again and more often than not, it opens immediately the second time...
Any ideas??? Is this a bug that Apple needs to fix or do I need to do something to Safari (or something else) to fix this problem???
thanks... bob...

Robert Paris wrote:
Whoa... Now I'm really confused... When I go to my System Preferences, then Network, highlight Airport, then click on Advanced, then choose the DNS tab, all I see under DNS Servers is the internal IP address of my Apple Router (10.x.x.x).. And next to that under Search Domains is hsd1.ca.comcast.net... And that is all there is... And I didn't set any of that up... When I bought my Apple Extreme Router a couple years ago, I was so impressed because I came home, plugged it in, basically said "GO" and the router set it all up and just worked... And I'm pretty sure (though not positive) that the Router put the 10.x.x.x in that preference panel, in other words, pointed to itself for DNS services...
This is effectively saying that the DNS configured in the router will be the default.
So help me understand... If I change the DNS settings on the mac from 10.x.x.x to the OpenDNS values, the router would still have the Comcast values in it??? How does that work??? And if I only change them on my mac, then the rest of the computers on my home network would still be using the original Comcast DNS servers as established on the router, yes??? I mean I think that would have to be...
If you change your Mac, that is what it will use. Other computers will use whatever
they are configured to use.
See my confusion??? Again, I know only enough about Network settings to know that if I click a wrong button I could make a lot of trouble... So I don't move until I understand what at least a little more than clearly I know now...
So how do local (mac) settings for DNS play (or not) with DNS settings up at the router level???
The local settings should override anything else since that is what will
be used first. They have no interaction with what is at the router level.
thanks... bob..
Dave

Logic pro 8 will not close in snow leopard

I have a quad core intel mac pro and have just installed Snow loepard, now when I run logic pro 8 I can not close it down (Logic pro 8) I have to force quit every time I finnish. Does anyone know if this can be fixed? (latest version of SL and LP8)

Hey Karl,
Not a problem!
Ah, I was hoping we'd finally find that there was something common that was causing this issue! I noticed that none of the AU instruments you are using are the ones I use, so it doesn't seem that this issue is related to any of those (I only use BFD2, Melodyne and Ozone)...
I am keeping my fingers crossed that now I've unticked the "backup to MobileMe" box, it will continue to allow a proper quit over the next few days! (Sometimes things seem to be fixed and then the next day the issue returns...!)
Let me know if you do get closer to a solution. I am using Logic 9, not 8, but the issue started when I moved to Snow Leopard 10.6.1 (I'm pretty sure... it was definitely some time after getting 10.6) and I believe we are having the same problem despite different versions of Logic.
Cheers,
Mike

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.

Will updating to Snow Leopard delete my files & prefrences

I just ordered the family pack. And was concerned about losing data while updating to snow leopard. What are general precautions before making such a giant change to my iMac?

I just ordered the family pack. And was concerned about losing data while updating to snow leopard. What are general precautions before making such a giant change to my iMac?
As a general rule it is a very good idea to have a full backup before doing a major upgrade, such as moving to Snow Leopard.
Assuming you have an external disk, SuperDuper (free version) or Carbon Copy Cloner would be very good choices to make that special pre-upgrade backup.
Historicall, you get 3 (and a half) installation options (on Friday we will know for sure), but they have been in the past
a) Upgrade in place, which replaces the operating system and leaves all applications and personal files alone.
b) Archive and Install, which moves the current OS into a saved folder, installs the new OS from scratch, but keeps all your personal files and a few global system preferences, such as your network settings.
c) Clean install, which erases the disk and creates a new clean file system. All your data is removed. Unless you have a backup, you will of course loose your data.
c and a half) Typically used for transferring your data from an older Mac to a new Mac. This allows you to attached your old Mac to the new Mac via Firewire and put the old Mac into Target mode, then the new Mac during system setup, copies over your old system settings, applications, and personal data.
This "c and a half" mode as I'm calling it, can also be used with an external disk containing a backup of your system.
I would only use this "c and a half" if something happened that causes you to loose your original data, and you were then using the backup.
It is always possible that Snow Leopard will have additional installation options, and we will find out Friday.

Migrating from Snow Leopard to Mountain Lion Server

Hi all. I kinda drop in and out of this forum, mostly when I've got a puzzler that I can't figure out. My journey from Snow Leopard to Mountain Lion was a little slow. I tried to make the transition from Snow Leopard to Lion and failed, but this time I made it and I thought I'd share a little scratchpad post I wrote to document what I did. Mostly this is about adding back a few things that I really need. Here's the list of stuff that I added back:
Firewall management (IceFloor)
MySQL
Webmail, email filtering rules and email aliases (RoundCube)
"Group" emails (short, multi-recipient email exploders)
Mailing lists (Mailman)
I also dramatically improved reliability by adding a lot of memory, and doing nightly-restarts of the machine.
Here's a link to the post
http://www.haven2.com/index.php/archives/migrating-from-snow-leopard-server-to-o sx-server-mountain-lion
I'm happy to report that the new server has been running for a month or so and all seems fine. Whew. A long journey. Thanks to all of you who posted things that helped me along the way. Hopefully this will return the favor.

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.

Upgrade from Snow Leopard Server to Lion Server hangs at configuring services...

I am running the Mac mini with snow leopard server 2.53 ghz 2GB of ram, 2x500GB hard drives, and have followed through the process to install Lion Server. The installation appears to be hung at the Configuring Services section of the setup process. I have left it for a couple of hours and nothing has progressed.
Should I leave it longer, hoping that it will work through the process (if in fact it is working through something)?
How long should this normally take?
As this is my work server, hosting mail, web, FTP, and file sharing, it is rather important to get it up and running as quickly as possible.
Any thoughts on how I can get it moving?
Hard power off of the Mac Mini reboots the machine, then proceeds back to the setup page, and then hangs on the same Configuring Services.
Any assistance would be much appreciated.
Thanks.

Lion Server Upgraders,
beware and proceed with caution.
Apple web site is naively optimistic on the upgrade process:
"To upgrade your Mac to OS X Lion, you don’t need to drive to a store, bring home a box, and install a bunch of discs. All you do is click the Mac App Store icon, buy Lion for $29.99, and your Mac does the rest. Just make sure you have what you need to download Lion to your Mac."
And then has a 3 step process...
This is completely miss leading.
Read this document first: http://manuals.info.apple.com/en_US/lion_server_upgrading_migrating.pdf
It will make it readily apparent that moving from Snow Leopard Server to Lion is not going to be simple.
Having done this twice now.. I have found that:
1. Open Directory migration is a weak point. Lion & Snow Leopard Open Directory are not compatible, so if you have masters & replica then expect trouble. I have an unresolved issue trying to get a simple Lion Server to Lion Server Open Directory replica up and running. This compatibility seems to also cause migration to fail, as I found that all my local User/Groups transferred ok but non of the /127.0.0.1/LDAPv3 (Open Directory) ones did. This is a very important item, as all the mail accounts in dovecot use LDAP generated UID, so you have to be careful that you do not loose mail accounts.
2. Mail - your mail aliases will not transferred, so you will need to reapply the aliases.
3. Web Server Setup - This broke, under migration as I gather the entire Web serving tree has changed. In particular I had "Snow Leopard" Web Mail (which is based on Squirel) on my "Snow Leopard" Server and this is now dead...
4. Digital Certificates - I found that the valid (ie signed by trusted CA's) did not get migrated, so I had to re-imported my Digital Certificates. If you have paid for third party CA certificates then make sure you have got these copied somewhere, as if you loose them then you will likely need to go to your provider and get a certificate revocation and new certificate, which will cost you money!
Cheers,
Zebity.

Snow Leopard: calendar contents lost

I upgraded from Tiger to Snow Leopard (purchased the "Mac Box Set" which included Snow Leopard, iLife 09 and iWork 09). Although the calendars I created under Tiger are still listed, their contents are no longer displayed. Any chance I can recover the contents of these calendars? No, I do not have a back up (part of the reason of moving to Snow Leopard was so I would have time machine to recover from such problems).

This happened to me as well when I upgraded straight from Tiger to Snow Leopard. Everything transferred fine except iCal. (Come on Apple! You're supposed to make **** like this seamless!)
I tried everything suggested in the following articles- none of them worked.
http://support.apple.com/kb/TS1906
http://discussions.apple.com/thread.jspa?threadID=1364074
http://support.apple.com/kb/TS1880
I do have Backup, but I couldn't even restore my iCal from that after trying multiple times from different backup files in multiple ways (so don't feel bad you didn't have Backup- it's not working anyway!).
After searching endlessly and trying everything, the only way I was able to get my Calendar back was to get it from my iPhone (which I'd been avoiding syncing because I was afraid my Mac might overwrite its calendar with emptiness). It prompted me by saying there was a big discrepancy and what should it do (I told it to proceed with adding events to my Mac's iCal). So that worked when nothing else would.
But maybe some of the above articles will work for you. Just wanted to get my experience out there in case anyone else is in the same situation.

Restoring multiple Snow Leopard calendars in Lion?

I was able to restore my old mail by following the instructions here:
http://macs.about.com/b/2011/08/05/moving-your-snow-leopard-mail-to-lion.htm
At the bottom, in the comments, it says you can do basically the same for calendars in iCal (and he gives the iCal-specific instructions).
I have been trying to do this for iCal, but it doesn't seem to work. There is no 'updating/importing' message, and the old calendars don't show up. As a matter of fact, once I have opened iCal, the ~/Library/Calendars files I restored from Time Machine disappear. I only have the default, empty calendars for Home, Work, and Birthdays and none of the 12 or so calendars I had in the Snow Leopard version.
The only step I have skipped in his instructions are the keychain part. I had restored my keychain back when I successfully restored my mail with these same instructions.
At first I thought maybe the Lion version of iCal could only do those 3 calendars; but now I've seen mention of people who were able to restore multiple calendars from the old iCal. However, I haven't found any other instructions on how to do this.
What am I missing? How can I restore my old calendars to the new iCal?

Well, alrighty then! I had tried my 1st set of steps (at the link I included) three times without success. I tried them one more time, but wrote my message above before looking, assuming that there was no way the same thing would work.
When I opened iCal and went to the Calendars button to look for the 'Go Offline' selection - my calendars were there! I have no idea what, if anything, I did differently to make it work, but they're all there now, and correctly showing in the calendar once I clicked the checkbox to select each calendar to show. (They're categorized as "on my mac".)
As for the 'Go Offline' option? It wasn't there. It was, though, under Calendar (no 's' on the end) on the menu.
I then exited iCal (fearing that they might disappear as you described, MadisonP), and came back in. They are still listed, but they didn't stay checked. I have to manually re-check the checkbox to select to show them again.
I'll try your export portion to see what happens and get back with you. Thanks for the help!

Keyboard viewer on my iMac (running Snow Leopard) recently has lost small size. Green " " button is just moving big keyboard size up. I would appreciate a hint how to fix it. Alex

Keyboard viewer on my iMac (running Snow Leopard) recently has lost small size. Green "+" button is just moving big keyboard size up. I would appreciate a hint how to fix the problem. Alex

You can resize the keyboard window, positioning the mouse pointer at the edge of the window, clicking and dragging to the desired size.

I've moved to Mail 4.0 in Snow Leopard. Very nice.

After a long stretch with a combination of Thunderbird and Entourage, the exchange server support in Snow Leopard caused me to take a new try at Mail 4.0. I was surprised at how easy it was for Mail 4.0 to get connected to my work's exchange server. I can also now accept or reject calendar invitations from work directly from within Mail 4.0. I've also setup Mail 4.0 to access my gmail via IMAP. I'm surprised at how fast Mail 4.0 is compared against Entourage and Thunderbird. Very nice.

I just moved from entourage to mail 4 in Snow Leopard. I am on an exchange server. All my emails, contacts and appointments came over to Mail 4.0. But I have one Project in Entourage that I cannot see or find. Does anyone know if Mail 4.0 will support Projects that is in Entourage and Outlook?

Copying and Moving Mail from Snow Leopard to Lion

Hello
What is the best way to move mail data from a Snow Leopard machine to a Lion machine?
My mail data is presently on my iMac which is running Snow Leopard. I want to copy and move this mail to my new MacBook Air that came installed with Lion (not an upgrade from Snow Leopard).
In the past, it was just a matter of copying the "mail" folder in the library and the plist and pasting them in the same location on the new machine. However, I have read that this does not work any more.
What is the best way to do this?
Looking forward to some guidance.
Cheers!
Darren
Tokyo

Hi ozdazza,
I have managed to solve the problem and move all my emails from my old mac running 10.5.8 to my new mac running 10.7.2 with the following steps. Please note that in order for these to work, you need to have copy of your old email accounts either at your new mac desktop or in your time machine (or any external HD connected to your new mac)
1- In my new mac, I created email accounts similar to the ones in my old mac (names and setting),
2- I copied my old emails (one email account at a time so I do not get confused) and placed it on my new mac desktop. Please note that inbox messages in OS 10.5.X are stored in user/library/mail/pop.file/inbox.mbox. And outbox messages are stores in user/library/mail/pop.file/outbox.mbox and so forth. For copying messages in your inbox the file you should copy to your desktop is the inbox.mbox NOT the mail file or NOT the pop file.
3- Open your mail app in your new mac and chose “import mailboxes” under file menu.
4- Chose import data from “Apple Mail” which is the first choice.
5- Chose the inbox.mbox file to be imported.
6- After the importing process finish, you will see all your messages in a new folder called “Import” in your mailboxes column within your new mail app.
7- Now click on that import box to display all your messages in the middle column in your email app.
8- Highlight all the messages by clicking comm+A
9- Drag all the highlighted messages to your newly created inbox.
10- After the drag&drop process finished, you can delete the import box.
Above process can be done with the sent.mbox as well, but in such process you use the sent.mbox for old email account and drag its messages (step 9) to the sent file in your new email account box.
I had managed to move or transfer 3 emails account each one with 2 boxes (inbox and sentbox) with a total size of over 8GB in only less than 10 minutes.
The key problem in all my previous import attempts is that I was importing the wrong file and trying to place it in the wrong place.
I hope above process works well for you as it did for me.

Moving accounts from Snow Leopard Macs to Mac mini with Snow Leopard Server

I got my brand spanking new Mac mini today with Snow Leopard Server! So far, we (at home) were managing our accounts on individual iMacs and a MacBook Pro. While I will be getting into the innards of account migration, management etc. I thought I'd post a quick question here; Currently I have an iMac with three user accounts on it (wife and two kids). I also have my own personal MacBook Pro with my account (the only Admin account) on it. We'll soon be getting another iMac for our daughter (who currently has an account on the existing iMac). My idea in getting the Mac mini was to move to and centrally manage all the user accounts in the household on the Mac mini server. What is the best way to accomplish this? What is the best way to move the existing accounts on to the server?
Additionally, I'll be looking into connecting the two stationary iMacs with Powerline Ethernet (where one runs Ethernet over existing electrical wires in the walls). My other option would be to rely on wireless network (I don't think this would be a good idea for if I am going to be placing the user accounts on the server and there needs to be a constant on, reliable connection between the server and the client computers as they will be talking to each other a lot!). Any thoughts on Powerline? (I am not looking forward to installing Ethernet cabling behind walls :o))
What say the wise men of Mactopia?!
Thanks,
Kenneth.
P.S. I had earlier accidentally posted this in the corresponding section of Mac OS X instead of the Mac OS X Server forum.

Ok so the esiest way to explain this is to tell you what i just went through.
I have 3 user accounts. All the accounts are network Users meaning that there home folder are kept on the server. I was having a problem with Time Machine giving me error 41 and error 11. After scratching my head for 2 days I ended up copying (Drag-n-Drop) the Home Folders to an External Hard Drive. I then proceeded to erase both of the internal hard drives on the mac mini and did a fresh local install of the Server OS.
Everything was fine at that point. Now this is where Snow Leopard stopped being nice.
I went and Created the user account again using WGM. I let WGW create the home folder and the 9 folder inside. I made sure the short names were the same and the passwords were the same as they were previously.
However, once i Copied files from the external drive to the home folders the permissions copied as well, Which i guess should be expected. So now at this point apparently the UID's of the newly created users wasn't the same as they were before the clean install. I have multiple instances of root listed in the ACL for several folders and also had several instances of System listed sporadically.
Now, This isn't to say that you can't drag n drop because now That I have it all squared away and everything is now working ok, I would probably still drag n drop the home folder off to an external disk, but only because I now know what to do to clean things up.
if you drag and drop be sure to use the CHOWN command and theCHMOD commands afterwards. Take a look at this MacFixIt article: http://reviews.cnet.com/8301-13727_7-20013630-263.html?tag=mncol;title
If you copy your local imac users to the home directory on the server you may want to follow the steps on the URL I gave plus you will most likely also have to do the following. In a nutshell you are going to use the chmod command to strip all the ACL Permissions then you are going to use the chown command to re-specify the correct owner and the correct permissions for the network user.
!) Go into ServerAdmin and click on Sharing
2) Go to the users folder you are using and select the user you are going to work with.
3) Click on the Permissions option
4) click on the +sign at the bottom (this will open the users & groups list to the right)
5) Drag the current user from the users list to the owner permissions line under posix section
5a) Click Save
6) Click on the Gear button at the bottom
7) Check the box for Owner Name and Owner Permissions.
8) Uncheck the box for Access Control List then click ok
Once you've gone through that rigmarole you can go back into ServerAdmin and fix the permissions for public and Sites folder which should only take a minute or so.
So the moral of this story and as I found out when i ended up calling Enterprise support is that the act of dragging and dropping user home directories from one server to another, or as in your case, from a local machine to a the server isn't anything that apple recommends or supports. you might want to read through the man pages for "Ditto" or so apple tells me, but honestly now that you know, the steps above aren't all that bad. It's true Knowing IS half the battle!
have Fun!
P.S. FWIW If you run into problems and have to call Enterprise Support be prepared for them to tell you to refer to the user Guides. So reading those would be to your advantage even though they aren't the easiest things to understand unlike apple's consumer products user guides

Moving TM backups using Finder in Snow Leopard

It has been suggested by Apple to some users that in Snow Leopard the folder backups.backupdb containing all TM backups can be copied from one hard drive to another if one wants to migrate TM backups to a new drive. It is also suggested in this kb article
http://support.apple.com/kb/TS2986
that one can just move this folder around on a single drive if necessary.
I've tested this extensively and and found this advice to be mostly false. Copying the backups.backupdb folder using Finder does work technically but it completely destroys all hard link structure. this means that one should expect the total space taken by the backups to increase by a large factor. for example, if you are backing up 100GB of data and have about 10 TM backups, after you copy the backups.backupdb folder to a new location (on the same drive or on a different drive) it will occupy 1TB of space there. if you don't have enough space the copy process will fail.
Note that due to the use of hard links the original backups will occupy much less space on the drive, usually, less than 150GB in the above example.
This restriction makes the process completely unfeasible for all but the smallest backups with very few incremental backups existing.
the only situation where the hard link structure is preserved is if you trash the backups.backupdb folder and then use the "Put back" feature to get it out of trash.
Therefore I would still recommend never to move this folder (or anything in it) using Finder. Migrating TM backups to a new drive should still be done using a cloning tool like Superduper or using the restore tab in Disk Utility.
Message was edited by: V.K.

I was surprised to note that it took nearly the same amount of time as the Restore tab of Disk Utility (which I'd expected to be faster). So the only advantage I can see, even if it worked reliably, would be the ability to get the backups off a partition that has other data on it. Guess I'll have to change the FAQ yet again.
Mumble, grumble.
I still haven't heard back from them about the other issue where they changed the FAQ, about no full backup after a full restore, where you and I also get different results. Maybe I'll press the issue and add this one.
I'm also working one that you may have seen, where a +Verify Disk+ on the boot drive somehow interferes with TM's ability to find changes from the +Event Log,+ until you do a Restart. Two or three other folks have seen it, too. That one I reported to Apple Care last Wednesday; they said I'd hear something in 24-48 hours . . .

Moving to Snow Leopard

Similar Messages

Maybe you are looking for