Exchange 2013 New-MailboxRestoreRequest :: The term 'New-MaiboxRestoreRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Issue : From Exchange management Shell, Running command is providing this error

New-MailboxRestoreRequest –SourceDatabase <Source-Database> -SourceStoreMailbox <Disconnected-Mailbox> -TargetMailbox <Destination-Mailbox> -TargetRootFolder <Folder-in-Destination-Mailbox> -AllowLegacyDNMismatch

New-MaiboxRestoreRequest : The term 'New-MaiboxRestoreRequest' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ New-MaiboxRestoreRequest -SourceDatabase "recovery" -SourceStoreMailbox "dd ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : ObjectNotFound: (New-MaiboxRestoreRequest:String) [], CommandNotFoundException
   + FullyQualifiedErrorId : CommandNotFoundException 


Resolution: Open EMS in Administrator mode and run the command again

 -AllowLegacyDNMismatch : this switch will allow to restore Database into different location from the original

To receive GUID for the user

Get-MailboxStatistics –Database recoveryDatabase | ft DisplayName,MailboxGUID,DisconnectReason –AutoSize

Get-MailboxRestoreRequest //This command can helpus to check with restore status

Create Recovery Database

New-MailboxDatabase -Recovery -Name RDB1 -Server MBX2

New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath "C:\Recovery\RDB2\RDB2.EDB" -LogFolderPath "C:\Recovery\RDB2"

Get-MailboxDatabase <RecoveryDatabaseName> | Format-List
New-MailboxRestoreRequest -SourceDatabase DB1 -SourceStoreMailbox 1d20855f-fd54-4681-98e6-e249f7326ddd -TargetMailbox Morris

Get-MailboxRestoreRequest -Status Completed | Remove-MailboxRestoreRequest

LDP from Exchange Command Prompt

Get-Mailbox mb1 | % { dsquery * $($_.DistinguishedName) - attr * }

Eg:
get-mailbox "zena.james" | % {dsquery * $($_.distinguishedName) -attr *} 

Where MB1 is the alias of the Mailbox user

LDP > Connection "FQDN of DC" >> Bind > Tree "Ok" > Search the Object >> Goto the Connection > Click new >> and then click again on the Object > Output is on the right side

Exchange 2010/ Outlook 2010 "One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server"

Environment
Exchange 2010
Outlook 2010

Issue:
Users has been migrated from Exchange 2003 to Exchange 2010 and now few users are reporting that they are unable to share Calendar with the other users. 

While Adding users from GAL it shows RED Mark on the user and 
they are receiving following error

 "One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server"

Resolution : 

Convert the Mailbox Type to Regular, 

Set-Mailbox Useralias -type Regular

You can check the status from the following command

Get-Mailbox UserAlias | FL *type*

Still not resolved, then opend ASIEDIT.msc, > Domain Configuration > User Properties and find Attribute 

MxchRecipientDisplayType : 1073741824

MxchRecipientTypeDetail  : 1

In my Case MxchRecipientDisplayType value was set to '0' and changing to 1073741824 resolves the issue.

More information from the blog:

http://blogs.technet.com/b/benw/archive/2007/04/05/exchange-2007-and-recipient-type-details.aspx

Outlook Calendar checking tool version 2.4

"Calendar sharing is not available with the following entries because of permission settings on your network' Exchange 2010

Environment: 

Exchange 2010, Outlook 2010

Issue: 

Users are unable to share the Calendar and receiving the message from Outlook and OWA

Resolution : This could be due to the Cached User name, Try renaming the .PK2 file and restart outlook or Use GAL to select the contact and then share the Calendar.

Outlook Credentials Management

Outlook Credential Manager from Command Prompt

rundll32.exe keymgr.dll, KRShowKeyMgr


Alternatively Go to control panel, User Accounts, manage your credentials, and delete any outlook entries under "Generic Credentials"

Close outlook and reopen. That solved our problem

In Lab, Windows server 2008 R2 are unable to communicate with each other

Issue : 
In my Hyper-v Lab, two machines are unable to communicate with each other.
Ping to destination IP show "Request timed Out" and when reboots ping shows "Destination host unreachable", which indicates the connection is being refused from the destination server.

Resolution : 
Properties of "Windows Firewall with Advanced Security on Local Computer" > Domain Profile Tab > Firewall State "On" and changed the Options "Inbound Connections" Block (default) to Allow.

this option is useful when you don't want to disable the firewall, alternatively you can make rules to enable the Inbound traffic from other server

VSSAdmin DNPublish

for System 
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
  For volume: (C:)\\?\Volume{1f579c24-a50d-11dd-83df-xxxxxxxxxxxxx}\
  Shadow Copy Storage volume: (C:)\\?\Volume{1f579c24-a50d-11dd-83df-xxxxxxxxxxxxx}\
  Used Shadow Copy Storage space: 47.256 GB
  Allocated Shadow Copy Storage space: 49.405 GB
  Maximum Shadow Copy Storage space: 50 GB

c:\>vssadmin list shadows 
This will provide more information about what program is using the shadow storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
For Exchange 
Issue: Backup is taking long time to complete or Inconsistent

1. Troubleshooting steps
vssadmin list writers

2. In Application Log, Related Event with Backup 
Event Id : 3156 

3. Increase the Diagnostic logging for "Exchange Writer"

Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level Expert

To revert the Changes 

Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level Lowest

and 
Set-EventLogLevel "MSExchangeIS\9002 System\Backup Restore" -level Expert
Set-EventLogLevel "MSExchange Repl\Service" -level Expert



4. Restart the "Microsoft Exchange Server Extension for Windows Server Backup" service