Solved

Powershell, Scheduled Task, Exchange

Posted on 2012-04-13
11
779 Views
Last Modified: 2012-04-13
Hello Experts,

I have a somewhat bizarre problem which I cant figure out. I have a windows 2008 server r2, which acts as a script runner. In other words it's only purpose is to run scheduled scripts.
Everything and all of the scripts works fine, except one of the scripts. This script bulks out mailbox end user information from exchange 2003 and outputes it to a csv file.

My problem:
When I run the script manually I get all the headers + information out in the csv file
When the script is run from scheduled tasks, it does not output all the information required.

Script code:
$Date = Get-Date
$Date = $Date.ToString("ddMMyyyy")

Get-WmiObject -Class Exchange_Mailbox -NameSpace root\microsoftexchangev2 -ComputerName ExchangeServerName1,ExchangeServerName2 | where {$_.DateDiscoveredAbsentInDS -eq $null} | select @{Label='SamAccountName';Expression={(Get-QADUser -Identity $_.LegacyDN).SamAccountName}}, @{Label='mail';Expression={(Get-QADUser -includedproperties "mail" -Identity $_.LegacyDN).mail}}, ServerName, StorageGroupName, Storename, Size, mailboxdisplayname | Export-Csv C:\Management\MailboxUserInfo\Exchange2003MUI$date.csv -NoTypeInformation

When i run the script manually heres what the output looks like:
SamAccountName,"mail","ServerName","StorageGroupName","Storename","Size","mailboxdisplayname"
Firma,"Firstname.Lastname@domain.se","SMCR090V","First Storage Group","Std2","184319","FullName"
EM0403,"Firstname.Lastname@domain.se","SMCR090V","First Storage Group","Std2","567","FullName"

But when ran from scheduled tasks, the output looks like this:
SamAccountName,"mail","ServerName","StorageGroupName","Storename","Size","mailboxdisplayname"
,,"SMCR090V","First Storage Group","Std2","184319","Fullname"
,,"SMCR090V","First Storage Group","Std2","567","Fullname"


Conclusion:
As you can see when the script is ran from scheduled tasks it will not output the SamAccountName and Mail... Any ideas experts ?

cheer,s

//Juuso
0
Comment
Question by:JuusoConnecta
  • 5
  • 2
  • 2
  • +2
11 Comments
 
LVL 17

Expert Comment

by:Anuroopsundd
ID: 37842136
in the Schedule task have you entered the username and password with account that you running manually? it may be the permissions issue.
0
 
LVL 11

Author Comment

by:JuusoConnecta
ID: 37842165
Thanks for the input. I've taken that into consideration and the result is the same.
I have scheduled the script to be run with the same user account and password than when I run it manually..
0
 
LVL 12

Expert Comment

by:prashanthd
ID: 37842177
Have you set script to run with highest privileges?
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 11

Author Comment

by:JuusoConnecta
ID: 37842187
Yes
0
 
LVL 12

Expert Comment

by:prashanthd
ID: 37842435
how did you schedule the script? In a batch file?
0
 
LVL 11

Author Comment

by:JuusoConnecta
ID: 37842474
No, its directly a powershell script.

Program script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Add argument: C:\Management\Scripts\WorkingScripts\Exchange2003UserInfo.ps1
0
 
LVL 17

Expert Comment

by:Anuroopsundd
ID: 37842543
can you check below post and see if this can be the reason

http://www.jamssupport.com/KnowledgebaseArticle50027.aspx
0
 
LVL 11

Author Comment

by:JuusoConnecta
ID: 37842588
Have tried that as well, that isnt the issue. The script is fully functional when running it manually, but not when running thru scheduled tasks, regardless if you use the parameter set-executionpolicy.

I can also add that all other scripts, for example a script that basically does the same thing runs against Exchange 2010 works perfectly, but not the one that goes against exchange 2003..

regards
0
 
LVL 6

Accepted Solution

by:
slidingfox earned 500 total points
ID: 37842623
Looks like the SAMAccountName and Mail items are pulled using the Quest tools (Get-QADUser). Could you try adding the following to the top of the script and see if it makes a difference?

Note: This is assuming that you've installed the Quest AD CmdLets in the default location.

Add-PSSnapin Quest.ActiveRoles.ADManagement
& 'C:\Program Files\Quest Software\Management Shell for AD\qsft.ps1'

Open in new window

0
 
LVL 69

Expert Comment

by:Qlemo
ID: 37842628
Did you issue exact the same commandline? Get-QADUser is Quest cmdlet not loaded as part of the default modules. Your command for testing it manually should say
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe C:\Management\Scripts\WorkingScripts\Exchange2003UserInfo.ps1

Open in new window

, started in e.g. a Cmd window.
0
 
LVL 11

Author Comment

by:JuusoConnecta
ID: 37842739
Cheers slidingfox, been working so many scripts lately in the same powershell session (probably havent closed it for 3 weeks), so I did not even notice that the quest modules were already in the session, of course I didnt have the add-pssnapin parameter in the scheduled script...

Thanks for this, it was the last of my 10 scripts =), can now relax with a good conscious. Cheers!
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
how to add IIS SMTP to handle application/Scanner relays into office 365.

680 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question