PST Capture 2.0 not running on Windows 8.1 and Windows Server 2012 R2 due to PowerShell 3.0->4.0 replacement

Does anybody know if we can expect an update to PST Capture 2.0 that runs on PowerShell 4.0?

In Windows 8.1 and Windows Server 2012 R2, even explicitly starting PowerShell 3.0 lifts the environment to 4.0, which isn't supported by PST Capture 2.0, which then can't be installed on these two platforms.

Thanks,

Ren

December 12th, 2013 8:32pm

Hi

According to this article only up to Server 2012 and windows 8 is supported:

http://technet.microsoft.com/en-us/library/hh781033(v=exchg.141).aspx

Free Windows Admin Tool Kit Click here and download it now
December 13th, 2013 4:28am

I have the same issue. Running the installer from Powershell using the "version 3.0" switch doesn't work either.
January 8th, 2014 2:13am

I also have the same issue, as do others apparently:

http://community.office365.com/en-us/forums/156/t/205974.aspx

Anyone heard of an impending update?  Otherwise I'll have to look for another machine running 64-bit Win 7 or Win 8 (pre-8.1 update).

Free Windows Admin Tool Kit Click here and download it now
February 6th, 2014 7:54am

I also have the same issue, as do others apparently:

http://community.office365.com/en-us/forums/156/t/205974.aspx

Anyone heard of an impending update?  Otherwise I'll have to look for another machine running 64-bit Win 7 or Win 8 (pre-8.1 update).

Actually I'm finding a hard time finding an applicable machine to run PST Capture!  I don't have any Win 8 machines, only the updated Win 8.1.  And the Win 7 or earlier machines I have access to right now are all 32-bit (PST Capture requires 64-bit).

Still need to offload several hundred GB"s of PST data to Exchange Online mailboxes!


  • Edited by vipkl Monday, February 17, 2014 6:03 AM
February 17th, 2014 5:58am

This is ridiculous!

How on earth should we as partners ever give proper support to our customers that we have - i think more and more mistakenly - put in O365!?

Come on, how hard could it be to remove the hardcoded depency towards PS3.0?!

MS is making my life very difficult! And NO - using manual option like Outlook PST import is not an option when you have +80 users!


Free Windows Admin Tool Kit Click here and download it now
July 18th, 2014 9:32am

Hello everyone!

Sorry for commenting on this old thread, but this the first result in google and bing, and I had a workaround that worked for me that I wanted to share with everyone.

Installing PSTCaptureAgent.msi in compatibility mode:

Right click PSTCaptureAgent.msi > Properties > Click Compatibility tab > under "Compatibility Mode", check "Run this program in compatibility mode for:" > click the "Run compatibility troubleshooter" > click "Test the program" and the installation wizard will start.

Just go through the wizard and install the agent.

I have been able to run a PST Search on the agent and it returned result.

Have not tried to import yet, but this may work fo

September 2nd, 2014 5:21am

This.. did not work.

Care to share exactly what the troubleshooter actually set?

Or.. do I get to iterate all the settings and post back?...

It's pretty piss poor that a program published by Microsoft Coporation isn't compatible with the current server platform.. from Microsoft Corporation.. for almost a year now.

And you tell us partners we have a year to get OUR systems upgraded within 12 months for our partner program software licenses..

Free Windows Admin Tool Kit Click here and download it now
September 12th, 2014 11:14pm

Okay.. so I poked around with InstEd.. sure enough.. why.

Table AppSearch:  Property POWERSHELL30_MINE: Signature_ POWERSHELL30

Table RegLocator: Signature_ POWERSHELL30: Key SOFTWARE\Microsoft\PowerShell\3\PowerShellEngine : Name PowerShellVersion
Table InstallExecuteSequence: Action RedGateRequirePowerShell30: Condition POWERSHELL30_MINE <> "3.0"


See the FRIGGIN' problem with sloppy coding?  That condition can be read as "Check that reg key for the value.. and if it isn't EXACTLY "3.0" then fail.  If you publish a product which has a system requirement of "PowerShell 3.0 or higher" then CHECK THE VERSION PROPERLY TO SEE IF POWERSHELL MIGHT BE HIGHER THAN 3.0.. PLEASE.

Three hacks.. edit the MSI to update the condition check.. or change the value it checks for to "4.0".. or regedit the value back to "3.0", run, and change back.  Any does the job, the first is the more permanent package fix.

  • Proposed as answer by BradyOsborne Saturday, October 18, 2014 6:18 PM
  • Marked as answer by René Balzano Saturday, October 18, 2014 6:44 PM
September 12th, 2014 11:38pm

This worked for me!  Thanks so much!
Free Windows Admin Tool Kit Click here and download it now
October 18th, 2014 6:18pm

To install PST Capture 2.0.0 on Windows 8.1, I've edited the condition

Table InstallExecuteSequence: Action RedGateRequirePowerShell30: Condition POWERSHELL30_MINE <> "3.0"

to

Table InstallExecuteSequence: Action RedGateRequirePowerShell30: Condition POWERSHELL30_MINE <> "4.0"

in the MSI using SuperOrca(DL:http://www.pantaray.com/msi_super_orca.html )

and used "Tools > Run MSI". Works like a charm, thanks for the idea and workaround. It's a shame MS doesn't update his own Tools for own product dependencies.

MCP Server, Hyper-V, SCCM




  • Edited by K. Heinz Thursday, January 01, 2015 9:12 PM
January 1st, 2015 9:09pm

Thank you so much K.Heinz! Works fine here using SuperOrca :)
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2015 9:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics