Do you have any MCX settings or policies pointing your machines to your 10.5
SUS?

If so, changing them manually would only take effect until the next time the
policy or the Management Framework is enforced...

I had this problem until I got my SUS upgraded to Snow Leopard Server.
On Feb 18, 2010, at 10:48 AM, Steve Wood wrote:

What I did was create a Smart Computer Group of 10.6x clients, and created a new policy, scoped to that group, run once, which executed the following command:

jamf removeSWUSettings

As others have said, you have to watch Workgroup Manager or other policies which set a default SWU server (I think I disabled any policies in Casper that set the SWU server/undefined any SWU servers, as I didn't want this set vs. reset battle to continue - and I pretty much knew any new machines hitting my network were going to be 10.6).

Hope this helps,

--Robert

I had a policy that enforced the SWU settings, and it was set to run once a
day, but I've disabled that.

And the issue in the JSS was happening instantly. I could go into the
inventory for a machine, change the SWU setting, click Save, and then
immediately go back into Edit the settings for that machine and it would be
back to my internal SWU server.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475
Sent from Dallas, TX, United States

Also, there are a couple ways to go about setting which SUS a machine points
to.

1. Set up smart groups for 10.5 and 10.6 machines. Create a policy to set your 10.6 SUS and click the 'Override Default Settings for Policy...' button and tell the machines to use your new SUS.
2. Use MCX profiles for 10.5 and 10.6 machines. Tell each of them to point to their respective SUS's via the com.apple.softwareupdate template.

Bob

What I did was create a Smart Computer Group of 10.6x clients, and created a new policy, scoped to that group, run once, which executed the following command: jamf removeSWUSettings

Oh, brilliant! I didn't even think about using the jamf binary to do this!

As others have said, you have to watch Workgroup Manager or other policies

which set a default SWU server (I think I disabled any policies in Casper that set the SWU server/undefined any SWU servers, as I didn't want this set vs. reset battle to continue - and I pretty much knew any new machines hitting my network were going to be 10.6).

I don't have any MCX policies setting this, and I've disabled my JSS policy
that enforces the SWU.

Thanks for the head slap on the jamf binary!

Steve