Snow leopard server is created endless duplicates in OSX Lion clients

I am running a snow leopard server with address book server. My client computer was Snow leopard and have no problem syncing with the 10.6 server in address book. After the client computer is upgraded to 10.7 Lion, the address book application is creating a never ending stream of duplicate address entries in the client computer. It happens to all the upgraded 10.7 computers. The entries just keep multiplying into the thousands until I stop the address book server. Anybody know of this problem and how to fix it??

The address book on my mac somehow duplicated my contacts to the point where instead of about 200, I have about 100,000! The program crashes - if it even opens at all, which is sometimes doesnt - whenever I try to delete more than just a few. And if it doesn't crash, it just takes forever to process. At this rate I need a solid 3 hours to sit here and delete a few contacts at a time! Did you ever figure out how to resolve this problem?

Similar Messages

How do I create a virtual directory in Snow Leopard Server Admin program?

Hi, how do you use the server admin program in snow leopard server to create an apache virtual directory? I can't see it in the applet anywhere. Thank you.

Well this is what I thought too but I don't think I'm doing something right. I have a default website on port 80 and I created a second site on the same port. They are two different websites. One is the initial one that comes stock with the osx. The second one I created.
When I browse to my server I get the second site. How can I get the default to be the one that points to the mail, wiki, calendar stuff, while my second domain is something totally different.
http://myserver (should be the default stuff like mail.)
http://myserver/mysecondsite (should be my other stuff.)
The problem is that when I go to http://myserver it is going to http://myserver/mysecondsite
What am I doing wrong? Thank you.

Does Snow Leopard Server iCal Service support iCal Groups?

I have successfully configured iCal Service on Snow Leopard Server 10.6.8v1.1 and have several client Mac system (runing SL 10.6.8v1.1) connected to this service via CalDAV. I can create new calendars and those calendars and any test events propigate to all machines that have this CalDAV account configured. But whenever I try to create a calendar group it always appears as a local calendar group. Is this a feature missing when using iCal Server and CalDAV? Am I doing something wrong?
Thanks

Hi
I doubt if you'll find a step-by-step as most people's requirements are different. One of the places most people start is here:
http://support.apple.com/manuals/#macosxserver
Have you tried searching the Forum itself?
http://discussions.apple.com/forum.jspa?forumID=1352
Tony

Trying to install Snow Leopard Server into Parallels 9

Help! I have a 10.8 macbook, purchased Parallels 9 and Snow Leopard Server to create virtual environment for old ppc software (namely final cut pro 6), but the SLS installation halts saying not enough free RAM, but laptop meets min 2gb requirements... Does anyone know how to solve?
I get as far as b in step 6 here
http://forums.macrumors.com/showpost.php?p=17285039&postcount=564
Any help would be greatly appreciated!
Lulu

lulumalmgren wrote:
Help! I have a 10.8 macbook, purchased Parallels 9 and Snow Leopard Server to create virtual environment for old ppc software (namely final cut pro 6)...
Final Cut Pro 6, which is a component of Final Cut Studio 2, is not a PowerPC application; it was written for Intel Macs and should run fine in 10.8, Mt. Lion.
The problem is that there is a "bug" in the installer application that triggers the "PowerPC" dialog box when attempting to install FCP 6 into a Mac running Lion, Mt. Lion or Mavericks.
If the MacBook is old enough to run Snow Leopard, one solution is to partition your hard drive, or add an external one, and install Snow Leopard on it. Then use the "dual-boot" method to run either Snow Leopard or Mt. Lion on your MacBook. When running Snow Leopard, you can then install FCP 6 and run it.
In theory, once you have successfully installed FCP 6 into Snow Leopard, you could then upgrade this partition to Mt. Lion as well, and it should continue to run.
If your MacBook will not run Snow Leopard, review Jeremy Johnstone's method to use Terminal to install FCP 6 into Mt. Lion:
http://www.jeremyjohnstone.com/blog/2012-03-11-installing-final-cut-pro-studio-2 -0-on-mac-os-x-10-7-lion.html
...and as Bill Gates always says:
"You can never have too much money, or too much RAM!"

Printer Sharing broken in Snow Leopard Server

I have a Mac Pro running Leopard Server 10.5.8 doing various things, as well as Printer Sharing. After recently attempting to upgrade it to Snow Leopard Server, printer sharing no longer works. Existing clients with the shared printers added can no longer print. I attempted resetting the printing system on the server then readded the printers, then did the same on a client. When adding the printers advertised through Bonjour, the printer model is not detected and it wants to use the generic postscript driver. When printing with this driver, the printer hangs and wants to ask what paper tray to feed from.
How can I get this working as it was in 10.5.8? I don't want to have to go around and reconfigure all 50 clients on my network, and if I do have to, adding it with Bonjour should do most of the work.

There are server user accounts and computer user accounts. System Preferences is for creating and managing computer user accounts. Server Preferences and Workgroup Manager are for creating and managing server user accounts. If you created the account in System Preferences, you won't be able to manage it with Server Preferences or Workgroup Manager.

