Implementing WSUS on SBS 2003
Hi.
despite my best efforts at with the Microsoft instructions, I have been unsuccessful at implementing WSUS on a SBS 2003 server - specifically having the server recognise the workstations. Can somebody please help me.
Cheers,
Greg
despite my best efforts at with the Microsoft instructions, I have been unsuccessful at implementing WSUS on a SBS 2003 server - specifically having the server recognise the workstations. Can somebody please help me.
Cheers,
Greg
Irwin W.
Take a look at this post of mine. It will help you https://www.experts-exchange.com/questions/24089458/How-to-use-WSUS-to-push-windows-updates-on-domain-computers.html
Hi hainsNET,
> specifically having the server recognise the workstations. Can somebody please help me.
I just wanted to let you know that the WSUS Server will not reach out to the client workstations like SMS would, the workstations need to be directed to contact the internal WSUS Server (and have an up to date WAUC installed) that you setup. To do this typically you would do it in a corporate environment by way of GPO (Group Policy on a Domain). If you do not have a Domain environment, you can setup the local policy to point to the WSUS Server you setup, instead of the default WSUS provided by Microsoft (for all).
If you need step by step instructions how to do this, let me know:-)
> specifically having the server recognise the workstations. Can somebody please help me.
I just wanted to let you know that the WSUS Server will not reach out to the client workstations like SMS would, the workstations need to be directed to contact the internal WSUS Server (and have an up to date WAUC installed) that you setup. To do this typically you would do it in a corporate environment by way of GPO (Group Policy on a Domain). If you do not have a Domain environment, you can setup the local policy to point to the WSUS Server you setup, instead of the default WSUS provided by Microsoft (for all).
If you need step by step instructions how to do this, let me know:-)
ASKER
Hi, and thanks for these responses everybody.
The single 2008 SBS server I have installed did the whole lot automatically for me, its the 2003 SBS server install thats giving me grief. Shamefully I'm not so familiar with Group Policies on a domain, but am very comfortable with the registries and scripting, so if there is something I can do via a command line or a login script to give the client workstations a nudge I'd be very grateful. It would be a right royal pain if I had to go to every workstation too - so central is good!
Thanks,
Greg
The single 2008 SBS server I have installed did the whole lot automatically for me, its the 2003 SBS server install thats giving me grief. Shamefully I'm not so familiar with Group Policies on a domain, but am very comfortable with the registries and scripting, so if there is something I can do via a command line or a login script to give the client workstations a nudge I'd be very grateful. It would be a right royal pain if I had to go to every workstation too - so central is good!
Thanks,
Greg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nappy_d, very nice walk through :-)
ASKER
Hi Nappy_D
Thanks for this detailed process. Just a question - at what point or how do they get added to the group I have created? At login? When A/D "feels" like it?
Greg
Thanks for this detailed process. Just a question - at what point or how do they get added to the group I have created? At login? When A/D "feels" like it?
Greg
The machines unlike users get their policies at startup, which is the y point at which the computer is logging on to the network.
That being said, sometimes, if you find that computers are not applying the policies you put in place, you could enable the policy "Always wait for network".
This policy is located under computer configuration\Administrati
That being said, sometimes, if you find that computers are not applying the policies you put in place, you could enable the policy "Always wait for network".
This policy is located under computer configuration\Administrati
ASKER
Hmmm. Still not grabbing, but you have given me a great helping hand, so I will close the job with thanks. I will continue to pursue this area as I don't want to take up more of your time - unless you want to see it through. :)
I wanna see it thru!! let's go!
OK, follow my instructions and we are gonna get this up and running..
- Is WSUS up and running on your server? yes/no?
ASKER
Hi Nappy_D,
Thank you for your persistence. Being in IT and support myself I know how frustrating it can be to get only half a solution delivered (although you have given a lot already) so am happy to pick your brain till the end of this task.
OK. WSUS is up and running. It has downloaded updates, schedules have been set, and all looks OK, except there are no workstations in the list to administer. I made those changes above - including the optional "forced" option, but still they evade me. I must admit I'm not terribly proficient with policies (local or domain) but can do practically anything with scripting (Win or CLI).
What can I do now to populate this list?
Cheers,
Greg
Thank you for your persistence. Being in IT and support myself I know how frustrating it can be to get only half a solution delivered (although you have given a lot already) so am happy to pick your brain till the end of this task.
OK. WSUS is up and running. It has downloaded updates, schedules have been set, and all looks OK, except there are no workstations in the list to administer. I made those changes above - including the optional "forced" option, but still they evade me. I must admit I'm not terribly proficient with policies (local or domain) but can do practically anything with scripting (Win or CLI).
What can I do now to populate this list?
Cheers,
Greg
You now need to apply the group policy for WSUS to the OU in which the computers reside. Have you done this?
ASKER
If it was listed above in the 4th image, then yes, otherwise no. Im sorry - Im not good at this. lol
OK, the image above shows configuring the GPO. The GPO must be located in the OU where the computers reside, like below
Picture-61.png
Picture-61.png
ASKER
Hi.
I found this at GPMC.MSC and put the name of the client as per the last image in your (4) screen dumps above, and ensured they were enforced, link enabled etc. This was by Adding and Linking a GPO in this section. There was only one group to add as the organisation only has about 20 PCs so no need for more groups. From this description, does it look like I've done the correct procedure?
(This is one area I'm not familar with. :( )
If so, this list will now populate as users login in or as A/D updates?
Greg
I found this at GPMC.MSC and put the name of the client as per the last image in your (4) screen dumps above, and ensured they were enforced, link enabled etc. This was by Adding and Linking a GPO in this section. There was only one group to add as the organisation only has about 20 PCs so no need for more groups. From this description, does it look like I've done the correct procedure?
(This is one area I'm not familar with. :( )
If so, this list will now populate as users login in or as A/D updates?
Greg
Yes that is correct. How is the list going? Is all OK now?
ASKER
Hi Nappy_D.
No, still nothing in the list. I'm afraid I'm a pain in the bu77 here. I just cant seem to get it right.
Would you be up to taking remote control of the server and looking at it for me? I would be happy to pay you for your extra time/services.
Greg
No, still nothing in the list. I'm afraid I'm a pain in the bu77 here. I just cant seem to get it right.
Would you be up to taking remote control of the server and looking at it for me? I would be happy to pay you for your extra time/services.
Greg