Fix: The Specified address list could not be edited. Address lists created by using legacy versions of Microsoft Exchange must be upgraded

When opening the Address List on the Organization Configuration/Mailbox/Address List, you will notice the error:

The Specified address list could not be edited. Address lists created by using legacy versions of Microsoft Exchange must be upgraded by usng the "ForceUpgrade" parameter of the Set-AddressList cmdlet

This can be solved by using the Exchange Powershell and running the following commands:

Set-AddressList "All Users" -IncludedRecipients MailboxUsers
Set-AddressList "All Groups" -IncludedRecipients MailGroups
Set-AddressList "All Contacts" -IncludedRecipients MailContacts

Fix: Emails not showing in Exchange after IMAP import

When importing from PST files exported from an IMAP Server, the messages might not be showing when viewing them in Outlook although they are there. The messages are visible in OWA (Outlook Web Access) and you cannot move emails into the folders when this is done from OWA.

This is because when you import the PST, the messages are imported with the IMAP message format and need to be changed to IPF.NOTE format.

Download the ExFolders from the Microsoft website or from the tools page here.
Extract Exfolders.exe into C:\Program Files\Microsoft\Exchange Server\V14\Bin
Run the Registry file and import it

Make sure you have ‘Manage As’ permissions on the mailboxes you need with the logged in user.

Open ExFolders from the bin folder

Goto Tools and Options
Enable Logging to File

Goto File and select Connect with
Type: Mailboxes
Connect by: Database
Select the GC server
Select the Mailbox Database
You should see all the mailboxes listed

Goto Tools and open Custom Bulk Operation
Select Mailboxes as your Base Folder
Enter (&(0x3613001E=IPF.Imap)) in the Overall Filter
Click on the Add button and select Other Folder Properties and click OK
Select Action as Modify
Select PR_CONTAINER_CLASS : 0x3613001E as Property
Enter IPF.Note as Value
Click OK and OK

This should process the folders and emails. From here Exfolders will walk through the mailbox container(s) and change each instance of the PR_CONTAINER_CLASS from IPF.Imap to IPF.note

Fix: Command execution failed: The supplied handle is invalid on Lync 2010 Edge

When deploying a Lync Edge setup and during the ‘Setup or Remove Lync Server Components’ you might get the error:

Command execution failed: The supplied handle is invalid. This can happen when trying to set an ACL on an anonymous kernel object.

This could be because the name of the computer/server exceed the 15 characters since the setup uses the NETBIOS name rather than the FQDN. To fix this, change the computer name to less or equal to 15 characters. Then you have reconfigure Lync Edge server by doing the below:

– Change computer name to less or equal to 15 characters and restart
– Remove any installed application on the Edge server
– On the Front-End Server open the Topology builder
– Remove the Edge Pool for media from the Standard or Enterprise Front End node
– Remove the Edge Pool you created under the Edge Pool node
– Publish Topology
– Re-Export the configuration with Export-csconfiguration –filename c:\topology_export.zip
– Copy topology_export.zip on Edge server
– Re-start Setup

That should fix the issue

Fix: Blank page when enabling updates for other products

When enabling the option for Windows Update to download updates for other products, you will get a blank white page on the Internet Explorer. The URL you visit is http://www.update.microsoft.com/microsoftupdate/v6/vistadefault.aspx?ln=en-gb.

To fix this when the IE window opens click on the Compatibility View button on the top and it will show the page.

How to: Move all FSMO roles on a domain controller

When moving roles, the right way to do it is to view exactly where the roles are at the moment. Firstly to check this one can open the command prompt and use the following command.

Netdom /query FSMO

This will show the roles and who is the owner like below.

C:\Users\Administrator.dom>netdom /query fsmo
Schema master     srv01.mydomain.com
Domain naming master     srv01.mydomain.com
PDC     srv01.mydomain.com
RID pool manager     srv01.mydomain.com
Infrastructure master     srv01.mydomain.com
The command completed successfully.

Now, to change the FSMO owner one must change the settings in the Active Directory Users and Computers, Active Directory Domains and Trusts and Active Directory Schema. This operation would be best to be done on the new server to transfer to.

1. Open the Active Directory Users and Computers and right click on the domain name node, in my case mydomain.com and select Operations Master. Make sure that the entry is the old server on the top dialog box and the new server on the bottom dialog box. Click on the Change button. Switch to the PDC tab and Instrastructure and do the the same operation.

2. Open theActive Directory Domains and Trusts. Right click on the root of the node and select Operations Master. Make sure that the entry is the old server on the top dialog box and the new server on the bottom dialog box. Click on the Change button.

3. Open a command prompt as Administrator and type regsvr32 schmmgmt.dll to register the schema DLL file. Open MMC.EXE and click on File/Add remove Snap-in. Now find the Active Directory Schema from the list. Click on Add and OK. Right-click on the Active Directory Schema node and select Change Active Directory Controller. Select the new server, in this case srv02.mydomain.com. Right-click on the Active Directory Schema node and select Operations Master. Make sure that the entry is the old server on the top dialog box and the new server on the bottom dialog box. Click on the Change button.

If you will run below command, Netdom /query FSMO, you will notice that the roles are now pointing to the new server i.e. srv02.mydomain.com.

 

 

 

How to: Migrate Public Folders from Exchange 2007 to 2010

Create new public folder on Exchange 2010.

On Exchange Powershell run the below:

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder “\” -ServerToAdd

Make sure that you run it on the Exchange 2010 powershell because, if you run it on the 2007 you will get the below error:

Get-PublicFolder : There is no existing PublicFolder that matches the following
Identity: '\'. Please make sure that you specified the correct PublicFolder Id
entity and that you have the necessary permissions to view PublicFolder.

Run the below to verify the replicas are functioning and the folders are showing

Get-PublicFolder -Identity “\” -Recurse -ResultSize Unlimited |ft identity,replicas –auto

To view the item count of the replica run

Get-PublicFolderStatistics

It will show as below

Name ItemCount
---- ---------
Public Foler 33
Sales 111
CompanyBook 592

You can run the above powershell command on the 2007 server to check the amount of items so that you can compare with the new server.

Once the replication is ready,

Got to folder C:\Program Files\Microsoft\Exchange Server\v14\scripts and run:
./MoveAllReplicas.ps1 -Server -NewServer

You can now remove or un-mount the old 2007 Public Folders

Fix: Cannot open your default e-mail folders in Outlook

When opening Outlook you can be presented with the error Cannot open your default e-mail folders. The information store could not be opened. To fix the issue follow the below steps.

– Close Outlook
– Open C:\Program Files (x86)\Microsoft Office\Office14 folder or the folder where Outlook.exe is located.
– Right click on Outlook.exe and select properties.
– On the Compatibility Mode tab
– Un-tick the option Run this program in compatibility mode.
– Open Outlook

Fix: Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405

When importing a database in your SQL instance you would find yourself with Cannot use the special principal 'sa'. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the database. To fix this,
Open SQL Management Studio and Click New Query. Type:

USE mydatabase
exec sp_changedbowner 'sa', 'true'

Close the new query and after viewing the security of the sa, you will find that that sa is the DBO of the database.

How to: Clean User’s Active Directory Schema from previous Lync installation

Sometimes when you install a Lync setup and change the server, you might have problems when adding the clients back to the newly created server. Some issues might be that that you cannot log in or mostly you get an error on the management panel on Lync when you enable a user as below:

"RegistrarPool" with identity "1234567890" assigned to "sip:sysadmin@noelpulis.com" has been removed from the configuration store.

You may also encounter the error,

Cannot move user in enable operation. Use the Move user cmdlet instead

To cleanup the user you will need to edit the Active Directory schema. Open the ADSI Edit from your domain controller. Connect as the Default naming context, find the user you need to change (in this case sysadmin) and select properties. Change the below properties to either blank or .

msRTCSIP-ArchivingEnabled
msRTCSIP-FederationEnabled
msRTCSIP-InternetAccessEnabled
msRTCSIP-OptionFlags
msRTCSIP-PrimaryHomeServer
msRTCSIP-PrimaryUserAddress
msRTCSIP-UserEnabled
msRTCSIP-UserPolicies

After you set the below, exit the ADSI Edit and retry on Lync. The user should be able to work.