DNS Changes (Mountain Lion Server & Airport Extreme)

I'm using a Mac Mini Mountain Lion Server with a Airport Extreme Router. The router is currently providing the DHCP funtion. Is it possible to change the DHCP settings on the router to use the DNS server on the Mac Mini Server rather than the one in the router.
I can't see any setting on either the Airport Utility or the Server App I was wondering if the DNS Server setting could be change via the comand line.
Many Thanks
Darren

Hi Darren,
Have you tried putting your Airport Extreme into Bridge Mode? That should enable you to use the DHCP service on your server.
Regards Alan

Similar Messages

Mac Mini/Lion Server/Airport Extreme Won't Sleep...?

I am at a loss with this one. I have a Mid-2011 Mac Mini running OS X 10.7.4 Server (11E53) connected via gigabit ethernet to an Airport Extreme. This computer will not sleep on its own using the system sleep timer.
If anyone has any ideas that may help, I'm all ears! The Mac Mini should sleep as intended and the Airport Extreme router should wake it if network resources are requested via a Magic Packet. This same Airport Extreme does wake the other computers on the network just fine when they are configured to Wake on Lan (womp 1 in the pmset -g output, below).
The server is configured to offer the following services: file sharing, Time Machine and screen sharing.
The power saver settings on the Mac Mini are configured to sleep in 45 minutes, turn the screen off in 1 minute and wake for network access is enabled. The output of pmset -g is below for reference:
Active Profiles:
AC Power                   -1*
Currently in use:
hibernatemode      0
disksleep          10
womp               1
networkoversleep   0
sleep              45
powerbutton        1
ttyskeepawake      1
hibernatefile      /var/vm/sleepimage
autorestart        1
panicrestart       15
displaysleep       1
If the Mac Mini is manually placed in sleep mode, via the Apple Menu or the button on the Login Screen for example, then it will sleep just fine. While the Mac Mini is sleeping, it will wake properly when the shared resources are accessed via another Mac on the network. For example, if the Macbook Pro tries to begin a Time Machine backup using the Time Machine Server on the Mac Mini, it will wake just fine and the backup will complete with no issues. The Mac Mini will not sleep again using the system sleep timer and must be manually put into sleep mode.
There is one printer (Canon MP560) installed on the Mac Mini, connected via USB, not shared on the network and no print jobs stuck in the print que.
I tried using the PleaseSleep software but that causes problems when the Mac Mini is used via Screen Sharing. When the Mac Mini is controlled remotely via Screen Sharing, PleaseSleep waits about a minute into the session and forces sleep mode, cutting the session short prematurely. This is unacceptable.
Also, there are no assertions that would prevent system idle sleep using the system sleep timer, as seen in the pmset -g assertions output below:
6/20/12 4:51:02 PM EDT
Assertion status system-wide:
   PreventUserIdleDisplaySleep             0
   CPUBoundAssertion                       0
   DisableInflow                           0
   ChargeInhibit                           0
   PreventSystemSleep                      0
   PreventUserIdleSystemSleep              0
   ExternalMedia                           0
   DisableLowPowerBatteryWarnings          0
   EnableIdleSleep                         1
   NoRealPowerSources_debug                0
   UserIsActive                            0
   ApplePushServiceTask                    0
Kernel Assertions: 0x0012
* Kernel Assertion ID = 500
   Created At = 12/31/69 7:02:29 PM EST
   Modified At = 12/31/69 7:00:00 PM EST
   Owner ID = 0xffffff80122f0000
   Level = 0
   Assertions Set = None (4)
* Kernel Assertion ID = 501
   Created At = 12/31/69 7:02:33 PM EST
   Modified At = 6/18/12 10:34:22 PM EDT
   Owner ID = 0xffffff8012302000
   Level = 255
   Assertions Set = None (4)
