Invoke admu discovery

The 'invoke-admu-discovery.ps1' script is used to output the 'admu_discovery.csv' that is used to call the conversion migration step.

The script will do the following:

• Create csv with headers
• Collect computer names from AD query e.g. systems last logged into in past 30 days, in a specific OU, DN name doesn't contain a value etc.
• Test network connection asyncronously and seperate into online and offline computers
• Run a script block to gather data for discovery csv on each system as a seperate powershell job name 'ADMU-DISCOVERY'
• Monitor running, complete, complete with error and errored jobs.
• Output log for each computer and combine successful jobs into discovery csv.

'output' folder in c:\windows\Temp\ & 'admu_discovery.csv'.

Each powershell job is outputed to a file.

Example txt Output:

Job Name: ADMU-DISCOVERY

Job State: Completed

Command:
        #Command ran on system

Output:

"10ENT17091","JCADB2\jsmith","C:\Users\jsmith.JCADB2","False","True",,"john.smith","Temp123!","true","false","false","false","false","1111111111111111111111111111111111111111","false","true",,"jcadb2.local"

The successful output is appended to the 'admu_discovery.csv'.

The 'admu_discovery.csv' should then be modified so there is one entry per system and all feilds are completed as required.

The 'admu_discovery.csv' has the following columns and will be used as inputs for the invoke-migration script: Invoke-admu-migration

• "ComputerName"
• "SelectedUserName"
• "LocalPath"
• "RoamingConfigured"
• "Loaded"
• "LocalProfileSize"
• "JumpCloudUserName"
• "TempPassword"
• "AcceptEULA"
• "LeaveDomain"
• "ForceReboot"
• "AzureADProfile"
• "InstallJCAgent"
• "JumpCloudConnectKey"
• "Customxml"
• "ConvertProfile"
• "MigrationSuccess"
• "DomainName"