File List Export 2 4 0 M

Supports the use of VBA projects and Excel 4.0 macro sheets (.xlm). Excel 97-2003 Add-In.xla. The Excel 97-2003 Add-In, a supplemental program that is designed to run additional code. Supports the use of VBA projects. Excel 4.0 Workbook.xlw. An Excel 4.0 file format that saves only worksheets, chart sheets, and macro sheets. Version 2.1.0.0 (Internal Release): Added: Option to include or exclude the file information in the export; Added: Option to specify the maximum depth level for the export operation; Added: Option to export drive or network share size information; Added: -exp 'File PathName.xml;File Path1Name.fsp' - Export command line parameter.

To migrate an AD FS federation server that belongs to a single-node AD FS farm, a WIF farm, or a SQL Server farm to Windows Server 2012 R2, you must perform the following tasks:

Export and backup the AD FS configuration data

To export the AD FS configuration settings, perform the following procedures:

To export service settings

1. Make sure that you have access to the following certificates and their private keys in a .pfx file:

   • The SSL certificate that is used by the federation server farm that you want to migrate Xmind zen 9 1.

   • The service communication certificate (if it is different from the SSL certificate) that is used by the federation server farm that you want to migrate

   • All third-party party token-signing or token-encryption/decryption certificates that are used by the federation server farm that you want to migrate

To find the SSL certificate, open the Internet Information Services (IIS) management console, Select Default Web Site in the left pane, click Bindings… in the Action pane, find and select the https binding, click Edit, and then click View.

You must export the SSL certificate used by the federation service and its private key to a .pfx file. For more information, see Export the Private Key Portion of a Server Authentication Certificate.

Note

If you plan to deploy the Device Registration Service as part of running your AD FS in Windows Server 2012 R2, you must obtain a new SSL cert. For more information, see Enroll an SSL Certificate for AD FS and Configure a federation server with Device Registration Service.

To view the token signing, token decryption and service communication certificates that are used, run the following Windows PowerShell command to create a list of all certificates in use in a file:

1. Export AD FS federation service properties, such as the federation service name, federation service display name, and federation server identifier to a file.

To export federation service properties, open Windows PowerShell and run the following command:

The output file will contain the following important configuration values:

1. Back up the application configuration file. Among other settings, this file contains the policy database connection string.

To back up the application configuration file, you must manually copy the %programfiles%Active Directory Federation Services 2.0Microsoft.IdentityServer.Servicehost.exe.config file to a secure location on a backup server.

Note

Make note of the database connection string in this file, located immediately after 'policystore connectionstring='. If the connection string specifies a SQL Server database, the value is needed when restoring the original AD FS configuration on the federation server.

File List Export 2 4 0 Morristown And Erie

The following is an example of a WID connection string: 'Data Source=.pipemssql$microsoft##sseesqlquery;Initial Catalog=AdfsConfiguration;Integrated Security=True'. The following is an example of a SQL Server connection string: 'Data Source=databasehostname;Integrated Security=True'.

1. Record the identity of the AD FS federation service account and the password of this account.

To find the identity value, examine the Log On As column of AD FS 2.0 Windows Service in the Services console and manually record this value.

Note

File List Export 2 4 0 Morristown And Erie New York

For a stand-alone federation service, the built-in NETWORK SERVICE account is used. In this case, you do not need to have a password.

1. Export the list of enabled AD FS endpoints to a file.

To do this, open Windows PowerShell and run the following command:

1. Export any custom claim descriptions to a file.

To do this, open Windows PowerShell and run the following command: Iconfactory.

1. If you have custom settings such as useRelayStateForIdpInitiatedSignOn configured in the web.config file, ensure you back up the web.config file for reference. You can copy the file from the directory that is mapped to the virtual path '/adfs/ls' in IIS. By default, it is in the %systemdrive%inetpubadfsls directory.

To export claims provider trusts and relying party trusts

1. To export AD FS claims provider trusts and relying party trusts, you must log in as Administrator (however, not as the Domain Administrator) onto your federation server and run the following Windows PowerShell script that is located in the media/server_support/adfs folder of the Windows Server 2012 R2 installation CD: export-federationconfiguration.ps1.

