After adding additional mailboxes to Outlook (Tools > Email Account > Change > More Settings > Advanced > Add), when you retrace your steps you may find that you are unable to remove the additional mailbox(es) because it isn’t listed, even though the mailbox is still visible in the main Outlook pane. When right-clicking on the mailbox and selecting “Close Mailbox – Name” you may receive the following error:

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.

Just to let you know Exchange 2007 SP3 Rollup 6 has been released

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

After resetting your password and signing into Lync, you may be repeatedly prompted to enter a user name and password so Lync can connect to Outlook. See below:

Solution

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

We had an issue recently with End User Recovery for DPM 2010  recently , where on certain shares on a file server we were backing up didn’t show previous versions, with the following error “There are no previous versions available”.

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

Microsoft have recently announced they will be releasing MCITP certification for Office 365. These will be in the form of two exams:

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

For all those out there who are looking to move some of their services to the cloud, there is an free online resource from Microsoft that will take you though the steps required in order to set up your environment for a move to the cloud:

http://technet.microsoft.com/en-us/office365/hh699847

You only need Silverlight installed and each lab is around 20 to 30 minutes in total. It also covers Exchange Online and SharePoint Online.

Used in conjunction with other online documentation answered a lot of questions that I had about setting this up.

Cheers

Paul

We had an issue recently when trying to access an external FTP site. We tried to open the FTP website via Windows Explorer, we typed our credentials in and we got the following error.

The part we are interested in is the “502 Active FTP not allowed” , this is due to the fact that Active FTP is automatically disabled via TMG.

To allow Active FTP in TMG do the Following

1. Open The TMG Management Console
2. Press System and go to the Application Filters tab
3. Right click the FTP Access Filter and press properties
4. Go to the FTP properties tab and select the tick box “Allow active FTP access”

Also do the following on the access rule you created to allow FTP access

1. Right click access rule and choose Configure FTP
2. Uncheck Read Only

You will now be able to access the FTP site

When using the SharePoint command-line tool STSADM, you may receive “Command line error.” even though the syntax is correct:

Solution

Manually type out the command rather than copying/pasting from another application such as Internet Explorer. This is caused by the encoding method, particularly any hyphens in the command. Hyphens and dashes vary between ANSI and UTF-8 encoding.

Microsoft have released an Outlook connector for Facebook , you can get the download from here http://www.microsoft.com/download/en/details.aspx?id=5039&WT.mc_id=rss_alldownloads_all

Instructions to Set up

• Once Installed restart Outlook and you may be prompted by the Outlook Social Connector configuration wizard to connect to Facebook.
  1. Under Social Network Accounts, select Facebook.
  2. For User Name: enter your Facebook email account.
  3. For Password: enter your Facebook password.
  4. Click Connect
  5. Once the connection is successfully completed, click Finish
• If you were not prompted by the Outlook Social Connector configuration wizard, you can still connect to Facebook.
  For Outlook 2010:
  1. On the View tab, in the People Pane group, click People Pane, and then click Account Settings.
  2. Under Social Network Accounts, select Facebook.
  3. For User Name: enter your Facebook email account.
  4. For Password: enter your Facebook password.
  5. Click Connect.
  6. Once the connection is successfully completed, click Finish.

Once Added you will be able to see your friends latest posts, status updates etc from the People pane in Outlook

Microsoft has recently revealed the new file system RsFS. Much more detail can be found at the following blog:

http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx

In this blog, I am just highlighting some of the key things to take away about ReFS:

• Only Windows Server 8 will include the ReFS
• Windows 8 desktop will continue with NTFS
• ReFS will not be usable as a boot drive, this will come in future versions of Windows
• ReFS cannot be used on removable media devices (USB Disks)
• Failover clustering is supported
• There will be no way to convert an existing NTFS drive to a ReFS. Creating a new ReFS drive and copying data will be the only migration path for moving files onto a ReFS drive.
• Bit locker encryption is supported on ReFS
• Corruptions automatically detected and fixed

Capacity limits of ReFS:

Cheers

Paul