Snow Leopard server, Lion clients

Good day I am running a 10.6.8 server (Mac Pro 2010) with 300 user account on it. At this time because out client computers needing compatibility with multiple applications upgrades we need to upgrade all out clients to 10.7.3. The decision has been made and I need to go with it. The server only runs user accounts, shared folders, Wiki and DNS. I am hesitant to upgrade the server to 10.7. I have attempted some quick searches for any issue with running 10.6.8 Server and 10.7 clients but it has not resulted in much.
What is the biggest issue I am going to be running into?
Will AFP still work with 10.7 clients?
Should I upgrade the server to 10.7 also?
What will I loose at this point upgrading everything?
Looking forward to what I can learn.

What is the biggest issue I am going to be running into?
What issues will you run into if you upgrade your clients to Lion, but leave your server on Snow Leopard? none. That's entirely valid.
Will AFP still work with 10.7 clients?
Yes
Should I upgrade the server to 10.7 also?
Not unless you specifically need some of the features in Mac OS X Lion Server, and absolutely not if you only have one server.
What will I loose at this point upgrading everything?
Probably several nights' sleep. Upgrading a server, and maintaining all the services without any downtime is a significant process. Snow Leopard Server doesn't stop running just because Lion is available, and it won't stop when Mountain Lion comes along, either.
If your mandate is to upgrade the clients, then do that, and take your time planning your server upgrade/migration.

Creating a versatile DNS and redirection service on Snow Leopard Server

