Windows Update Server

Hi,

I have installed and set-up a WSUS server. All seems ok but it does not detect any computers? From looking around i believe that the client computers contact the WSUS. I have configured group policy to download updates etc and set the intranet location to get the updates from.

From another post i have used the URL to contact the WSUS server and the vlient computer is asked to save or run a file, so I beleive it knows about the update server?

Not sure were else to look.

All help appreciated.
FattyPoAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jordie77Commented:
Could you execute the command gpupdate /force on computers which should be visble with wsus?
0
Mike ThomasConsultantCommented:
Are they being registered in unasigned compuers? if not check your group policy settings for the update server location and make sure the server name and syntax are correct.

Alosocheck how long how often the clients will check for updates.




0
Jordie77Commented:
It might take up to 3 workstation reboots for the policy to get applied,
even with gpupdate. You can check to make sure the policy is applied by
going to a workstation Control Panel -> Automatic Updates. You should be
able to see the settings, but you should not have the ability to change
anything if the GPO applied correctly.

Once the policy is applied on the workstation and you do wuauclt /detectnow,
it can still take like 10 minutes for the computers to appear.

If you're still not seeing them after a few reboots, another /detectnow, and
10 minutes, please go back to your GPO and make sure the update service
location is pointing to http://servername:8530
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

abt-itCommented:
Have a look at the client log file: \windows\WindowsUpdate.log

There you can see what wsus server is used and a lot of other things what happens.
0
FattyPoAuthor Commented:
Thanks for the info, the WSUS was installed about 3 weeks ago so the computers have been rebooted at least 10 times each. In Control panel the automatic updates are set to the settings in the GPO and are greyed out.

The servername however is \\servername which works on other servers i look after. I will try http://servername:8530.

The only other info is that historically there was a SUS sever but all the PC's are ponting to the new GPO settings.
0
FattyPoAuthor Commented:
Additionally the server itself is set to update every friday at 16:00, but i am not sure where is is picking the iinformation up from?
0
FattyPoAuthor Commented:
and the other server is set to 21:00, will these be local security settings?
0
Mike ThomasConsultantCommented:
"Additionally the server itself is set to update every friday at 16:00, but i am not sure where is is picking the iinformation up from?"

The WSUS Server will sync with Microsft and I would set this for everynight 2am or so, also the correct syntax is http://servername:8530. or just http://servername as stated above so I would change this.


0
abt-itCommented:
by default the wsus server gets Updates from the microsoft server. You can modify these settings get updates from another wsus server in your company. There is a synchronisation log to see if synchronisation works correct.

To see what the clients do, look at the client log i posted above.
0
FattyPoAuthor Commented:
i have looked at another PC and it is greyed out and receives update at 16:00 so i gues the first issue is to see why the client is not picking the info up from GPO?

The error in the log on the client is:

the logs show the client trying to update from the old server name, however i cannot find out were it is picking the info up from. i have looked in the GPO on the DC and nothing is enabled? Also on the new server with GPO were i have put the settings in. Should i update the DC with the correct settings?
0
Jordie77Commented:
You should have or make a seperate GPO for you workstations and / or servers and set this policy there. Maybe there is already another policy in which the old wsus computername is present.
0
FattyPoAuthor Commented:
i just used gpedit.msc and configured the settings in there? how do i get to a different GPO?
0
Jordie77Commented:
Ofcourse I dont'mean just for this policy a separate GPO, but also other settings for a specific group of computers / servers.
0
FattyPoAuthor Commented:
excuse my ignorance, i don't understand? can i access different GPO's assign to different computers?
0
Jordie77Commented:
The easiest way is to use the tool "group Policy Management" on your server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jordie77Commented:
I assume you have a Domain Controller with workstations which are Domain members?
0
Jordie77Commented:
With gpedit.msc you edit the local policy on the workstation, but this is not the easiest way to control your policys.
0
FattyPoAuthor Commented:
yes i do, i cannot see group policy management in administrative tools. So i assume this needs to be installed? Or i can go the AD users and computers and right click properties and select group policy, then in there i can see default domian policy? is this the correct place to look?
0
abt-itCommented:
to see which Policy is used run the command rsop.msc on the client (Result Set of Policies). On the result page you should find the Policy Name where the wsus settings from.

0
FattyPoAuthor Commented:
thanks just installing gpmc and will check settings.
0
FattyPoAuthor Commented:
thanks with using the rsop.msc command i have found the Policy name which the clients are associated to, and then by using the Group Policy Management console i have found and change the correct settings.

Many thanks to you all.
0
FattyPoAuthor Commented:
Many thanks for all the help. It has given me a better understanding of GPO's and their roles in an AD environment.

PC's now reporting to the WSUS server.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.