Chris,


I moved my script to a Win7 machine which has the latest PowerGui and what I believe is PowerShell v2 installed (I think Win 7 has it by default?)

Either I am executing the script wrong or something is missing here are my results.

When I Run the changed script from PowerGui I get no errors it runs clean but the results in the csv file are the same.

When I open up powershell and try to run the code I get the following errors.


Script


PS U:\> function func_Disabled_Users()
>> {
>> #region Get the current PowerPack configuration.
>> $configuration = Get-ActiveDirectoryPowerPackConfiguration
>> #endregion
>>
>> #region Connect if we're not already connected.
>> $configuration.Connect()
>> #endregion
>>
>> #region Set the data object on the current node.
>> Set-PowerGUINodeData -AssociatedObject @{'Connection'=$configuration.Connection}
>> #endregion
>>
>> #region Retrieve the disabled users.
>>   Get-QADUser -Disabled -PageSize $configuration.DefaultPageSize -SizeLimit $configuration.DefaultSizeLimit -Connecti
on $configuration.Connection -ErrorAction SilentlyContinue `
>>       | Add-Member -MemberType NoteProperty   -Name Connection -Value $configuration.Connection -Force -PassThru `
>>       | Add-Member -MemberType ScriptProperty -name MemberOfEx -value {$this | select -ExpandProperty memberOf} -Forc
e -PassThru `
>>       | Add-Member -MemberType ScriptProperty -name NestedMemberOfEx -value {$this | select -ExpandProperty nestedMem
berOf} -Force -PassThru
>> #endregion
>> }
>>
PS U:\>  func_Disabled_Users | where {'choice.internal/Internal Users/Admin + Service  Accounts No TS profiles','choice.
internal/Internal Users/Resources','choice.internal/Microsoft Exchange System Objects','choice.internal/Users','choice.i
nternal/Users/Configuration','choice.internal/Users/Network Associates'-notcontains $_.ParentContainer}| Select-Object -
property 'Name', 'ParentContainer', 'Email', 'MemberOf', 'NestedMemberOf' | Sort-Object -property 'ParentContainer' | Ex
port-Csv c:\ExportDrop\disabled.csv -NoTypeInformation

Error

The term 'Get-ActiveDirectoryPowerPackConfiguration' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
 again.
At line:4 char:59
+ $configuration = Get-ActiveDirectoryPowerPackConfiguration <<<<
    + CategoryInfo          : ObjectNotFound: (Get-ActiveDirec...ckConfiguration:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

You cannot call a method on a null-valued expression.
At line:7 char:23
+ $configuration.Connect <<<< ()
    + CategoryInfo          : InvalidOperation: (Connect:String) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

The term 'Set-PowerGUINodeData' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:10 char:21
+ Set-PowerGUINodeData <<<<  -AssociatedObject @{'Connection'=$configuration.Connection}
    + CategoryInfo          : ObjectNotFound: (Set-PowerGUINodeData:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The term 'Get-QADUser' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
 spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:13 char:14
+   Get-QADUser <<<<  -Disabled -PageSize $configuration.DefaultPageSize -SizeLimit $configuration.DefaultSizeLimit -Co
nnection $configuration.Connection -ErrorAction SilentlyContinue `
    + CategoryInfo          : ObjectNotFound: (Get-QADUser:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


Thx again
Tom

Why do you say that?

I'm using PowerShell v2 with the Quest AD cmdlets against a 2003 domain. Everything is working great.

-Chris