I am opening up a separate discussion although it sort of relates to my first issue this morning. SEPM ran out of disk space. When it did, it disabled the embedded database server. I cleaned up some disk space and fixed the issue. Once I did this, I turned the embedded database service back on and now it appears that all of my my computers are doing full updates. I have sites using GUPs so once they get the updates they need those sites won't have issues. The real problem is I have sites that do not have GUPs and are connected via a relatively slow WAN link. This is an issue because it appears like SEPM is issuing network wide full content updates even though the database server was down for maybe, 4 or 5 hours. 

What can I do? Do I have to sit here and wait for the updates to complete? I wouldn't care so much if it was off peak usage hours. Is there a way to delay the updates immediately?

Thanks in advance.

Stop SEPM service..

What would the ramifications be to limiting the number of connections or amount of bandwidth the web server can handle from IIS? IE drop it from unlimited to like 3 connections or reduce the bandwidth from unlimited to like 3mb/s. Would this only allow 3 clients at a time to download the content? Would it prevent the downloads from the content directory from exceeding a high bandwidth? If memory serves me the content is just shared out via web page. 

i think you would have made clients  in pull mode, after taking to sepm, sepm directed the clients to take from gup, now clients are going to gup, thats the reason even after shutting down sepm b/w is still high.make the content revisions in SEPM to 3, that would free the DB

I actually scaled back the content revisions to 5 and added 5 gigs of storage to the server. That seems to be working out pretty well. 

No comments on what may happen if you were to set limits on IIS for number of connections or bandwidth in regard to content updates to clients?

You can set those types of limits in your GUP policy

You can limit the connection in IIS for network as well as for content updates, they are stored in virtual directories as you see in IIS, if they are taking from GUP, then these limits wont apply :)

Sure you can, but what if some sites don't have GUPs?  =) We have a total of 390 devices currently on SEP. Of those 390 there are only about 70 or so that have GUPs associated with them. Because management doesn't understand the concept of a GUP they do not wish to just assign random workstations GUP responsibilities, they want the GUPs to be "server" grade devices. We only have about 5% of our locations with these "server" grade devices. No server on site means no gup... which means the clients at that remote site are managed by the SEPM, which means no throttling. I could in theory, make the SEPM a GUP and then I could control the bandwidth as you pointed out, but doing so wouldn't be without a lot of work and there would be many other things to consider. 

I don't believe it's recommended to make the SEPM a GUP. For what you need, it sounds like IIS tweaking is the way to go.

I think this is what you are looking for.

How to throttle network bandwidth used by the Endpoint Protection Manager (SEPM) website in Microsoft's Internet Information Server (IIS)

Nice Rafeeq. That's what I was looking for. Thanks to Brian81 and Vikram as well.