|
|
10.4: Manually add a Tiger Software Update Server
This hint is way too complicated. There's no need to manually edit a plist file; the 'defaults' command does everything you need. There are three options, depending on exactly how you want the preference saved:
10.4: Manually add a Tiger Software Update Server
giskard22,
10.4: Manually add a Tiger Software Update Server
Thank you for your comments. I didn't know about the defaults command and couldn't figure out how to make the preference system wide. Thanks.
10.4: Local SUS not reporting correctly
Great hint! However, I am obviously doing something wrong. I use the defaults command via Terminal to change the SUS to my local server "http://10.0.1.2:8088/" and the TestMac finds the SUS server as expected. However, the TestMac reports that no updates are required. When I point the TestMac back to the standard Apple SUS it reports the correct updates. Any ideas?
TIA!
10.4: Manually add a Tiger Software Update Server
I've moved a client machine out of an office where I had modified the SUS address to be our own server. Now that this client machine is in a different environment, I'd like to point it back to the official Apple Software Update Server but, cleverly, don't know that address. Anyone?
10.4: Manually add a Tiger Software Update Server
You don't actually need the address. If you remove the key pointing to your internal server it will default back to Apple. Try: -
or if you added it for root: -
or System-wide: -
I would suggest doing a
10.4: Manually add a Tiger Software Update Server
this process doesn't work for me. i am able to force any user to revert to using apple's own softwareupdate servers by DELETING those pref files from any user's home folder as well as the root directory. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|