Important

The export script takes the following parameters:

• Export-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-CertificatePassword ]

  • Export-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-CertificatePassword ] [-RelyingPartyTrustIdentifier ] [-ClaimsProviderTrustIdentifier ]
  • Export-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-CertificatePassword ] [-RelyingPartyTrustName ] [-ClaimsProviderTrustName ]

  -RelyingPartyTrustIdentifier - the cmdlet only exports relying party trusts whose identifiers are specified in the string array. The default is to export NONE of the relying party trusts. If none of RelyingPartyTrustIdentifier, ClaimsProviderTrustIdentifier, RelyingPartyTrustName, and ClaimsProviderTrustName is specified, the script will export all relying party trusts and claims provider trusts.

  -ClaimsProviderTrustIdentifier - the cmdlet only exports claims provider trusts whose identifiers are specified in the string array. The default is to export NONE of the claims provider trusts.

  -RelyingPartyTrustName - the cmdlet only exports relying party trusts whose names are specified in the string array. The default is to export NONE of the relying party trusts.

  -ClaimsProviderTrustName - the cmdlet only exports claims provider trusts whose names are specified in the string array. The default is to export NONE of the claims provider trusts.

  -Path - the path to a folder that will contain the exported files.

  -ComputerName - specifies the STS server host name. The default is the local computer. If you are migrating AD FS 2.0 or AD FS in Windows Server 2012 to AD FS in Windows Server 2012 R2, this is the host name of the legacy AD FS server.

  -Credential - specifies a user account that has permission to perform this action. The default is the current user.

  -Force – specifies to not prompt for user confirmation.

  -CertificatePassword - specifies a password for exporting AD FS certificates' private keys. If not specified, the script will prompt for a password if an AD FS certificate with private key needs to be exported.

  Inputs: None

  Outputs: string - this cmdlet returns the export folder path. You can pipe the returned object to Import-FederationConfiguration.

To back up custom attribute stores

1. You must manually export all custom attribute stores that you want to keep in your new AD FS farm in Windows Server 2012 R2.

Note

In Windows Server 2012 R2, AD FS requires custom attribute stores that are based on .NET Framework 4.0 or above. Follow the instructions in Microsoft .NET Framework 4.5 to install and setup .Net Framework 4.5.

You can find information about custom attribute stores in use by AD FS by running the following Windows PowerShell command:

The steps to upgrade or migrate custom attribute stores vary.

1. You must also manually export all .dll files of the custom attribute stores that you want to keep in your new AD FS farm in Windows Server 2012 R2. The steps to upgrade or migrate .dll files of custom attribute stores vary.

Create a Windows Server 2012 R2 federation server farm

1. Install the Windows Server 2012 R2 operating system on a computer that you want to function as a federation server and then add the AD FS server role. For more information, see Install the AD FS Role Service. Then configure your new federation service either through the Active Directory Federation Service Configuration Wizard or via Windows PowerShell. For more information, see 'Configure the first federation server in a new federation server farm' in Configure a Federation Server.

While completing this step, you must follow these instructions:

• You must have Domain Administrator privileges in order to configure your federation service.

• You must use the same federation service name (farm name) as was used in the AD FS 2.0 or AD FS in Windows Server 2012. If you do not use the same federation service name, the certificates that you backed up will not function in the Windows Server 2012 R2 federation service that you are trying to configure.

• Specify whether this is a WID or SQL Server federation server farm. If it is a SQL farm, specify the SQL Server database location and instance name.

• You must provide a pfx file containing the SSL server authentication certificate that you backed up as part of preparing for the AD FS migration process.

• You must specify the same service account identity that was used in the AD FS 2.0 or AD FS in Windows Server 2012 farm.

1. Once the initial node is configured, you can add additional nodes to your new farm. For more information, see 'Add a federation server to an existing federation server farm' in Configure a Federation Server.

Import the original configuration data into the Windows Server 2012 R2 AD FS farm

Now that you have an AD FS federation server farm running in Windows Server 2012 R2, you can import the original AD FS configuration data into it.

