The Background Intelligent Transfer Service is stopped state is something you'll want to address. On a desktop OS, BITS should be configured with Automatic Start and it should be running. (On Win7 you can also configure it with Delayed Start to help with system start-up performance.) If BITS is not running, the WUAgent cannot download updates, and thus updates will not be installed.
The "error" on the Content v-dir when WSUS is running on Server2008R2 is caused because the Directory Browsing module is installed, but the client is being denied access. IIS returns an HTTP 403.14 to the client, and the Diag Tool traps the HTTP 403 as a proxy error (even though this isn't actually a proxy error). Generally, the Directory Browing module should not be installed on a WSUS server because it is not needed. The best option would be to remove that module. In the event that some other app requires that module (e.g. I presume from the server name that this may also be a SEP server), then just be aware of the source of the message and that it can be safely ignored in this instance.
Now, the other question here is what the significance of MDT2012 might be. I'm not understanding that part of the question.