Windows PowerShellTM Best Practices und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
  • Alle Preisangaben inkl. MwSt.
Nur noch 11 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Gebraucht: Sehr gut | Details
Verkauft von Warehouse Deals
Zustand: Gebraucht: Sehr gut
Kommentar: Gebrauchsspuren. Kleiner Fleck oder geringe Abnutzung auf der Vorderseite. Kleine Falte oder kleiner Knick auf der Vorderseite. Kleiner Fleck oder geringe Abnutzung auf der Rückseite. Kleiner Fleck oder geringe Abnutzung auf den Seiten. Kleine Falte oder kleiner Knick auf den Seiten. Amazon-Kundenservice und Rücknahmegarantie (bis zu 30 Tagen) bei jedem Kauf.
Ihren Artikel jetzt
eintauschen und
EUR 6,45 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Alle 2 Bilder anzeigen

Windows PowerShell 4.0 Best Practices (Englisch) Taschenbuch – 10. Januar 2014

Alle 2 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
"Bitte wiederholen"
EUR 38,95
EUR 35,70 EUR 21,50
56 neu ab EUR 35,70 6 gebraucht ab EUR 21,50

Wird oft zusammen gekauft

Windows PowerShell 4.0 Best Practices + Windows PowerShell 4.0: Das Praxisbuch + Windows PowerShell 3.0 - kurz & gut
Preis für alle drei: EUR 101,84

Die ausgewählten Artikel zusammen kaufen
Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.



Über den Autor und weitere Mitwirkende

Ed Wilson, MCSE, CISSP, is a well-known scripting expert and author of "Hey Scripting Guy!", one of the most popular blogs on Microsoft TechNet. Ed has written six books on Microsoft Windows scripting for Microsoft Press, including three Windows PowerShell titles: Windows PowerShell 2.0 Best Practices, Windows PowerShell Scripting Guide, and Microsoft Windows PowerShell Step by Step. He has delivered a popular Windows PowerShell workshop to Microsoft Premier customers worldwide, and has spoken at the Microsoft TechEd and TechReady conferences. Before coming to work for Microsoft, Ed was a senior consultant for a Microsoft Gold Certified Partner where he specialized in Active Directory design and Exchange Server implementation.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


Es gibt noch keine Kundenrezensionen auf
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne

Die hilfreichsten Kundenrezensionen auf (beta) 4 Rezensionen
6 von 6 Kunden fanden die folgende Rezension hilfreich
A great book with a few minor gotchas 30. Juni 2014
Von Amazon Customer - Veröffentlicht auf
Format: Taschenbuch Verifizierter Kauf
I really want to give this a 5-star review, as I believe that every single person administering any Microsoft server technology, and maybe anyone administering desktop operating systems, should own this book. It is one of the most thorough works on PowerShell that you'll find anywhere. It is, unfortunately, not perfect.

There is a strong list of positives that make this purchase more than worthwhile. First, you're getting a major work from Ed Wilson, who is undeniably among the best-of-breed of the PowerShell community. If you need a sample of his easy-to-follow writing style, you'll find hundreds on TechNet's "Hey, Scripting Guy!" blog. There is no doubt that this book imparts authoritative knowledge.

Second, this material is truly comprehensive. I doubt there are any stones in the PowerShell quarry that are left unturned by this tome.

Third, the insights provided by the "Notes from the Field" sidebars are truly invaluable. They are real-world solutions to real-world problems provided by real-world experts. There is a single exception to this, and that is the blatant advertisement from a SAPIEN VP. It's a pure product pitch that adds nothing to comprehension or the spirit of the material. That's not why I dinged this book a star, though. As unwelcome as it was to find a pop-up ad disguised as useful supplementary information partway through the book I paid for, the rest of it is too worthwhile for this to be anything more than a speed-bump irritant. I do hope that it's either the last of its kind from MS Press or that purchase prices can be subsidized by these product placements.

Now, for the reasons I docked a star. None of these on their own are that big of a deal, but cumulatively I think they hurt the book's appeal and reach.

First, the title and the material aren't well-aligned. I bought this book because of the author's name, not the title. Had a lesser-known author produced a book with this title, I either would have skipped it or waited for a super-sale price. "Best Practices" evokes images of lists and checkboxes and cheat sheets and processes outside of development and things of that nature. Best practices are certainly a prominent feature of this book, but they are hardly a cornerstone topic. In a few places, it felt like the author wrote out some in-depth, brilliant, and truly helpful material, and then sort of tacked on something about "best practices" because it was something he was supposed to do.

