10.6.8 Server - workgroup manager not authenticated

I have 10.6.8 Server that has suddenly stopped accepting the dradmin password when using Workgroup Manager. Workgroup Manager connects, but in not authenticated mode. When I click the lock icon and am prompted for the ID & Password it is rejected. I know with 100% certainty I am using the correct administrator ID and password. I am running Workgroup Manager directly on the server computer. I'm able to log on to the computer as the local administrator. Server Admin works fine with no authentication issues.
I have not applied the 10.6.8 Supplemental update, but wonder if that might be helpful.
It is very concerning to be locked out of my own server. Any suggestions why this is happening and how to reslove it?
Thank you,
-Joe

The logs revealed that dradmin was actually authenticating successfully, but for some reason Workgroup Manager was still in unauthenticated mode. I installed 10.6.8 Supplemental update and found no improvement.
All users have portable home directories and everything with Open Directory was functioning properly. DNS and Kerberos were confirmed to be working properly. Several restarts and shutdown/startups were performed and I never was able to get Workgroup Manager to authenticate. So after a few hours troubleshooting last weekend I decided to restore the server to a disk image that was created 20 days earlier. I elected to do this this because I needed to get it resolved on the weekend to minimize the chance of downtime during business hours. The only thing on the boot drive is the server OS an everything else is stored on an external RAID so it was fairly simple for me to restore then get everything current again.
I kept an image of the server with the problem so I can restore it to a standby server to experiment with any possible fixes that I may come across in the future. As of now I don't know why it happened nor how to fix it without restoring.

Similar Messages

I need to add new MacBooks to mac server workgroup manager. 10.9.5

i need to add new MacBooks to mac server workgroup manager. cannot find them by mac address, name or ip. how do i add the new MacBooks. i think there is no workgroup manger programs for mavericks, so there must be a new way to create and add new clients to workgroup manager. can someone please inform me or point me to a dock that explains how thank you.

OSX server workgroup manager Won't allow me to add a group because it thinks there is already one

OSX server workgroup manager Won't allow me to add a group because it thinks there is already one. Anyone can help with solution.

Worked it out all I had to do was put workgroup manager into local and delete group/s

Nested AD User Groups in Workgroup Manager not working in Mavericks

The setup is the traditional Golden Triangle, so Active Directory for users and groups, Open Directory for Managed Preferences. Both Apple clients and server are running 10.9.0
While I can successfully manage the Mac's via OD computer groups, the OD user groups with nested AD groups no longer appear to work. If I nest an AD user it works fine, but not the AD users group.
This is a new AD and new OD, no migrations. This is a setup I've done countless times over the years, but since Mavericks has been introduced, I can no longer make this work.
Any help would be greatly appreaciated.
Thanks,
Alex Price

Hello
I have been having the same problem, when adding an AD Group to an OD group the users in the AD group are not managed, but if i add the user to the OD group it works fine, (with about 5000 active users this is not an option) this has been a problem with 10.9 and has not been fixed with 10.9.1, i assume we need a update to Workgroup manager?
Maverick server is useless at the moment, cant upgrade the clients to Maverick if i cant manage them, are Apple just tring to make my job more difficult than it needs to be, i was happy that they provided Workgroup Manager for Mavericks because Profile Manager is simple not an option, but it would be good if it worked properly, its not a small problem so you would think apple would make it a priority.

Can't add Computer or New Computer list on 10.3.9 Server Workgroup manager

I have a 10.3.9 server with Open Directory running. I can manage user and group preferences (Workgroup manager v2.0.1) but can't add a computer or new computer list because the option is disabled. If I connect to it's open directory from another server running 10.3.9 and same version of Workgroup Mgr, the new computer list and adding computers is enabled. This other server is in another subnet and not typically available for use by the network admin of the problem server. Any ideas to get the computer management enabled?

