Microsoft
Windows is the most widely used desktop
operating system in the world. That doesn't necessarily make it the
best. For many of us, supporting it is how we make our living. One of the
endearing and annoying features of this
ubiquitous OS is the monthly
patch update process. Most of the time it occurs seamlessly.
It just kind of works in the background when you're not
looking. However, there are times when it rears its ugly head and demands
attention.
Windows Server Update Services
In our company we run WSUS - Windows Server Update Services - to keep all our Windows
desktops updated. In case
you are not familiar with it, WSUS is Microsoft's
free patch management tool. I don't know why they named
it WSUS. I
only use it to update my workstations. I don't
trust it on the servers. I would rather manage that process myself.
I'll install the updates on a non-critical
server during the week to test them. I do the
rest of the servers on the weekend.
But for the workstations it does a pretty good job - most of the
time. It pushes them out after I approve
them and then installs them late at night, usually
with an automatic reboot when completed. I have trained my users over the
years to
ALWAYS leave their computers on to accommodate the patch
process, the weekly AV scans and so that I can get into
their workstations any time I need
to work on them in the evening. They are
pretty good about logging off.
Microsoft
likes WSUS because it cuts down on
the number of users hitting the Windows
Update site. And that's what this post is
really about. Microsoft
has been slowly moving
everyone over to Microsoft Update instead of Windows
Update. If you don't
know the difference then you don't do Windows support.
OK, here's the main difference: In addition to OS patches, Microsoft
Update takes care of your MS Applications like
Office, SQL Server and Exchange.
Repairing Microsoft Update the old
way
Occasionally, the patch
process will throw up. WSUS has a good monitoring
and reporting feature that allows me to see at a glance which machines
are struggling with the stuff Microsoft is trying
to send to it. So I do a Remote Desktop session to the machine in
question and run the process manually. I know something is really messed
up when I get a 0x8024001D error or some other stupid hex number. That's
when it used to get really annoying. Not anymore.
Visit us:
http://microsofthelpline.com/
|
http://microsofthelpline.com/home/
|
https://microsofthelpline.com/about-us/
|
http://microsofthelpline.com/services/
|
http://microsofthelpline.com/microsoft-support-phone-number/
|
http://microsofthelpline.com/microsoft-helpline-phone-number/
|
http://microsofthelpline.com/microsoft-customer-support-phone-number/
|
http://microsofthelpline.com/microsoft-technical-support-phone-number/
|
http://microsofthelpline.com/microsoft-help-desk/
|
http://contactprintersupport.com/microsoft-support-phone-number/
|
http://microsofthelpnumbers.com/index.html
|
http://microsofthelpnumbers.com/about.html
|
http://microsofthelpnumbers.com/microsoft-helpdesk-number.html
|
http://microsofthelpnumbers.com/microsoft-support-number.html
|
http://microsofthelpnumbers.com/microsoft-customer-service-number.html
|
http://microsofthelpnumbers.com/microsoft-technical-support.html
|
http://microsofthelpnumbers.com/microsoft-helpline-number.html
|
No comments:
Post a Comment