Upgrade from OS X Server 10.6.8. to 10.7.

Hi
I have a mini mac server running 10.6.8. I just recently had to flatten the disc 'cause server was slower than slow. Before I flattend the server I was already running 10.7.3.
Now the problem starts. I booted up with the supplied CD (version 10.6.) deleted the partition and freshly started to install. .....and install....and install. Then I did the usual automatic updates etc. until 10.6.8.
Since I previously bought the App Store update to 10.7. I pulled it down again for installation but now I get the message "You can't use this version of the application Server with this version of Mac OS x. You have 10.6.8. The application requires 10.7. or later......
What am I doing wrong???? Any Ideas? Do I need to update to OS X 10.7. (desktop version)?
Thanks

For the upgrade approach, first determine if your current (presumably Xserve?) server supports OS X 10.8 (client), then (if so) purchase OS X 10.8 (client), then purchase and install Server.app. The OS X client upgrade will leave the server bits alone, and the Server.app server installation should detect the server bits and upgrade them.
One or more backups are strongly recommended.
The other approach is a new server, and migrating individual service settings and data manually. This is far more work.

Similar Messages

Upgrade from Windows Home Server 2011

Even though Windows Server 2012 Essentials is being mentioned as a replacement for Windows Home Server 2011, there doesn't seem to be any documentation or mention of can you upgrade from Windows Home Server 2011 to Windows Server 2012 Essentials?
Will this work with the beta download and will we then be able to upgrade this version to the RC and/or release version?
As you may guess I have a Windows Home Server 2011 and am interested in looking at Windows Server 2012 Essentials to see what it offers me. The storage spaces sounds exactly what I want to replace the drive extender on the previous home server version. The
problem is that I don't mind sacrificing my present server box by installing the beta but it would be nice if it actually retained what settings it could via an upgrade option, which I could then have a chance of using with a proper release version.

