Here’s a great tip on an issue you may run into if your using WSUS and Config Mgr 2007 for updates and defining settings via a Group Policy.This one comes from Anjana Kaku Tyagi, a Support Engineer in our Manageability group: ======== We have two options for resolving this issue: 1. Use the same WSUS server as the Software Update Point for the SCCM as well In this particular case we opted for the second workaround: To configure the WSUS server and the software update point server to be the same server with the same port number as well so that both the group policy and the SCCM use the same server as the update point. Configure the software update point to use a particular server and port # 2.Also, upgrading from older versions (up to Smarter Mail 6.x) can take up to several hours based on the amount of data.This is due to file structure changes that are in Smarter Mail 7.x.Microsoft is yet to release stand-alone ISOs for the RTM bits of Windows 8.1, so your only option to update right now is to use the built-in Store link.Lots of users, however, are provided with all kinds of errors, some of which block the installation process and restores the original Windows 8 configuration.The result is the same on the development system - multiple clients are unable to connect Outlook to the library and get the 0x80004005 error above. i dont know what im doing with this ::windows8 office 2013 : Task 'sharepoint' reported error (0x80040102) : ' Outlook cannot connect to the Share Point List (... The server may not be reachable from your location.Contact the Share Point site administrator for more information.
Other libraries (or other library sub folders) work fine with Outlook. The error is: Update 1: I verified the same issue occurs on Windows XP SP3 with IE 6 using Outlook 2007 SP2 and the same Share Point library (it was originally tested on Windows 7).The problem I'm talking about today is trying to upgrade your Windows 7 installation to SP1 by applying Microsoft's update KB976932, called "Windows 7 Service Pack 1 for x64-based Systems" and getting nothing but a failure every time.The same problem may affect 32-bit systems as well, and I'm not sure what the update number for that would be, but the solution should work for either one. Windows Resource Protection did not find any integrity violations.Configure the group policy to use the same port and server name for the updates to be distributed.
Windows Update to the same server and port as used by SCCM or b.
I'm the one person here that is not supposed to have issues like this. Microsoft is conducting an online survey to understand your opinion of the Technet Web site.