1. Import and configure other custom AD FS certificates, including externally enrolled token-signing and token- decryption/encryption certificates, and the service communication certificate if it is different from the SSL certificate.

In the AD FS management console, select Certificates. Verify the service communications, token-encryption/decryption, and token-signing certificates by checking each against the values you exported into the certificates.txt file while preparing for the migration.

To change the token-decrypting or token-signing certificates from the default self-signed certificates to external certificates, you must first disable the automatic certificate rollover feature that is enabled by default. To do this, you can use the following Windows PowerShell command:

1. Configure any custom AD FS service settings such as AutoCertificateRollover or SSO lifetime using the Set-AdfsProperties cmdlet.

2. To import AD FS relying party trusts and claims provider trusts, you must be logged in as Administrator (however, not as the Domain Administrator) onto your federation server and run the following Windows PowerShell script that is located in the supportadfs folder of the Windows Server 2012 R2 installation CD:

Important

The import script takes the following parameters:

• Import-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-LogPath ] [-CertificatePassword ]
• Import-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-LogPath ] [-CertificatePassword ] [-RelyingPartyTrustIdentifier ] [-ClaimsProviderTrustIdentifier
• Import-FederationConfiguration.ps1 -Path [-ComputerName ] [-Credential ] [-Force] [-LogPath ] [-CertificatePassword ] [-RelyingPartyTrustName ] [-ClaimsProviderTrustName ]

-RelyingPartyTrustIdentifier - the cmdlet only imports relying party trusts whose identifiers are specified in the string array. The default is to import NONE of the relying party trusts. If none of RelyingPartyTrustIdentifier, ClaimsProviderTrustIdentifier, RelyingPartyTrustName, and ClaimsProviderTrustName is specified, the script will import all relying party trusts and claims provider trusts.

-ClaimsProviderTrustIdentifier - the cmdlet only imports claims provider trusts whose identifiers are specified in the string array. The default is to import NONE of the claims provider trusts.

-RelyingPartyTrustName - the cmdlet only imports relying party trusts whose names are specified in the string array. The default is to import NONE of the relying party trusts.

-ClaimsProviderTrustName - the cmdlet only imports claims provider trusts whose names are specified in the string array. The default is to import NONE of the claims provider trusts.

-Path - the path to a folder that contains the configuration files to be imported.

-LogPath - the path to a folder that will contain the import log file. A log file named 'import.log' will be created in this folder.

-ComputerName - specifies host name of the STS server. The default is the local computer. If you are migrating AD FS 2.0 or AD FS in Windows Server 2012 to AD FS in Windows Server 2012 R2, this parameter should be set to the hostname of the legacy AD FS server.

-Credential - specifies a user account that has permission to perform this action. The default is the current user.

-Force – specifies to not prompt for user confirmation.

-CertificatePassword - specifies a password for importing AD FS certificates' private keys. If not specified, the script will prompt for a password if an AD FS certificate with private key needs to be imported.

Inputs: string - this command takes the import folder path as input. You can pipe Export-FederationConfiguration to this command.

Outputs: None.

Any trailing spaces in the WSFedEndpoint property of a relying party trust may cause the import script to error. In this case, manually remove the spaces from the file prior to import. For example, these entries cause errors:

They must be edited to:

Important

If you have any custom claim rules (rules other than the AD FS default rules) on the Active Directory claims provider trust in the source system, these will not be migrated by the scripts. This is because Windows Server 2012 R2 has new defaults. Any custom rules must be merged by adding them manually to the Active Directory claims provider trust in the new Windows Server 2012 R2 farm.

1. Configure all custom AD FS endpoint settings. In the AD FS Management console, select Endpoints. Check the enabled AD FS endpoints against the list of enabled AD FS endpoints that you exported to a file while preparing for the AD FS migration.

   - And -

   Configure any custom claim descriptions. In the AD FS Management console, select Claim Descriptions. Check the list of AD FS claim descriptions against the list of claim descriptions that you exported to a file while preparing for the AD FS migration. Add any custom claim descriptions included in your file but not included in the default list in AD FS. Note that Claim identifier in the management console maps to the ClaimType in the file.

2. Install and configure all backed up custom attribute stores. As an administrator, ensure any custom attribute store binaries are upgrade to .NET Framework 4.0 or higher before updating the AD FS configuration to point to them.

3. Cleanmymac x 4 4 5 x 8. Configure service properties that map to the legacy web.config file parameters.

   • If useRelayStateForIdpInitiatedSignOn was added to the web.config file in your AD FS 2.0 or AD FS in Windows Server 2012 farm, then you must configure the following service properties in your AD FS in Windows Server 2012 R2 farm:

     • AD FS in Windows Server 2012 R2 includes a %systemroot%ADFSMicrosoft.IdentityServer.Servicehost.exe.config file. Create an element with the same syntax as the web.config file element: . Include this element as part of section of the Microsoft.IdentityServer.Servicehost.exe.config file.

   • If was added to the web.config file in your AD FS 2.0 or AD FS in Windows Server 2012 farm, then you must configure the following service properties in your AD FS in Windows Server 2012 R2 farm:

     1. In AD FS in Windows Server 2012 R2, run the following Windows PowerShell command: Set-AdfsWebConfig –HRDCookieEnabled –HRDCookieLifetime.

   • If was added to the web.config file in your AD FS 2.0 or AD FS in Windows Server 2012 farm, you do not need to set any additional service properties in your AD FS in Windows Server 2012 R2 farm. Single sign-on is enabled by default in AD FS in Windows Server 2012 R2 farm.

   • If localAuthenticationTypes settings were added to the web.config file in your AD FS 2.0 or AD FS in Windows Server 2012 farm, then you must configure the following service properties in your AD FS in Windows Server 2012 R2 farm:

     • Integrated, Forms, TlsClient, Basic Transform list into equivalent AD FS in Windows Server 2012 R2 has global authentication policy settings to support both federation service and proxy authentication types. These settings can be configured in the AD FS in Management snap-in under the Authentication Policies.

   After you import the original configuration data, you can customize the AD FS sign in pages as needed. For more information, see Customizing the AD FS Sign-in Pages.

File List Export 2 4 0 Mac

Next Steps

Release note – Version 2.9.0.0

• [NEW] New 'resource editor' function (Settings menu) allow advanced users to personalize program configuration files. Usage of this feature requires a good knowledge of Log4OM.
• [NEW] FCC database support for STATE visualization in cluster data.
• [NEW] Log4OM joined the Off-Air Message Service, a new Ham Radio shared chat environment that joins Log4OM and GridTracker users. You can find it in the UTILITIES menu
• [NEW] downloaded eQSL's can now be viewed in QSO edit screen
• [NEW] Starting from this release we may release PUBLIC BETA versions to try and test new features before official release. You can subscribe to this opportunity by clicking on the 'Check for PUBLIC BETA updates' in SETTINGS -> PROGRAM SETTINGS. Public beta will be released through Log4OM website.
• You can now hide Statistics from F6 main UI tab via right menu button
• Removed DARC_DOK award from the list. Valid one is DLD
• Updated Clublog xmlns version to 1.3
• Updated predicted solar data function to read new JSON provided by NOAA Space Weather Prediction Center
• QSL Manager screen 'return key' will perform a search operation on current callsign value
• 2 more sounds added to the Alert/Chat notification options
• NET CONTROL: Added option to disable data lookup.
• NET CONTROL: Data manually inserted into callsign definition are no more overwritten by external lookup.
• NET CONTROL: Automatic country identification on new callsign definitions works without external lookup.
• LAZY LOG: New input keys for single QSO: name, comment, county and state
• Added support for user defined bandplan (added support for '_user' suffix)
• [FIX] Application deadlock during idle time should be fixed
• [FIX] CQ/ITU zone import from ADIF fixed when counterpart data are not available on search engines.
• [FIX] Award Confirmation import routine fix on date recognization
• [FIX] 000329: Saved filters don't work on re-load
• [FIX] 000325: Fixed POTA export from Award Stats