It can be caused by several issues. So this is what you should check, and possibly solve it.

Solution 1

Rename your Plugins folder and check if you can access admin menu, if issue has been caused by plugin you will be able to access.
Than try to isolate the plugin, by disabling them one by one.

Solution 2

Rename your original wp-admin and wp-include folders, Upload a new ones from fresh WordPress installation via FTP.

Solution 3.

Rename your functiuions.php filie wihich is usualy located under your current theme.
Sometimes WP-Admin get’s stuck because of a line in this file.

First option is to use HP recovery tools and try to use recovery/repair CD
Using this option you are in risk to lose your data-Not Good.

Other option is try using some other administrative account. I was able to login with local administrative account , also you can use domain admin.

From logs I found that what is causing the issue is the HP software installed on laptop . I removed all HP ProtectTools related SW.

To be more specific

• Device Access Manger for HP ProtectTools
• Privacy Manager for HP ProtectTools
• Drive Encryption for HP ProtectTools

After reboot you will be able to login with your account.

I read about third option.
You can also login in safe mode and reset user password.

In Order to disable automatic mapping:

1. Go to this user mailbox, right click on it and choose manage full mailbox access, then just remove your user from the full mailbox access page
2. You can use ADSIEDIT, and go this user properties, and under msExchDelegateListLink attribute, just remove the link to your user
3. You can use the following script for future mailbox permissions – this will add full mailbox access with no AutoMapping.
4. You can remove msExchDelegateListLink values from multiple users properties using ADModify.net

In order to find all users that have Full Mailbox Access on other users’ mailbox, run the following powershell:

Get-Mailbox -ResultSize Unlimited | Get-MailboxPermission | ? {($_.AccessRights -match "FullAccess") -and -not ($_.User -like "NT AUTHORITYSELF")} | ft Identity, User

Exchange 2010 allows us to use power shell for assigning calendar permissions. You can add Reviewer, Editor and all other permission types remotely without moving from your chair.

To assign Calendar Editor permission use the following command:

Set-MailboxFolderPermission -Identity Granter_Username:Calendar -User ‘Granted_username’ -AccessRights Editor

You can review calendar permissions with following PS command

Get-MailboxFolderPermission -Identity Granter_Username:calendar

You can use the same PS command to provide all available access rights.
Just replace the attribute after -AccessRights

Here is a list of folder permissions in Exchange 2010

If your favorites bar in outlook is missing from any reason you can return it by simple step.

• Close your outlook .
• Navigate to Start>run
• Type outlook.exe /resetnavpane

Your favorites bar will be restored but you will need to re-add your folders again.

In BES 4.1 there was an option to remotely wipe BlackBerry devices.

In BES 5 it exists to , but you need to dig little bit to find it.

It is located under:
BlackBerry solution management > User > Search for required user> Click the users PIN number> at the bottom of the page press on  “Delete all device data and disable device”

Windows 2008 has built in policy GPO for wireless setting management.
You can configure your network setting using Certificates. It is the most recommended and secure way
But if you like to deploy the wireless settings using static key, you will have to use other way.

The steps bellow describe the way to deploy Wireless LAN settings with a Pre-Shared Key
The purpose is to Automate Adding Wireless Profile in Windows.

Preparations

• Configure Wireless settings on one workstation
• from command prompt run
  netsh wlan export profile name="NameOfyourProfile" folder=c:temp interface="wirelesssettings”
• Confirm that under c:temp you have wirelesssettings.xml file
• Open wirelesssettings.xml file locate the following line
  <protected>true</protected>
• Change it to <protected>false</protected>
• Under you will see encrypted line <keyMaterial>01000000D08C9DDF0115D1118</keyMaterial>
• Change it to your key like that <keyMaterial>Yourkey</keyMaterial>
  

  Note: It means that your wireless key will be in clear text and everyone who has access to the file will be able to read your wireless key"

Deployment

• Copy your wireless settings xml file to NETLOGON
• Create a bat or cmd file with the following line
  netsh wlan add profile filename="\yourserverNETLOGONwirelesssettings.xml" user=all
• Run the bat file from some domain member computer and confirm that it works

After finishing all steps above you can deploy the script from GPO

Note: Setting are applicable for Windows Vista Windows 7 and Windows 2008 Only

