Archive for the ‘Office 365’ Category

To work around this issue, delete any cached passwords for your account and any modern authentication tokens from the Keychain. To do this, follow these steps.

  1. Exit Outlook and all other Office applications.
  2. Open Keychain Access by using one of the following methods:
    • With Finder as the selected application, click Utilities on the Go menu. Double-click Keychain Access.
    • In Spotlight Search, type Keychain Access and then double-click Keychain Access in the search results.
  3. In in the search field in Keychain Access, enter Exchange.
  4. In the search results, select each item to view the Account that’s listed at the top, and then press the Delete key. Repeat this step to delete all the items for your Exchange account.
  5. In the search field, enter adal.
  6. Select all items whose type is MicrosoftOffice15_2_Data:ADAL:<GUID>, and then press the Delete key.
  7. In the search field, enter office.
  8. Select the items that are named Microsoft Office Identities Cache 2 and Microsoft Office Identities Settings 2, and then press the Delete key.
  9. Quit Keychain Access.

You may notice that meetings with a ‘Room’ mailbox will by default only show a “Busy” status.
Many, including the organisation I work for, wish to have (at the very minimum) the following displayed in the Room’s calendar:

  • Organiser of the meeting, and
  • The subject of the meeting

Below I will demonstrate how to set the permissions so that all meetings (except those explicitly marked as ‘Private’) publicise the above details to all who view its calendar.

  1. First make sure you have the remote signed execution policy set to true. You can do this by running PowerShell in admin mode and running: Set-ExecutionPolicy RemoteSigned
  2. Next, run the following to authenticate your self and import PowerShell commands to your local session:
    $LiveCred = Get-Credential
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange-ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection
    Import-PSSession $Session

Set the Room calendar to show ‘limited details’ by default

We will do this using the Set-MailboxFolderPermission command. Click the link to see the full list of parameters you can pass in to the command. We will be using ‘limited details’ for the AccessRights variable.

Set-MailboxFolderPermission -AccessRights LimitedDetails -Identity Room:\calendar -User default

Set the Room calendar to show the ‘Organiser’ and ‘Subject’ of the meeting

We will do this using the Set-CalendarProcessing command. Click the link to see the full list of parameters you can pass in to the command.
Set-CalendarProcessing -Identity testroom -AddOrganizerToSubject $true -DeleteComments $false -DeleteSubject $false



Hvis din Office installation skal have ændret sprog. Download pakken herunde.

Ex. hvis Engelsk version er installeret fra en Office 365, og du vil have den ændret til dansk.

“Language Accesory Pack” hentes:

Auto-complete in Outlook 2010 missing after migration to Office 365

Step One: Close Outlook

Step Two: Browse to the RoamCache where the auto-complete file is stored. (location is C:\Users\%username%\AppData\Local\Microsoft\Outlook\RoamCache

Step Three: Rename RoamCache to old_RoamCache

Step Four: Open Outlook, and create a new email and put a valid email address in the to. .field. Close the new email (you don’t need to save ). Close Outlook

Step Five:  Step four creates a new Stream_Autocomplete_long GUID….xx.dat file in a new RoamCache folder.

Step Six: Change the extension of the file in Step 5 from .dat to .dat22

Step Seven: Copy the original Stream_Autocomplete…from old_RoamCache & paste into theRoamCache folder

Step Eight: Copy the GUID string from the .dat22 and replace the GUID of your previous Stream_AutoComplete

Step Nine: Open Outlook, all of your previous auto-complete entries are now available.

As part of adding your domain to Office 365 for professionals and small businesses, you update the name server records for your domain to point to Office 365-hosted name servers. Some domain name registrars, such as those in Denmark and Norway for .dk and .no domains respectively, have restrictions in place that prevent this step from being completed successfully.

IMPORTANT: The information contained in this document serves as a workaround for customers who are unable to add their domain to Office 365 Small Business due to restrictions enforced by their domain registrar. We do not recommend following these steps unless you are adding a .no or a .dk domain.

To add your .no or .dk domain to Office 365, do the following.

Sign in to Office 365 for professionals and small businesses as an administrator.
In the header, click Admin and then under Management, click Domains.
Click Add a domain.
Type the domain name that you’d like to add to your account, and then click Check domain.
Click Next.
Follow the steps in the wizard to verify with Office 365 that the domain name you have added belongs to you.

After your domain has been verified by Office 365, click Cancel to exit the wizard. Next, you’ll create the DNS records that are required for Office 365 hosted services to work with your domain.

In the header, click Admin, and then under Management, click Domains.
Click the domain name that you just added to Office 365.
On the DNS manager tab, you see the DNS records that are associated with Exchange Online, Lync Online, and SharePoint Online.

Using the information on the DNS Manager tab as a guide, login at your current DNS hosting provider (which may be your domain name registrar) and manually create the same DNS records. As you create the DNS records, keep in mind the following.

The DNS records associated with Exchange Online are the following:
MX record: Configures mail routing.
CNAME record (autodiscover): Enables Outlook users to easily configure a connection with Exchange Online.
TXT record: Used for the Sender Policy Framework (SPF), which helps prevent outbound mail from being delivered to a recipient’s junk mail folder.
The DNS records associated with Lync Online are the two SRV records.
The DNS records associated with SharePoint Online are the A record and the ‘www’ CNAME record. Both of these are required for routing network traffic to your website.

NOTE: If you want to host a public-facing website on SharePoint Online but you do not see the corresponding A and CNAME records that are required, you must enable SharePoint Online hosting for your domain. For more information, see Use a vanity domain for your SharePoint Online public website address.

After you complete these steps, your domain is configured to work with Office 365 hosted services.

If you choose to add your domain to Office 365 by using the steps described here, be aware of the following implications.

SharePoint Online: If you enable SharePoint Online to host your website, the DNS records that are required to route traffic to SharePoint Online will not be created automatically by Office 365. You must manually create those DNS records at your DNS provider. You must take this extra step because Office 365 is not hosting the DNS records for your domain.
Domain troubleshooting tool: Because you did not configure your name server records to point to Office 365 name servers, the Office 365 domains troubleshooting wizard will always report that your name server records are incorrect. You can disregard this warning since you have manually created the DNS records for each of your services.
DNS manager: Office 365 for professionals and small businesses includes DNS management tools that enable you to add custom DNS records. However, although you may have created custom records by using this tool, since you have not updated your name server records for your domain, the custom records will not work. You must create the records using your current DNS hosting provider.
Future updates:When new services are added to Office 365, we will not be able to automatically add the DNS records to enable them to work on your domain. You will need to manually add these DNS records at your DNS provide