Hi,
an additional discovery I made:
Take the account "A", which is functioning on these two "problem-clients". I change the password from "123456" to "abcdef".
I try to log in this account with one of these two Macs... -> does NOT work
I try to log in this account with another Client (w/o problems) -> does work
I change the password back to "123456"
I try to log in this account with one of these two Macs -> does work
I deleted the accounts and created new ones. The accounts work fine on every Mac despite these two machines.
It looks like these two clients are not updating the directoryservice information.
So I tried to get a look, which information is readable at the client machines (which are making the trouble):
lookupd version 369.5 (root 2006.12.02 12:00:25 UTC)
Enter command name, "help", or "quit" to exit
userWithName: test
Dictionary: "DS: user test"
lookupagent: DSAgent
lookupvalidation: 1195423412
gid: 1025
home: /Network/Servers/xserve/Volumes/DATA/HomeDir/test
name: test testuser Test User
passwd: ****** ******
realname: Test User
shell: /bin/bash
uid: 1026
+ Category: user
+ Time to live: 43200
+ Age: 0 (expires in 43200 seconds)
+ Negative: No
+ Cache hits: 0
+ Retain count: 7
I gathered this information on the client, which can NOT log into this account. I can try all new or changed accounts, all are visible to the client....
Does anybody here unterstand this?
• the used accounts are all ok
• other accounts work fine on this two machines
• the problem only occurs on changed or new accounts.
• reverting the changed accounts to the old state: the accounts work again
Regards
svenc

File Server Resources Manager not sending emails

Appears that the SMTP settings are not being set correctly via FSRM. Using 2012 R2
I get the below error in the event log when I try to configure them (via options/email notifications tab). If I click the 'send test email' button I get the test email which tells me my SMTP server is fine. Seems like I'm getting an access
denied message whenever I try to save the SMTP settings. I already tried restarting the server as well as running the FSRM console using the 'run as admin' command.
Source: SRMSVC
EventID: 16401
The following access-denied assistance error configuration was modified:
Error: 5
Enabled: FALSE
Client Display Flags:
Error Message: This can occur if you don't have permission to access the file or folder, or if your computer doesn't meet security policy requirements.
Message from the administrator of the file server:
- Ask your manager if you're in the right security groups
- For troubleshooting information, go to <a href="http://support.microsoft.com">Microsoft Support</a>
If you need more help, click Request assistance.
Email Flags: Put data owner on TO line, Put administrator on TO line, Include device claims, Include user information, Generate an event log when sending mail
Additional To Emails:
Email Message: For general support, contact: [Provide email address]
For share permissions support, contact: [Provide email address]

Hi,
Please try to assign the "Send-as" permission from the adsiedit.msc to the user account.
Is the SMTP server hosted on an Exchange server? If so, I suggest you ask for help from Exchange forums for better and accurate answer to the question.
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrdeploylegacy
Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Mountain Lion Server Profile Manager not accessible externally

What do I need to be checking if I can't access our Mountain Lion server's Profile Manager externally. From a test iPad on a carrier's 3G network, I get a "server not found" error when using http://fqdn/. I can bring up the server page if I use https://publicipaddress. but not https://publicipaddress/profilemanager. Apple tried accessing the server with the same findings. We're a state agency behind tight firewall and security and we're told that all Profile manager needed ports are open... Thanks.

Nelson -
Pretty much everything boiled down to DNS, firewalls and ports. Unfortunately, I was never able to acertain which of the three items were causing this problem because we have a separate group who manages the network and firewall (plus a separate security team). If I recall, once they focused on what it was I was trying to accomplish, most of the problems "magically" went away.
Is your reverse DNS working the way it's supposed to? Ex:
yourserver:~ login$ hostname
yourserver.yourdomainname
yourserver:~ login$ host yourserver.yourdomainname
yourserver.yourdomainname has address 10.x.x.x
yourserver:~ login$ host 10.x.x.x
3.34.2.10.in-addr.arpa domain name pointer yourserver.yourdomainname
yourserver:~ login$
Also be sure to follow "burton11234's" posts. https://discussions.apple.com/people/burton11234?view=overview

Workgroup manager crashes

Grretings,
Out of the blue, our workgroup manager stays open for only a minute or so. This can be shortened by clicking on a user name then selecting the "home" tab or better yet, selecting the "new" button.
This occurs even when accessing the server via a remote instance of the workgroup manager.
Any insight or guidance to resolving this would be appreciated.
Thanks

Antonio,
ServerAdmin proggie works fine. I have attempted to use the loopback address when accessing WorkgroupManager. Now I can average 30-60 seconds of navigation in the utility before it closes out. However, I am unable to modify any user settings during this brief time.
I will attempt removing the .plist file and rebooting after hours and report back the results.
I've included the output of the last attempt from the crash reporter:
+Host Name: webserver+
+Date/Time: 2007-09-12 07:56:36.815 -0400+
+OS Version: 10.4.10 (Build 8R218)+
+Report Version: 4+
+Command: Workgroup Manager+
+Path: /Applications/Server/Workgroup Manager.app/Contents/MacOS/Workgroup Manager+
+Parent: WindowServer [103]+
+Version: 10.4.4 (230.2.51)+
+Build Version: 136+
+Project Name: ServerManagerApp+
+Source Version: 2300251+
+PID: 5507+
+Thread: 0+
+Exception: EXCBADACCESS (0x0001)+
+Codes: KERNINVALIDADDRESS (0x0001) at 0x30386000+
+Thread 0 Crashed:+
+0 libobjc.A.dylib 0x90a40100 objc_msgSend + 32+
+1 com.apple.PMMUG.UserGeneral 0x0157315c HomeDirItemComparator(objc_object*, objc_object*, void*) + 29708+
+2 com.apple.WorkgroupManager 0x0005830c +[Searcher(PrivateMethods) callAddItemsToResultsSelector:] + 156+
+3 com.apple.Foundation 0x92beba0c __NSFireMainThreadPerform + 276+
+4 com.apple.CoreFoundation 0x9080eae0 __CFRunLoopPerformPerform + 104+
+5 com.apple.CoreFoundation 0x907de4fc __CFRunLoopDoSources0 + 384+
+6 com.apple.CoreFoundation 0x907dda2c __CFRunLoopRun + 452+
+7 com.apple.CoreFoundation 0x907dd4ac CFRunLoopRunSpecific + 268+
+8 com.apple.HIToolbox 0x93295b20 RunCurrentEventLoopInMode + 264+
+9 com.apple.HIToolbox 0x9329512c ReceiveNextEventCommon + 244+
+10 com.apple.HIToolbox 0x93295020 BlockUntilNextEventMatchingListInMode + 96+
+11 com.apple.AppKit 0x9377aae4 _DPSNextEvent + 384+
+12 com.apple.AppKit 0x9377a7a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116+
+13 com.apple.AppKit 0x93776cec -[NSApplication run] + 472+
+14 com.apple.AppKit 0x9386787c NSApplicationMain + 452+
+15 com.apple.WorkgroupManager 0x00003144 _start + 760+
+16 com.apple.WorkgroupManager 0x00002e48 start + 48+
+Thread 1:+
+0 libSystem.B.dylib 0x9004a6e8 syscallthreadswitch + 8+
+1 com.apple.Foundation 0x92bf65dc +[NSThread sleepUntilDate:] + 152+
+2 com.apple.AppKit 0x93817a10 -[NSUIHeartBeat _heartBeatThread:] + 1100+
+3 com.apple.Foundation 0x92bde1a0 forkThreadForFunction + 108+
+4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96+
+Thread 0 crashed with PPC Thread State 64:+
+srr0: 0x0000000090a40100 srr1: 0x100000000000f030 vrsave: 0x0000000000000000+
+cr: 0x44002228 xer: 0x0000000000000000 lr: 0x000000000157315c ctr: 0x0000000090a400e0+
+r0: 0x000000000157315c r1: 0x00000000bfffe4b0 r2: 0x0000000030386000 r3: 0x0000000005f31b40+
+r4: 0x0000000090aa3fa8 r5: 0x000000000158cf78 r6: 0x00000000003fe758 r7: 0x0000000005f02200+
+r8: 0x000000000000078c r9: 0x0000000000000009 r10: 0x00000000003fe750 r11: 0x000000006f543fa8+
+r12: 0x000000000000357b r13: 0x0000000001593048 r14: 0x0000000000000000 r15: 0x0000000005f30440+
+r16: 0x00000000003ffed0 r17: 0x0000000001593048 r18: 0x0000000000000000 r19: 0x000000000158cf98+
+r20: 0x0000000001593048 r21: 0x000000000158cf88 r22: 0x0000000001593048 r23: 0x0000000005f44f20+
+r24: 0x00000000003fe750 r25: 0x000000000158cf78 r26: 0x0000000005f122b0 r27: 0x0000000005f31700+
+r28: 0x0000000001593048 r29: 0x0000000000000000 r30: 0x0000000005f31b40 r31: 0x0000000001573048+
+Binary Images Description:+
+0x1000 - 0x95fff com.apple.WorkgroupManager 10.4.4 (230.2.51) /Applications/Server/Workgroup Manager.app/Contents/MacOS/Workgroup Manager+
+0x48d000 - 0x4a8fff com.apple.PMMUG.ComputerGeneral 2.2 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/ComputerGeneral.PMMUG/Contents/MacOS/ComputerGener al+
+0x4b1000 - 0x4d1fff com.apple.PMMUG.GroupGeneral 2.2 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/GroupGeneral.PMMUG/Contents/MacOS/GroupGeneral+
+0x4dd000 - 0x4e7fff com.apple.PMMUG.Nimrod 1.1 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/Inspector.PMMUG/Contents/MacOS/Inspector+
+0x508000 - 0x52bfff com.apple.PMMUG.NAdmin 1.1 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/NAdmin.PMMUG/Contents/MacOS/NAdmin+
+0x53a000 - 0x568fff com.apple.PMMUG.Privs 2.3 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/Privs.PMMUG/Contents/MacOS/Privs+
+0x6c1000 - 0x757fff com.apple.mcx.prefpluginone 1.3.1 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/MMPlugInOne.PMMUG/Contents/MacOS/MMPlugInOne+
+0x1535000 - 0x158afff com.apple.PMMUG.UserGeneral 3.3 /Applications/Server/Workgroup Manager.app/Contents/PlugIns/UserGeneral.PMMUG/Contents/MacOS/UserGeneral+
+0x8fe00000 - 0x8fe52fff dyld 46.12 /usr/lib/dyld+
+0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib+
+0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib+
+0x9021b000 - 0x90268fff com.apple.CoreText 1.0.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText+
+0x90293000 - 0x90344fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS+
+0x90373000 - 0x9072efff com.apple.CoreGraphics 1.258.75 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics+
+0x907bb000 - 0x90894fff com.apple.CoreFoundation 6.4.7 (368.28) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation+
+0x908dd000 - 0x908ddfff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices+
+0x908df000 - 0x909e1fff libicucore.A.dylib /usr/lib/libicucore.A.dylib+
+0x90a3b000 - 0x90abffff libobjc.A.dylib /usr/lib/libobjc.A.dylib+
+0x90ae9000 - 0x90b59fff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit+
+0x90b6f000 - 0x90b81fff libauto.dylib /usr/lib/libauto.dylib+
+0x90b88000 - 0x90e5ffff com.apple.CoreServices.CarbonCore 681.15 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore+
+0x90ec5000 - 0x90f45fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices+
+0x90f8f000 - 0x90fd0fff com.apple.CFNetwork 129.20 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork+
+0x90fe5000 - 0x90ffdfff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore+
+0x9100d000 - 0x9108efff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit+
+0x910d4000 - 0x910fdfff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata+
+0x9110e000 - 0x9111cfff libz.1.dylib /usr/lib/libz.1.dylib+
+0x9111f000 - 0x912dafff com.apple.security 4.6 (29770) /System/Library/Frameworks/Security.framework/Versions/A/Security+
+0x913d9000 - 0x913e2fff com.apple.DiskArbitration 2.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration +
+0x913e9000 - 0x913f1fff libbsm.dylib /usr/lib/libbsm.dylib+
+0x913f5000 - 0x9141dfff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration+
+0x91430000 - 0x9143bfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib+
+0x91440000 - 0x914bbfff com.apple.audio.CoreAudio 3.0.4 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio+
+0x914f8000 - 0x914f8fff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services+
+0x914fa000 - 0x91532fff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE+
+0x9154d000 - 0x9161ffff com.apple.ColorSync 4.4.9 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync+
+0x91672000 - 0x91703fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore+
+0x9174a000 - 0x91801fff com.apple.QD 3.10.24 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD+
+0x9183e000 - 0x9189cfff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices+
+0x918cb000 - 0x918ecfff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis+
+0x91900000 - 0x91925fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent+
+0x91938000 - 0x9197afff com.apple.LaunchServices 182 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices+
+0x91996000 - 0x919aafff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis+
+0x919b8000 - 0x919fefff com.apple.ImageIO.framework 1.5.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO+
+0x91a15000 - 0x91adcfff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib+
+0x91b2a000 - 0x91b3ffff libcups.2.dylib /usr/lib/libcups.2.dylib+
+0x91b44000 - 0x91b62fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib+
+0x91b68000 - 0x91c1ffff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib+
+0x91c6e000 - 0x91c72fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib+
+0x91c74000 - 0x91cdcfff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib+
+0x91ce1000 - 0x91d1efff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib+
+0x91d25000 - 0x91d3efff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib+
+0x91d43000 - 0x91d46fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib+
+0x91d48000 - 0x91e26fff libxml2.2.dylib /usr/lib/libxml2.2.dylib+
+0x91e46000 - 0x91e46fff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate+
+0x91e48000 - 0x91f2dfff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage+
+0x91f35000 - 0x91f54fff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib+
+0x91fc0000 - 0x9202efff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib+
+0x92039000 - 0x920cefff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib+
+0x920e8000 - 0x92670fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib+
+0x926a3000 - 0x929cefff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib+
+0x929fe000 - 0x92aecfff libiconv.2.dylib /usr/lib/libiconv.2.dylib+
+0x92aef000 - 0x92b77fff com.apple.DesktopServices 1.3.6 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv+
+0x92bb8000 - 0x92de3fff com.apple.Foundation 6.4.8 (567.29) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation+
+0x92f10000 - 0x92f2efff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib+
+0x92f39000 - 0x92f93fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib+
+0x92fb1000 - 0x92fb1fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon+
+0x92fb3000 - 0x92fc7fff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture+
+0x92fdf000 - 0x92feffff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition+
+0x92ffb000 - 0x93010fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI+
+0x93022000 - 0x930a9fff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink+
+0x930bd000 - 0x930c8fff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help+
+0x930d2000 - 0x930fffff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting+
+0x93119000 - 0x93128fff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print+
+0x93134000 - 0x9319afff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering+
+0x931cb000 - 0x9321afff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices+
+0x93248000 - 0x93265fff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound+
+0x93277000 - 0x93284fff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels+
+0x9328d000 - 0x9359bfff com.apple.HIToolbox 1.4.9 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox+
+0x936eb000 - 0x936f7fff com.apple.opengl 1.4.7 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL+
+0x936fc000 - 0x9371cfff com.apple.DirectoryService.Framework 3.1 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce+
+0x93732000 - 0x93733fff com.apple.ServerControl 10.3.0 /System/Library/PrivateFrameworks/ServerControl.framework/Versions/A/ServerCont rol+
+0x93770000 - 0x93770fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa+
+0x93772000 - 0x93da5fff com.apple.AppKit 6.4.7 (824.41) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit+
+0x94132000 - 0x941a4fff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData+
+0x941dd000 - 0x942a1fff com.apple.audio.toolbox.AudioToolbox 1.4.5 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox+
+0x942f3000 - 0x942f3fff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit+
+0x942f5000 - 0x944b5fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore+
+0x944ff000 - 0x9453cfff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib+
+0x94544000 - 0x94594fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib+
+0x9459d000 - 0x945b1fff com.apple.CoreVideo 1.4 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo+
+0x945bf000 - 0x945e0fff com.apple.framework.Admin 1.5.6 /System/Library/PrivateFrameworks/Admin.framework/Versions/A/Admin+
+0x945f4000 - 0x945f4fff com.apple.AFPDefines 3.1 /System/Library/PrivateFrameworks/AFPDefines.framework/Versions/A/AFPDefines+
+0x946a3000 - 0x946b5fff com.apple.frameworks.preferencepanes 11.0.1 /System/Library/Frameworks/PreferencePanes.framework/Versions/A/PreferencePanes +
+0x946c2000 - 0x946defff com.apple.securityfoundation 2.2 (27710) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation+
+0x946f2000 - 0x94736fff com.apple.securityinterface 2.2 (27692) /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face+
+0x9475a000 - 0x94769fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib+
+0x94771000 - 0x9477efff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib+
+0x947c4000 - 0x947ddfff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib+
+0x94b76000 - 0x94be7fff libstdc++.6.dylib /usr/lib/libstdc+.6.dylib
+0x96046000 - 0x9604bfff com.apple.URLMount 2.1.7 /System/Library/PrivateFrameworks/URLMount.framework/Versions/A/URLMount+

