#Print cost details for the Account for current month
$currDate = Get-Date
$firstDay = Get-Date $currDate -Day 1 -Hour 0 -Minute 0 -Second 0
$lastDay = Get-Date $firstDay.AddMonths(1).AddSeconds(-1)
$firstDayFormat = Get-Date $firstDay -Format 'yyyy-MM-dd'
$lastDayFormat = Get-Date $lastDay -Format 'yyyy-MM-dd'

$interval = New-Object Amazon.CostExplorer.Model.DateInterval
$interval.Start = $firstDayFormat
$interval.End = $lastDayFormat

$costUsage = Get-CECostAndUsage -TimePeriod $interval -Granularity MONTHLY -Metric BlendedCost

$costUsage.ResultsByTime.Total["BlendedCost"]

I figured using MDT PowerShell module, can be pretty handy at this task. The only thing I’m using this module, is to utilize MDTProvider so that I can browse through entire share. I wrote this little script that takes few parameters and creates an output CSV file with bundles and apps of the bundle.

Here is how it is used:

-- Example:

    .\pupulateBundles.ps1 -mdtShare "\\Server1\Share1" -Server "Server1" -standardApps "\applications\Image Deployment\Standard Apps" -appBundles "\applications\Image Deployment\App Bundles"

populateBundles_1.zip

I figured using MDT PowerShell module, can be pretty handy at this task. The only thing I’m using this module, is to utilize MDTProvider so that I can browse through entire share.

Here is the snippet of the code:

## Check for module and import, if not already. 
 if(-not(Get-Module -Name MicrosoftDeploymentToolkit))
 {
 try
 {
 Import-Module "C:Program FilesMicrosoft Deployment ToolkitbinMicrosoftDeploymentToolkit.psd1" -ErrorAction Stop
 }
 catch
 {
 “Boooo”
 $_.exception | fl * -Force
 }
 }
 
 ## Create a drive using MDT provider. 
 if(!(Test-Path SERVER1:))
 {
 New-PSDrive -Name "SERVER1" -PSProvider MDTProvider -Root "\SERVER1ShareName1"
 }
 
 ## Populate all objects from bundles & apps. All dependency apps in bundles reside in Apps path. 
 $allBundles = dir "SERVER1:applicationsApp Bundles"
 $stdapps = dir "SERVER1:applicationsApps"
 
 ## Create CSV file 
 $csvFile = New-Item -Type file -Path "C:ProgramDatatemp1" -Name ((Get-Date -f MMM-dd-yyyy-HH-mm-ss)+".csv") -Force
 
 "Name, Bundle, Guid, Version, Path, Commandline" | Out-File $csvFile -Append -Encoding ascii
 
 
 ## Populate and fill data into CSV
 foreach ($bundle in $allBundles) 
 { 
 "------------------------------------------------------------"+ ","+ ","+ ","+ ","| Out-File $csvFile -Append -Encoding ascii
 $bundle.name + ",****"+ ",****"+ ",****"+ ",****"| Out-File $csvFile -Append -Encoding ascii
 "------------------------------------------------------------"+ ","+ ","+ ","+ ","| Out-File $csvFile -Append -Encoding ascii
 foreach ($dep in $bundle.dependency) 
 {
 $stdapps | foreach {
 if($_.guid -eq $dep)
 {
 $_.name + "," +$bundle.Name +","+ $_.guid + "," +$_.version + "," +("\SERVER1ShareName1" + $_.workingdirectory.remove(0,2)) + "," + $_.Commandline + "," 
 }
 
 } | Out-File $csvFile -Append -Encoding ascii
 
 
 }
 
 } 
 
 ## Open CSV
 
 & $csvFile 
 

You can modify the script as per your need, like adding/replacing more properties etc.. Once the object is in hand, you can fetch anything around it.

This is MDT 2012 Update 1 and trying to publish applications for Windows 7.

So, here is the error:

VERBOSE: Performing operation "import" on Target "Application".
VERBOSE: Beginning application import
VERBOSE: Copying application source files from X:\AutoDesk\Design Review\2013\Sequenced App\Autodesk_DesignReview_2013_UN_01_APPV to \\WNServer1\PHSDeploy$\Applications\Design Review
Import-MDTApplication : The system cannot find the path specified at

+         Import-MDTApplication -path $MDTBaseAppFolder -enable "True" -Name $App.Name - ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Import-MDTApplication], DeploymentPointException
    + FullyQualifiedErrorId : Win32Error,Microsoft.BDD.PSSnapIn.ImportApplication

All I'm doing is, trying to run Import-MDTApplication with parameters as below:

Import-MDTApplication -path $MDTBaseAppFolder -enable "True" -Name $App.Name -ShortName $App.ShortName -Version $App.Version -Publisher $App.Publisher -Language $App.Language -CommandLIne $App.CommandLIne -WorkingDirectory $App.WorkingDirectory -ApplicationSourcePath $App.AppSourcePath -DestinationFolder $App.DestinationFolder -Verbose

Above command is wrapped into a PS1 script file called APPV5Install.ps1, which will take inputs for above parameters from a CSV file taken as a script parameter. This is to simplify task and do multiple entries into MDT.

The CSV file has similar to below data:

The issue was, there was a trailing space after 'Destinationfolder' and 'WorkingDirectory' field. After removing the space, I was able to import application successfully.

Many of the times, we might need to dig deep into the event log, which might not be easily available through default fields available. For example, below event contains much more information than it displays in the event log.

Log Name:      Microsoft-Windows-GroupPolicy/Operational

Source:        Microsoft-Windows-GroupPolicy

Date:          5/27/2013 2:08:57 PM

Event ID:      7004

Task Category: None

Level:         Error

Keywords:     

User:          SYSTEM

Computer:      PC1.fabrikam.com

Description:

Manual processing of policy failed for computer fabrikam\PC1$ in 243 seconds.

Event Xml:

<Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{fEAgB4h-97j1-45k2-A64C-4D69FFFD92C9}" />

    <EventID>7004</EventID>

    <Version>1</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>2</Opcode>

    <Keywords>0x4000000000000000</Keywords>

    <TimeCreated SystemTime="2013-05-27T02:08:57.106317800Z" />

    <EventRecordID>138644</EventRecordID>

    <Correlation ActivityID="{2B97A5FB-108B-4FtB-BCy8-A8uAE40C1E42}" />

    <Execution ProcessID="640" ThreadID="3040" />

    <Channel>Microsoft-Windows-GroupPolicy/Operational</Channel>

    <Computer> PC1.fabrikam.com</Computer>

    <Security UserID="S-1-5-18" />

  </System>

  <EventData>

    <Data Name="PolicyElaspedTimeInSeconds">243</Data>

    <Data Name="ErrorCode">1053</Data>

    <Data Name="PrincipalSamName">FABRIKAM\PC1$</Data>

    <Data Name="IsMachine">1</Data>

    <Data Name="IsConnectivityFailure">false</Data>

  </EventData>

</Event>

A simple filter around critical/errors/warning on this provider would look like this:

PS C:\WINDOWS\system32> $query = @”

<QueryList>

  <Query Id="0" Path="Microsoft-Windows-GroupPolicy/Operational">

    <Select Path="Microsoft-Windows-GroupPolicy/Operational">*[System[(Level=1  or Level=2 or Level=3)]]</Select>

  </Query>

</QueryList>

“@

PS C:\WINDOWS\system32> Get-WinEvent -FilterXml $query

   ProviderName: Microsoft-Windows-GroupPolicy

TimeCreated                     Id LevelDisplayName Message

-----------                     -- ---------------- -------

5/27/2013 2:08:57 PM          7004 Error            Manual processing of policy failed for computer FABRIKAM\PC1$ in 243 seconds.

5/27/2013 1:18:28 PM          7004 Error            Manual processing of policy failed for computer FABRIKAM\PC1$ in 0 seconds.

5/27/2013 1:18:28 PM          7326 Error            Group Policy failed to discover the Domain Controller details in 0 milliseconds.

5/27/2013 12:27:03 PM         7004 Error            Manual processing of policy failed for computer FABRIKAM\PC1$ in 251 seconds.

5/27/2013 11:32:52 AM         7004 Error            Manual processing of policy failed for computer FABRIKAM\PC1$ in 0 seconds.

.

.

.

.

Let’s check the first event and try to see what it displays by default

PS C:\WINDOWS\system32> Get-WinEvent -FilterXml $query | select -First 1 | fl *

Message              : Manual processing of policy failed for computer fabrikam\pc1$ in 243 seconds.

Id                   : 7004

Version              : 1

Qualifiers           :

Level                : 2

Task                 : 0

Opcode               : 2

Keywords             : 4611686018427387904

RecordId             : 138644

ProviderName         : Microsoft-Windows-GroupPolicy

ProviderId           : aea1b4fa-97d1-45f2-a64c-4d69fffd92c9

LogName              : Microsoft-Windows-GroupPolicy/Operational

ProcessId            : 640

ThreadId             : 3040

MachineName          : pc1.fabrikam.com

UserId               : S-1-5-18

TimeCreated          : 5/27/2013 2:08:57 PM

ActivityId           : 2b97a5fb-108b-4fdb-bcc8-a85ae40c1e42

RelatedActivityId    :

ContainerLog         : Microsoft-Windows-GroupPolicy/Operational

MatchedQueryIds      : {}

Bookmark             : System.Diagnostics.Eventing.Reader.EventBookmark

LevelDisplayName     : Error

OpcodeDisplayName    : Stop

TaskDisplayName      :

KeywordsDisplayNames : {}

Properties           : {System.Diagnostics.Eventing.Reader.EventProperty, System.Diagnostics.Eventing.Reader.EventProperty,

                       System.Diagnostics.Eventing.Reader.EventProperty, System.Diagnostics.Eventing.Reader.EventProperty...}

Convert it to XML:

PS C:\WINDOWS\system32> [xml]$evt1 =(Get-WinEvent -FilterXml $query | select -First 1).toXML() # Cast it with [ xml ]

PS C:\WINDOWS\system32> $evt1

Event

-----

Event

PS C:\WINDOWS\system32> $evt1.Event.EventData

Data

----

{PolicyElaspedTimeInSeconds, ErrorCode, PrincipalSamName, IsMachine...}

PS C:\WINDOWS\system32> $evt1.Event.EventData.Data

Name                                                               #text

----                                                               -----

PolicyElaspedTimeInSeconds                                         241

ErrorCode                                                          1053

PrincipalSamName                                                   fabrikam\pc1$

IsMachine                                                          1

IsConnectivityFailure                                              false

PS C:\WINDOWS\system32> $evt1.Event.System

Provider      : Provider

EventID       : 7004

Version       : 1

Level         : 2

Task          : 0

Opcode        : 2

Keywords      : 0x4000000000000000

TimeCreated   : TimeCreated

EventRecordID : 138660

Correlation   : Correlation

Execution     : Execution

Channel       : Microsoft-Windows-GroupPolicy/Operational

Computer      : pc1.fabrikam.com

Security      : Security

Now, you can see we have control over EventData and System channel, as we could see in XML format of the Event. Let’s see if we want to filter out events only containing the error code 1053 and export them to a file, here is how it could look like:

PS C:\WINDOWS\system32> $file = New-Item -Name log1053.txt -Path c:\temp -Force -type file

PS C:\WINDOWS\system32> Get-WinEvent -FilterXml $query | %{

       $evt = [xml]$_.toxml(); # Cast here with [ xml ]

       if($evt.Event.EventData.Data | ?{$_.'#text' -eq 1053 -and $_.name -eq "errorcode"})

       {

$_ | fl * | Out-File $file -Append

}

 }

Hope this is helpful.

Posting this snippet in case someone needs to add a local group to AD LDS readers role, using PowerShell/ADSI.

#Get the SID of a local group

$myGroup = New-Object security.principal.ntaccount("myGroup2")

$myGroupSid = $myGroup.Translate([security.principal.securityidentifier])

#connect to partition

$readersRole = [adsi]"LDAP://mdt:389/CN=Readers,CN=Roles,DC=myPartition"

#Add the group as member to Readers

$memberToAdd = "<SID=$myGroupSid>"

$readersRole.member.Add($memberToAdd)

$readersRole.CommitChanges()

#connect to partition again, to confirm (or can use adsiedit.msc)

$readersRole = [adsi]"LDAP://mdt:389/CN=Readers,CN=Roles,DC=myPartition"

$readersRole.member