* Kernel Assertion ID = 502
   Created At = 12/31/69 7:02:57 PM EST
   Modified At = 6/20/12 4:05:41 PM EDT
   Owner ID = 0xffffff801238ee00
   Level = 0
   Assertions Set = None (32)
* Kernel Assertion ID = 503
   Created At = 6/18/12 10:32:27 PM EDT
   Modified At = 12/31/69 7:00:00 PM EST
   Owner ID = 0xffffff8011f22c00
   Level = 255
   Assertions Set = None (8)
* Kernel Assertion ID = 507
   Created At = 6/19/12 10:56:46 PM EDT
   Modified At = 12/31/69 7:00:00 PM EST
   Owner ID = 0xffffff8018b1c400
   Level = 255
   Assertions Set = None (8)

I Have the same issue with pleasesleep.
No ARD Session without sleep ;-)
My stup is a little bit different to yours.
My MacMini act as an HTPC for Plex and it dosent sleep as well.
I guess it has something to to with External USB HDDs or in your case printers or USB Hubs or etc. etc.
I found a AppleScript called Nacrolepsy 2.0
It dosent work probebly right now but I hope It could be a solution in the near future.
Take a look at
http://blog.schreiter.info/narcolepsy-2-0-for-mac-os-x/

Mountain Lion Server 10.8 DNS ERROR READING SETTINGS

Hi! Well I changed from windows 2008 server to Mountain Lion Server. So far, I have been able to set up website hosting for one website, and I must say works better than windows server 2008, maybe thats because the mac keeps the drive spun up, while in windows server it was an external drive, whatever the issue mac serves up the site much faster that it comes exploding onto the screen of the searcher.. Then I went to try to set up email, I was totally excited, but I think I did a no no in the dns settings, and now, I cant even see them, I just get "Error Reading Settings" Of course I see things in the log that I should undo, but I cant access the DNS settings at all. Any ideas how I can get to the dns settings so I can undo my booboo? Now it has streched its error self into the file sharing, and I cant access those settings anymore either, so that means I cant set up other websites because I cant give permission to view those folders. I also just got another err saying "Multiple errors occured on this server while processing commands. Just exactly what the heck did I do? I must have REALLY SCREWED THIS THING UP! Also strangely Safari browser no longer acceses the web from the server computer. I THINK I KILLED IT.
Any Ideas?
Thanks I really appreciate any tips, I havent got to calendar or vpn, or any fun stuff yet.. Or maybe it might not be fun at all? hahahahahaa!
Thanks

I've gotten into this mess as well and Apple solved it for me.
The Server should be able too lookup itself so running DNS is a good thing, actually the server sets up DNS at install time if it can't find a server to serve it's DNS so it can lookup itself.
The main error in my case was that there wasn't a NS record pointing the machine itself and that there were some firewall rules preventing DNS lookups. Since there is no way to edit the firewall rules via GUI the engineer manually changed some stuff, but wasn't sure where the problem lies exactly, so he passed it on to another engineer.
At this point I was already forced to switch to Google Apps for Business and my website was already running at GoDaddy, at much lesser costs and to much lesser frustration I might add.
Let's face it, Apple has to deliver a better product with the old Server Admin back into place for those who want it for the extra control.
My servers were running great with Lion (eventually), but Apple just had to remove Server Admin from OS X Server... #their_loss

How do I properly change the server name in mountain lion server?

I need to change my server name to a FQDN, but tried this with Lion server in the past without success. I know in lion you'd use server app, but that's no longer avaiable in mountain lion server and I want to make sure I get this right the first time.
Thanks!

I was able to get everything working with some assistance from Apple's enterprise support. After changing the host name, the DNS was still not resolving properly and I couldn't turn on open directory so that I'd be able to start profile manager. The DNS interface is considerably different than that in previous versions of server. The network was set to manual ip with dhcp, which was pulling back an external IP. Overriding the DNS info coming in via the dhcp, setting it to localhost, resolved the issue.
Thanks!