Server admin not seeing directory users from workgroup manager

I am setting up a new Xserve with Snow Leopard (get 'em while we can). We have eight other XServes running Leopard or Snow Leopard server. On those machines we have set up file sharing over AFP. The machines are connected to our Active Directory server and our users authenticate using their domain passwords. All of our other servers were setup in Leopard and were upgraded to Snow Leopard. We have not had any issues authenticating to those boxes.
This is the first one that we have actually setup new-out-of-the-box in Snow Leopard. I can set Workgroup Manager up to connect to our AD, and can see and search my domain users and groups in Workgroup Manager. When I try to set up my File Shares in Server Admin, none of my domain users show up-only local accounts.
What have I missed? In Leopard, when I connected to the domain, the users immediately became available in Server Admin. Not so in SL, at least on this box.
Help?

Hi
The first thing to check is if you've bound the Server to the AD Domain. The second thing is if the /Active Directory/All Domains is in the Search Policy. If you don't do either of these WorkGroup Manager won't display anything coming from the AD Schema.
In 10.6 Apple moved the Directory Utility from where it used to be in /Applications/Utilities and made it part of the Accounts Preferences Pane. Perhaps it's this change that's confusing you? I would not advise doing this but it's also possible you used the Server Setup Assistant to do most of the configuration? If you did maybe something went wrong at that stage (won't be the first time) and you need to manually bind the Server instead?
As ever make sure this server is using the same NTP Server as the others.
Tony