Just clarifying about the 'upgrade path' and 32b vs 64b.
Yes, no in-place upgrade. However, one could theorise about some form of 'migration' being possible, where the list of users, the content of your shares, the current backups, would be 'moved' from old box to new.
I was in fact pretty sure no such process existed. (Wouldn't it be neat though? AND in future _at least theoretically_ possible, using processes similar to SBS AD migration.)
From this perspective putting the new box onto the network is similar to replacing WHSv1 with WHS11, in that nothing is carried over. No gain, but no lesser. Working on currently available information.
The later comment about the work laptop is, TTBOMK, a resounding 'NO'. When attempting to join a member of another AD the 'connect' process stated 'You must 1st remove the PC from the other AD'. I haven't tested this extensively but believe that PC's _capable_
of operating in an AD (Pro, vs Home, versions) will be made members of the WS12E AD. It is only PC's that do not have 'domain join' capability that are left in workgroup mode.
TTBOMK, AFAICS, so far, etc...

How can I upgrade from os X server 10.6.8 to the 10.8 server

I want to upgrade to the current version of x server from 10.6.8.
The available pathways to get there do not seem to exist.
How does one accomplish this?
Thanks...

For the upgrade approach, first determine if your current (presumably Xserve?) server supports OS X 10.8 (client), then (if so) purchase OS X 10.8 (client), then purchase and install Server.app. The OS X client upgrade will leave the server bits alone, and the Server.app server installation should detect the server bits and upgrade them.
One or more backups are strongly recommended.
The other approach is a new server, and migrating individual service settings and data manually. This is far more work.

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.

Upgrade from Oracle Web Server to Oracle 9ias(9.0.4).

Hi,
I want to upgrade Oracle Web Server to Oracle 9ias(9.0.4).
Can anybody please tell me what are the pre-requisites for this and where can I find the documentation for this?
Regards - Sachin

Hi Sachin,
If you are indeed running Oracle (Web) Application Server 4.0.8.2 or similar, the best way to upgrade will depend on what applications that you are running.
There are upgrade guides from Oracle (Web) Application Server to Oracle Internet Application Server 1.0 as well as guides from 8i to 9i and 10g avaliable under documentation here at OTN.
The latest version avaliable right now is 10.1.2.0.2. It might make sense to go to 10.1.2.0.2 than to 9.0.4 at this time.
Regards,
Mathias

ASW Upgrade from 10.4 Server to 10.5.. anyone having Serial Number problems

i have successfully upgraded 10.4.10 sever on a PPC mac-mini with a gig of ram to 10.5, but the ASW provided Serial Number is not working for me.. anyone else having this problem?

I've got news for you, guys-- it isn't just serial numbers from ASW. I'm trying to upgrade a customer server from the ASW tryout using a 10-client retail 10.5 serial number, and I'm getting the same thing. I love how the "protection" built into the system is resulting in difficult installs/upgrades. First the artificial hardware exclusion (a PBG4/867 w/ no L2 will work, but a Dual 800 w/ 2MB L2 won't???), now the "expired" serial #. Oh, and Server Admin is so obsessed w/ showing me the spinning beach ball that I cannot yet select the server in question and fix the serial # problem remotely!
Fun! Fun!
Fredo

Upgrade from a 1-server config to a 2-servers config

I'm wondering if it's OK to use this upgrade procedure:
- server1 is active but no replication configured (serves traffic)
- add server2, configure and start replication
- set server2 active (both servers accept traffic but no data replication done)
- stop traffic on server1, configure and start replication
- set server1 active; if a replication threshold has been reached on server1, start a duplicate procedure
- both servers accept traffic and DB are synchronized
This has the advantage of presenting no interruption of service, but I'm not sure it's the right way to proceed (do we need to force a duplicate even if no replication threshold is reached on server1?).
The alternative would be to stop both servers, configure and start replication on both, then set server1 active, start the duplicate procedure on server2 and set server2 active. This has the downside of not serving any traffic while both servers are being configured.
Christophe

Hi Christophe,
This is not really the correct procedure for this and would likely run into problems with e.g. consistency etc. The correct procedure is mush simpler actually:
1. server1 is active (serving traffic) but no replication is configured
2. Prepare server2 (install TimesTen, creste DSN definitions etc.)
3. Configure replication scheme at server1, including of course the definitions for the (not yet existing) datastore on server2 and start replication agent
4. Create datastore on server2 via a 'duplicate' operation from server1 (be sure to specify -setMasterRepStart)
5. server2 starts to serve traffic
This is the standard procedure for rolling out a replicated environment; it does not interrupt service at server1 and it ensures complete synchronisation of both datastores.
Regards,
Chris

Upgrade from OS X Server 10.8.5 to Server 10.9

I have a mini Mac running OS X Server 10.8.5 and would like to upgrade to Mavericks Server.
I see the download for Mavericks, which is the desktop OS. I also see that there is a Server App option for $19.99 USD.
What are the recommended steps?
I want to easily upgrade my server to the latest without being required to re-configure all server settings. Will this be preserved in the process?
thx

Step 1. Backup your current server (full disk is preferred)
Step 2. Stop all non-essential services
Step 3: Install Mavericks
Step 4: Install Server.app
Step 5: Run Server.app and cross fingers
Step 6: Active services disabled in step 2
Step 7: Test and hope you don't need to restore from the backup in step 1
In a nutshell, those are the steps. However, in more depth is that you analyze what your server is doing and what your risk level of the upgrade is. What services are you currently running? What impact will the upgrade have to your environment? If there is a problem, what impact to the workflow will there be? Etc.
In a perfect world, applying Mavericks + Server.app to a 10.8.5 system will just work. In reality, there may be service migration issues. The healthier and more "by the book" configuration of your 10.8.5 system, the easier the migration.
The important piece here is backing up your current server and having a restoration plan in the event that the upgrade fails. If you are hosting services like mail, contacts, calendars, I would also suggest disabling port forwards until you validate the upgrade was successful.
R-
Apple Consultants Network
Apple Professional Services
Author "Mavericks Server – Foundation Services" :: Exclusively available in the Apple iBooks Store

Upgrading from Crystal Reports Server V0 to V1

We're looking into upgrading Crystal Reports Server V0 to V1. According to the upgrade guide we have to do a complete uninstall of our V0 before installing V1. It seems risky to uninstall before we have a working version of the upgrade. Wondering if anyone out there has gone through this process and if so what were your experiences? Did you have a method to test the upgrade process before uninstalling V0?
Thanks!

Ajith,
Thanks 4 ur response, but when I ge there, all i could see is web page with the following
SAP BusinessObjects packages and products
>Address Directories
>SBOP EDGE INTEG. FOR SAP SOL.
>SBOP INTGR. FOR SAP
Unable to find the Business Objects Product Version you require?
As part of the migration from the legacy ESD site, every effort has been made to ensure all legacy products have been transferred from the ESD site to the SAP Support Portal.
There are exceptions where some products are now only available in physical format. These products are outlined below:
Crystal Reports Visual Advantage 2008
Crystal Enterprise 10
Crystal Enterprise 8.5
Crystal Enterprise 9
Crystal Reports 10
Crystal Reports 8.5
Crystal Reports 9
Crystal Reports Server XI
SECAM 6.5
WAREHOUSE
If you require any of the above, you can request a copy of the media using the message component XX-SER-SWFL-SHIP.
If you identify other products that you feel should be visible in your SMP account, but are not, you can also raise a message using component XX-SER-SAPSMP-SWC.
BusinessObjects Temporary License Keys
Find all the necessary information on how to receive temporary license keys on the Licence Keys page of the SAP Service Marketplace.
On the License Keys page you will also find all the requirements that need to be fulfilled for obtaining a license key.
The temporary license keys will be valid for four weeks.
What do I do from here? Do i have to raise a message ?
Thanks

Upgraded from 10.9 server 3 to yosemite server4.0

As above and now my internal ASUS is not working.
I can see the server has downloaded all the updates from Apple
However all clients get Cant load data from the Software update server
Please help
Thanks

Hi Mark,
I'm sorry to hear you are having issues with your recent Server update. While the following articles may not directly resolve your current issue with the internal Software Update service, you may find them helpful in narrowing down the cause (apologies if you have already seen them):
OS X Server: About the Software Update service - Apple Support
Using OS X Server's Software Update service with multiple Mac OS X client versions - Apple Support
Requirements for Software Update Service - Apple Support
OS X Server: Software Update Service compatibility - Apple Support
Regards,
- Brenden

ADWS Broken after in-place upgrade from Server 2008 R2 to Server 2012 R2

I performed an in-place upgrade from 64-bit Server 2008 R2 to Server 2012 R2. This machine ran Active Directory Web Services. After the upgrade ADWS will not start. I get the following event log error:
Log Name:      Application
Source:        .NET Runtime
Date:          11/21/2014 3:23:02 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      COMPUTER
Description:
Application: Microsoft.ActiveDirectory.WebServices.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException
Stack:
   at System.ServiceModel.Channels.CommunicationObject.Close(System.TimeSpan)
   at Microsoft.ActiveDirectory.WebServices.WindowsHostService.StartService(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-21T20:23:02.000000000Z" />
    <EventRecordID>65596</EventRecordID>
    <Channel>Application</Channel>
    <Computer>COMPUTER</Computer>
    <Security />
</System>
<EventData>
    <Data>Application: Microsoft.ActiveDirectory.WebServices.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException
Stack:
   at System.ServiceModel.Channels.CommunicationObject.Close(System.TimeSpan)
   at Microsoft.ActiveDirectory.WebServices.WindowsHostService.StartService(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)
</Data>
</EventData>
</Event>

I compared the registry with a working system but the Counters - and all other keys - looked fine.
At the same time as upgrading a DC a colleague was updating an unrelated server, and he started to see similar events in the event log (but for the Dell OpenManage Essentials service, not ADWS). The error was complaining about KERNELBASE.dll which set my
spider sense tingling. We knew that this server had Windows Updates pending. Fully updating it solved the problem on that server.
I solved the ADWS problem in the end by fully Windows Updating the DC. In particular, the ADWS Service started successfully after installing KB2919355 and rebooting. That also
'unlocked' a further 59 updates pending.
After the in-place upgrade I always fully Windows Update but I'm 99% certain that KB2919355 did NOT show up when I did a Check for Updates straight after a reboot so I thought the DC was up-to-date. I then spent hours investigating the ADWS problem and rebooted
as part of the diagnostics. It was then that I noticed on the logon screen that there were updates pending...
Moral of the story? Windows Update, then Update again, and again, and again. The length of time it takes to Windows Update after an upgrade from 2008R2 to 2012R2 is painful though.

In place upgrade from Windows Server 2000 to Windows Server 2003 ADS

Hi...is anyone aware of any issues with performing an in place upgrade from Windows 2000 Server to 2003 Server, which is currently running ESSBASE? Please advise, if you have any information. Thank you.

You can post your question in ESSBase forum
Essbase

Upgrade From Snow Leopard Desktop to Snow Leopard Server

I just installed Snow Leopard on my Mac Pro and it's running great! I upgraded it from 10.5 and it worked just fine for me. I was looking at the Snow Leopard Server and all the features it offers for the other Macs on my home network. My question is this: Can I install Snow Leopard Server on my Mac Pro without having to do a clean install? I have everything set up perfectly and I really don't want to have to reconfigure everything.
My other question is, besides the server software, is there any difference between the server and desktop versions? More specifically, am I still going to be able to use my audio creation/editing software and play the few games I have? Does the server strip out any functionality or is it exactly the same thing as the desktop version, but with added server tools?
Thanks in advance for your input!

1. No, you cannot upgrade from Client to Server. You will need to erase and install.
2. Generally, you can do the same things. It isn't exactly the same, even ignoring the server tools. Are there some things that won't work? Maybe. Namely because developers don't typically code with MOSXS in mind.
My question to you is this: What do you want from MOSXS that you cannot do with the Mac OS Client? And are you set on using it on your Mac Pro?
I ask because:
1. Client does most of the thing people want to do that are "server" like.
2. It isn't a good idea to mix server and production environments. OS X Server is typically easy to setup for basic operation, however, there will be issues and you will have to dig a little to get things working. Which means you will stopping and starting services, issuing terminal commands, modifying plists and .confs and rebooting. Sometimes it goes so wrong that you have to reinstall.
This is why if you are serious about a server, you should really consider a separate machine. The Mac Mini is a great option for a light duty server.
Also, carefully consider your needs. Can the things you want to do be accomplished with OS X Client and maybe a few web services. Not trying to sway you either way, but it isn't always as simple as "Click the Start button and the service is working."

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

LDAP Change in Upgrade from CRS XI to CRS 2008

We are in the process of upgrading from Crystal Reports Server XI R1 to Crystal Reports Server 2008 R1. Both systems are up and operational on separate Windows virtual servers. The old XI installation was using LDAP authentication from a SUN server. The new 2008 installation is using LDAP authentication from an IBM Directory Server.
The question that I have is related to using the Import Wizard. Since we have different third party LDAP authentication vendors and both are operating correctly right now, can we export all of the users, groups, folders, objects, instances, etc from the XI box to the 2008 box? I know we have to import everything together in order to preserve security, but will it work with different types of LDAP users? The LDAP group is different and I wasn't sure if CRS 2008 would recognize the users from the other LDAP group. I cannot find any documentation on changing LDAP server types for an import.

Sorry for the confusion, I did not state that question very clearly. That is exactly what I meant. There is only one group for LDAP that we are not using for security. We have Enterprise groups that we have created that we are using for the bulk of our security setup. I'd like to import the Enterprise groups then assign the new users to imported Enterprise groups.
Thanks so much for your response. It was very helpful!

Upgrade from OS X Server 10.6.8. to 10.7.

Similar Messages

Maybe you are looking for