Upgrading from Powershell v2 to Powershell v3

This topic contains 3 replies, has 3 voices, and was last updated by  Scott Bass 4 years, 3 months ago.

  • Author
    Posts
  • #6576

    Scott Bass
    Participant

    Hi,

    My corporate arrangement with my IT department is a funny one.  They've put together the server (Windows 2008 Enterprise x64 under VMWare).  They apply patches and otherwise maintain the O/S.  However, I have admin rights and maintain other software that I and my department use.  I'm an "IT Type" with a fair bit of experience, but in the business unit.

    Why they don't consider Powershell to be part of the operating system is beyond me.  My request to upgrade has been met with "that's a Server 2012 feature, but you can do it yourself".  Perhaps they're just lazy 😉

    In any case, they have left it to me to upgrade to PS V3, should I so desire.  Which I do.

    So, are there any gotchas or issues with an upgrade to PS V3 on this environment?  Is there anything I need to know other than launch the installer and click next/ok?  Is PS V3 fully backwards compatible with PS V2, i.e. it won't break existing scripts?

    If I stuff this up it would be a "career limiting move" lol.

    Thanks for the advice!

  • #6577

    Don Jones
    Keymaster

    Several gotchas, in fact. Most of the server products (Exchange, SQL, etc) aren't supported with v3 installed. v3 is not, it seems, completely backward compatible. You'll want to use caution and research each product, and have a rollback plan.

  • #6601

    David Zemdegs
    Participant

    One big tip. I installed Powershell V3 on a production server which is only available through RDP. When I restarted the box, RDP broke i.e. I could no longer RDP into the server. This is a known issue.

    What we found out was that there was a problem with MS update KB2667402 which, combined with POSH v3, breaks RDP.

    What I do now if I want to install V3, is to see if the server has hotfix 2667402 installed. If it has, I uninstall it and then install Posh v3. So far things are OK.

  • #6705

    Scott Bass
    Participant

    Thanks Dave.  This is a huge gotcha for us.  We (my entire team) RDP into this server on a daily basis.

    If 2667402 was installed, and I installed Posh v3, I'd have no way to get back into the server and fix it.  And IT might take days to rollback the install.

    If 2667402 is not installed, and I install Posh v3, and later IT apply the hotfix, RDP again breaks.

    I think at this point I'll hold off on Posh v3.  A pity, but the new features do not outweigh the risks.

You must be logged in to reply to this topic.