Solved

Powershell, Scheduled Task, Exchange

Posted on 2012-04-13
11
778 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
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 
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

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

The following article is intended as a guide to using PowerShell as a more versatile and reliable form of application detection in SCCM.
Windows 10 came with  a lot of built in applications, Some organisations leave them there, some will control them using GPO's. This Article is useful for those who do not want to have any applications in their image (example:me).
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

856 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