Best Practice Analyzer for Forefront Identity Manager 2010 R2

In Forefront Identity Manager 2010 R2 management, best practices are guidelines that are considered the ideal way, under normal circumstances, to configure a server as defined by experts. While best practice violations, even critical ones, are not necessarily problematic, they indicate server configurations that can result in poor performance, poor reliability, unexpected conflicts, increased security risks, or other potential problems.

Topics in this section can help you bring FIM 2010 R2 running on Windows Server® 2008 R2 into compliance with best practices. Content in this section is most valuable to administrators who have completed a Best Practices Analyzer scan of FIM 2010 R2, and who want information about how to interpret and resolve scan results that identify areas of FIM 2010 R2 that are noncompliant with best practices.

For more information about Best Practices Analyzer and scans, see Best Practices Analyzer.

FIM 2010 R2 BPA Pre-requisite Software

The Forefront Identity Manager 2010 R2 Best Practice Analyzer requires the Microsoft Baseline Configuration Analyzer 2.0 or later before it can be installed and run. The Microsoft Baseline Configuration Analyzer 2.0 (MBCA 2.0) can help you maintain optimal system configuration by analyzing configurations of your computers against a predefined set of best practices, and reporting results of the analyses. Best practices are developed by a product development team or domain experts, and are packaged in the form of a best practice model.You can download the Microsoft Baseline Configuration Analyzer 2.0 here (http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=16475).

FIM 2010 R2 BPA Pre-requisite Tasks

In order to use the FIM 2010 R2 BPA you must ensure that Windows PowerShell Remoting is enabled on the server or servers that you wish to run the Best Practice Analyzer against. For more information on Windows PowerShell Remoting see Enable-PSRemoting.

FIM 2010 R2 BPA Installation

To install the FIM 2010 R2 BPA use the following procedure.

To install the FIM 2010 R2 BPA

1. Open a command prompt with elevated permissions, navigate to the directory that contains the FIM2010R2BPA.msi and enter the following:
   msiexec /i FIM2010R2BPA.msi /l*v c:\FIMBPALOG.txt
   

   This will start the installation wizard and creates a log file in case there are any issues with the installation.
2. On the welcome screen click next.
   
3. On the EULA screen, read the EULA and if you accept place a check in the I accept the terms in the License Agreement checkbox and click Next.
4. On the Ready to Install screen click Install.
5. Once the installation has finished, click Finish.

Using the FIM 2010 R2 BPA

To start the FIM 2010 R2 BPA use the following procedure:

Using the FIM 2010 R2 BPA

1. Click start, select All Programs, and select Microsoft Baseline Configuration Analyzer 2.0. This will bring up the Microsoft Baseline Configuration Analyzer 2.0.
2. In the drop-down under Select a product, select Forefront Identity Manager 2010 R2 BPA.
   
3. Click Start Scan.
   
4. Once the scan has completed any Non-compliant rules will appear under the Noncompliant tab. Under the All tab you can view all of the Compliant rules.
   
5. You can also view the data that was collected by selecting the Collected Data radio button.
   
6. At this point you can export the report to XML.

FIM 2010 R2 BPA Parameters

The following table is a list of parameters that can be set when using the FIM 2010 R2 BPA.

Name	Description
Alternate_Server_to_Scan	The server that you want to run the scan against. You can use either the NetBios or the FQDN of the server. Example: APP1 or app1.corp.contoso.com.
Database_Name_For_Database_Scan	The name of the database you wish to scan. This can be left blank and you can simply enable Analyze_FIM_Service_Database and Analyze_FIM_Sync_Service_Database.
SQL_Server_Instance_Name_For_Database_Scan	The name of the SQL instance that the databases are running under. If nothing is specified then the default instance will be used.
Analyze_FIM_Service	Compares the current environment with the best practices for the FIM Service. To enable this select the checkbox.
Analyze_FIM_Service_Database	Compares the current environment with the best practices for the FIM Service Database. To enable this select the checkbox.
Analyze_FIM_Sync_Service	Compares the current environment with the best practices for the FIM Sync Service. To enable this select the checkbox.
Analyze_FIM_Sync_Service_Database	Compares the current environment with the best practices for the FIM Sync Service Database. To enable this select the checkbox.
Analyze_FIM_Certificate_Management	Compares the current environment with the best practices for the FIM Certificate Management. To enable this select the checkbox.
Analyze_BHOLD	Compares the current environment with the best practices for BHOLD. To enable this select the checkbox.

More information about Forefront Identity Manager 2010 R2

Common identity is an important tool in ensuring your users have appropriate access to corporate information. Without an efficient method of establishing and maintaining a common identity across complex heterogeneous systems, significant challenges arise. These can include high help-desk costs for password resets and smart card deployment, loss of productivity as users struggle to access the resources they need, and serious risk to the business due to noncompliance with internal and external regulations.

