Things are starting to get a little quieter here as we finish out the final tasks for this release. One of those tasks is to help developers build on the product, and make something even better than what we're already providing.
To that end, several of us are starting to work on short snippets of code that demonstrate interesting uses of our API. If you're new to PowerShell or the WSUS API (or both), you'll be able to take the samples, make a quick start, and actually accomplish some useful tasks.
Some of the samples will help you build your own solutions to some of the common feature requests we didn't get to in this release.
Some things we're playing with:
I have a general question about the new release. If I were to approve all updates, regardless of whether the update pertains to my environment, does WSUS 3.0 download the update immediately or does it wait until one of my machines actually needs it?
Really looking forward to the new release!
I have to say that with WSUS 3 I find the approval process and the synchronization to be confusing or at least less informative than in 2.0
Just in trying to match my production WSUS2 in terms of what updates are approved and what ones are not, the views in 3 are very limiting.
I look very forward to the API and samples as without those my implementation of WSUS 2.0 would have never happened.
Jeff: They'll download as soon as they're approved. You can wait until you see machines need the update, before actually approving it. You can easily filter an update view to Approval: Unapproved + Status: Needed.
John: Have you posted examples at the newsgroup? That'd be a better place to discuss the issues you're having.
One thing I would like to see in the new 3.0 is the WOL wake on lan and under the computers pages i would like to see an option to add a column for computer make and computer model. This would allow me to search by computer model
Really like the 3.0 (used the RC for the last couple of months)
Would like better reporting options (like saving your own custom reports and emailing them as a scheduled task)
We used Patchlink in the past and I think WSUS 3 is much better.
One thing I would like to see better reporting options(ie) we should be able to print, email the server overview, the updates overview, the computers over view. Management doesn't have time to log into the servers and if we can give them a shapshot of the over all system they will see the value of the WSUS server and help with the IMO's
I'd love to know how to import a Microsoft released MSI/MSP/EXE into WSUS and then deploy the imported package to clients.
I've seen indications of what coding terms to use, but not being a programmer it's a little above my head!
BONJOUR ? SVP Comment faire partie de votre blog ? Avez-vous bonne documentation ? Je ne connais rien en informatique ? Email= email@example.com !!
je vous remercie beaucoup ! Salutations de PHMUZART
If you want do delete your site from our spam bases - just email us with domain of your site:
I have found few blogs having good content. And I think you are doing a very good work buddy. Keep up your work. This post was really a nice piece of your work. http://www.penizenlargement.com