RE: Hour offset in public calendar
- From: Joe Schmeier <JoeSchmeier@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 18 Feb 2007 07:49:00 -0800
Thanks! Wow what a mini tutorial. I appreciate it.
"Phil E." wrote:
All of our SBS SP1 installations with the exception of two due to hard drive.
space constraints, are running WSUS 2.x SP1.
I like it. It gives us a chance to work through Microsoft's updates before
they are released at the client level. If we find a bug, or problem with one,
we can hold them back until the problem gets fixed.
It also provides an "at a glance" perspective on the patch level of all of
the servers and workstations on the network.
Our Workstations are set to receive their updates automatically and reboot
if necessary and our servers are set to download and notifiy so that we don't
run into problems with a nonresponsive service after a reboot.
I am starting to get comfortable with the WSUS 3.x integration into SBS R2.
It is not quite what I am used to, not as granular in the ability to control
what is happening - though I am beginning to change that opinion a bit, and
has all aspects of the update service show up in your daily server report. I
am growing used to its simplicity in management though... :D
R2 installs the appropriate WSUS 3.x Group Policies for you, where WSUS 2.x
SP 1 expects you to build your own and implement them. For the 2.x
installations I setup at least 3 distinct policies. One at the domain global
level that points all systems to the WSUS server, and then 1 each for servers
and workstations to either download and notify (for servers) and schedule and
install (for workstation).
Of course, your mileage may vary! We have a number of installations with
distinct OUs for workstation groups where an extra GP or two for WSUS update
times are needed.
And, as far as hardware requirements, if your client install is already
labouring the system, then I would give it careful thought. Keep in mind that
your WSUS download database of updates , which is stored on a local server
hard drive, can grow as large as 12GB+.
You will need to use the osql command to put the WSUS MSDE SQL db system
memory usage in its place. It tends to soak up to the max after installed.
Anymore questions? :D
Philip E.
"Joe Schmeier" wrote:
I have not tried WSUS on a SBS yet. It seems you have, any input?
Specifically, do you see any drop in performance with adding yet another task
onto the hardware?
I am looking for the DST updates now and will post later as to the success
thereof.
"Phil E." wrote:
Do you have WSUS installed? If so, there should be a bunch of DST updates
showing up there.
If not, then some of your machines may have taken their DST related updates
and others may not have.
Specifically, it sounds like updates may have been applied to the clients,
but not to Exchange as of yet?
http://support.microsoft.com for the KB related articles, and
http://www.microsoft.com/downloads for the downloads themselves.
Hope this helps,
Philip E.
MPECS Inc.
Microsoft Small Business Specialists.
"Joe Schmeier" wrote:
I have what seems to be a bizarre calendar problem.
I have set up a shared calendar in our public folders. All 5 of us in the
office post to it. If user A puts an appointment in for 9 a.m. on her
machine, the appointment displays on user B's calendar at 10 a.m. All
appointments are one hour later, including all day appointments which make
those appointments look like two day appointments.
All machines in the office are in the same time zone. What am I missing?
- References:
- RE: Hour offset in public calendar
- From: Phil E.
- RE: Hour offset in public calendar
- Prev by Date: Re: Renaming the "external" DNS for your SBS server
- Next by Date: Re: Multi site network configuration
- Previous by thread: RE: Hour offset in public calendar
- Next by thread: Re: SBS R2 Premium - Monitoring & Reports Broken.
- Index(es):
Relevant Pages
|
