Export results to log file of commands in script

Hey Experts.  Here is a script that I found and am trying to tweak.  I want to echo the results of the script to a log file so I can review it and see how well the script ran.

#Specify the OU you want to search for inactive accounts 
#Specify the OU you want to move your inactive computer accounts to 
#Specify the number of days that computers have been inactive for 
    $NumOfDaysInactiveFor = 60
#Specify the description to set on the computer account 
    $Today = Get-Date 
    $Description = "Account disabled due to inactivity on $Today" 


Get-QADComputer -InactiveFor $NumOfDaysInactiveFor -SizeLimit 0 -SearchRoot $searchOU -IncludedProperties ParentContainerDN | foreach {  
    $computer = $_.ComputerName 
    $SourceOU = $_.DN 
    #Remove the commented # from the next line if you want to set the description to be the source OU 
    #$Description = "SourceOU was $SourceOu" 
    Set-QADComputer $computer -Description $Description 
    Disable-QADComputer $computer 
    Move-QADObject $computer -NewParentContainer $destinationOU  

Open in new window

The log would show which computer(s) were disabled and moved to the Inactive OU.  I'm figuring this would be pretty easy for some PS guru but that isn't me so your help is greatly appreciated!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mcsweenSr. Network AdministratorCommented:
Open Powershell prompt:
c:\path\to\script.ps1 | tee-object c:\path\to\outputfile.txt

Open in new window

samiam41Author Commented:
Thanks mcsween.  Can the command not be placed in the script?
mcsweenSr. Network AdministratorCommented:
You define the output when you call the script so you cannot place it within the script.  You could however create a second script with that command in it which  you can call.

Also, if you don't want the output on the screen and only in the file you can use this instead to overwrite
c:\path\to\script.ps1 > c:\path\to\outputfile.txt

Open in new window

or use this to append to the output file
c:\path\to\script.ps1 >> c:\path\to\outputfile.txt

Open in new window

Challenges in Government Cyber Security

Has cyber security been a challenge in your government organization? Are you looking to improve your government's network security? Learn more about how to improve your government organization's security by viewing our on-demand webinar!

samiam41Author Commented:
Gotcha.  Yeah I just want the results to show up in the log file, not on screen.  I'll test with the information you provided.
samiam41Author Commented:
I couldn't get the PS script to work as their was some sort of error relating to not having the AD piece installed or enabled or whatever.  I wrote a batch script and never looked back at PS.

I have no idea if that works but believe that it does.  I will ask a mod to verify so that you can get the proper credit rather than delete the question out on you since I can't determine whether or not it does.  I'd rather you have the points AND a verified answer.

Hope that you understand.  Thanks!
mcsweenSr. Network AdministratorCommented:
If you want to use that powershell script you need to install Quest AD tools

Add this line to the top of your script (not the batch file)
Add-PSSnapin Quest.ActiveRoles.ADManagement

Open in new window

Then you would run the script from a batch file like this
powershell.exe -command "& 'c:\path\to\script.ps1' " > "C:\path\to\outputfile.txt"

Open in new window


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mcsweenSr. Network AdministratorCommented:
So you can test until you get your original script running do the following.  Save the following line of code that calls  a single cmdlet to a new file C:\test.ps1.

Open in new window

Then you can use the following command to launch the script and output to a file called c:\output.txt
powershell.exe -command "& 'c:\test.ps1' " > "C:\output.txt"

Open in new window

My original post assumed you were running this script from within a powershell prompt.  This one assumes you are running from a cmd window, run dialogue, or task scheduler.

Also make sure you execution policy is set to unrestricted or these scripts will not run.
Open Powershell Prompt and issue Get-ExecutionPolicy cmdlet.  If it returns anything but Unrestricted issue this command.
Set-ExecutionPolicy Unrestricted

Open in new window

mcsweenSr. Network AdministratorCommented:
Comment http:#a40366831 should be accepted as the answer as it directly answers the author's original question of how to save script output to a text file.
mcsweenSr. Network AdministratorCommented:
My last commend just disappeared so re-posting.

Commend http:#a40369764  should be the accepted answer with a grade of A as it directly answered the author's original question of how to save script output to a text file.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.