Authenticating Workgroup Manager to Active Directory.

Dear all,
I've searched the forums and Internet and tried various things that could help my situation but I'm still having issues.
I am running 10.4.11 server 10.4.11 client machines. All machines and server are connected to Active Directory via the built in AD plugin.
Logging on to a client machine with an AD login works fine, no issues.
System image deployment over the network from the Xserve work fine.
The I have is implementing managed preferences from Workgroup Manager. When I open it, it will show me all of the users and groups. It says:
*Viewing directory: /Active Directory/All domains. Not authenticated*
When I click the padlock to authenticate, and enter my domain admin username and password, it says:
*The login information is not valid for this server.*
My login works as it allows me to add machines to the domain.
More info available as needed. If anyone can assist, thanks in advance.
Regards,
M.

Hi
Viewing directory: /Active Directory/All domains. Not authenticated
When you bound the server to the Active Directory Realm what user name and password did you use? It will be this name and password that you will need to authenticate to the Active Directory node. This name and password should be the one that already exists on the AD that has authority for that server. Its also the name and password that should be used when binding mac clients to the AD node using the Active Directory plugin in Directory Access.
This name and password can be the same as the one created for promoting your server to OD Master (diradmin). Its a good idea to create this account on the AD first (make it authoratative for the AD) before promotion and client binding.
If you want to augment the AD with OSX Server managed preferences (MCX) then create a group within the /LDAPv3/127.0.0.1 node (assuming you have promoted the server to OD Master and disabled sso). Have two windows open in WGM (better done from a client). One window will show you the AD node and the other the OD node. Drag users or groups from the AD node into the newly created group in the OD node.
Apologies if you already know this, Tony

