![]() ![]() Without the user filter, all these users appeared in the shared buddy list AND all could log in. Except for the admin user, they should all be black with a red asterisk. I then clicked ‘Enable contact list group sharing,’ named it, clicked ‘Share group…’ and ‘All users.’īefore you click ‘Save,’ take a look at the listed group members. Under Users/Groups:Groups:Group Summary, I selected an OD group that contained all my users.Which allowed my iChat clients to send their passwords securely. If you don’t do this, the above user filter will keep your admin user from registering.Ĭontinuing to the Admin Console, I did the following… In the Chat field, add a record, and select ‘Jabber’ from the popup menu. This is easily done in Workgroup Manager under the Info tab. IMPORTANT: Before you continue, add a Jabber address to the Open Directory user that will be administering OpenFire. User Filter= (&(uid=)(apple-imhandle=Jabber*)) Host= The FQDN of my Open Directory serverīase DN= dc=subdomain,dc=domain,dc=lan (obviously, you’ll put your base dn here)Īuthentication: I don’t believe this is necessary for OD. Profile Settings= Directory Server (LDAP) I did the basics when running through the initial setup:ĭomain= The FQDN of the server (automatically entered) (Credit to Wolf Gilbert : Link to thread) $JAVA_HOME/bin/java -server -jar “$OPENFIRE_HOME/lib/startup.jar” =/usr/local/openfire/lib& JAVA_HOME= /System/Library/Frameworks/amework/Versions/1.6/Home It wasn’t the first thing I did, but knowing what I know now, I would have done it right after running the install pkg. It wasn’t honoring my settings in Java Preferences, so I modified /usr/local/openfire/bin/extra/openfire-launchd-wrapper.sh. OpenFire Server: Mac OS X Server 10.5.8 (Intel Xserve)Ĭlients: Various Mac OS X 10.4.11 - 10.6.3 - iChatįirst, I couldn’t stand that OpenFire was using 32bit Java 1.5. Open Directory Server: Mac OS X Server 10.6.3 (MacMini Server) I hope this helps fellow Mac users get their OpenFire servers up and running more quickly than I did. Some of this I’ve learned from others and I will try to give credit insofar as my notes and memory allow. I’ve learned a few things that might come in handy for others in my shoes. I’ve spent the last day setting up OpenFire in our Mac environment. Now you are left with the previous version of Java.I apologize if all this has been covered elsewhere… Quit all open applications and run the installer. Download the Mac OS X 10.6.3 combo updater, which weighs in at a hefty 784MB but is a troubleshooting godsend. ![]() You may need to restore some saved username/password information, browser information, etc. Make sure to select “Preserve Users and Network Settings.” After installation, you’ll be left with an earlier iteration of Mac OS X 10.6.x (current retail discs include Mac OS X 10.6.2), but an otherwise largely intact system. When prompted, choose the normal “Install” option. Insert your Snow Leopard installation disc, then restart while holding down the C key. Navigate to Applications/Utilities/Java and select the previous iteration of Java as the preferred version, then restart. Download the standalone Java update installer and re-run it. Most of these issues can be resolved via one of three methods. This had been an issue after the last update at the end of 2009.” Has anyone come across this issue and is there a solution at this time. Network access broken.angelaravi: “It appears that the new Java update that was just released is affecting Network Connect and is not allowing users to remotely access their networks.They show up as a blue cube with a question mark.” jpg, jpeg, bmp, etc.) they no longer appear. iPhoto, or any other storage file, and regardless of their format, i.e. The one that is my primary problem right now is that when I embed images in an email (regardless of where they come from on my system, i.e. Richard in NYC writes: “Well, now some weird things have started happening with my system. However, the heap size was normal when the java process crashed from my jconsole log.” The crash log indicates that the hot-spot complier was trying to allocate a large amount of memory. The java process will simply uses up all available memory and crashes. Apple Discussions poster Howard SOA writes: “one of my server applications suffers serious memory leak problem. Among the reported problems: Free Mac Os X 10.6 A handful of users have reported issues after applying the recently released Java for Mac OS X 10.6 Update 2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |