Todorovic Dragan

Senior Consultant - SharePoint & Office 365

All Posts
Monthly Archives: July 2014

Jul.31

How to wrap menu items in SharePoint 2013 global navigation?

This is a quick post to show the code snippet I used to wrap the global navigation items in SharePoint 2013. You can also use custom CSS code in order to get some space between navigation lines and items. First, open default masterpage of your site collection and find the following:

<SharePoint:AspMenu
   ID="TopNavigationMenu"
   Runat="server"
   EnableViewState="false"
   DataSourceID="topSiteMap"
   AccessKey="<%$Resources:wss,navigation_accesskey%>"
   UseSimpleRendering="true"
   UseSeparateCss="false"
   Orientation="Horizontal"
   StaticDisplayLevels="2"
   AdjustForShowStartingNode="true"
   MaximumDynamicDisplayLevels="2"
   SkipLinkText="" />

and replace with the code below:

<SharePoint:AspMenu
   ID="TopNavigationMenu"
   Runat="server"
   EnableViewState="false"
   DataSourceID="topSiteMap"
   AccessKey="<%$Resources:wss,navigation_accesskey%>"
   UseSimpleRendering="false"
   UseSeparateCss="false"
   Orientation="Horizontal"
   StaticDisplayLevels="2"
   AdjustForShowStartingNode="true"
   MaximumDynamicDisplayLevels="2"
   SkipLinkText=""
   ItemWrap="true"
   RenderingMode="List" 
   cssClass="mycss"/>

As you can see, the only diference is:

ItemWrap="true"
RenderingMode="List"
cssClass="mycss"

Create custom CSS file with the following content:

.mycss .level1
{
margin-left: 10px;
margin-right: 20px;
}
.mycss .level2
{
margin-left: 10px;
margin-right: 20px;
}
.mycss .level3
{
margin-left: 10px;
margin-right: 20px;
}

Jul.21

Dragan Todorovic 0 Office365

Office 365 Uptime Stats

Jul.04

Dragan Todorovic 0 Office365,CERTIFICATES

How Office 365 manages DNS records for mail service?

When you set up Office 365, you might have a choice between managing your own DNS records at your DNS hosting provider and having Office 365 create and manage the DNS records for your domain. I definitely recommend letting your existing hosting provider or domain registrar to manage your records, because in case you decide to host MX records outside of Office 365 , it will not be possible. Simply, you can’t change your DNS records to host email outside of Office 365.

Jul.03

Dragan Todorovic 0 Office365,CERTIFICATES

Enable XML attachments on Exchange Online

Right click on the PowerShell Console icon and chose the option: Run as administrator.
To change the Execution policy open the Microsoft Online Services Module for Windows PowerShell and type the command:
```
Set-ExecutionPolicy unrestricted
```
For creating the remote connection we will need to use a set of three PowerShell commands. Each command perform different task and include variable that serve as a “container” for information such as: user credentials, URL etc. Execute the following command:
```
$cred = Get-Credential
```
```
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic –AllowRedirection
```
```
Import-PSSession $Session
```
A pop out windows will appear. Type your credentials by using the UPN (user Principal name) format. User should have global administrator rights in the office 365 environment. To view all the allowed file type, you can use this command:
```
(get-OwaMailboxPolicy OwaMailboxPolicy-Default).AllowedFileTypes
```

To allow a specific file type (such as .xml file), use this command:

Set-OwaMailboxPolicy OwaMailboxPolicy-Default -AllowedFileTypes  @{add= '.xml'} Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -BlockedFileTypes @{Remove = ".xml"}
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -AllowedFileTypes @{Add = ".xml"}
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -BlockedMimeTypes @{Remove = "text/xml", "application/xml”}
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy –AllowedMimeTypes @{Add = "text/xml", "application/xml”}

Disconnect the remote connection with the following command:
```
Remove-PSSession $Session
```

Jul.01

Dragan Todorovic 0 Office365,CERTIFICATES

530 5.7.1 Client was not authenticated

Exchange Online implementation for new customers also includes local Outlook settings in order to send/receive messages from desktop application. Few days ago, users have reported the following error: “530 5.7.1 Client was not authenticated” during account setup in Outlook 2010/2013.

This kind of issue is cause by incorrect SMTP authentication setting.

From the File menu, select “Info” and choose “Account Settings”
Select your account and click the “Change” button above.Click the “More Settings…” button in the bottom-right corner of the E-Mail Accounts window.
In the Internet Email Settings window, click the “Outgoing Server” tab.
Ensure that the box next to “My outgoing server (SMTP) requires authentication” is checked and “use same settings as my incoming mail server” is selected.