AD Users not showing up in Workgroup Manager

Hi, I'm configuring a new installation of 10.4 server on an Intel Xserve to integrate with an already existing AD domain and provide group policies to Mac users via OD.
So far, the install has been so smooth, fast, and simple. The Xserve has been joined to the AD domain, Kerberos is running, and I have an active OpenDirectory Master.
Now, when I go to Workgroup Manager, the users in the AD domain do not show up and if I try to authenticate with the same username and password I used to bind to the domain I get the error "The login information is not valid for this server". Also, if I use dscl I can navigate to "/Active Directory/All Domains/Users" but if I try to run ls I get "ls: DS error: eDSCannotAccessSession".

Hi Tim
You are almost there but not quite.
Firstly its not important if the AD Server does not have a reverse pointer. As long as the OD Master does that should be enough. Ultimately it would be better if there was one configured but there is not much you can do about that is there? I doubt very much if the AD Admin is going to want to fiddle with a 'live' DC's DNS Service if its likely to affect his domain?
What I generally do is this:
Make sure SMB Digital Signing is Not Enabled on the AD Server. There should be at least two places where this has to be disabled. If the 'powers that be' have defined SMB Digital Signing then SFM (Services For Macintosh) must be installed. If its 'nada' to both then you will be severely limited in integrating OSX Server and mac clients with AD. Yes of course make sure there is an (A) and Reverse PTR for the mac server. Next bind all mac clients to the AD Server and make sure the AD Server is listed first for Authentication and Contacts, also make sure mac clients are using the AD for authentication. Test and verify a mac client to see if (a) home folders are created and accessed and that mac clients successfully log in. You sometimes don't get the two.
Now turn your attention to OSX Server. Make sure you have (a) reserved a fixed IP address for it in the AD's DHCP Service and you have placed the AD's IP address as the primary IP address in the DNS Server's field in the Network Preferences Pane (b) tested DNS fully and that OS X Server resolves correctly on the forward and reverse pointers for itself. Now bind OSX Server to the AD using the Active Directory plug in in Directory Access and an AD admin account that has authority for the Domain. Launch Workgroup Manager and you should see AD Users and Groups have 'flowed' into the /Active Directory/All Domains node. Quit out of WGM and launch Server Admin. Enable the AFP Service and set the authentication method to Any Method. Select Open Directory and change the Role from Standalone to Open Directory Master. You will be prompted to create the default Directory Administrator account diradmin (UID 1000). You should see the Kerberos Realm and search base fields autofill with the fqdn of the Server. Change both of these to reflect the fqdn of the AD Server. For example if the fqdn of your mac server is osxserver.addomain.com and the windows server is adserver.addomain.com then change the information presented in thos fields to ADSERVER.ADDOMAIN.COM and dc=adserver,dc=addomain,dc=com. As you can see you should only need to change the first part. Click OK or Continue and you should now have an OD Master that is not the KDC (Kerberos has been stopped). This is the state you want it be in before going any further. You can now 'kerberize' the AFP Service you started previously by selecting the kerberize button and using the same AD admin account you used to previously bind the server to the AD. To doublecheck if the AFP Service has been kerberized launch terminal and issue:
sudo kadmin.local -q list_principals
You should see an entry for [email protected] amongst others.
Now launch Directory Access and make sure the server's loopback address is listed in the LDAPv3 plug in. Make sure that the server is listed first in the Authentication and Contacts fields. Quit out of Server Admin and launch WGM. Navigate to the /LDAPv3/127.0.0.1 node and you should see diradmin waiting for you. Open another connection window in WGM and navigate to the /Active Directory/All Domains node. When you authenticate the /LDAPv3 node you use diradmin, when you authenticate the /Active Directory node you use the AD admin account. Create a Group in the /LDAPv3 node select the + icon and toggle between the two nodes as you select users or groups and add them to your /LDAPv3 node. Once you are happy select a preference to manage, apply desired changes and save the changes. This is better done on a client machine with the Server applications installed.
Back to your mac clients. Begin to join these to the LDAP node using the LDAPv3 plug in in Directory Access. Use the Server's IP Address or its FQDN if the DHCP Server is also doling out DNS information to networked clients. Its IP address should be good enough. Don't bother with authenticated binding and make sure clients are not using the OD master for authentication and contacts. Lastly make sure the Active Directory/All Domains and the /LDAPv3/OD Master IP address or fqdn are in that order for browsed directories.
Its best if you have a secure local admin account on all your mac clients and that each mac is named differently. Set this in the Sharing Preferences Pane.
Begin to test. If everything is OK you should now have mac clients logging into home directories controlled by AD as well as OD Managed Preferences being applied.
One final thing. Avoid using .local as the basis for the DNS Service. I realise in your environment you have no control over that. In which case make sure all mac clients have the AD's .local domain name in the Search Domains field in the Network Preferences Pane. If your clients have Leopard installed you should not have to bother as Leopard copes with .local name resolution better than previous versions of the OS.
As ever how successful you are and how long it takes will depend mostly on how well the AD is configured. There is no magic bullet that can be used on the mac side to fix a poorly configured AD environment. If everything is as it should be regarding the AD Server it should not take you longer than 10-20 minutes (after server installation) for the server and possibly 2-3 minutes for each client. It really should not take that long.
Does this help?
Tony

