Not sure if you've seen this posting in Bill Anderson's blog, but for those of you who may use SMS and WSUS together in the same environment, we'd sure like to understand more about the different reasons that works well for you!
Any comments you can provide on bill's post (or this one ) would be much appreciated.
Thanks and have a great weekend!
I think deployment of patches through WSUS is much-much easier than with SMS, and who doesn't need the granularity of SMS than WSUS could be the best option. On the other hand we like the software distribution, reporting technology of SMS therefore we use them together.
My group builds, deploys, and maintains servers. While we used to leverage the available SMS infrastructure (primarily used for lifecycle management of client PCs) for Remote Control of NT4 servers, we never used it for software management. When SUS came along, it was certainly better than our hand-made update scripts, which ran the appropriate QFE installs silently, and made a final call to QCHAIN.exe. SUS allowed us to set policy around the approval of QFE updates for distribution. The fact that it leveraged the heavily-used AU client provided with the OS, combined with the stateless nature of the relationship between SUS server and AU client, made it a very flexible solution. However, there were some reliability issues with the initial AU clients.
With the current WSUS product and the AU clients, the products work in tandem quite well and are also well-focused. Reporting is not great, but we are planning on using MOM to generate QFE-related reports in the future, so that's not a large concern. WSUS works well for patching our 500+ servers.
The SMS 2 SUS Feature Pack requirement of manually entering silent installation switches was an unnecessary burden as standalone SUS had no such requirement; the free SUS was considerably easier to use than SMS SUS. I switched based upon the differences in time and overhead for patch deployment. When I moved to SMS 2003 I reevaluated patching, finding the same disparity between SMS 2003 and WSUS as I did between SMS 2 SUS and SUS; WSUS was easier to use for distributing patches.
reporting, and other tools = sms,
but patching = WSUS.
But quick question guys, can i have both installed on the same machine?
the most convenient and cheap replacement battery online shop in uk. We specialize in http://www.batteryfast.com laptop batteries,laptop AC adapters. All our products are brand new, with the excellent service from our customer service team.
SUS allow us to set policy arounds the approvals of QFE updates for distributions thank.
Whens SUS came alongs, it was certainly better than our hand-made update script, which ran the appropriates QFE installs silently, and made a finals call to QCHAIN.exe thanks you very much.
The fact that it leverageds the heavily-used AU clients provided with the OS, combined with the stateles nature of the relationship betweens SUS server and AU clients, made it a very flexible solutions very good.
On the others hand we like the software distributions thanks
Any comment you can provides on bill's posts (or this one ) would be muchs appreciateds thank you very nice
http://www.batteryfast.co.uk/compaq/229783-001.php Battery fits COMPAQ EVO N600 N600C N610C N610 N620C laptop battery,
http://www.batteryfast.co.uk/compaq/146252-b25.php Battery Fits Compaq Armada E500 E500S V500 V300 laptop battery,
http://www.battery-export.com/dell/dell-inspiron-6400.html Dell Inspiron 6400
http://www.battery-export.com/dell/dell-inspiron-640m.html Dell Inspiron 640m
http://mircse.com http://mircindir.cc mirc indir mirc yükle mirc downloand
Thank's and happy new year