“Error:
Active Directory operation failed on DC.domain.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

The user has insufficient access rights.”

Resolution

To resolve this we had to do the following

1, Open Active Directory Users and Computers and View advanced features

2, Find the user account for the mailbox with the issue and go to the properties of this account

3, Go to the security tab and hit advanced

4, Now check the box that says include inheritable permission and apply this setting

5, Now when you set the send as permission and all works

“Completed

Exchange Management Shell command completed:
Add-ADPermission -Identity ‘CN=User,OU=Users OU,DC=Domain=DC=com’ -User ‘Domain\User1′ -ExtendedRights ‘Send-as’

Elapsed Time: 00:00:00”

msra.exe /offerRA HOSTNAME

or

msra.exe /offerRA IP Address

If you get the following message:

You need to ensure that you are running the command as a user that is a member of the local group “Offer Remote Assistance Helpers”:

Cheers

Paul

Please see the command below on how to do this (In this example the user is test@test.com and he would like the secondary email address to be test1@risual.com)

Run the below from the Exchange management shell.

Set-Mailbox test@test.com -EmailAddresses @{add="test1@test.com"}

Once we reinstalled the x86 version we were unable to run the CRM Configuration wizard and if we opened outlook the CRM add-in appeared to be there but was not functional at all.

Resolution

To fix this we did the following

1, Uninstall the CRM 2011 Client

2,Open Registry Editor

3, Delete the following key “HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient

4, Re-install CRM Client and it all works

When running logging in TMG we could see the RDP server hitting the server but then immediately getting a closed connection with the following message “A connection was abortively closed after one of the peers sent an RST packet”

Resolution

1.  First Log onto your TMG Server

2. Right-click the highlighted icon and choose “Open Network and Sharing Center”

3. If you then choose “Change Adapter Settings”

4. If you know right click the Adapter for you Internal Network named LAN and press properties and make note of the name of the adapter.

5. If we now go to START > Administrative Tools > Remote Desktop Services > Remote Desktop Host Configuration

6. You Should see a connection named RDP-Tcp if you select this and then Disable and Re-enable the connection

7. If you know right click the connection named RDP-Tcp and choose properties

8. If you then navigate to the Network Adapter tab and choose the Internal Network adapter we found out in Step 4 and choose ok

9. If you then disable and re-enable the connection again

After this all worked again even after a reboot

Solution:

Navigate to the following in the registry:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Default

Look through each of the folders, and delete the folder that correspond to the additional mailbox(es) causing an issue.

You can download the rollup from http://www.microsoft.com/download/en/details.aspx?id=28751

Rollup 6  contains the following fixes (Referenced from http://support.microsoft.com/?kbid=2608656)

• 2289607 - The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment
• 2498852 - "0×80041606" error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment
• 2499841 - An arrow icon does not appear after you change the email message subject by using OWA in an Exchange Server 2007 SP3 environment
• 2523695 – A "System.ArgumentOutOfRangeException" exception occurs when you click the "Scheduling Assistant" tab in Exchange Server 2007 OWA
• 2545080 - Users in a source forest cannot view the free/busy information of mailboxes in a target forest when the cross-forest Availability service is configured between two Exchange Server 2007 forests
• 2571391 – Applications or services that depend on the Remote Registry service may stop working in an Exchange Server 2007 environment
• 2572010 – The Microsoft Exchange Information Store service may crash after you run the Test-ExchangeSearch cmdlet in an Exchange Server 2007 environment
• 2575360  – A new feature is available to automatically stop the Microsoft Exchange Information Store service when a time-out is detected in an Exchange Server 2007 SP3 environment
• 2591655 – A journaling report remains in the submission queue when an email message is delivered successfully in an Exchange Server 2007 environment
• 2598980 – The PidLidClipEnd property of a recurring meeting request has an incorrect value in an Exchange Server 2007 environment
• 2616427 – An Outlook Anywhere client loses connection when a GC server restarts in an Exchange Server 2007 environment
• 2617784 – Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment
• 2626217 – Certain changes to address lists may not be updated in an Exchange Server 2007 environment
• 2629790 – The Exchange IMAP4 service may stop responding on an Exchange Server 2007 Client Access server when users access mailboxes that are hosted on Exchange Server 2003 servers
• 2633801 – The SCOM 2007 SP1 server cannot alert certain issues in an Exchange Server 2007 organization
• 914533 – The Microsoft Exchange Information Store service may stop responding on an Exchange Server 2007 server
• 976977 – The scroll bar does not work in OWA when there are more than 22 all-day event calendar items in an Exchange Server 2007 user’s calendar
• 2641312 – The update tracking information option does not work in an Exchange Server 2007 environment
• 2653334 – The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment
• 2656040 – An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes
• 2658613 – The "PidLidClipEnd" property of a no ending recurring meeting request is set to an incorrect value in an Exchange Server 2007 environment

Solution

Remove the Microsoft_OC1:uri=username@domain.com:specific:EWS1 entry from Credential Manager (Windows Vault)

Working Previous version on file share

Failing Previous versions on the same file share

To resolve this issue we had to do the following

• First log on your DPM 2010 server
• Open Server Manger
• Expand Roles > File Services
• Choose Share and Storage management
• Navigate to the Shares tab
• Now right click the share thats shows no recovery points and choose Stop Sharing

Now we’ve removed the share from DPM we will need to do some changes in AD via ADSI Edit.

The first thing we need to do is find the canonical name of the share, so if you open command prompt on a server with AD tools and Asdiedit installed such as a DC and run the following command.

Change the below in Bold to match your domain

dsquery * cn=ms-sharemapconfiguration,cn=system,dc=Domain, dc=com –attr ms-productionSrvShare cn -limit 1000 > C:\shares.txt

Once you have run the above command open the shares.txt file on the C drive that would of been outputted

Example of outputted file

ms-productionSrvShare                                                            cn                                   
                                                                                                            MS-ShareMapConfiguration             
\\Server\Share                                                                            def225c9-0816-4192-bcea-46f1fb71f5b6

Now open ADSIEDIT but keep the shares.txt file open so we can refer to it

• Open ADSIEDIT
• Expand Domain
• Expand DC=Domain, DC=com
• Expand CN=System
• Now select CN=MS-ShareMapConfiguration
• Now we need to refer back to our shares.txt file to find the CN name of the share we need to fix the previous versions for
• now delete the object that matches the CN file from the shares.txt file

Once that has been done wait for your AD to replicate or force replication.

Now you need to modify the protection group that is backing up the file share in question.

• Exclude the folder with the issue with previous versions from the backup and update the protection group and wait for consistency check to complete
• Re-add the folder we just excluded and update the protection group again

Wait for the consistency check to complete and then previous versions should be working again

Exam 70-323: Administering Office 365 intended for IT professionals who administer Microsoft Office 365 in an environment that may include Microsoft Exchange, Microsoft Lync, and/or Microsoft SharePoint – link . Once passed you will be awarded with Microsoft Certified Technology Specialist (MCTS): Administering Office 365.

AND

Exam 70-321: Deploying Office 365 intended for consultants and IT professionals who plan and implement Office 365. This includes migrations to Office 365 (simple and hybrid deployments) – link . Once passed you will be awarded with Microsoft Certified IT Professional (MCITP): Office 365 Administrator.

Cheers

Paul