Changing the SUS to Apple's SUS for all clients.

Here is what I do in Terminal:

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate CatalogURL

Not a complete help, but you can do it using ARD.

Also, remember, the new Apple Caching Server doesn't even require you to touch the clients. Works very slick.

https://www.apple.com/support/osxserver/cachingservice/

Terminal command:

sudo jamf removeSWUSettings

Should also work.

So with the new SUS in Yosemite, should the update server for the Macs be Apples SUS address now? Then if they are on the network, they will pull updates from the new caching server?

In JAMF what would I put here: Settings > Computer Management > Software Update Servers.

Currently it's the IP address of my SUS.

Its all automatic. If you have a Apple Caching Server on your network, the clients (OS X or iOS) will automatically pull updates from the server without any setting needed. So you would HAVE to have the SUS address back to default on the clients.

Been working since 10.8 server I believe. It is especially awesome for iOS, very fast downloads!

But if it's not pointing to the internal server as it's SUS you lose the ability to pick and choose available updates... correct? I apologize if that seems elementary, but I haven't had an opportunity to use the caching server yet and we have to maintain a very controlled software update schedule and catalog.

Oh! I see...I think the only thing you can adjust is how much space the Caching Server uses. If you need to selectively push out Apple Updates you very well might be stuck with the old SUS server.

Thanks @lehman00,

So would I just delete this entry in the JSS, and leave it blank?

Settings > Computer Management > Software Update Servers.

All good suggestions. However, I do want to point out that you can create a quick and simple policy for this as it's built into the JSS already. Just create a new policy and in the "Software Update" section you can choose "Install Software Updates From" and then choose "Apples Software Update Server". No URL needed. Set your scope to "All Computers" with a frequency of "once per computer" and you should be 100% as per your request here.

Question:
We have been running the SUS server for a while, do we need to run both SUS and the Cacheing Server? Or does the Cacheing Server also include what the SUS provided?

That depends. here's the skinny from Apple (http://help.apple.com/serverapp/mac/4.0/#/apd74DDE89F-08D2-4E0A-A5CD-155E345EFB83)

Compare Caching service to Software Update service The Software Update server and the caching server both provide updates to software installed on Mac clients with some key differences: The Software Update server caches only Mac updates; the caching server can cache updates and App Store purchases for Mac computers and iOS devices. The Software Update server requires you to manually configure clients to only use a specific software update server; the caching server requires no client configuration. OS X and iOS devices automatically access the available caching server on the network they’re currently connected to, making it mobile-client friendly. For example, when a user is using an OS X or iOS device at work, the device uses the caching server at work. When the same user uses the same device at home, it automatically uses another caching server. The Software Update server downloads and caches all available updates when it first starts up; the caching server downloads and caches software based on OS X and iOS device requests. The Software Update server provides client management functionality, such as the ability for administrators to restrict which updates can be seen and downloaded by clients. The caching server doesn’t provide any client management functionality. If you need client management functionality, use the Software Update server for updating your Mac clients. Also, if you configure your client to use the Software Update server, it takes precedence and the client cannot use the caching server. Important: The Caching and Software Update servers can coexist on the same server, but they don’t share cached content, which may result in additional disk space being used.