To create the connector described in this section, configure the tabs in the Management Agent Designer as described in the
Windows PowerShell Connector for FIM 2010 R2 Technical Reference.
The sample connctor uses a template file to provide schema information to the Synchronization Service. Create a text file in the Extension folder called SampleInputFile.txt.
By default, the Extensions folder can be found at:
%ProgramFiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions\.
Paste the following data in to SampleInputFile.txt.
Keep the defaults as listed below.
Select the Row Object Type as shown below.
Select each of the four attributes (EmployeeID, FaxPhone, MobilePhone, OfficePhone) as shown below.
Specify the EmployeeID attribute as the Anchor attribute for the Row Object Type as shown below.
Once the connector has been created, create a run profile with a Full Import run step. Create an additional run profile with a Full Export run step.
↑ Back to top
Create a text file called InputFile.txt in the connector’s
MAData folder, and then paste the following sample data into it:
By default, the MAData folder can be found at:
%ProgramFiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\MAData\
Next, run the Full Import run profile for the connector. If successful, the results should look similar to the following screen capture.
The Windows PowerShell connector supports logging and tracing of connector and script activities for troubleshooting purposes.
Critical errors will be logged to the Application log on the Synchronization Service server and additional tracing can be enabled by the administrator.
When a fatal error occurs while the PowerShell connector is running, or during the configuration of the connector in the Management Agent Designer, the Synchronization Service will log an event with the following details:
The Windows PowerShell connector can be configured to emit tracing information to any .NET TraceListener (e.g. event log, XML file, text file, etc.).
Administrators can also configure the connector to log information produced by the Write-Warning, Write-Verbose, and Write-Debug cmdlets to the trace log.
To enable tracing, follow these steps:
To trace information from Windows PowerShell scripts, you must complete two steps: