Solved

WSUS Installation & Configuration Questions

Posted on 2006-06-21
14
306 Views
Last Modified: 2010-08-05
Hi all,

I just installed WSUS on my box. All seemed to go well with the install and I got no unexpected results. Its up and running on port 8530 on the server.

I followed the instructions that Jeff - TechSoEasy provided me with in an earlier thread and this page does say that the documentation is being updated (whatever that may mean) http://sbsurl.com/wsus (I followed to the letter, with the exception that I created a partition exclusively for the WSUS data files 30GB drive F:\ )

I have created 2 groups - Server & Clients. Naturally the SBS box is in the server group and so far I have added a single PC to the Client group and both have had their status reported:-)

I also ran the original synchronization as specified in the documentation (succesfull) and set a scheduled synch overnight which also ran succesfully.

Now to the questions

On the Homepage of the WSUS in the To Do List I have an error, "One or more service components could not be found. Check your server status and ensure that the  Windows Server Update Service is running. Non Running Service: SelfUpdate

Is that "Windows Server Update Service" called WSUS in the Services? if so I don't see it at all. I could have sworn it was there but I might be deluding myself?

I have spent a couple of hours trawling through technet and Googling and the most logical expanation I can find is a problem with Sharepoint which is described here http://technet2.microsoft.com/WindowsServer/en/Library/b23562a8-1a97-45c0-833e-084cd463d0371033.mspx?mfr=true

I don't want to just start changing stuff without being certain that I am doing the correct thing so any advice would be welcomed.

Learning more every day:-)

Thanks

Steve  



0
Comment
Question by:stevendawson
  • 7
  • 7
14 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16950054
First to clarify what "documentation is being updated" refers to... My link, http://sbsurl.com/wsus, goes to the Official SBS Product Documentation Team's blog... it's not the actual documentation.  I provide this because the documenation writers post here and the information is more up-to-date.  The item they mention has already been integrated into the document on page 20.  I think I'll probably change that link to just go to the document now.

Okay... that being said... the error message is somewhat misleading.  The first sentence is more important than the second... it's saying that it can't find the service which means either permissions or port assignment OR your XP machine does not have either Service Pack 1 or Service Pack 2 installed.

If the XP Machine does not have any service packs installed, please install SP2 manually.

Otherwise, please open the Server Management Console > Advanced Management > Internet Information Services > Web Sites > Default Web Site.  Right click on SelfUpdate > Properties > Directory Security Tab.  Click the Edit... button under IP address and domain name restrictions, and make sure that "Granted Access" is selected.

If none of that is the problem, please post back.

Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 16950253
Hi Jeff

The XP machine is a clean install. It is already running SP2 and if I read and understood all the documentation correctly, that is exactly why it is able to automatically find the WSUS server?

SelfUpdate does indeed have "Granted Access" set and in fact in the documentation it states to check settings are the same on default web which they are.

 
Steve
0
 
LVL 2

Author Comment

by:stevendawson
ID: 16982647
Solution Found

I also have CRM3.0 installed on this SBS box and it seems that caused the problem because it required the use of my internal IP address. This article explains another issue that led to the solution to this problem. http://www.experts-exchange.com/Operating_Systems/SBS_Small_Business_Server/Q_21895832.html#16964102

Regards

Steve

 
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16999208
Well, in reading the other question I'm rather confused... you shouldn't have more than one Internal IP Address... So the recommendation in that question is going to cause you problems in the future.  There were actually two choices provided to you... one was to add an IP address, and the other was to use host headers.  

Using Host Headers was really the right way to go and what should have been done.

Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 16999416
Hi Jeff,

Oh, I got it wrong then!

What happened was as I used the suggestion 1 from that other post and it worked OK I figured that he was reccomending that order, i.e thats first choice.

the other suggestion

2. add the fully qualified domain name of your server ( if not in use by any other web site) to the HTTP host header feild and assign it your internal IP address.

Can you give me further clarification on how to add host headers and what I should use in them? I'd soonercorrect it now so I can be sure it will be best configured for the future.

Thanks

Steve
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16999512
Well, taking a step back... did you follow all steps in http://sbsurl.com/crm for your install?  Did you follow-up with any issues that may be in http://sbsurl.com/crmtrouble ?

Because you can't use a host header on the SQL Reporting site... but you don't need to.  

