Change user account in snow leopard server??

Trying to change a user account picture in snow leopard server. Have couple computers that are on snow leopard and it uses the the network server that has all the login in. I can't change the user icon within system prefernces. Please help me!

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.

Similar Messages

Change IP Address in Snow Leopard Server

I have a client who has been operating naked on the Internet for years. Every machine in their office has its own public IP address. They have had some issues with former employees accessing their machines and are becoming a bit more security minded. I have purchased an Airport Extreme for them to use as their firewall and provide wireless for the growing number of laptops and iPhones.
My question is as follows:
If I set up their AE to provide NAT for them and change the IP addresses from the public 67.xxx.xxx.xxx to a private network 192.168.xxx.xxx, how is this going to effect name resolution on the network? Will it cause any other issues that I should be aware of before making the change?
Thanks for any help and insight you can provide
SK

It very much depends whether you plan to put the SLS within the Airport LAN or not. You could easily leave it parked on its current public IP, and simply put the rest of the computers in the Airport LAN.
If you do that, it probably won't make any difference at all to the users - they'll pick up DNS information from the Airport Extreme rather than the server, but still be looking at the same location for any server based services they use (e.g. iCal server, mail etc.).
If you move the server to be within the Airport LAN then you will have to make a number of changes to the configuration of the server. Which ones need updating depends on what the server is used for. If you look on pages 132 to 144 of the manual Mac OS X Server - Advanced Server Management - which you can download from the documentation section of the Apple Support web site (http://manuals.info.apple.com/enUS/ServerAdminv10.6.pdf) you get a clear discussion of what services are affected by a change in IP address, and how to update the server to reflect such changes.
Hope this helps.

Switch users/accounts in snow leopard

i have a visitor coming to my house today and i am trying to figure out how to switch users. i followed all the instructions on the site about checking the necessary boxes in system preferences/accounts. however, my icon in the menu bar and the login window continue to only give 1 option for logging in: me. how can i do fast switch user or fix this problem? thank you.

i followed the instructions on help to a "t." i checked all the boxes it told me to check as per this document:
http://docs.info.apple.com/article.html?path=Mac/10.6/en/8672.html

Snow Leopard Server and PPC clients

Just three short questions :
Has anyone managed to have Tiger PPC 10.4.11 accounts on Snow Leopard Server 10.6.4 ?
If yes, have this clients a network home directory on the Server ?
Have you encountered any trouble with these Tiger's clients ?
You don't have to post a long reply. Just answer yes or no and that way I would know if I've made a mistake or if there is a bug in Snow Leopard Server.
Thanks in advance for all your answers.

Hi
Ditto with Jeff
+"Has anyone managed to have Tiger PPC 10.4.11 accounts on Snow Leopard Server 10.6.4?"+
Yes. Lots of times. Also had 10.4, 10.5 and 10.6 clients logging in with network accounts on a 10.4 Server.
+"If yes, have these clients a network home directory on the Server?"+
Yes.
+"Have you encountered any trouble with Tiger clients?"+
No.
Tony

Mobile account users can not log on to the snow leopard server machine?

Hi all,
I've setup a network user and designated it as a mobile account. ** OS X 10.6.2 **
When the user logs out of the snow leopard server machine, home sync tries to sync the local and network home directories. It is never able to connect. The network home directory is automounted and is not the default path /Users. I can see the two home directories on disk.
Anyone else able to have their mobile users log in to the snow leopard server machine without issues?
OS X 10.6.2 **

It was the Sync server was down and did not know it

Kadmin can't change dsimport'ed passwords in Snow Leopard Server

Hello, World.
I am attempting to manage user accounts in Open Directory from a non-Mac system. After a good deal of investigation on Leopard Server, I wound up ssh'ing to our Open Directory server to create new accounts with 'dsimport', and then to manage later changes to the account through LDAP (for non-password data) and through Kerberos with kadmin, on the theory that kadmind was supposed to propagate the encrypted plain text passwords into Password Service for all of P.S.'s hashing needs.
This worked great in Leopard Server, but under Snow Leopard Server, any attempt to change a user's password via kadmin fails with
'change_password: KDC policy rejects request while changing password for <principal name>'
At the same time, the system log (/var/log/system.log) shows
Nov 2 17:53:46 od1 sandboxd[76028]: mkpassdb(76026) deny file-read-data /usr/sbin/mkpassdb
Nov 2 17:53:46 od1 sandboxd[76028]: mkpassdb(76027) deny process-exec /usr/bin/ldapsearch
However, if I create a principal directly with kadmin, kadmin does allow me to change the password for the principal I just created.
Use modprinc to remove attributes (REQUIRESPREAUTH DISALLOW_SVR) from the dsimport'ed principals doesn't affect anything in any positive manner, though the principals I create manually in kadmin do lack these attributes.
So, does anyone know what the story is, here? Is there no supported API that I can use from a Solaris/Linux server to fully manage accounts under Open Directory?

I have a Similar issue, Details below. the summary is that Using the Snow Leopard GUI interface I created 17 users with a generic low security Password. then transferred and converted some mail files to the server. Once the mail was working properly, I changed the passwords to a slightly more secure password, and set it so my users would have to change their password to a more secure password at log in.
Even after these password changes it is very easy to get other user's ticket information, if you know the original low Security Password with
kinit <other user name>
Details and demonstration.
oursvr:krb5kdc root# kpasswd someuser
Please enter the old password for [email protected]:
Please enter the new password for [email protected]:
Verifying, please re-enter the new password for
[email protected] again:
Server error
Unknown error code: 2802413321
KDC policy rejects request Unknown error code: 2802413326
Please enter the old password for [email protected]:
oursvr:krb5kdc root# kadmin.local
Authenticating as principal root/[email protected] with password.
kadmin.local: cpw [email protected]
Enter password for principal "[email protected]":
Re-enter password for principal "[email protected]":
ambiguous user name.
change_password: KDC policy rejects request while changing password for
"[email protected]".
kadmin.local: q
oursvr:krb5kdc root# kinit someuser/admin
Please enter the password for someuser/[email protected]:
oursvr:krb5kdc root# klist
Kerberos 5 ticket cache: 'API:Initial default ccache'
Default principal: someuser/[email protected]
Valid Starting Expires Service Principal
12/21/09 12:00:53 12/21/09 22:00:53
krbtgt/[email protected]
renew until 12/28/09 12:00:53
oursvr:krb5kdc root# kadmin
Authenticating as principal someuser/[email protected] with password.
Password for someuser/[email protected]:
kadmin: cpw someuser
Enter password for principal "someuser":
Re-enter password for principal "someuser":
change_password: Unknown error code: 2529638924 while changing password
for "[email protected]".
oursvr:krb5kdc root# kdestroy
oursvr:krb5kdc root# kinit otheruser
Please enter the password for [email protected]:
oursvr:krb5kdc root# klist
Kerberos 5 ticket cache: 'API:Initial default ccache'
Default principal: [email protected]
Valid Starting Expires Service Principal
12/21/09 12:07:55 12/21/09 22:07:50
krbtgt/[email protected]
renew until 12/28/09 12:07:55
CONFIGURATION
=============
Contents of /var/db/krb5kdc/kadm5.acl:
## This file autogenerated by KDCSetup ##
*/[email protected] * *
[email protected] * *
ADDITIONAL INFORMATION
======================
(1) Using 'passwd' to change the password does not change the Kerberos
password.
(2) Using "dscl /LDAPv3/127.0.0.1 -passwd Users/someuser" does not change
the Kerberos password.
(3)
(4) From /var/log/system.log:
Dec 21 11:57:01 oursvr edu.mit.Kerberos.kadmind[79131]: ambiguous user name.
Dec 21 11:57:01 oursvr sandboxd[82190]: mkpassdb(82189) deny file-read-data
/usr/sbin/mkpassdb
(5) From /var/log/krb5kdc/kadmin.log:
Dec 21 12:02:36 oursvr.sub.dom.tld kadmind[79131](Notice): Request:
kadm5chpassprincipal, [email protected], KDC policy rejects
request, client=someuser/[email protected],
service=kadmin/[email protected], addr=VVV.WWW.YYY.ZZ
Dec 21 12:02:36 oursvr.sub.dom.tld kadmind[79131](Notice): Request:
kadm5chpassprincipal, [email protected], KDC policy rejects
request, client=someuser/[email protected],
service=kadmin/[email protected], addr=VVV.WWW.YYY.ZZ
(6) From /var/log/krb5kdc/ldc.log:
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: NEEDED_PREAUTH:
[email protected] for kadmin/[email protected],
Additional pre-authentication required
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: NEEDED_PREAUTH:
[email protected] for kadmin/[email protected],
Additional pre-authentication required
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: ISSUE: authtime 1261414611, etypes
{rep=18 tkt=16 ses=18}, [email protected] for
kadmin/[email protected]
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: ISSUE: authtime 1261414611, etypes
{rep=18 tkt=16 ses=18}, [email protected] for
kadmin/[email protected]
(7) mkpassdb -dump 0x4b2bf32f30c3d4860000001e0000001e
slot 0030: 0x4b2bf32f30c3d4860000001e0000001e someuser 12/21/2009
12:28:17 PM
Last password change: 12/21/2009 11:00:36 AM
Last login: 12/21/2009 12:28:17 PM
Failed login count: 0
Disable reason: none
Hash-only bit: 0
Last Transaction ID: 2052
Transaction requires kerberos: 1
Record is dead: 0
Record is not to be replicated: 0
Access Features:
isDisabled=0 isAdminUser=0 newPasswordRequired=0 usingHistory=0
canModifyPasswordforSelf=1 usingExpirationDate=0 usingHardExpirationDate=0
requiresAlpha=0 requiresNumeric=0 expirationDateGMT=18446744073709551615
hardExpireDateGMT=18446744073709551615 maxMinutesUntilChangePassword=0
maxMinutesUntilDisabled=0 maxMinutesOfNonUse=0 maxFailedLoginAttempts=0
minChars=0 maxChars=0 passwordCannotBeName=0 requiresMixedCase=0
requiresSymbol=0 notGuessablePattern=0 isSessionKeyAgent=0
isComputerAccount=0 adminClass=0 adminNoChangePasswords=0
adminNoSetPolicies=0 adminNoCreate=0 adminNoDelete=0 adminNoClearState=0
adminNoPromoteAdmins=0
Group(s) for Administration: unrestricted
digest 0: method: *cmusaslsecretSMBNT
digest length: 16
digest: D6B093421FDF17380F0B695721F0F26A
digest 1: method: *cmusaslsecretSMBLM
digest length: 16
digest: 5C957C596B14237409A48A7AC23C7AB2
digest 2: method: *cmusaslsecretDIGEST
digest length: 16
digest: 8E9181A5F7697D7FB83BF2DA430CBB70
digest 3: method: *cmusaslsecretCRAM-M
digest length: 32
digest:
A08E4B9266A4B8676DEFA8584758F9013D29A479D81EE4E41D857D5A5CA4FA71
digest 4: method: KerberosRealmName
digest: OUR.KRB5.RLM
digest 5: method: KerberosPrincName
digest: someuser
digest 6: method: *cmusaslsecretPPS
digest length: 24
digest: A5AC9D1843D42ED4AF39EFB4AB91E536F733FB2580978860
digest 7: <empty>
digest 8: <empty>
digest 9: <empty>
slot checksum: 7DAA85870308B253D5A9294483A4B0EF
(8) dscl /LDAPv3/127.0.0.1 -read Users/someuser | grep -A 2 authAuthority
dsAttrTypeNative:authAuthority:
;ApplePasswordServer;0x4b2bf32f30c3d4860000001e0000001e,1024 35
14773688809506996593092824880872774590718495204127440029375223520574013330136617 78685429961896612181406054801454823310071429734609519569726042321602422714273008 59946509691313082062885828226653436410277560435615063784052163315144051817774743 254036483144235604939879290290235050919364398951613699884041179183857
[email protected]:VVV.WWW.YYY.ZZ
;Kerberosv5;0x4b2bf32f30c3d4860000001e0000001e;[email protected];OUR.KRB5.R LM;1024
35
14773688809506996593092824880872774590718495204127440029375223520574013330136617 78685429961896612181406054801454823310071429734609519569726042321602422714273008 59946509691313082062885828226653436410277560435615063784052163315144051817774743 254036483144235604939879290290235050919364398951613699884041179183857
[email protected]:VVV.WWW.YYY.ZZ

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

Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

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.

HT201240 Re: OS X: Changing or resetting an account password (Snow Leopard and earlier)

Can someone help please! I cannot log in to my Mac
Followed these intructions from earlier posts this thread, and got to:
4. Select your Mac OS X hard disk volume. DONE
5. Select the user name of your original administrator account. COULD NOT COMPLETE
- But my original administrator account is not showing. The only option shown for me is "System Administrator (root)".
Luckily I read the note below: Important: Do not select "System Administrator (root)".
So now I wait for further advice...

Forgot Your Account Password
For Lion, Mountain Lion, or Mavericks
    Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
     When the menubar appears select Terminal from the Utilities menu.
     Enter resetpassword at the prompt and press RETURN. Follow
     instructions in the dialog window that will appear.
     Or see:
       Reset a Mac OS X 10.7 Lion Password
       OS X Mountain Lion- Reset a login password,
       OS X Mavericks- Solve password problems,
       OS X Lion- Apple ID can be used to reset your user account password.
For Snow Leopard and earlier with installer DVD
     Mac OS X 10.6- If you forget your administrator password,
     OS X- Changing or resetting an account password (Snow Leopard and earlier).
For Snow Leopard and earlier without installer DVD
    How to reset your Mac OS X password without an installer disc | MacYourself

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.

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.

The Windows SMB feature has file locking if multiple users are accessing the same file. Does Snow Leopard Server File Sharing (AFP) provide similar features?

The Windows SMB feature has file locking if multiple users are accessing the same file. Does File Sharing (AFP) on Snow Leopard Server provide similar services?

Were you ever able to solve this problem. I'm having similar issues since upgrading to snow leopard. Four macs connect to a Windows Server 2003 for shared files. Each user has full permissions & when we "get info" it shows read & write permissions. Two of the computers were running 10.4, two were running 10.5. Everything worked properly until upgrading to snow leopard. Some files let me copy, move, delete. Others either just hang up or we get a "no permission" error. Also getting a "pdf is in use" error, even when the file/folder doesn't contain a pdf. We had our IT rep check the server who said everything is in working order. They don't represent macs any longer but feel that it's a mac problem. I would have to agree since this problem only started after the upgrade, and the one machine that was not upgraded (still running 10.5.8) is not dealing with these problems.
Lastly, I would install 10.5 back on all of the computers if I could, but the leopard disk that came with one of the computers wouldn't work with the 2 machines running 10.4 and I didn't see it available at the apple store. I'll buy it if it's still available, but why wouldn't the disks that I have work?
Thanks for any help

IOS & Snow Leopard Server Mail, Contacts, Calendars Account

Is there any way to add a single IMAP/Cardav/Caldav account in iOS 5, or OS X 10.6/10.7 that goes back to Snow Leopard Server? Adding each type of account works, but it'd be cleaner if I could setup one account with multiple services like I can with Exchange, iCloud, MobileMe, Yahoo, etc..
Anyone have an idea?

This is the problem I'm trying to describe. It is now happening multiple times every day.
Any advise would be appreciated. The problem is the accounts are being de-accessed.

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.

Change user account in snow leopard server??

Similar Messages

Maybe you are looking for