Microsoft Forefront Identity Manager (FIM) 2010 R2 helps you resolve these issues by providing self-service identity management for your users, automated lifecycle management across heterogeneous platforms for your administrators, and a rich policy framework for enforcing corporate security policies and detailed audit capabilities.

FIM 2010 R2 integrates new functionality through the Microsoft BHOLD suite to provide role-based access control and allow administrators to review access rights continually across the organization. The FIM 2010 R2 release also adds an improved self-service password reset experience, along with performance, diagnostic, and reporting improvements.

For more information about FIM 2010 R2, see Forefront Identity Manager 2010 R2.

Product Category for System Center in WSUS

New product family to your WSUS server today – System Center. The System Center product family will contain updates for versions 2012 and higher of System Center products, which include System Center 2012, a product that combines components such as:

• Operations Manager
• Configuration Manager
• Data Protection Manager
• Service Manager
• Virtual Machine Manager
• Endpoint Protection
• Orchestrator
• App Controller

The System Center product family will allow a variety of update types, e.g. service packs, optional updates, critical updates, and security updates. System Center updates will also be available in the Microsoft Update Catalog at http://catalog.update.microsoft.com.

You will see new product categories appear under the System Center product family as new updates are available for each product or product component. The first product category to be added will be System Center Advisor. For additional information about System Center Advisor, see http://www.SystemCenterAdvisor.com/.

We encourage you to synchronize the System Center product family if you are planning to deploy System Center 2012, either through upgrades or new licenses, or if you already have System Center 2012 products in your managed environment. For additional information about System Center 2012, see http://www.microsoft.com/en-us/server-cloud/system-center/default.aspx.

Error installing SCCM MP Point in domain controller...

 

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISADMIN

3. In the right pane, right-click DependOnService, and then click Modify.

4. In the Edit Multi-String dialog box, type Netlogon in the Value data box, and then press ENTER.

5. In the Value data box, type DNS, and then press ENTER. The contents of the Value data box appear as follows:

RPCSS
SamSS
Netlogon
DNS

6. Click OK, and then exit Registry Editor.

Active Directory Health Checks for Domain Controllers

 

The Event Viewer is always a must to checked.

Dcdiag.exe /v >> c:\temp\pre_dcdiag.txt
Will tell you if there is trouble with your DCs and/or services associated with it .

Netdiag.exe /v >> c:\temp\pre_Netdiag.txt
This will let me know if there are issues with the networking components on the DC. 

Netsh dhcp show server >> c:\temp\pre_dhcp.txt
This allows to verify the server count and names.

Repadmin /showreps >> c:\temp\pre_rep_partners.txt
This shows all replication and if it was successful or not. 

repadmin /replsum /errorsonly >> c:\temp\pre_repadmin_err.txt
This is the one that always takes forever but will let you know who you are having issues replicating with.

SCCM Task Sequence fails

 

The execution of the group (Capture Files and Settings) has failed and the execution has been aborted. An action failed.

Remove KB974571 and advertise the task Sequence again..

Hyper-V: Using Hyper-V and Failover Clustering

 

http://technet.microsoft.com/en-us/library/cc732181(WS.10).aspx

Restoring Single Mail in Exchange 2007 using Microsoft DPM 2010 Beta

 

Restoring Single Mail in Exchange 2007 using Microsoft DPM 2010 Beta

v Create Recovery Storage Group

Open the Exchange MMC go to toolbox, Database Recovery management & enter the Label ,Exchange name & domain.

Select Create a recovery Storage Group.

Then Link it with the Existing Group.

Name the recovery storage group and verify the location of the exchange data and logs.

Click Create the RSG…

Go to the DPM 2010 Server open the DPM 2010 MMC & to the Recovery Tab, then select the early a back up ( not the Latest).

Then select the Mail box you want to Restore Rite click then select Restore will get the below Review Window. & Click next..

Select the Recovery Type.

You need to Specify the Destination the Exchange sever name, Storage, & the DB name.

Then you get the Recovery Option u can modify or level it …

And the Summary page will appear then click recover it will start to recover the mailbox.

If it is Successful u will get a status message like below

The recovery storage group will not show up in the exchange MMC , then only way to see it via the Shell with the

command( get-storageGroup -server exchange)

Mount the Recovered Database

You will find it already mounted

Then merge the database

Then Click Gather Information .

In this step we need to Specify the single mail that we need to Restore ( in this case i have put my subject of the mail Hi to you)

Then the restore will start & finish

Then log in to the mail and check you will see your lost mail restored.

After restoring you need to remove the RSG.

Select the Database and dismount it

Then click Remove RSG

And delete the folder that is created by the RSG.

Enjoy Dpm2010