Move-AdmObject in Try statement

Question

Hi

Using 2018.1 (3.9.15631.0) I'm not sure if this is an issue as such, or if it is a known thing with the Adaxes powershell commands but when using the Move-AdmObject command within a Try statement, if the command fails the error is not caught.

Thanks

Comments

Hello,

For troubleshooting purposes, could you post here or send us (support[at]adaxes.com) the script you are using?

---

Sure, the script I was using is

Import-Module Adaxes
$TargetPath = "%adm-CustomAttributeText1%"
$Context.LogMessage("Target OU is $TargetPath", "Information")
try { Move-AmdObject -Identity "%objectGUID%" -TargetPath $TargetPath }
catch { $Context.LogMessage("Failed to move the user with error $Error[0]", "Error") }

Where %adm-CustomAttributeText1% has been set earlier in the process and the value is correct in the log file.
If I import the Adaxes module in Powershell directly and fudge the GUID to a non valid one, I get the error

 Move-ADMObject : Can't find an object with identity 'invalid guid'.  
 At C:\\Users\\...\\Desktop\\TestUserMove.ps1:8 char:7  
 + try { Move-ADMObject -Identity $testguid -TargetPath $Destination }  
 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
  + CategoryInfo : ObjectNotFound: (:) \[Move-AdmObject\], IdentityResolvingException  
  + FullyQualifiedErrorId : Softerra:Adaxes:PowerShellModule:Commands:MoveAdmObjectCommandExecutor:ProcessRecord:IdentityNotResolved,Softerra.Adaxes.PowerShell  
  Module.Commands.MoveAdmObjectCommand

The Catch statement is never executed.

Thanks

Answer 1

Hello,
You need to set the ErrorAction parameter to stop for the cmdlet. For details about the parameter, check the following article on Microsoft blog: https://blogs.technet.microsoft.com/hey ... shell-way/. Your script will be like the following:

Import-Module Adaxes
$TargetPath = "%adm-CustomAttributeText1%"
$Context.LogMessage("Target OU is $TargetPath", "Information")

try 
{
    Move-AdmObject -Identity "%objectGUID%" -TargetPath $TargetPath -ErrorAction stop
}
catch 
{
    $Context.LogMessage("Failed to move the user with error $Error[0]", "Error") 
}

Also, make sure that you enter the correct cmdlet. It should be Move-AdmObject, not Move-AmdObject.

Comments

Thanks for the info, I'll try adding the erroraction and see see what happens.

Additional quick question, would it work if I were to change the process to use the inbuilt 'Move the User' action and set the destination to %adm-CustomAttributeText1%?

---

Hello,

Yes, it will work fine. Just make sure that the custom attribute of the user account for which the action is executed is set to the distinguished name (DN) of the target container.

---

Brill, I'll use than instead then, will make it all easier :D