Workgroup manager without OSX server

A little trick picked up at an IT conference....
Im using Workgroup manager on client machine to get a high level of control on local user accounts.
Does anyone know of a way the get WGM control of AD authenicated users on the same local machine?

Hi
If I understand your post correctly then yes - up to a point. Installing Server Admin tools (WGM and SA) on a client is a good way of defining MCX for users and groups that exist on the AD. Bind the client to the AD using the Active Directory plug-in in Directory Utility (/Applications/Utilities), join client to an OD Master (if you are also looking for this functionality) using the LDAPv3 plugin using the same application and you should now see all users and groups as they exist on the AD. Select the Preferences option in the Workgroup Manager menu and enable the 'Show all tabs and inspector' option. You should now see a new icon appear by the side of the computer lists icon - looks like a bullseye. Select this, select users from the pop up menu and you can now inspect all the schema attributes and values for users and groups that exist on the AD.
You can create a group in the OD node and drag users and/or groups that exist in the AD node into that group, define managed preferences from there. On the client side you join the AD first and the OD second and make sure they are in that order in the Authentication and Contacts tabs. De-select the authentication option in the LDAPv3 plugin. Now clients will authenticate using their AD credentials, pick up their home folders as defined on the AD and have OD managed preferences be applied to them. All the principals in this environment participate in SSO.
You can - if you wish - edit some of the unassigned attributes with values of your own to give you extra functionality. Its not a good idea to edit existing attributes and values. Besides I don't think the AD will allow it, you'll get a dsnoderroplugin error message. If you want to edit AD attributes and values you'll have to do it on the AD itself using the relevant schema modification tool.
Tony

