Just to play it safe I rebooted the client, but to no avail, it will not see my local SUS. Unfortunately, the client still pings apple's SUS for updates. Finally, I re-bound the client to OD and re-added the machine to it's correct group in WM. I noticed the machine group still had a residual (broken?) member from the unbound client I manually removed this. Next, I checked WM and confirmed the computer record was gone. I noticed it was not pointed at my local SUS, so I checked the OD binding it was fine. I did this on several client computers with no success.įor example, today I was working on one of the Tiger clients. My immediate thought was to unbind/rebind the problematic machines. As I said, results are mixed across OS's, but some clients will not "sync" at all. I noticed that some of the clients (10.4/5/6 alike) seemed to get the settings immediately, others didn't show the new settings until after a reboot. When I first configured all this stuff on the server (a few weeks ago) I was closely monitoring a few of the client machines to confirm that they received the custom settings.
My problem is that the server pushes the SUS settings to some of the client machines, but not all. Each group is configured with a custom SUS URL, and the managed client computers are members accordingly (see ) In Workgroup Manager, I have created 3 machine groups for each client OS.
The clients bound to the OD are a variety of Mac's running OS X 10.4, 10.5 or 10.6. The SUS is configured to serve Tiger, Leopard and Snow Leopard clients (see ) I have also enabled and configured Software Update service on the machine.
#MACOS SERVER NOT UPDATING MAC OS X#
I have an Xserve G5 running Mac OS X Server 10.5.8 configured as an Open Directory master.
0 kommentar(er)