For the few of us who use Snow Leopard Server as a main DNS for our small network, the following is a workflow that I would like to share with the board for creating redirection services to not just sites found on the locally hosted apache but also external sites.
+IF you are adding a second domain name, the reverse domain lookup will not appear and you will need to add a Machine/A record with the fully qualified domain "domainname.com." (don't forget the . at the end) into the new zone and it will point to the "server" Machine/A record ip address.+
*DNS Portion* : (ServerAdmin > DNS > Zones >
Add Zone > Primary > Create a fully Qualified Domain name and dns "server" in the Machine / A Record
Create the (add Record > Alias/ CNAME) subdomain pointing to the server.domainname.com e.g. (library)
*Web / Apache Portion :*
Create a new site (ServerAdmin > Web > Sites > Plus button)
With General > host name exactly as spelled in above subdomain in full (library.domainname.com)
Select Web Folder where the site is hosted
If you are creating a redirection, create a folder on the server, add an index.php (with the script below)
Add Alias with the same subdomain as number 2
_PHP script :_
<?php
$location = "http://example.net";
header("Location: ".$location, "301 Moved Permanently");
?>
// Edit the "http://example.net" to which ever e.g. "http://apple.com"
_Alternatively you can also mask the page with :_
<html>
<head>
<title>Same Title As Your Homepage</title>
<script type="text/javascript">
function changeTitle()
if (top.frames['main'].document.title)
top.document.title=top.frames['main'].document.title;
</script>
</head>
<frameset>
<frame name="main" src="http://actual-url.anotherhost.com/page.html"scrolling="auto" target="main" ONLOAD="changeTitle();">
<noframes>
<body>
Place a suitable message here for people with browsers that can't read frames.
</body>
</noframes>
</frameset>
</html>

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Snow Leopard Server - Managed Dock Settings

Hello Everyone,
In our environment, we are running Snow Leopard Server 10.6.7 with a mix of 10.5 and 10.6 clients. We are managing settings via Open Directory. We have a computer group policy configured to manage our dock policy settings among a few others. Within WGM, our dock policy settings are setup to be managed "once." When the policy was configured, our Mac administrator put together a customized default dock arrangement with the most commonly utilized applications included in our base image allowing our end users to start with a small clean dock arrangement and add applications/folders as desired.
Regrettably, last week I inadvertently made a change within WGM's managed dock settings in our default production policy. The following morning, several end users logged on to find that their dock customizations had been discarded and replaced with the default setup. To minimize the impacted users, I enabled "merge with user's dock" to avoid further loss of dock customizations. Looking forward, as we roll out new hardware with new images to our existing users, I would like to start with the same scaled back dock with the commonly utilized applications included in our base image. The problem with enabling "merge with user's dock" is that the default set of Mac OS X icons is included causing the dock to be cluttered.
Is there anyway to only apply managed dock preferences if there is not a local profile on the machine the user is logging into? Any other thoughts for circumnavigating the mess I created?
Thanks!

Enabling "merge with user's dock" created problems of its own by introducing duplicate icons for some users. In the end, I unchecked it. Unfortunately, all users are going to receive the default dock arrangement and have to re-customize their dock preferences as desired.

Can't rename folders on Snow Leopard Server

I have 10.6.8 Snow Leopard Server running on a new Mac Mini server. Attached I have a Pegasus Raid storing all my files. I have a sharepoint set up for every project we work on but a couple act strangely. Users can create and delete folders but can not rename them once created. In order to rename they must drag the folder onto the desktop, rename and then replace the folder on the server. All permissions are set up identical to the other sharepoints which work fine. I have had a couple so-called "experts" look at the permissions in both the terminal and Server Admin. Everyone seems stumped. Any ideas?

Thanks for the input but I finally soved the problem. Here is what I found...
Although I had given users/group the ALLOW/FULL CONTROL premission with a sharepoint, I discovered that in Server Admin if you double-click on the User or Group name under the ACL permissions that a drop down box appears. This box allows you to fine tune the ACL but it appears that by default all of the boxes are not checked even though I granted the user Full Control. After checking all of the boxes I was able to create and rename folders in my share as expected.
This also had an similar effect if I denied Full Control. Some of the boxes remained unchecked and it left holes in my system where denied users could still access some files. Again by checking all boxes these holes were closed.
Does anyone know how to change the default so that all boxes are checked when assigning the Full Control permission?

I transferred files from a NAS server to the Mac Mini Snow Leopard Server and now some of the files have Custom Access and can't be opened by some users. How do I fix this?

We're setting up our Mac Mini Snow Leopard Server, and in the process transferred files that had been stored and accessed from our Blackarmor NAS server over to the Mac. These files were all created on PC's and are Office Excel files, WordPerfect files or PDF's. When you look at the files on the Mac from the Mac and bring up Get Info for the affected file, it says that the file has Custom Access. The files that work properly don't have that configuration. I can access and open the files on some computers, but some users can't open the files from their computer even though they can see it. We're all using PC's and they get the Error: Access Denied-Contact your administrator--or something similar. I've seen on the web similar issues and it may have something to do with ACL permissions. I don't know enough about Mac OS to understand this, but what is baffling is that they can be opened from some PC's but not others, and all of the Users have the same accessibility to the files. Thanks for a solution!!

Oh, on the losing Internet, try this...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
For 10.5/10.6, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
208.67.222.222
208.67.220.220
Click OK.
PS. Your English is quite good & completely understandable.

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

Can i install bootcamp on mac mini snow leopard server 2010

hello,there are 2 harddisks on a mac mini server 2010 (snow leopard server.)i want to use the other hdd for installing Windows home server 2011 x64 .
but there is no bootcamp on the server.(do i have to download it?)
how can i do this,or do i have to use parallels desktop.
i have also a mac mini and a macbook pro and an alienware and a clevo laptop so i want the 2 servers seperate(and the mac-server on all the time)

You would need to install SL (non sever) on you Mac Mini Server.
You may be able to install the nonsever version on your 2nd HDD
-Partition you 2nd HDD to the max BootCamp Partition
-Install Windows Home Server on the BootCamp Partition (don't know of Windows Server is supported)
So you would have:
hdd1 - SnowLeopard Server
hdd2 - SnowLeopard (non-server) + Bootcamp Partition
Scenario 2:
If you don't have a need for SL Server SW, then wipe out the system and put only the regular SL (non sever) on disk 1. Partition Disk2 for Bootcamp only.
hdd1- SL (non-sever)
hdd2 - Bootcamp
I really don't know if you can copy the Bootcamp app onto SL Server OS to create a Bootcamp partition.

Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

Hello,
I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4. While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD. I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager. Towards the end of the week though this stopped working. Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding". If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen. My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else.
I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly. I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD. I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
Is anyone else having this issue? Any help would help me keep my sanity.
Thanks,
Dane

Have you had any luck finding a solution to this? The only thing I have found was to unbind and then bind without authentication. Any help with progress on your end would be appreciated!
Nick.

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

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

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

New Snow Leopard Server, Slow Network Accounts

We've installed Snow Leopard Server on our XServe quite a while ago and since then all users who work with network accounts are complaining about serious perfomance issues. These issues are for instance logins which may very well take up to several minutes, or applications like Adobe InDesign which take their time to load files from the users network shares.
Our System consist of:
1 XServe running OS X 10.6.8 Snow Leopard Server
48 iMacs running OS X 10.5
1 Windows Server 2008
The XServe serves as an OpenDirectory and Fileserver, while the Windows Server delivers DNS.
We have created ~500 users and 25 groups in the OpenDirectory. All user files are located in their roaming profiles on the Xserve. Additionaly every user has access to one group folder, which is located on the Xserve as well.
All group folders are Sharepoints and added to the dock of all users in the appropriate group.
I have already checked DNS settings, user accounts, network connectivity in general, network load during peak hours, the ACLs on the group folders....
By now im simply out of ideas what my cause the problem, let alone how to solve it.
Any hints are greatly appreciated.

Are you using any redirections? Redirecting the cache folder from the network home to the /tmp should improve speed. Use this white paper from apple. http://images.apple.com/education/docs/Apple-ClientManagementWhitePaper.pdf The redirections are on page 53.

Snow leopard server is created endless duplicates in OSX Lion clients

Similar Messages

Maybe you are looking for