Can not locate Workgroup Manager; possibly not installed?

Here's the story:
I'm trying to get my new camera software installed and one of the steps is to launch Image capture.
Image capture gives me an error saying: "No Image Capture Device connected."
Apple says to fix this I need to open Workgroup Manager (in /Applications/Server/) and change some preferences.
But, I can not find Workgroup Manager for the life of me. I used spotlight with no luck. I also don't have a folder in Applications titled Server. This worries me and makes me wonder if the program could have been deleted or not installed at all?
Any suggestions on how to find WgM would be welcome.

Whoa... somebody got confused someplace... I wouldn't guess you are running OSX Server on a MacBook, but the oSX CXlient instead, so no idea how Apple came up wih that solution.
You likely should not have a Server folder there, nor the APP they speak of.
What kind of Camera exactly, and how does it connect?

I am using 10.6.8 and I cannot get an Imac to appear in workgroup manager, the mac is bound to both AD and OD. I have removed the bindings, rebuilt the mac and also removed it from bot system but still it does not appear in OD in work group manager.

I have a mac which is connected to a network and is bound to both OD and AD with no issues on my server when I try to manage it through Workgroup manager it does not appear.
I have unbound it , removed it from both systems completely and even rebuilt it but it still does not appear in WGM.

If your server is 10.6 and your client is 10.7 you'll have to add it manually to WGM
via mac address. 10.7 clients don"t automatically appear in 10.6 server wgm

Problem with home directories NOT in Users and Workgroup manager

I am setting up a Leopard server (10.5.3) with the users directories in /h1. This is mounted as /Volumes/h1.
It is exported under AFP as /h1.
When I try to get Workgroup manager to create a home directory, I can enter the home directory as:
afp://quattro.innocon.com/h1
path is 'user'
Full path is:
/Network/Servers/quattro.innocon.com/Volumes/h1
However, when I try to log in as this this user, it says that the directory /Network/Servers/quattro.innocon.com/h1/username does not exist.
I cannot seem to figure out why the 'Volumes' part of the full path is being lost.
Any ideas on how to get this right?

have you checked to see if /Network/Servers/quattro.innocon.com exists?
I'm having ALOT of issues with automount not picking up on the mount-maps set by Open Directory.. If anyone has any solutions on this it would be great.

10.6.8 Server - workgroup manager not authenticated

Similar Messages

Maybe you are looking for