|
#1
03-14-2011, 04:37 PM
|
||||
|
||||
SBS 2011 WSUS issues - Any experts here??
Hi,
I have just recently installed SBS 2011 as I would like to make use of WSUS to update client PC's so as to reduce my bandwith usage. All sounds well and good but... The SBS server will not self-update and the clients will not update. WSUS has synchronized and has downloaded the updates which have been approved for installation to the various groups. Whenever the server or client checks to see if any updates are available none are returned although they show in WSUS console as being required for those machines. I have checked the WSUS virtual directorys and an error is produced when testing the connection. Quote:
Does anyone have any ideas? as I am now tempted to try SBS 2008. Here are some Windows Update logs from the SBS... Quote:
|
|
#2
03-14-2011, 05:11 PM
|
||||
|
||||
|
Did you configure any of this in the WSUS console as opposed to the SBS console? The reason I ask is that in SBS2008 at least, doing certain things in the WSUS console breaks the link between the two consoles and causes problems. I've no idea if the same problem exists in 2011. With SBS 2008 the rule is: if you can do it in the console then do it there because doing normal Server 2008/IIS/WSUS/Exchange things outside of the console occasionally screws it up.
Have you run the best practice analyser? Often that will find and help you solve various underlying problems. I had WSUS problems with 2008 out of the box too which were solved by installing the latest rollups for SBS2008, service packs for 2008 Server and updating IIS and WSUS to the latest recommended versions. Best place to ask is here: http://social.technet.microsoft.com/...server/threads I got useful help here troubleshooting 2008, although I did end up reinstalling in the end. It can be tricky to troubleshoot as there is a lot going on one server. Last edited by MobileTechie; 03-14-2011 at 05:13 PM.
|
|
#3
03-14-2011, 05:22 PM
|
||||
|
||||
|
Hey MT, I thought you would be first\only one to reply...
 Yes I have used the WSUS console rather than the SBS console as I didn't want it downloading updates for every single product. This does break the connection with the console but apparantly doesn't stop WSUS from working. I may reverse that and check it out. I will run the Best Practice Analyser this evening and see what the results are. I have also posted this in the WSUS section of the technet forum, but it seems very slow to respond which is why I thought I would chance it here as well. TLE
|
|
#4
03-14-2011, 07:13 PM
|
||||
|
||||
|
Out of the box you'd expect it to work but SBS is so damned sensitive at times. I think the best way to deal with it is to do everything by the book and using the console until you have confirmed everything is running as it should be. This shouldn't require any special settings like changing permissions, but may require updates/SPs/rollups. Then take a full backup and only then start configuring it. Once it starts going wrong it can be a big headache sorting it out.
I think the problem is that it's lots of different things packaged together and it's the installation and subsequent wizards that hold it all together, giving each element (OS, exchange, IIS, WSUS etc) the settings that form ithem into a complete system. Normally you'd install these things yourself and with settings you made up. So to a certain extent it's like coming into a system someone else setup even though it's just been installed. I've spent hours trying to work out exactly what a particular wizard is actually doing under the hood. If you've not done so I highly recommend getting the trainsignal course and watching the videos from start to finish. I found it incredibly helpful. Plus if you absorb all of it, you'd be able to take the relevant MCP and pass which is cool. I find SBS quite rewarding as it's like a mini corporate environment in a box. There is a enough learning to be had to keep you occupied for a long time. Last edited by MobileTechie; 03-14-2011 at 07:17 PM.
|
|
#5
03-15-2011, 01:39 PM
|
||||
|
||||
|
I managed to get to the bottom of this by reviewing the installation logs. A SharePoint update failed to install during the installation of SBS 2011. I downloaded the package but it wouldn't install successfully. The reason it failed?? I removed the installation media after the initial set up...Doh!!! I can only assume it shafted the web services which WSUS relies on so heavily.
Re-installed last night, and it is happily chugging away installing it updates from WSUS. I have been backing it up at every possible opportunity, just in case. I will be installing Forefront this evening and spending a few hours adding the various exclusions in again!!!
|
|
#6
03-15-2011, 02:36 PM
|
||||
|
||||
|
Oh good news. So in a way it was the same problem I had with not having up to date Sharepoint.
So which Forefront product are you installing?
|
|
#7
03-15-2011, 02:53 PM
|
||||
|
||||
|
Yeah, sound like the same issue. Just a shame it wouldn't install using the standalone fix. Oh well, lesson learnt.
I am using the older ForeFront Client, not the newer Endpoint version as it wouldn't install. I have looked at Avast, Trend, AVG, Kaspersky, Eset and a few other but they are all just to expensive, or they have require that you get a minimum of 5 licences. I decided to try out Forefront after speaking to the admins at my work as we use it on all of our servers here. The main thing is getting all the exceptions added which is time consuming and mundane. In addition to this, at heart, I'm a Yorkshire Man and don't like opening my wallet unless really necessary  The main thing when installing Forefront as a standalone client is that you use the 'clientsetup.exe /nomom' switch. You have to install it using cmd. What AV did you go with in the end MT? Last edited by TLE; 03-15-2011 at 04:37 PM. Reason: Can't spell!!
|
|
#8
03-15-2011, 04:07 PM
|
||||
|
||||
|
Quote:
For a recent client I installed Eset Exchange for the server as a trial and MSE for the clients. As you know there doesn't appear to be an officially complete list of exceptions for SBS so you have to add up the exceptions for Exchange, Server, IIS, Sharepoint and SQL so it take quite a while. So far Eset hasn't caused any problems. It's not caught anything either but then it wouldn't by now. It seems pretty OK value-wise.
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
