to “Microsoft Active Directory Health Check PowerShell Script Version 2.01”

1. 
   Sekar Says:
   February 22, 2018 at 4:27 pm

   Hi Carl,

   I am unable to get the output file, getting below error

   WARNING: 02/22/2018 17:34:31: Unable to save the output file, C:\Users\temp\Desktop\Downloads\temp\ADHealthCheck.docx
   ProcessDocumentOutput : Unable to save the output file, C:\Users\temp\Desktop\Downloads\temp\ADHealthCheck.docx
   At C:\Users\temp\Desktop\Downloads\temp\ADHealthCheck_v2.ps1:4052 char:1
   + ProcessDocumentOutput
   + ~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
   + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ProcessDocumentOutput

   Reply

   • 
     Carl Webster Says:
     February 26, 2018 at 7:44 am

     This is the #1 support email I receive. I absolutely HATE Click-to-run Office. Your issue is usually resolved by doing the long online repair option. With click-to-run, not every feature of Word the script needs are installed until they are needed. Try the repair option and see if that fixes it.

     Thanks

     Webster

     Reply

2. 
   Chris Says:
   March 3, 2017 at 3:58 pm

   I am running this remotely from a machine that has Office on it, with enter-pssession servername, and it is still saying “this script directly outputs to Microsoft Word, please install Microsoft Word”. Am I not running it correctly from enter-pssession? Or is there something else I’m missing?

   Reply

   • 
     Carl Webster Says:
     March 3, 2017 at 4:03 pm

     If the computer running the script is a domain member, there is no need for PSSession.

     If you are using PSSession, I believe the script will check that computer for all the prereqs. I have never needed to use a PSSession to run the script.

     Webster

     Reply

     • 
       Chris Says:
       March 3, 2017 at 5:19 pm

       Thank you for the quick response! That was it for some reason I was thinking I had to be connected to a DC to do it. Great script!

       Reply

3. 
   mikevanderham Says:
   November 9, 2016 at 9:30 am

   Hi Webster,

   I constantly got the error:

   ProcessDocumentOutput : Unable to save the output file,

   No clue why , I ran powershell as admin and got all rights on the to be saved location?

   cheers,Mike

   Reply

   • 
     Carl Webster Says:
     November 9, 2016 at 9:33 am

     This happens to some people some of the time. If you are using the 64-bit version of PowerShell, try the x86 version. I have no idea why some people have this issue and some people do not. I have run the various scripts in both 32-bit and 64-bit PowerShell with both 32-bit and 64-bit Word and never have been able to reproduce this issue.

     Thanks

     Webster

     Reply

     • 
       Scott Says:
       May 9, 2017 at 10:54 am

       It has this failure when running in Powershell ISE. Works fine in regular Powershell.

       Reply

       • 
         Carl Webster Says:
         May 9, 2017 at 10:59 am

         I never test or run my script in ISE because of the foreign language characters.

         Webster

         Reply

Leave a Reply