Short and simple: if you are running Exchange 2010 or Sharepoint 201, DO NOT install Windows Management Framework 3.0 (WMF 3.0).
For a slightly more descriptive explanation, check out my good friend Michael Smith’s blog post.
Archive for WSUS – Page 2
After installing a SharePoint update to your SBS 2011 server, you may see one (or both) of the following warnings the next time you run the SBS Best Practices Analyzer (BPA) utility:
Use psconfig.exe to upgrade one or more SharePoint databases (Source: 348)
Use psconfig.exe to upgrade SharePoint (Source: 349)
To resolve these warnings, it will be necessary for you to manually run the psconfig command, as it is not run automatically after an update has been applied.
- Open an Administrative command prompt
- Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
- Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Please note: it may take some time for the psconfig command to complete. And, in some cases, if you get any errors, it is recommended to run the above psconfig command again.
After this, please check that your SharePoint sites are working properly, and rerun BPA to confirm that the warning messages have been cleared.
For more information on this, please check out the following two posts from the Official blog for Windows Server Essentials and Small Business Server support:
There have been several reports about recent updates taking an extremely long time (4-6 hours) to completely install on SBS 2008 servers. For example, some report that after rebooting the server and it starts to apply updates, it may sit at 0% for more than an hour.
The reaction is to think that something is wrong and to force a reboot.
These issues are being investigated, but the best advice is that if you have already started updating your server, just let it run and do not force a reboot. And expect that it may be down for several hours.
If you have not yet started applying updates, my typical procedure is as follows:
Reboot the server BEFORE installing any updates
Install updates in groups – all security patches first, then .Net patches, then each rollup or service pack individually
After the updates have been applied, some things may still not work, such as some services not starting or Companyweb not available. In these cases, first try rebooting the server again, and checking things out. for companyweb, please remember that you generally need to manually run the psconfig command after installing SharePoint updates.
finally, it is always advisable to make sure you have a full, validated backup of your server before installing any patches, rollups or service packs,
Are you running or supporting a Small Business Server (SBS) 2008 network?
Are you planning to introduce Windows 8 clients to your SBS 2008 network?
If you answer YES to both questions, then you will want to take a look at installing SBS 2008 Update Rollup 6 (KB 2729101) to your server.
Specifically it addresses/fixes 3 issues:
- Allows Windows 8 workstation to be joined to an SBS 2008 domain using the client deployment tools
- Windows Store apps now work on a Windows 8 workstation after joining it to the SBS domain
- Allows connecting to a Windows 8 client workstation from the Remote Web Access web page
As always, it is strongly recommended that you have a good backup of your server before applying updates.
Step 1 – Approve update either through WSUS or MU
WSUS:
Microsoft Update:
Step 2 – Install update – this takes less than a minute to install
Step 3 – Restart your server
At an SBS 2011 site, workstations were recently updated with the latest Windows Update Agent (version 7.6.7600.256). When I attempted to run Windows Update from the workstations, it generated the following error message: Code 800B0001 windows Update encountered an unknown error
This error occurred on Windows 7 SP1 workstations both 32-bit and 64-bit versions. I tried following the posted suggestion to run the System Update Readiness tool as well as suggested “Fixit” solution, but that did not resolve the situation.
Note that the error with windows Update would only occur when trying to connect to the SBS/WSUS server. WU would work if I selected the “check online for updates from Microsoft”.
It turns out that the SBS/WSUS server needs to be updated as well. The solution is to download and install KB 2720211 on the SBS server.
No reboot is required, and no services need to be restarted. After installing the patch, workstations successfully connected to the SBS/WSUS server.
If you read the Summary Notes associated with the WSUS Update KB 2720211, you will see that it recommends using the WSUS Cleanup Wizard and to re-index the WSUS DB.
Running the WSUS Cleanup wizard is something that I do with all my SBS servers — either manually, or via a scheduled task (see Eriq Neale’s blog post on this subject).
However, I was unaware of any need to re-index the WSUS database.
I asked some of my fellow SBS MVPs to see if this is something they do, and several responded that they, too, were not aware of any need to re-index the WSUS database, and had never run it.
The steps to re-index the WSUS DB can be found in this Technet article.
YMMV!
Exchange 2010 Service Pack 2 was released on December 4, 2011. But I’ve waited over a month before deciding to install this on my production server.
First, two questions you may have:
Q: Why don’t I see the Exchange SP2 in WSUS or Windows Update?
A: The explanation is simple: there is no ability to uninstall Exchange Service Packs, so Microsoft does not automatically push them out.
Q: If it doesn’t show up in WSUS or WU, how would I know that there is an Exchange Service Pack to download?
A: The SBS 2011 Best Practices Analyzer will inform you if there is a Service Pack to be installed (see screenshot of warning message)
And since we have to manually download and install Exchange Service Packs, this also gives us a chance to make sure that our server has been backed up before proceeding. So, let’s get started:
Step1: Reboot, Backup and Download
- I would strongly advise that you restart your server before proceeding
- Then make sure you have a current backup of your server on hand (just in case)
- Download SP2 by clicking on the link in the Resolution portion of the BPA warning message, or click this link to go to the Exchange 2010 SP2 Download page
- Click on the Download button and then select to Save the SP2 file (be sure to click on SAVE, and not RUN
I normally create a specific folder for service packs. In this case, I created E2010SP2.
- When finished with the download, click on Open Folder
Step 2: Unblock – Extract – Stop Services
This is a very important, and perhaps unexpected step: after downloading the SP2 executable, you must UNBLOCK it before you can extract it, and then we must stop a service before we begin installing SP2.
- Right click on the Exchange2010-SP2-x64.exe file, then click Properties. From the bottom of the Properties window click Unblock –> Apply –> OK
- Double click the .exe file to extract it, then click OK to extract it to the directory you created
- Click OK when you see the Extraction Complete message
- Click Start –> type: services.msc, and then locate and stop the Windows SBS Manager service.
Step 3: Run the Update
Finally, we are ready to install Exchange 2010 SP2!
- Double click on setup.exe
- Click on ‘Install Microsoft Exchange Server upgrade’
- Click Next on the Introduction window:
- Click to “I accept the terms in the license agreement”, then click Next
- It now performs a Readiness check to verify that Exchange is ready to be upgraded. If everything passes, you are ready to click Next. Otherwise you will need to resolve any identified issues, and then restart setup.exe.
- Click finish when the upgrade is completed
- Be sure to restart the Windows SBS Manager that we stopped in Step 2. Although not required, I would also suggest rebooting your server
Rerun the BPA to confirm that the Exchange SP2 warning no longer displays.