Change a User's Primary E-mail Address

In the cloud-based service, user IDs are formatted like e-mail addresses. In Microsoft Live@edu, the user ID is a Microsoft ID.

A cloud-based user signs in to their mailbox using their user ID, and the user ID is also the user's e-mail address. There are occasions, however, when an administrator may want to change a user's e-mail address without affecting their user ID.

When would you want to do this? Suppose you manage the cloud-based organization for a large university that uses student identification numbers for the user ID, such as 1234567@contoso.edu, but <first name>.<last name> for the e-mail address, such as kim.akers@contoso.edu. The user Kim Akers receives mail sent to 1234567@contoso.edu and kim.akers@contoso.edu, but kim.akers@contoso.edu is the primary "reply to" e-mail address on all messages sent from the mailbox.

You have to use Windows PowerShell to set the primary e-mail address. The user's primary e-mail address appears in the E-Mail Options section of the user's mailbox in the Exchange Control Panel, but you can't modify it there.

Note   To change the user ID and primary e-mail address to the same value at the same time, see Rename a User ID.

Change the primary e-mail address of an existing user

---

Run the following command:

Set-Mailbox <Identity> -EmailAddresses SMTP:<new primary e-mail address>,<user ID>,<existing proxy address 1>,<existing proxy address 2>...

For example, suppose your cloud-based organization and all the user IDs are in contoso.com, and you have configured accepted domains and proxy addresses for all mailboxes in contoso.net and contoso.org. You want to change the primary e-mail address of a user named Kim Akers, who has the user ID of kakers@contoso.com, to kim.akers@contoso.com. You also want to keep the existing proxy addresses on the mailbox. To do this, run the following command:

Set-Mailbox kakers@contoso.com -EmailAddresses SMTP:kim.akers@contoso.com,kakers@contoso.com,kakers@contoso.net,kakers@contoso.org

Note:

You specify the primary e-mail address by using the case-sensitive qualifier, SMTP. If you don't specify SMTP, the first e-mail address becomes the primary e-mail address.

Change the primary e-mail address for many existing users by using a CSV file

---

To change the primary e-mail address of many existing users at one time, you must create and import information about the existing users by using a CSV file. The following procedure imports data from C:\My Documents\ChangeAddress.csv. The CSV file has the following format:

UserID,NewAddress,Proxy1

akol@contoso.com,aylakol@contoso.com,akol@contoso.net,tjohnston@contoso.com,tamarajohnston@contoso.com,tjohnston@contoso.net

The column names in the first row of this CSV file, (UserID,NewAddress,Proxy1), are arbitrary. Whatever you use for column names, make sure you use the same column names in the Windows PowerShell command.

After you create the CSV file by using the existing user IDs, existing proxy e-mail addresses, and new primary e-mail addresses for the users you want to update, run the following commands:

$Users = Import-CSV "C:\My Documents\ChangeAddress.csv"

$Users | ForEach {Set-Mailbox $_.UserID -EmailAddresses $_.NewAddress,$_.UserID,$_.Proxy1}

Note   Because this procedure doesn't use the case-sensitive qualifier, SMTP, the first e-mail address that is specified for the EmailAddresses parameter becomes the primary e-mail address.

 

Error when you try to configure a second federated domain in Office 365: "Federation service identifier specified in the AD FS 2.0 server is already in use."

This article discusses Microsoft Office 365, Microsoft Office 365 Preview, and Microsoft Office 365 pre-upgrade. The info about Office 365 Preview in this article, including any links, is provided as is and is subject to change without notice.

In Microsoft Office 365, you can't set up a second federated domain on an Active Directory Federation Services (AD FS) 2.0 server. When you use the Windows Azure Active Directory Module for Windows PowerShell to run the new-MSOLFederatedDomain cmdlet or the convert-MSOLDomainToFederated cmdlet, you receive the following error message:

The federation service identifier specified in the Active Directory Federation Services 2.0 server is already in use. Please correct this value in the AD FS 2.0 Management console and run the command again.

The Windows Azure Active Directory (Windows Azure AD) authentication system requires a unique federation brand uniform resource identifier (URI) for each federated domain. By default, AD FS 2.0 uses a global value for all federated trusts. When you try to federate a second domain in a scenario where a federated trust already exists, the request fails because the URI is already being used.

SOLUTION

To resolve the issue, you must use the -supportmultipledomain switch to add or convert every domain that is federated by Office 365. This includes federated domains that already exist.

Step 1: Install Update Rollup 1 for AD FS 2.0

On each node of the AD FS 2.0 Federation Service farm, download and install Update Rollup 1 for AD FS 2.0. For more information about how to download and install Update Rollup 1 for AD FS 2.0, click the following article number to view the article in the Microsoft Knowledge Base:

2607496 Description of Update Rollup 1 for Active Directory Federation Services (AD FS) 2.0

Note This update requires a restart of the computer. If you do not restart the computer, you will experience the issue that is described in the following article in the Microsoft Knowledge Base: 

2635357 Unable to logon after implementing multiple top level domain or client access policies

Step 2: Check that the update-MSOLFederatedDomain cmdlet can be run successfully against the AD FS 2.0 environment

a.       Click Start, point to All Programs, point to Windows Azure Active Directory, right-click Windows Azure Active Directory Module for Windows PowerShell and select Run As Administrator.

b.       At the command prompt, run the following cmdlets in the order in which they are presented. Press Enter after each cmdlet.

a.  Connect-MSOLService

Note When you are prompted, enter your Office 365 global administrator credentials.

b.  Set-MSOLADFSContext -Computer <AD FS 2.0 server name>

Note In this command, <AD FS 2.0 server name> is the computer name of a node in the AD FS 2.0 Federation Service farm.

c.  Update-MSOLFederatedDomain -DomainName <Federated Domain Name>

Note In this command, <Federated Domain Name> is the name of the domain that is already federated with Windows Azure AD for single sign-On (SSO).

Leave the Command Prompt window open for later use.

3. If the update-MSOLFederatedDomain cmdlet is successful and you do not receive error messages, go to step 3 to remove the federated trust from the AD FS 2.0 server

Step 3: Update the federated trust on the AD FS 2.0 server

Warning The following steps should be planned carefully. Users for which SSO functionality is enabled in the federated domain will be unable to authenticate between the completion of steps C and D. If the update-MSOLFederatedDomain cmdlet test in step 2 was not completed successfully, step D of this procedure will not finish correctly. SSO-enabled Office 365 users will be unable to authenticate until the update-MSOLFederatedDomain cmdlet can be run successfully.

a.   Log on to the console of the AD FS 2.0 server, click Start, point to All Programs, point to Administrative Tools, and then click AD FS 2.0 Management.

b.       In the left navigation pane, click AD FS 2.0, click Trust Relationships, and then click Relying Party Trusts.

c.        In the pane on the right side, delete the Microsoft Office 365 Identity Platform entry.

d.       Re-create the deleted trust object by using the -supportmultipledomain switch. In the PowerShell window that is open from step 1C, run the following cmdlet, and then press Enter:

Update-MSOLFederatedDomain -DomainName <Federated Domain Name> -supportmultipledomain

Note In this command, <Federated Domain Name> is the name of the domain that is already federated with Office 365 for SSO.

Step 4: Use the -supportmultipledomain switch to add or convert additional federated domains

After you update the existing trust in step 2, use the -supportmultipledomain switch to add or convert additional federated domains. This switch informs the cmdlet to use a unique URI namespace for each domain that is federated by Office 365. To do this, use one of the following cmdlet syntaxes:

·         New-MSOLFederatedDomain -domainname <domain name> -supportmultipledomain

·         Convert-MSOLDomainToFederated -domainname <domain name> -supportmultipledomain

Note In this command, <domain name> represents the name of the domain that you are trying to federate.

 

How to create an E-mail Merge using Microsoft Outlook 2010




*Note: Just like in Word 2007, Word is the only editor in Outlook 2010 (by default).


1. Open up Word 2010. Create a new e-mail message in Word. Now you are ready to begin the merge by selecting the "Mailings" tab in the ribbon.

 2. In the "Start Mail Merge" grouping, click on the "Start Mail Merge" button. It will show a list of mail merge options available. You can choose Letters, E-Mail Messages, Envelopes, Labels or Directory. In this case we want to send an email… click on "E-Mail Messages"

3. Next you need to select the recipients of your email merge. These names could come from any number or sources… maybe an Excel 2010 spreadsheet or your Outlook 2010 Contacts. To do that, click on the "Select Recipients" box in the "Start Mail Merge" group. Either find your data source, your outlook contacts, or create a new list. If you want to edit any of the recipients in the list, now is the time to click on "Edit Recipient List" in the "Start Mail Merge" group.

4. The next step is to add the appropriate fields to personalize the greeting, the recipient’s name, or to add any other piece of data you might have on the contact anywhere throughout your recipient list. You can find the appropriate fields in the "Write & Insert Fields" group (still on the "Mailings" tab). More than likely you will want to add at least a greeting line (Dear Bill… or something like that). To do that, click on the "Greeting Line" button in the "Write & Insert Fields" group. The following dialog box appears:

5. Once you are happy with your greeting line format, click "OK". Word 2010 will now drop the field into your document. Now you can preview your results to ensure that everyone’s name is coming up correctly. Click the "Preview Results" button in the "Preview Results" group… then use the forward and back arrows beside it to run through your recipient list.

6. If you are happy with the preview, now is the time to finish things off and complete the merge. In the "Finish" group on the "Mailings tab" you will see a button called "Finish & Merge". Click on it, and then click "Send E-mail Messages." You will be asked to give your message a Subject and then you can click on OK to send the messages.

7. Now Word 2007 automatically generates all the individual emails, and sends them to your Outlook 2010 outbox (or your default email client). Your email merges will be recorded in your sent items folder.

NOTE: Attachments are not an option in an email merge. All data must be within the body of the email message.

 

SkyDrive Pro does not sync anymore

In fact, SkyDrive pro is the replacement of the SharePoint 2010 ‘Workspace’ and it also integrates very well with Windows Explorer. That being said, SkyDrive Pro should also be able to sync SharePoint 2010 Document Libraries.  But for one or another reason, the current build of SkyDrive Pro had some problems to keep my SharePoint 2010 content synced.

I did a rename of my SharePoint folder located in my user directory, but that’s something SkyDrive Pro doesn’t really like (at least on my machine). The error I got was “An error occurred while attempting to synchronize this tool.”

It seems like it is indeed a bug with the current build of SkyDrive Pro. As for now, the only solution is to clear the SkyDrive Pro cache, and re-sync your library. So you will lose all settings. To clear your cache, close all your Office processes like groove.exe (which is SkyDrive Pro), msouc.exe,  msosync.exe, office library sync,…

Browse to “C:\Users\%username%\AppData\Local\Microsoft\Office\Spw” and delete all the content. (you will see that this is all related to groove and spw = SharePoint Workspace). Next, go to “C:\Users\%username%\AppData\Local\Microsoft\Office\15.0\OfficeFileCache” and also delete all content from this folder. This is where all the caching from your files are stored.

After you deleted everything,  you should be able to start SkyDrive Pro again (using “C:\Program Files\Microsoft Office\Office15\GROOVE.EXE“). You can now start configuring your clean environment. Good luck!

 

 

 

To Manually Rebuild the Icon Cache using the Command Prompt

1. Close and save anything that you are working on. This command will kill explorer and restart the computer when completed.

2. Open a command prompt in Windows 7 or Windows 8

3. In the command prompt, Copy and paste each command line below exactly as is one at a time and press enter after each command.


WARNING: The last command will restart the computer, so be sure to close and save anything that you are working on first.

·         ie4uinit.exe -ClearIconCache

·         taskkill /IM explorer.exe /F

·         DEL "%localappdata%\IconCache.db" /A

·         shutdown /r /f /t 00

4. The IconCache.db file has now been rebuilt.

5. If the icons are still not displaying properly, then download and merge the ICO option in this tutorial for Windows 7 or Windows 8 to restore the default associations of .ico (icon) files.

How to restore IIS and clean up Active Directory when you uninstall Active Directory Federation Services 2.0

Restore IIS on a federation server or federation server proxy computer

When AD FS 2.0 is installed on a computer that is configured for the federation server or federation server proxy role, it will create the /adfs and /adfs/ls virtual directories in IIS. AD FS 2.0 will also create a new application pool named ADFSAppPool. When you uninstall AD FS 2.0 from a federation server or federation server proxy computer, these virtual directories are not removed. Additionally, the application pool is not removed. This can create problems if AD FS 2.0 is installed again on the same computer.

To manually remove these directories from the decommissioned federation server or federation server proxy computer, follow these steps:

1.       Click Start, select Administrative Tools, and then select IIS Manager.

2.       Expand the server name node, expand Sites, and then select Default Web Site.

3.       In the Actions pane, select View Applications.

Note You should see the following two virtual directories associated with AD FS 2.0:

o    /adfs

o    /adfs/ls

4.       Right-click the AD FS 2.0 application that is in each virtual directory, and then click Remove.

5.       In the Actions pane, select Application Pools.

Note You should see an application pool named ADFSAppPool.

6.       Right-click ADFSAppPool, and then select Remove.

Note: The next two steps show how to remove the \adfs directory from the "inetpub" directory. If you have made custom changes to the content within this directory, we recommend that you back up this content to another location before removing the directory.