You may face this error while user is sending email from outside the company  to distribution group in your Exchange 2010 organization.
You can’t send it either from internet internal mail relay or SMTP server When review logs you see "550 5.1.1 User unknown" error .

it works fine with no issues If you use Outlook or OWA

Why: When you create new Distribution group In Exchange 2010 an Require that all senders are authenticated has been marked by default.So unauthenticated users are unable to send emails to distribution groups.

To fix this:

• Double click on Distribution Group name in EMC locate the Mail Flow Settings tab
• Press on Message Delivery Restrictions

• Uncheck the Require that all senders are authenticated

Please note that it will allow external users to send emails to internal distribution groups . It is not recommended to set the setting to “All company” and other large mailing lists

While performing maintenance to Exchange 2010 DAG server you should first remove the DAG member from DAG group.Other wise you may have unwanted DB failovers and many other unexpected issue that may affect company mail services availability

Shutting Down DAG Members

The Exchange 2010 high availability solution is integrated with the Windows shutdown process. If an administrator or application initiates a shutdown of a Windows server in a DAG that has a mounted database that’s replicated to one or more DAG members, the system attempts to activate another copy of the mounted database prior to allowing the shutdown process to complete.

However, this new behavior doesn’t guarantee that all of the databases on the server being shut down will experience a lossless activation. As a result, it’s a best practice to perform a server switchover prior to shutting down a server that’s a member of a DAG.

The correct way to perform any maintenance is to run first  StartDagServerMaintenance.ps1 script that is located under “C:Program FilesMicrosoftExchange ServerV14scripts”
This script moves all the active databases to next preferred DAG server and prevents active databases from moving to that server during the maintenance.
In addition the script ensures that all critical DAG support functionality that may be on this server has been moved to next proffered server

To run the script open EMC
Type:
cd $exscripts
StartDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Suspend-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Pauses the node in the cluster, which prevents the node from being and becoming the PAM.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to blocked
• Moves all active databases currently hosted on the DAG member to other DAG members.
• If the DAG member currently owns the default cluster group, the script moves the default cluster group (and therefore the PAM role) to another DAG member.

If any of the preceding tasks fails, all operations, except for successful database moves, are undone.

After the maintenance is complete and the DAG member is ready to return to serve clients you need to run the following script:

cd $exscripts
StopDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Resume-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Resumes the node in the cluster, which enables full cluster functionality for the DAG member.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to Unrestricted

I highly recommend using  Start/StopDagServerMaintenanceInstalling maintainance scripts before any action that requiers server Reboot/ShutDown or Update Rollups instalation.

Most of the material has been taken from Managing Database Availability Groups MS article

Get Quota report
Get-Mailbox | Format-Table alias, *quota

Delete message from Mailbox
get-mailbox -resultsize unlimited | search-mailbox -SearchQuery “Subject:ABDCEV’” -DeleteContent

Turn Off firewall on all profiles
netsh advfirewall set allprofiles firewallpolicy allowinbound,allowoutbound

Exchange 2007 – check DB copy status.
Get-StorageGroupCopyStatus -StandbyMachine mtvmail01

Message Tracking log to csv (| Select Sender, Recipients, TimeStamp, MessageSubject)
Get-MessageTrackingLog -Server servername-ResultSize Unlimited | Where { $_.Sender -like “username*” } | Export-CSV “c:username.csv”

Put Exchange DAG cluster member to Maintainance
cd $exscripts
StartDagServerMaintenance.ps1 -server servername

Get Exchange DAG cluster member from Mainatainance

cd $exscripts
StopDagServerMaintenance.ps1 -server servername

Set Distribution group owner
Set-DistributionGroup groupname -ManagedBy “User Name” -BypassSecurityGroupManagerCheck

Access rights to all mailboxes in DB or All
Get-Mailbox | Add-MailboxPermission -User “Username” -AccessRights FullAccess -InheritanceType All
Get-MailboxDatabase –identity “DBNAME” | Add-ADPermission -User “UserName” -AccessRights GenericAll

Move Mailbox
New-MoveRequest -Identity user@mail.com -TargetDatabase DBNAME -BadItemLimit 100 -AcceptLargeDataLoss

Add permition to send as
Add-ADpermission -Identity “DatabaseName” -user “username”  -ExtendedRights Receive-as