I did a search on BING and found some blogs that helped us resolve the issue. Sharing it on my blog if you are in a similar boat

http://blogs.technet.com/b/exchange/archive/2010/07/26/emc-and-certificates-with-failed-revocation-checks-in-exchange-2010.aspx

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/299c8ebe-223c-43ab-8cbc-c8221991813a

(There could be more so please share your comments )

Option1

1.            Create a text file with the alias of each Exchange 2003 mailbox that you want to move to Exchange 2010 per line saved as C:\Temp\ListOfExchange2003MailboxAlias.txt

2.            Put the following in a text file with a .ps1 extension for example Exchange2003MailboxMoveRequest.ps1

a.            Foreach ($Exchange2003Mailbox  in (Get-Content C:\Temp\ListOfExchange2003MailboxAlias.txt)) {New-MoveRequest -Identity $Exchange2003Mailbox -TargetDatabase ReplaceWithExchange2010MailboxDatabase}

3.            Use Task Scheduler to schedule the script to run at whatever time you want

Option2

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c1ea6f2c-5e37-4ab9-9dcc-c649be832e9c

Option 3

http://blogs.catapultsystems.com/tharrington/archive/2010/06/15/mailbox-migration-to-exchange-2010-powershell.aspx

For increasing parallel migrations

1. Configuration file change to increase parallel migrations - http://markswinkels.nl/2011/04/migrate-mailbox-from-exchange-2003-to-exchange-2010/

The following guided labs require Silverlight.

Guided Labs

Provide resources through self-service requests

This demo addresses creating and publishing new requests for cloud capacity resources in a service catalog and requesting new cloud resources with the service request form. (view as .wmv)

Drive consistent service delivery

This demo addresses showing a request being routed to the Virtual Machine Manager administrator for fulfillment, demonstrating integration to drive systems automation, and showing process management for delivery of service. (view as .wmv)

Provision additional cloud infrastructure

This demo addresses performing a bare-metal deployment of a Microsoft Hyper-V host, creating a new logical network and IP pool, and adding a new host to an existing cluster. (view as .wmv)

Delegate cloud resources

This demo addresses creating private cloud resources and creating and modifying a user role. (view as .wmv)

Create consistency through service templates

This demo addresses creating a virtual machine template, adding an application, and creating a service template with Service Designer, a component of Microsoft System Center 2012. (view as .wmv)

Perform a standardized application deployment to test

This demo addresses configuring a service deployment and deploying the service. (view as .wmv)

Stage application resources

This demo addresses using the App Controller component of Microsoft System Center 2012 to manage application resources. (view as .wmv)

Self-service deployment of an application to a production environment

This demo addresses deploying a new application and exploring dynamic, on-demand configuration options. (view as .wmv)

Gain insight and visibility through reporting

This demo addresses accessing reports in Service Manager and creating and sharing reports. (view as .wmv)

Monitor infrastructure

This demo addresses network monitoring and visualization and reporting. (view as .wmv)

Taking corrective actions in the infrastructure

This demo addresses seeing a holistic view of cloud and network health and performing an automated remediation. (view as .wmv)

Reduce time to resolution with application performance monitoring

This demo addresses configuring application performance monitoring, creating a dashboard, and gaining deeper application insight. (view as .wmv)

Deploy an update to service instance

This demo addresses modifying a service template and applying an in-place update. (view as .wmv)

Explore creating dashboards

This demo addresses creating private cloud resources and creating and modifying a user role. (view as .wmv)

“The user "domain\administrator" isn't assigned to any management roles."

To resolve this, I followed the steps -

1. First please check If you have "Allow inheritable permission..." checked for Microsoft Exchange Container and on Org Container ADSIEDIT.

Note: You can follow the steps below to find the settings.

1. Please try to start ADSIedit.

2. Navigate to "Configuration->Services->Microsoft Exchange"/"Configuration->Services->Microsoft Exchange->First Organization"

3. Righte click on it and select to "Properties".

3. Select "Security" tab.

4. Click "Advance". There please check if you have ticked "Allow inheritable permission" option.

2. Then please verified the attributes msExchRoleLink and msExchUserLink attributes on CN=Role Management-Organization Management-Delegating,CN=Role Assignments,CN=RBAC,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=….

The value should be "CN=Role Management,CN=Roles,CN=RBAC,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=…"

3.  Please check if "Role Mangement" exists under CN=Roles,CN=RBAC,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=…

4.  Also check if "Allow inheritable permission" ticked for "Role Management".

After that, please test the issue again.

If the issue still persists, then please follow the steps below to try to solve the problem

1) Open Windows PowerShell (not the Exchange Management Shell)
a. If you have UAC enabled, right click Windows PowerShell and click Run as
administrator.
2) Run Start-Transcript c:\RBAC.txt and press enter
a. This will start logging all commands and output you type to a text file.
3) Run Add-PSSnapin *setup and press enter
a. This adds the setup snap-in which contains the setup cmdlets used by Exchange
during install. You may see errors about loading a format data file. You can ignore
those errors.
DO NOT run any other cmdlets in this snap-in without direction from Microsoft.
Doing so could irreparably damage your Exchange installation.
4) Run Install-CannedRbacRoleAssignments -InvocationMode Install -Verbose and
press enter.
a. This cmdlet should create the required role assignments between the role groups
and roles that should have been created during setup.
b. Be sure you run with the Verbose switch so we can capture what the cmdlet
does.
5) Run Remove-PSSnapin *setup and press enter
6) Run $Session = New-PSSession -ConfigurationName Microsoft.Exchange
-ConnectionUri http://<FQDN of Exchange 2010 server>/PowerShell/ -Authentication
Kerberos and press enter
a. Be sure to replace <FQDN of Exchange 2010 server> with the FQDN of your
server.
7) Run Import-PSSession $Session and press enter
8) Run Get-ManagementRoleAssignment and press enter
9) Run Stop-Transcript and press enter

My new interface on the public domain. Keep visiting my site.

I had added the 3 SIP domains via topology builder, I was able to provision users with all 3 SIP domains and the users were able to sign-in via Lync Client.

Issue was with the  MEET URL’s.

Meet.a.com (which was the initially configured at the time of Lync deployment) was working both internally and externally.

For b.com and c.com – I had created A records pointing to the same IP. (same as meet.a.com) both internally and externally.

When I was trying to access meet.b.com internally – I was getting “404 – file or directory not found error. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable”.

Spoke to the internal folks and one of my colleagues suggested me a solution – sharing it so that if in case you have a similar scenario, you can leverage my blog.

Steps followed -

• Create a Meet URL per SIP domain, so meet.a.com and link it to a.com SIP domain, meet.b.com and link it to B.com sipdomain and same for C.
• Next, rerun the Lync deployment wizard (or bootstrapper) to configure these new Meet URLS in the URL Rewrite module. You would need to do this on all front-ends that are receiving these requests. The problem was with the URL rewrite module.

Once these steps were done, it started to work

Post these steps, I had to update the certs and apply the certs to the setup.

So, its all working now as desired

After some search on the MS KB’s / blog sites, I found a post wherein a similar issue was reported. I followed the following steps and it resolved the issue. Sharing the blog/steps with all so that in case you are stuck at a similar issue, you can follow the steps.

http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/0e69d9c4-62b7-445f-8c22-c8f50149e096/ 

1. From OperationsManager DB, run the following queries:

Select * from MT_ManagementGroup

(Column 6 contains the correct GUID)

And,

SELECT ManagementGroupId FROM __MOMManagementGroupInfo__

You will notice that the GUID which you have got from the first query will be different with the Second Query, but again to confirm that only (__MOMManagementGroupInfo__) is affected or not we have to run the following query on OperationsManagerDWDB

2. From OperationsManagerDW DB, run:

SELECT ManagementGroupGuid FROM vManagementGroup

3. Then also check the “web.config” file which is on the reportingserver directory (For SQL Server 2008, it can be found in C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer) for the following entry:

<appSettings>

<add key="ManagementGroupId" value="GUID" />

</appSettings>

This should confirm that the only GUID that is different is the one specified in the __MOMManagementGroupInfo__ table.

4. To resolve the issue, please perform the following steps to update this GUID in __MOMManagementGroupInfo__ to match the GUID from the vManagementGroup table.

1) Go to RMS. Stop Opsmgr SDK, Config and Health service.

2) Backup OperationsManager database. If possible, backup OperationsManagerDW database either.

3) Run the following SQL statement:

update __MOMManagementGroupInfo__ set ManagementGroupId = ‘GUIDNUMBER which you have got from ManagementGroupId’

4) Start Opsmgr SDK, Config and Health service.

I got stuck at an issue wherein the Remote User was not able to sign-in.

• The clients that the customer had XP clients and the user was getting “Lync was unable to sign in error”.

• Lync Server 2010 was deployed on Windows 2008 R2 and the DC’s are also Windows 2008 R2.

Capturing the SIPstack from the logging tool at edge – setting all flags and all levels clicked on analyse.

" There is a mismatch between NTLM security settings on client and server computers.”

After some research I found a KB and the blog link that talks about the similar issue.

Referring point8 in the KB

Default Domain Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network security: Minumum session security for NTLM SSP based (including secure RPC) clients

Default Domain Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network security: Minumum session security for NTLM SSP based (including secure RPC) servers

this step requires the Default Domain Policy from Not Configured to be Configured with the "Require 128-bit encryption" unchecked.

Did this in the local secpolicy at the Edge, FE and applied the above group policy settings on DC and wallaaahhh ..it started to work

I had done a POC for MS VDI for a partner in the past and this has again come up for another POC :) so I am going to re-use what I did sometime back.   I am happy :)

If you have a smiliar requirement, may be this can help you too

 Refer the Team blog article for Role HA options

http://blogs.msdn.com/b/rds/archive/2010/03/01/microsoft-vdi-high-availability-deployment-options.aspx

Key Microsoft role services that should be made highly available

1. Remote Desktop Session Host (RD Session Host) in redirection mode
2. Remote Desktop Connection Broker (RD Connection Broker)
3. Remote Desktop Virtualization Host (RD Virtualization Host)
4. Remote Desktop Web Access (RD Web Access)
5. Remote Desktop Licensing (RD Licensing) and Remote Desktop Gateway (RD Gateway)

High availability options for each role service

1. RD Session Host in redirection mode

A high availability solution for the RD Session Host server consists of high availability of the hardware, as well as high availability of the Remote Desktop Session Host role service.  You can use multiple RD Session Host servers and round robin DNS to provide high availability at both levels. High availability is obtained by virtue of the Remote Desktop Protocol (RDP) client trying all the IP addresses returned by the DNS server. All the RD Session Host servers should be running in active-active mode.

2. RD Connection Broker

Similar to RD Session Host, the RD Connection Broker role service can be made highly available at both the hardware and the service level by clustering multiple servers running the RD Connection Broker role service. Failover clustering guarantees that in the event of hardware or software (service) failure on the active node, a failover is triggered. In other words, a new active node would be selected at that time.  A step-by-step guide about how to configure an RD Connection Broker server in active-passive mode for high availability will be available soon on TechNet.

3. RD Virtualization Host

The Microsoft VDI solution supports highly available Hyper-V virtual machines. Setting up a failover cluster environment with multiple Hyper-V hosts will ensure that in the event of a hardware failure on a Hyper-V host, the virtual machines will fail over to another Hyper-V host and automatically start. If the Remote Desktop Virtualization Host Agent service fails, this service is configured to restart automatically. Thus all the Hyper-V virtual machines would be available all the time.

4. RD Web Access

High availability of the RD Web Access role service is achieved by deploying it in an active-active mode. Multiple RD Web Access servers can be configured as part of a Network Load Balancing (NLB) cluster to achieve this. You could also use round robin DNS in place of an NLB cluster to make the RD Web Access role service highly available.

5. RD Licensing and RD Gateway

For high availability of RD Licensing and RD Gateway, see the following:

· Deploying Remote Desktop Licensing Step-by-Step Guide (http://technet.microsoft.com/en-us/library/dd983943(WS.10).aspx)

· Improving TS Gateway availability using NLB (http://blogs.msdn.com/rds/archive/2009/03/24/improving-ts-gateway-availability-using-nlb.aspx)

Unsupported high availability deployment configurations

There are two deployment configurations that are not supported:

1. Clustering RD Connection Broker servers on RD Virtualization Host servers.
2. An active-active RD Connection Broker installation.