CRM should be accessed via https://SBSServerName:5555

Then, did you follow all the steps in the document linked from http://sbsurl.com/wsus?  Specifically did you create a NEW web site for WSUS that is configured to use port 8530?

This would make it so that you would get to the Admin page at http://SBSServerName:8530/WSUSAdmin

And you would configure your client computers to access WSUS at http://SBSServerName:8530

There generally isn't a need for host headers in these configurations.

Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 16999550
Hi Jeff,

Yes to all of your questions. I followed them all to the letter and everything is available using the URLs and ports as you describe above.

Just to clarify a couple of things.

THIS ORIGINAL QUESTION

"On the Homepage of the WSUS in the To Do List I have an error, "One or more service components could not be found."

I no longer have this error.

The Other Question  - About problems with /connectcomputer http://www.experts-exchange.com/Operating_Systems/SBS_Small_Business_Server/Q_21895832.html#16964102

When I fixed that by adding the additional IP then the WSUS proplem went away. Maybe that was totally unrelated? Certainly the WSUS install appears to be working fine and is updating every day as per its schedule.

Perhaps I should remove that extra IP and try and connect another computer with /connectcomputer?

Thanks as always,

Steve
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 500 total points
ID: 17000091
That may have resolved the problem of WSUS, and /connectcomputer... but as usuall with SBS if you resolve a problem and don't do it the SBS-way, you'll most likely fix one or two things while breaking others.  WSUS is designed to work on SBS with a separate port assignment rather than a separate IP address.  

So, it doesn't make sense to me that you could access WSUS at http://SBSServerName:8530 while http://SBSServerName/Exchange or http://SBSServerName/Remote would still work.  Or even more importantly, do those work from your External IP address?

All that being said... I think you got the 400 error due to something you changed on the default website... you'll note that this KB: http://support.microsoft.com/kb/842693, while not directly towards connectcomputer explains what can happen.  (connectcomputer WOULD be affected as well under this scenario).


Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 17001181
Hi Jeff

OK, first thing is that I have removed the additional IP from the card. (if its wrong then its wrong so I took it out)

All of these are accessible from the internal network

WSUS at http://SBSServerName:8530 while http://SBSServerName/Exchange or http://SBSServerName/Remote would still work

and these work from the external IP address.

 http://SBSServerName/Exchange or http://SBSServerName/Remote

but WSUS at http://SBSServerName:8530 does not work external IP (That did not surprise me before as I knew the port was closed on the router) anyway, I opened up 8530 and it is still not accessible from the external IP. I assume it should be and I have something else wrong then?

Steve



0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17006131
WSUS should NOT work externally!  Why would you want it to??

Does https://SBSServerName:5555 work for your CRM?

Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 17007251
Hi Jeff,

I agree, I wouldnt want it to work externally but you included it in your comment...

----------
So, it doesn't make sense to me that you could access WSUS at http://SBSServerName:8530 while http://SBSServerName/Exchange or http://SBSServerName/Remote would still work.  Or even more importantly, do those work from your External IP address?
----------

So I thought maybe it "Should Work Externally"

I'll close that port back down then. So now I need to try adding another PC to the network using /connectcomputer and see if I still have the original problem.  If I do I'll open another ticket.

Either way this WSUS problem has gone.

Thanks again Jeff.

Steve
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17007465
I was referring to the /Exchange and /Remote URL's not the first one... sorry about that confusion.

Jeff
TechSoEasy
0
 
LVL 2

Author Comment

by:stevendawson
ID: 17097467
Hi Jeff,

I'm not 100% certain of how this problem was resolved but I have accepted the answer that most helped in the understanding of the question.

As usual, thanks for your help.

I have another question open which you may be able to help with. If you have the opportunity I'd appreciated your opinion.

Best Regards

Steve

http://www.experts-exchange.com/Operating_Systems/SBS_Small_Business_Server/Q_21899461.html
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17098335
It was resolved by removing the extra IP address from your NIC configuration.

Jeff
TechSoEasy
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

A lot of problems and solutions are available on the net for the error message "Source server does not meet minimum requirements for migration" while performing a migration from Small Business Server 2003 to SBS 2008. This error pops up just before …
In the event you manage a Small Business Server 2003, and you are audited for PCI compliance, there are several changes you must make in order to pass the audit. I can take no credit for discovering any of these fixes or workarounds, but there is no…
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now