How To Set Up Mountain Lion Server/Point DNS to Mac Mini Server

Hello, First of all I have no experience with setting up servers whatsoever. Below is what I have
- Mac Mini with Mountain Lion Server
- Time Capsule as my router
- Comcast as my service provider
My goal is to set up my MacMini as a sharepoint for files and other data with my other partners.
- I have purchased a domaine name from NetworkSolutions. Does this mean that they are my DNS hosting as well? Not really sure. My biggest question is how to point my DNS to my mac mini server correctly.
1. How do you point the DNS to my mac mini server.
2. I've read somewhere to use the IP address from my mac mini server. The only IP address I see is from my Time Capsule (router). I know what my public IP adress is but I am not sure if that's the one to use. I think once I figure this DNS thing I can figure out the rest.
Thanks - Need lots of help.

Here's a detailed write-up on setting up internal (private) DNS on OS X Server, and no, you're probably not going to be setting up external DNS on your servers. Your public DNS service will be hosted on and served from the Network Solutions DNS servers.

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.

Unable to add/remove users in Mountain Lion Server (Options are greyed out)

For some reason, im unable to add/remove users in Mountain Lion server. The + and - are greyed out. It seems like something is wrong with the permissons because it looks like it cant write the the Ldav3 file (although that may be speculation). Does anyone have any advice for me? I URGENTLY need to add users.
Maybe theres a way to restore default permssions for the boot drive (if that in fact is the issue). Hopefully there is a way that I can fix this while leaving all users, groups, their permissions and shares intact.

Anything interesting and relevent in the server logs?
Anything interesting in the server alerts?
Since it's far and away the most common cause of problems with OS X Server and with distributed authentication (Open Directory is entirely based on network encryption and digital certificates and on responses from your local DNS server(s)), verify your local DNS configuration is working and requires no changes with the following Terminal.app (Applications > Utilities) harmless, diagnostic command:
sudo changeip -checkhostname
sudo requires an administrative password. You might get a one-time warning about the sudo, and that can safely be ignored. The command will display some details, and indicate whether the local configuration appears valid and no changes are required, or further diagnostics for (most) common errors that can arise.

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

VPN to Mountain Lion Server issues

Hi,
I checked a lot of VPN threads here today, but I wasn't able to find a solution for my problem just now. I try to connect by VPN to my Mountain Lion Server, but I get an error message that the VPN server is not responding. I get this message from iPhone and Mac. The Mountain Lion Server is a new installation, no upgrade from an older server.
Some informations on my setup:
I installed the server with a hostname like myserver.mycompany.com and option 3 (internet access), as I want to use it for email at a later stage. All services are working fine (except VPN). DNS is active, but basically it only contains the adress myserver.mycompany.com and forwards everything else to our router.
I changed the DNS settings of our domain ( hosted by an ISP - so not in the local DNS ! ). I created a subdomain vpn.mycompany.com which points to the static IP of our router.
In the router I opened the UDP ports 500, 1701 and 4500, and for 1701 i made the same thing for TCP (I found this in a forum, but I think this is not necessary?), the ports are pointing to the ip of the os x server.
In OS X Server I started VPN for L2TP using the vpn.mycompany.com hostname, and a shared secret.
When I try to connect with I client from outside I try to connect using L2TP via vpn.mycompany.com using the shared secred and user-id and password. The user-id is created in OS X Mountain Lion server and is configured to use VPN service. When trying to connect I get the error message "L2TP-VPN server is not repsonding...".
In the log file of the server I see some entries for each connect:
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: Connecting.
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IPSec Phase1 started (Initiated by peer).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 1).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 2).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 3).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 4).
Oct 10 20:21:48 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
Oct 10 20:22:06 --- last message repeated 2 times ---
Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (2,0)
Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Library/PrivilegedHelperTools/com.apple.serverd' [1716] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (100000,0)
Oct 10 20:22:06 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
No more entries in log file now. Anyone any ideas what's going wrong. Might there be a problem as I use another servername outside as inside (vpn... instead of myserver...)?
Thanks!