7.       In Windows Explorer, browse to the "inetpub" directory. This directory is usually located in the following path:

%systemdrive%\inetpub

8.       Right-click the Adfs directory, and then click Delete

Delete the certificate sharing container in Active Directory

When you install AD FS 2.0 and use the Federation Server Configuration Wizard to create a new Federation Server in a new Federation Server farm, the wizard will create a certificate sharing container in Active Directory. This container is used by all the federation servers in the farm. When you uninstall AD FS 2.0 from the last added federation server in a farm, this container is not deleted from Active Directory.

To manually delete this container in Active Directory, follow these steps:

1.       Before you remove AD FS 2.0 from the last federation server in the farm, run the following PowerShell commands on the AD FS 2.0 STS to determine the location of the certificate sharing container in Active Directory:

o    Add-PsSnapin Microsoft.Adfs.Powershell

o    Get-AdfsProperties

2.       Note the CertificateSharingContainer property in the output from the previous step.

3.       Log on to a server where the ADSIEdit tool (ADSIEdit.msc) is installed.

4.       Click Start, click Run, type ADSIEdit.msc, and then press ENTER.

5.       In the ADSIEdit tool, connect to the Default naming context by following these steps:

a.       Right-click ADSI Edit, and then click Connect to.

b.       Under Connection Point, click Select a well-known Naming Context, and then select Default naming context.

c.        Click OK.

6.       Expand the following node:

Default naming context, {your domain partition}, CN=Program Data, CN=Microsoft, CN=ADFS

Note Under CN=ADFS, you see a container named CN={GUID} for each AD FS 2.0 farm that you have deployed, where {GUID} matches the CertificateSharingContainer property that you captured by using the Get-AdfsProperties PowerShell command in step 1.

7.       Right-click the appropriate {GUID} container, and then select Delete.

Suggested Contacts vs Auto-Complete

The Suggested Contacts feature creates contact items in the Suggested Contacts folder when you are sending an email to someone who isn’t in your Contacts folder yet.

The Auto-Complete feature keeps a list of addresses of everyone that you emailed to, regardless if or where that contact/address is stored. This list is kept as a combination of a hidden message in your mailbox and in the RoamCache folder on disk (see below).

Note: They already did away with the Suggested Contacts folder in Outlook 2013. For more information see: SuggestedContacts folder missing or doesn’t save new addresses in Outlook 2013.

Resetting the Auto-Complete cache

To reset your cache, it is recommended to use the “Empty Auto-Complete List” button in the Options dialog.

File-> Options-> Mail-> section: Send messages-> button: Empty Auto-Complete List

Resetting the Auto-Complete cache is the first step to fix and refill the list.

As an alternative, you can start Outlook with the cleanautocompletecache switch.
(Note the space in the commands below)

§  Windows XP
Start-> Run; outlook.exe /cleanautocompletecache

§  Windows Vista, Windows 7 and Windows 8
Start-> Type; outlook.exe /cleanautocompletecache

In addition, you could manually clean up the RoamCache folder when Outlook is closed.

§  Windows XP
C:\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Outlook\RoadmCache

§  Windows Vista, Windows 7 and Windows 8
C:\Users\%username%\AppData\Local\Microsoft\Outlook\RoamCache

Filling the Auto-Complete cache with Contacts and Suggested Contacts

Once you’ve reset the Auto-Complete Cache, you can fill it again with contacts from your Contacts and Suggested Contacts folder in the following way;

1.       Place Outlook in Offline Mode by clicking on the “Work Offline” button on the Send/Receive tab.

2.       Create a new email.

3.       Click on the To… button.

4.       Select all the addresses from the Contacts folder

5.       Click on the To-> button

6.       Repeat step 4 and 5 for contacts stored in other locations which you can select by clicking on the list under Address Book.

7.       Click OK.

8.       Send the message.

9.       Move the message from your Outbox folder back to your Draft folder.

10.    Place Outlook back in Online mode by again clicking on the “Work Offline” button on the Send/Receive tab. (Note that the icon itself alwaysholds a red cross in it)

Your Auto-Complete feature should now work again when addressing a new email.

You can quickly refill the Auto-Complete cache after a reset.

Still no suggestions after restarting Outlook?

Is your Auto-Suggest feature broken again after restarting Outlook? As the cache is being stored when Outlook closes, it is very likely that an add-in isn’t letting Outlook close gracefully.

To troubleshoot this see; AutoCompleteaddresses lost in Outlook 2010