Currently Being ModeratedSep 13, 2011 5:29 AM (in response to damonposey)
Same thing here as well. Binding to AD and OD. AD works fine, shows up without issue. However, OD binding appears to work, however it doesn't show up in Computers of Workgroup Manager. I'm not sure what the next step might be.
Currently Being ModeratedSep 13, 2011 7:32 AM (in response to damonposey)
So one of my guys did figure out a workaround on this one. If you go into Workgroup Manager, then under Accounts click on Computers tab and New Computer, you can manually enter the computer, On the General tab enter the name for the computer and on the Network tab enter the MAC address (use the Ethernet MAC address). Then when you go into Computer Groups, it will appear and can be added to a group and everything else seems to work normally.
Try it out and let me know. Bit of a hassle, but it seems to work for now.
Currently Being ModeratedOct 27, 2011 5:51 AM (in response to damonposey)
Same problem here with 10.7.2 client and server. I've just start to look at Lion server.
If I join a client to the server, under WorkGroup Manager I can't see nothing. If i bind my clients to the server, I can see only a "$" entry in WorkGroup Manager with Hardware ID Corresponding with the binded machine.
Currently Being ModeratedNov 16, 2011 3:47 PM (in response to damonposey)
My colleague Kyle made this scrip to help get 10.7 lion clients into Workgroup Manager. The problmes is in the mDNSresponder in 10.7 it will not talk to WGM corectly. Blast this out as a unix comand in ARD to the 10.7.x clients and they will show up in WGM long enuff for you to get them into a group. once you stop the command the comptuers will not be able to be seen by WGM but will stay in the group. This could also be made into a lunchd item if you want them to alwas show up.
# Created by Kyle on 11/8/11.
hostname=`hostname -s | cut -c 1-`
MAC=`ifconfig | grep en0 -A2 | grep ether | cut -c 8-24`
UUID=`system_profiler | grep UUID | cut -c 22-`
mDNS -R ""$hostname" ["$MAC"]" _workstation._tcp. local 9 uuid="$UUID"
Currently Being ModeratedDec 15, 2011 9:45 PM (in response to MattMPS)
I'm experiencing the same thing too. 10.7.2 clients and 10.7.2 OD master.
Thanks for the script Kyle and Matt. I thought I was going crazy with this issue, but glad others are experiencing it too. I will use the script for now and hopefully 10.7.3 will resolve this.
Currently Being ModeratedJan 31, 2012 11:09 AM (in response to MattMPS)
Thanks to you for posting this, and to your friend Kyle for writing it! This worked like a charm for me, I was losing my mind, and wasted an hour on the phone with Enterprise support listening to them berating my setup before I found this. Anyway, again, thanks!
Message was edited by: RCPSadmin
Currently Being ModeratedFeb 18, 2012 8:13 AM (in response to ivaldiz)
Actually it seems to not be fixed in 10.7.3. I got 144 Clients and 2 Servers here. All 10.7.3. Only 10 showed up.
I used Kyle's script and it worked like a charm! Big kudos man!
Currently Being ModeratedMay 18, 2012 2:31 PM (in response to damonposey)
hmmm, that's interesting. I have a 10.6.8 server and have had no problems whatsoever binding over 300 Lion clients and then seeing them in WGM. I have tried this with 10.7.2, 10.7.3, and now 10.7.4 clients without issue.
My 10.6.8 server is also my DNS server ... and I did set up LDAP port inquiries to point to my 10.6.8 server ... maybe that's why ... ? I thought I would throw it out there in case it might help someone else ...
Currently Being ModeratedJun 3, 2012 1:20 AM (in response to damonposey)
I created a "Service" entry in DNS for ldap (_ldap._tcp) ... port 389 ... which points to my 10.6.8 authentication server ...
As I said, I don't know if this helps but we have not had this issue so I am wondering why as well.
We will be moving to Lion in the next few days so I hope that transition is smooth ... you hate to change something that is working ...