Comments from the survey

As you probably know, we've been running a survey for, which helps us both improve the site and create demographic information that makes us appealing to sponsors (who, you know, pay for everything here). We've gotten a ton of great feedback. Yeah, we really are reading every single comment you left.

Let's start with the biggies:

Maybe some more guest writers for articles? I imagine it's difficult with all the articles that get posted all over the net every day, but maybe some of those folks (like the scripting guys or scripting wife) can do some to help the community.

You find us guest authors, we'll give 'em a place to write. Problem is, not many folks want to write. We try to aggregate the better PowerShell-related blogs out there (we link to the original site so that we're not stealing their traffic) just as a discovery mechanism, but I'm not sure what else we could do.

On the forum almost every thread remains 'unsolved'. Maybe moderators can close threads, and even remove posts that are not relevant. I also see a lot of questions returning, for example on 'how to change a property in AD'. I don't know if this can be avoided, but if you know a way to diminish double threads, that would be great.

Testify, brother. You tell me how to fix it and we'll give it a shot. The rest of the interwebz would probably like to know how to fix that, too. We can't make people click "solved," and believe it or not they get TESTY if we click it for them. Seriously. Been yelled at. And don't know how to make people search before they post. Just don't.

And now for some shorter responses:

  • PHPBB forums for questions... just link to StackExchange. Honestly, whatevs. We literally have at least one comment telling us to use every piece of forums software out there, and/or link to every other forum already out there. ServerFault, ExpertsExchange, we've got 'em all in here. We'll continue having our own forums mainly because it's easier to ensure newcomers (especially) get a polite answer, not a brush-off, which happens too often in some of the other forums I've seen. As for software, we're moving off of phpBB in June.
  • I don't know if that something not to like - but I do think that people should be awarded for contributing to the community. Agreed. Looking into it.
  • forum email notifications work sporadically (does not always send an email for notices/updates). I'm not sure they're that sporadic - I've looked into this a LOT. A lot a lot. Problem is that people have their spam settings set to DEFCON 1, with three layers of filtering. ForeFront Online Protection, for example, had a global block against our hosting company's IP addresses that we had to get resolved - when things are blocked at that level, you'll never see it in your Spam folders.
  • I love the simplicity of the site, please DON'T make it too busy with meaningless ads and trivialites. Dang. There goes our plans for putting ads every three inches on the page. Oh, well.
  • It needs rss feeds. It has 'em.
  • Regarding Summit info, and especially the session registration process has been a bit confusing. I'm not sure of a single place to optionally check status updates. I know. That's my fault. We're going to do better next time, putting everything in the "Announcements" category here.
  • There is too much fokus on American area. We need more European stuff / events. Dude, you help us put it together, then. You live there. Asking Americans to put on a European event does not smell like a recipe for success, ya know?
  • It's not possible but it'd be nice if the moderators when stumped would reach out to the masters to get threads answered. We really try to. Sometimes the other folks aren't all that responsive. They got jobs too, and whatnot.
  • The home page isn't very appealing - not a big complaint but it could do with a makeover. Done. Hope you like it. The Forums will be moving, too.
  • There's a lot of good email newsletter design templates available out there to make it more reader friendly and not just a wall of text. Well, PowerShell's pretty text-heavy. Guess we're not big GUI folks <grin>.
  • I do not like the fact that you make business around powershell. Yeah, I'm not sure you and I agree on what a "business" is. We set up, Inc., so that an entity could own the Web site and pay for its hosting. We make about enough money from sponsorships to pay those bills. Officially,, Inc. is "not for profit." Nobody draws a salary or gets paid. We can't give you all of these resources for free without someone paying, and the "business" gives that money a place to go so that it is only used to run the community. Nobody else can pinch off pieces of the money for their own purposes.
  • More integration / collaboration with PowerShell User Groups. Yeah, working on it. Literally, Mark Schill (who runs that site) and I have been exchanging e-mails this morning. We both understand the value in having one place to discover user groups and keep up with their schedules; we're trying to figure out the best way to deliver the functionality user group leaders require to post that information, and where the best place is for it to all live. We'll link to it from here, wherever that turns out to be. Stay tuned.
  • Put newsletters in an online archive. Working on it. The March switch in mail providers was in large part to facilitate this. I just need some time to finish up the programmery bits needed.
  • Live hangouts/webinars in the vein of what vBrownbag does for virtualization. Awesome idea. You volunteering to lead 'em? Please, contact me if you are.

Y'all had a bunch of nice things to say, too, which we all appreciate. We'll be sharing the complete survey results once it finishes running at the end of May.

But let's wrap with a big philosophical comment, because I'd really like your feedback on this one - just drop a comment below if you care to weigh in.

I would like to see a site that becomes the authoritative place to go for resources since Microsoft doesn't really seem all that interested any more. There are way to many sites hosting scripts and pieces of "stuff". I would really like to have "One site to rule them all." 😉

I get that. But... in some cases, the folks running a great resource (take want to rule their own destiny, and not become part of the collective. Nothing wrong with that - it lets them do their own thing. We're trying to just link to the best of those community resources, so that people can find them when they run across this site. If someone wants to jump in and be part of, we'll try and make it happen - our charter is to offer support and resources to anyone who's contributing - but we don't really lobby for them to do that. If you see something out there you like, and you think they should hook up with us in some fashion, tell them.

Posted in:
About the Author

Don Jones

Profile photo of Don Jones

Don Jones is a Windows PowerShell MVP, author of several Windows PowerShell books (and other IT books), Co-founder and President/CEO of, PowerShell columnist for Microsoft TechNet Magazine, PowerShell educator, and designer/author of several Windows PowerShell courses (including Microsoft's). Power to the shell!


  1. PowerShell on Linux exists to help Windows admins to help them transition away from Windows Server. But In a decade, when > 75% of workloads running on Azure are Linux, the tools used to manage those workloads will be designed for and meet the needs of the Linux administrator mindset. Linux administrators have a great set of mature tools and it isn't entirely clear why they'd want to transition to using PowerShell. Linux has won. The growth of Linux on Azure shows that. It's time for Azure to be a Linux First environment - and PowerShell on Linux doesn't really fit because it's primarily trying to graft a new and unproven Microsoft way of doing things onto successful practices and culture. Sure they can do it - but they'd be better off retraining everyone to "Think Linux".

    If Microsoft has (apparently) given up on Windows Server and understand that only a few legacy holdouts will want to run it in Azure in 10 years time (with the majority of workloads being Linux), they are wasting resources trying to reinvent how Linux administrators do things as a way of placating legacy Windows administrators. Legacy Windows administrators should bite the bullet and go "all-in" and adopt existing successful open source administration paradigms. The clock is ticking on their relevance and if they spend precious time investing in a nascent administration technology instead of fully transitioning to an open source mindset, they'll be less employable in future.

    PowerShell on Linux would be a neat idea if Windows Server had a future. It'll remain around in the same way that mainframes are still with us - but Microsoft has no interest in making a compelling case for organizations to choose their product over the free alternative. The future of Windows Server is the current reality of Windows Phone.

    • Thank you SO much for contributing your perspective! I do think - and I'm not a Microsoft fanboy per se - that you're misinformed, or at least under-informed. Time will tell, of course, but I suspect you've brought some personal bias to your viewpoint.

    • Interesting perspective. But I think you missed the point why Microsoft is actually open sourcing PowerShell. If you followed the talks that Jeffrey Snover did the last few years, it became clear that they want to be able to support heterogeneous environments. And for what I've seen now from Microsoft, and especially the PowerShell team, is that they don't have a hidden agenda. Microsoft is not the Microsoft anymore from let's say, 5-10 years ago.

      I agree with you, that there's a lot of Linux on Azure. But many, many companies I come are mainly Windows based infrastructures. Also guys that I know that work for other companies almost only see Windows based infra's.

      Yes, Linux has it's place in this world, but according for Microsoft there's no battle between Windows or Linux. They're citizens in IT which Microsoft wants to support best. And PowerShell is not a tool per se, it's meant to be a management framework. A framework that operates with built-in tools or in the case of Windows, the .NET framework.

      Windows Server has a big future, just look at the developments Microsoft is doing on Nano server.

    • Do you really think in 20 years well be dealing with "OS war" ?

      Do you think well see linux or windows in 20-30 years ? I dont.

      Do you think there is a loosing side or a winning side ? There are never winners in any war.

      From my POV, the shift towards lean kernels to accommodate the cloud, will get us eventually to a unified kernel of some sort getting the best of breed of all OSes, giving developers and IT the option to focus on the tools and the frameworks and less about the underlying layers.

      Running a business that creates OS is becoming very expensive. No one wants to be limited in the tools they want to use, thus the SQL on Linux is a huge huge thing in that sense and it will only get bigger with more such products going the same way. I have yet to see any major party offer anything similar things, coming from the Linux side because it takes money and effort very little companies have, so MS in that sense is helping transform the ecosystem again and its in a very good direction.

      Powershell on Linux exists so I, as a windows admin will have a lower barrier of entrance, if my boss decides one day to invest some our company assets on linux. If I can help my company get the right decisions that will save it money and achieve more and if that means going with a non MS way, guess what, I can still use my skills from the windows side without the hassle of the learning curve.

      For a long time I've been an advocate of learning both windows and Linux, no matter what I do mostly in my work time, as they are just tools to make the job, means to achieve a goal..they are not the goals themselves, and the movement to the cloud just emphasize it even more.

      I think your notion of what open source and free means is what's leading you in the line of thought and that's where I think you were wrong, imho.
      Not saying that my notion of what open source and free means is better, but its somewhat less biased. Nothing is free. Open source doesn't mean security (look at the horrible OpenSSL hole that's been there for two years and only recently been closed, or support-when-you-NEED it, that will always cost money, either by support contracts or having devs that know that specific language to deal with the bugs internaly (which by itself is even more limiting with the amount of languages and frameworks popping every second day).

      As for hidden agendas, you need to remember this is still a business. There's always money involved and business opportunities to be made. MS along they years was always good in creating those opportunities for itself and its partners and it continues to do so, the bottom line will be the tools. If you have ones that do the job for you, keep using them. If MS puts money and effort to create better tools with the community, who's the winner ? Everyone.

      I've seen this in the heated arguments on the PS repo the second it went public. The lack of broader vision some of the Linux base audience showed, the arrogance, the "Its mine, dont touch it" is somewhat alarming. I'm just happy to know that the sysadmins in 20 years, the ones born today well have a different starting point where they will choose the tools and be told what to use by old retiring sysadmins that are trying to hold to their precious seats instead of embracing change and supporting it in the evolving it world.

  2. If I have to copy files from installation folder to destination and I have to do exception handling because everything is automated, then how to do that? What all errors may arise and how to recognize and handle them? Please help.

  3. powershell ought to get the credit it deserves for enabling a developer to rapidly create rich output handling complex decisions based upon datasets gathered from various means and implementing a nearly infinite number of actions based on these. Simply put, it can be, and it is, much more than an admin tool, in the right hands.

  4. To start this is a thing of beauty in it's simplicity.
    Does anyone have experience with how much memory the results occupy and doing Get-job | Receive-Job at the end? If I run say a 1000 or 10,000 will this cause memory problems? I am thinking doing Get-Job -State Complete | Receive-Job & then |remove-job inside the loop (and logging it) would reduce the chance of running the host out of memory, or am I just over complicating it?

  5. a) Remoting
    The primary purpose of PS on *nix will be remoting to Win-Hosts, such as Bash on Windows vice versa.

    Due to the nature of *nix as document driven OS, an object based shell does not make that much sense. We're missing the API level. Jeffrey told us so, long ago.

    b) Religious affairs
    It's not about publishing the code (which is nevertheless great!).
    The GPL especially is the denial of the biz model that drives the revenue of Microsoft. So, indeed, haters will hate. Agree.

    But, in for a penny, in for a pound, PoSh is part of Windows which is an expensive, closed down product, increasingly incapacitating the user.

    c) The role of Community
    Sorry to say that, but the PS community is so much more than the few "Get-Expert -wellknown | Get-Random" MVPs. I know it's hard to see that inside the bubble.

    PoSh itself is gorgeous but - at the end - just a shell, such as Korn, C, Z and all the others.

    Far more important: the promise of a datacenter abstraction layer beyond the borders of specific vendors, automation and the refusal of a click UI.

    In this sense, publishing the underlying code is a statement which can't be exaggerated!

    Great Post, Don!

  6. Thanks, Don. This article saved me tons of frustration. I was writing a fairly simple script that would iterate through a list of servers and grab some WMI information. However, using Get-Content, I found that once the file went beyond some threshold, my script would no longer work properly. Implementing your method fixed my problem, and the script works perfectly.

Leave a Reply

Your email address will not be published. Required fields are marked *