Second, the organization leaves something to be desired. I read this book straight through, but along the way I was careful to use small sticky notes to mark anything that I thought I might ever want to revisit. I highly recommend that you do this as well. If you don't, then you are unlikely to ever again stumble across that little nugget that you are certain is in there somewhere. As an example, if you remember that there's a spot on using WMI to read the registry, and go to section 1 where there is all sorts of talk about using WMI, you'll be out of luck. You have to go to the "Identifying scripting opportunities" chapter instead. I would say that this is a pervasive condition throughout the book. Additionally, the "Notes from the Field" sidebars are completely unindexed, and often don't have enough in common with the material around them to be easily locatable. And of course, like most technical books of this nature, the index isn't all that great anyway. I do acknowledge that organization is a problem that's common to just about any technical book of size because so many things can fall under so many categories, but I feel that the problem was unnecessarily aggravated in this book by trying to shoehorn the content into the "best practices" motif.

Third, some of Ed Wilson's personally-designed scripts are referenced by scripts in this book without preamble. One of these, New-Underline, is given in Chapter 14 under an unrelated topic, but called by scripts in earlier chapters. Since the normative practice for custom PowerShell scripts is to follow a standard naming convention, it's not going to be obvious to some readers that the scripts they are dutifully copying are failing because they haven't yet seen a necessary supporting script. This is probably a very minor issue for most readers, but it seemed to be worth a mention as I'd think that as a "best practice", it would be good to note places in a script where other non-built-in scripts are necessary.

Finally, there were a few places where I felt that the motifs of "best practices" weren't well-served by the material. As an example, comment-based help makes a late appearance, following a great many scripts that just use blocks of comments. I also found that this book's advice on using "filter {}" (as opposed to "function {}") seemed to be in direct opposition to the advice given in the book "PowerShell In Depth: An Administrator's Guide" without any way for non-experts to reconcile these differences. There were a few other points that I'm fairly certain have been superseded by newer practices, but I unfortunately did not bookmark them and don't now recall what they were. My real point here is that this book should be read for PowerShell knowledge much more so than for PowerShell best practices.

Overall, I think these negative points are dramatically outweighed by the positives of this book. It is well-worth the sticker price and is likely to quickly become a well-worn member of your library.
5 von 5 Kunden fanden die folgende Rezension hilfreich
Great book to improve your PowerShell skills. 13. Juni 2014
Von Bjorn Houben - Veröffentlicht auf
Format: Taschenbuch
The book was released late January 2014 and is the most recent book about PowerShell that has been released to my knowledge. This means it includes PowerShell 4.0, Desired State Configuration DSC and references to Windows 8.1 and Windows Server 2012 R2.

In my opinion the book was very well written and contains a good mix of theory, sample scripts and "notes from the field" from many PowerShell specialists. The sample scripts are available for download at Technet Script Center.

The best practices that are described in the book are very recognizable and I had already adopted many of them based on the many great blog posts by the community. In the book they are all bundled and well explained including examples. Where the book really shines though in my opinion is that it describes how PowerShell is used in real-life, how it relates to many other processes within a company and what you need to consider.

I think this book is a must-have for anyone working with PowerShell. For those starting with PowerShell, I recommend first reading the books "Learn Windows PowerShell In A Month Of Lunches" and "Learn PowerShell Toolmaking In A Month Of Lunches" and then read this book.
2 von 5 Kunden fanden die folgende Rezension hilfreich
Great reference - use it frequently 21. April 2014
Von H. M. Lane - Veröffentlicht auf
Format: Kindle Edition Verifizierter Kauf
This is a must! I use it frequently at work. It has some very useful examples that I have adapted and also use frequently.
1 von 36 Kunden fanden die folgende Rezension hilfreich
My take on it...fascinating reading 27. Januar 2014
Von NSlone - Veröffentlicht auf
Format: Taschenbuch
Do you remember the good old days when you could work in DOS? The command line that was used before Microsoft gave a GUI in Windows, which stands for Graphical User Interface. Now, technically, PowerShell doesn’t really seem to have much in common with DOS. Yet it too uses the command line, although it’s now called cmd. It seems to me as if the cmdlets, or scripts are pretty much like bat files from the good old DOS days.
According to webopedia, a script is another term for a macro or batch file. I don’t know about you, but most people who are used to the command line is well versed in the use of batch files. Here is their definition in its entirety:
“Another term for macro or batch file, a script is a list of commands that can be executed without user interaction. A script language is a simple programming language with which you can write scripts.” (Reproduced with permission.
Copyright 1999-2014 QuinStreet, Inc. All rights reserved.)
Yeah, I know, but I liked DOS. You could do so much with DOS and tinker with the system to your heart’s desire. Of course, with PowerShell, you still can, or even without it, although it does give you more leeway in what you wish to accomplish. I suppose working with PowerShell and the command line is as close to DOS as one can get without actually running an earlier version of Windows or just going back to DOS, say 6.2x.
DOS has it purposes, and so does Windows GUI. For one thing it makes it so much easier to get work done. It is easier to click a mouse button than to type in what you want to happen. That rather makes it sound like a turnaround doesn’t it? It isn’t. I like some things about Windows, just like I also like some things about Linux. Personally I also believe we had more control over our machines when we used DOS. With all that said, I still like PowerShell. If you don’t know anything about PowerShell, then it behooves you to learn, especially if you are in an IT or administrative career.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.