Solved, first of all we tested to establish the VPN connection locally by adding the ip address of the server to /etc/hosts for vpn.mycompany.com. The VPN connected without problems then, so it was clear that it is a firewall/router problem, and not a server problem.
After that we studied some more documentations and found that we don't have to open port 50, but ip protocoll 50 (ESP) on the firewall. After that was done, the connection was working from the internet as well.

Server App can't connect to a Mountain Lion server

Hi,
I installed OS X Mountain Lion Server (2.2.1) on a 2012 Mac Mini running OS X 10.8.4. I am able to access all the options using the Server.app on the Mini. Then I installed the Server.app (2.2.1) on a 2010 MacBook Pro running 10.8.4. On trying to configure the Server options on the Mac Mini from the MacBook Pro by providing the correct Mac Mini admin credentials, the password is not validated correctly. This happens when both the systems are on the same network or on different networks.
I am certain that the username / password provided is correct, since using the same credentials I can successfully remote into the Mac Mini using Apple Remote Desktop (3.6.1) when both the systems are on the same network or on different networks.
My situation supersedes the resolution provided in http://support.apple.com/kb/TS3960?locale=en_US. Note that the command sudo launchctl list | grep -q com.apple.servermgrd && echo loaded || echo not loaded returns loaded on the Mac Mini.
Please help!

I am having exactly the same setup and exactly the same problem - nevertheless I would like to add some more information in order to hopefully find / get help from other readers in here.
I am using DynDNS - not a dedicated domain. I do not utilize an AirPort Extreme for port forwarding and else. All the necessary port forwardings were triple checked!
- First of all "Apple Remote Desktop" is able to connect to my server over the internet (screen sharing) and locally in my LAN. No troubles here.
- My iOS devices can connect using various VNC clients without any troubles.
- VNC connections started within Safari (MacBook Pro) do work very well, too.
- All kinds of WebDAV connections are working like a charme.
- When connecting with "Server.app" from my MacBook Pro it asks if I would like to trust the self-signed certificate before I can enter name and password. After trusting that certificate it doesn't matter which account information I am entering: none is accepted. It does not make any difference if I am using a local user account or a user network account (both configured as being allowed to administer that server). "Server.app" does not accept any information provided.
I've been following the KB advice, too that c xavier mentioned. "servermgrd" is loaded!
For some odd yet unknown reason neither WAN nor LAN FTP login does work, too. It just gives me a time out, as already mentioned WebDAV is working fine.
Sorry I could not help You, c xavier! I just thought that some additional information could help...

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.

Firewall gui for Mountain Lion Server

Is there an easy firewall for Mountain Lion server? Im amazed Apple took this feature away. For what reason? I dont know command line very well and shouldnt have to learn it seeing as how Macs are supposed to be "user friendly". Doing a port scan I see about 20 ports open that I want to close but just dont know how as they're not application specifc (like pop3...). Any suggestions would be helpful.
thanks.

Scott Howe wrote:
I meant to say "Is there a GUI for the Firewall for Mountain Lion Server"
I totally agree with you, the whole point of OS X was to be easy to use i.e. GUI based, if we wanted a pure CLI system we would get Linux
There are actually two different Firewalls on Mountain Lion Server, the 'standard' one you see in System Preferences which is an Application level firewall (ALF), and has extremely limited options but does have a GUI, and the CLI only one which is pfctl (Packet Filtering).
Note: ipfw is depreciated in Mountain Lion.
There is a third-party tool for configuring pfctl called IceFloor. Be careful though, I managed to screw up a system with it, as always make sure you have a backup before making changes.
See http://www.hanynet.com/icefloor/

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.

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...

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

DNS Changes (Mountain Lion Server & Airport Extreme)

Similar Messages

Maybe you are looking for