Category: Cloud Services

Branded email setup using custom domain name for professional business communication in accounting and healthcare

Branded Email using Custom Domain Name

There are many reasons your business needs to use a branded email address using a customized domain name. Let’s look at what the top ones are:

Branded Email Establishes Legitimacy

Customers want to trust a companies before they choose to give their business to them. This is the number one reason businesses should use branded email – not only does it give your business a deeper level of branding, but it establishes the business’ legitimacy. This is because your email is often the customer’s first impression of you, especially if email or print marketing had an email for contact. It makes your business look professional and can set it apart from the competition. Phishing schemes are a very real concern these days and many of these fake emails come from people trying to pose as a legitimate business. The best way for your customer to know if the email is really from you or a potentially dangerous location, is by the email address’ domain name. If the customer can look at the sender address and see your business’ domain, they will feel more confident clicking links or replying back with sensitive information.

Branded Email Builds Your Brand

A business can never have too much company branding. From business cards to bumper stickers to coffee mugs, there are branding opportunities everywhere. This should includes your business email too. Every time your employees send an email, it reinforces your business brand to the customer. It not only reminds the customer that you have a website, but gives them a peek into what your company is all about.

Branded Email Separates Company Departments

Having a branded email allows you to create multiple email addresses or email aliases for different departments and company objectives. This is a huge benefit as yourname@mycompanyname.com may not always the best address to email or your business may not want the customer to directly contact your employees. It helps compartmentalize the work and make sure that the right person / department receives the correct emails. You can create emails like support@mycomanyname.com, info@mycompanyname.com, sales@mycompanyname.com and many others that can point to one or more members of the organization. It also helps the customer, by pointing them to the right email address for the issue they need addressed.

Branded Email Isn’t Expensive

With Office 365’s Hosted Exchange service your business can add as many individual email addresses and email aliases to your company’s branded domain on an as needed basis, access email from anywhere across all major platforms, get industry leading anti-malware / anti-spam filtering built in, send email attachments up to 150MB in size and get 50GB of storage per mailbox. Prices start at just $4 per user per month. Microsoft manages the email server and Farmhouse Networking handles the setup / administration of the rest, which making it simple for you to have a professional branded customized business email address.

If you don’t have a branded email address, now is the perfect time to get one. Small businesses often think they don’t need one or can’t afford it, but that is simply not true. Help your business by setting up a branded email today by giving us a call or email to let our Office 365 experts get your business started on the path to better branding.

Office 365 Meeting Rooms

Shared calendars for the use of shared meeting space reservation is becoming a thing of the past. Office 365 has a better type of calendar specifically made for rooms. This guide will show you how to set up these Office 365 Meeting Rooms in Microsoft’s Office 365 admin portal. Login to the Office 365 Portal with an administrator account and do the following:

Setup Office 365 Meeting Rooms

  1. Click on the Meeting Rooms tab on the left of the Office 365 admin center.
  2. Click on the + symbol to begin the creation of the meeting room object.
  3. Fill in the needed information (Name, Email Address and Room Capacity) then click Create.
  4. Now users can access these meeting rooms when creating a new Meeting in Outlook by clicking on the Rooms button and selecting them.
  5. Once selected that room for that date at that time will be marked off on the associated calendar. There are also color coated indicators as to the availability of the meeting rooms on the selected date in the calendar.

The meeting room will also now appear in their Calendar tab of Outlook and can be used similarly to other calendars. If you have any issues setting things up for your site, please feel free to contact our Office 365 experts to guide you through the process.

Missing Active Directory Attribute Editor Tab

Ran into this issue a couple times now while migrating Small Business Server (SBS) clients from on-premis Exchange to Office365. After setting up the DirSync tool on the server, to add an email alias to a user’s Office 365 account it needs to be setup in the Active Directory Attribute Editor tab under the proxyAddresses attribute. The easiest way to do this is add a record as follows:

Add the Active Directory Attribute Editor Tab in Small Business Server

smtp:[useralias@yourcompany.com]

into the proxyAddresses section of the Attributes tab:

Active Directory Attribute Tab

This is normally easy to do and then run a manual DirSync to add the alias to the user’s Office 365 account, but what if the Attributes tab is missing? It is time to break out the ADSIedit tool again to make the needed changes to the way these pages are displayed. Here are the steps to get it done:

  • open ADSIedit.msc
  • Right click on ADSIedit and choose “connect to”
  • Under connection point select “select a well known Naming context” and in that window choose “Configuration”
  • Under computer leave as “Default (Domain or server that you logged into)” then click OK
  • Expand CN=configuration, DC=[your domain], DC=local
  • Expand CD=DisplaySpecifiers
  • Click on CN=your language. (The language # can be found on http://support.microsoft.com/kb/324097 for example US English is 409, so CN=409)
  • In the right hand window locate CN=User-Display right click and choose properties
  • Locate AdminPropertyPages, highlight it and click “edit” and add the line

11,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}

  • In the right hand window locate CN=Computer-Display right click and choose properties
  • ocate AdminPropertyPages, highlight it and click “edit” and add the line

12,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}

  • In the right hand window locate CN= Default-Display right click and choose properties
  • Locate AdminPropertyPages, highlight it and click “edit” and add the line

4,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}

Make sure to click on the View menu in Active Directory Users and Computers to choose the Advanced Features option if not already selected to see these newly added Active Director Attribute Editor Tab in the display.

Change Office 365 Distribution Group Restriction

If an Office 365 Distribution Group is being synced from on-premise Active Directory environment then you cannot receive emails to that group from an external source by default. If you try to change the setting in Office 365 the following error appears:

The action ‘Set-DistributionGroup’, ‘RequireSenderAuthenticationEnabled’, can’t be performed on the object ‘[Your Distribution Group]’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

Office 365 Distribution Group Error

This can be changed using the ADSIEdit tool. Navigate through the Active Directory hierarchy and find the Distribution Group then right click and choose Properties. Scroll down to “msExchRequireAuthToSendTo” and change the setting to FALSE. Run a manual DirSync to effect the changes in Office 365.

Office 365 Distribution Group - ADSI Edit

Deploy Office 365 Desktop Apps

Recently had to deploy Office 365 Desktop Apps on a terminal server which did not work with the standard download from the web portal due to licensing issues. Only customers with Office 365 E3 licenses or greater are able to use the deployable version of the Office 365 Desktop Apps in a terminal server environment. Here are the steps needed to deploy the apps:

Deploy Office 365 Desktop Apps on Terminal Server

  • Download the Office Deployment Tool for Click-to-Run here.
  • Run and extract the tool to a folder on your Terminal Server.

  1. Edit and configure the configuration XML file as follows including the \\[SERVER]\[SHARE]\ path:

    <Configuration>
    <Add SourcePath=”\\[SERVER]\[SHARE]\” OfficeClientEdition=”32″>
    <Product ID=”O365ProPlusRetail”>
    <Language ID=”en-us” />
    </Product>
    </Add>
    <Display Level=”None” AcceptEULA=”True” />
    <Property Name=”SharedComputerLicensing” Value=”1″ />
    </Configuration>

  2. Please visit this TechNet article for more details on the configuration file settings, like excluding apps from deployment.
  3. From an elevated Command Prompt, navigate to the folder extracted files are located in, and run the following to download the installation files:

    Setup.exe /download configuration.xml

    The Office365 ProPlus installation files will be downloaded to the specified share with the following structure.

  4. From an elevated Command Prompt, run following to install Office Click-to-Run:

    Setup.exe /configure configuration.xml

    When the installation is complete, the Office 2016 suite will be available for use.

  5. On starting the application, you will be prompted to Activate Office. Click Next and Sign in.
  6. Once signed in, you are ready to go. Office will automatically activate and configure the applications. This is supposed to work similarly with deployment via Group Policy. If your company is using a terminal server for your remote access and need help to deploy Office 365 Desktop Apps, then contact us for assistance.

Share Users Office 365 Calendar

The old way to accomplish Exchange calendar sharing between users was to either connect to each individual users workstation to right click and share the calendar to users in the Global Access List (GAL) or to install their profile on your system and do the same. There have been some wonderful advances since the advent of Powershell that allow Office 365 calendar sharing permissions to be set remotely as follows:

How to share Office 365 Calendar via Powershell

1. Make sure the Windows Azure Active Directory Module for Windows PowerShell is installed properly

2. Open Windows Azure Active Directory Module for Windows PowerShell as administrator

3. Type in the following to run signed scripts for Exchange Online:

Set-ExecutionPolicy RemoteSigned

4. Type in the following to enter the administrative credentials for Office 365:

$creds = Get-Credential

5. Enter the Office 365 Administrator credentials then click "OK" button. 6. Type in the following to connect to Office 365 via PowerShell:

Import-Module MsOnline

Connect-MsolService -Credential $creds

7. Type in the following to connect to Exchange Online via Powershell:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $creds -Authentication Basic -AllowRedirection

Import-PSSession $Session

8. Type in the following command to change the calendar permissions:

Add-MailboxFolderPermission -Identity sharinguser@domain.com:\calendar -User recipient@domain.com -AccessRights Editor

Once this command has been executed for each individual recipient that will access the sharing users calendar, then you can have them right click to add the shared calendar in their Outlook. For a list of possible Access Rights see this great page by the University of Wisconsin. If your company is using Office 365 Calendar and needs help sharing them, then contact us for assistance.

Setup Microsoft Mobile Device Management (MDM)

Recently had some issues where another tech company was unable to properly setup MDM for their clients, so reviewed the documentation and their current efforts then came to the conclusion that they had skipped a couple steps in the initial setup that were causing the issue. Here is the proper initial setup steps:

Activate Mobile Device Management in Office 365

1. Sign in to Office 365 as an administrative user
2. Click on the Admin pane
3. Click on Mobile Management on the list to the left hand side
4. Click on the “Get Started” button
5. Wait awhile (5 minutes to 2 hours) for the setup to complete

Configure Initial Domain DNS Settings

1. Back in the Mobile Management section, look for the red x circle and click on “Manage settings”
2. First to configure custom DNS needed for automatic configuration, click on the “Set up” next to “Configure domains for MDM”
3. Click on the primary domain used for Autodiscover, etc. then click on “Domain settings”
4. Under “Domain purpose” click on “Change domain purpose”
5. Put a check next to “Mobile Device Management for Office 365” then click on “Next”
6. Take note of the following cname records:

enterpriseregistration enterpriseregistration.windows.net 3600
enterpriseenrollment enterpriseenrollment.manage.microsoft.com 3600

7. Enter these into the customers custom DNS records along with any others that are listed on that page which weren't entered previously.
8. Return to this page to confirm that the DNS settings have changed properly.

Configure Apple Push Notification (APN) Certificate

1. Back in the Mobile Management section, look for the red x circle and click on “Manage settings”
2. Click on “Set up” next to “Configure an APNs Certificate for iOS devices” to request the needed certificate to manage Apple devices.
3. Click on “Download your CSR file” to save the file locally then click “Next”
4. Click on “Apple APNS Portal” to open the Apple Push Certificates Portal
5. Sign in with a valid (hopefully domain associated) Apple ID
6. Click on the “Create a Certificate” button
7. Agree to the Terms of Use
8. Upload the Certificate Signing Request (CSR) that was save locally earlier
9. Download the new Mobile Device Management certifcate and save it locally
10. Go back to the “Install Apple Push Notification Certificate” page and click “Next”
11. Upload the new Mobile Device Management certifcate tjat was saved locally from Apple

Configure Basic Mobile Device Management Policy

1. Create a Security Group in Active directory that will be used to apply the MDM policy and run DirSync manually.
2. Back in the Mobile Management section, click on “Manage device security policies and access rules”
3. Click on the + to add a new policy
4. Give the policy a name and click “Next”
5. On the pop-up page leave the defaults and check next to “Require managing email profile (required for selective wipe on iOS)”
6. Also select “Block access and report violation” to keep users off the network until they comply with the new policy then click “Next”
7. On the following page there are additional option that give additional security but are not required, when done click “Next”
8. Change selection to “Yes” and chose the Security Group in Active Directory that will be used for MDM enforcement then click “Next”
9. Click on “Finish” to begin enforcing this new policy

The next time any user opens an associated Office App on their supported devices it will ask them to start the enrollment process which goes through a compliance check which usually requires them to delete their current Exchange Active Sync profile to continue.

Special thanks to the guys at ExchangeServerPro.com for their blog entry with the basics. Also a thanks to the Microsoft Office Blog Team for their detailed look at MDM policy setup.
If your company is using Office 365 or has a Bring Your Own Device (BYOD) policy which need mobile device management, then contact us for assistance.

Create Office 365 Shared Calendars

Often when migrating a client from on-premise Exchange server to the Office 365 platform, the company will have an Exchange pubic folder shared calendar or two that are used for various reasons. Here is the steps for creating the new kind of Office 365 shared calendars:

Creating a Public Folder Mailbox

1. Open the Office 365 portal with an administrative user
2. Open the Admin panel
3. Open the Exchange Admin panel
4. Click on Public Folders, then on the Public Folder Mailboxes
5. Click on the + symbol then give the new Public Folder Mailbox a name and click Save

Creating the Root Public Folder

1. Still in the Public Folders section click on Public Folders at the top
2. Click on the + symbol then give the new Public Folder Mailbox a name and click Save
3. Click on the new Public Folder then on the right hand side click on Manage under Folder permissions
4. Add all administrator users to the Folder Permissions

Creating the Shared Calendar Public Folder

1. Open Outlook on administrative users workstation who will be the "Owner" of the folder
2. Click on Folders at the bottom and expand into the new root Public Folder
3. Right click on the root and choose Add New Folder
4. Give it a name and choose Calendar Items under folder contains then click OK
5. Right click on the new Public Calendar click on Properties then on Permissions tab
6. Add all users who will be accessing the calendar and appropriate permissions for them

Adding the Calendar folder to Outlook

1. Open Outlook on each users workstation
2. Click on Folders at the bottom and expand into the new Public Calendar
3. Right click on the Public Calendar and choose Add to Favorites which then makes it listed under their calendar tab.

If your company is migrating from on-premise Exchange to Office 365 or are in need of an Office 365 Shared Calendars setup, then contact us for assistance.

Office 365 Email Distribution Group

Had a client that was using Office 365 Directory Synchronization (DirSync) to manage their users / groups in Office 365 via the local Active Directory which meant that there was not end-user manageability of those groups. A user asked to have a new email distribution list created that they could manage, so performed the following to make that happen:

Create an Office 365 Email Distribution Group

1. Open Active Directory Users and Computers.
2. Navigate to where in the hierarchy that the Distribution Group will be created.
3. Right click on the Organizational Unit where it is to be created and choose New then Group.
4. Give the Group a name and leave the default Group scope of Global and change Group type to Distribution then click OK button.
5. Double click on the new group to open it. Type in the email address to use then click on the Attribute Editor tab.
6. Scroll down and double click on the proxyAddresses item. Add the email in the format SMTP:[username@domain.com] then click on the Add button and OK button.
7. Click on the Managed By tab and click on the Change button to search for the user who will be the group administrator.
8. Click OK button then run a manual DirSync to send the changes to the cloud.
9. Open the group administrators Outlook.
10. Click on the Address Book button.
11. In the Address Book drop down list choose the Global Address Book (this may take some time to download the update).
12. Find the newly created Distribution Group and double click to open then click on the Modify Members button to add users.
If your company is using Office 365 and needs end users to manage their Office 365 Email Distribution Group, then contact us for assistance.

Archives

Categories

Plant a Seed @ 541-761-9549
233 Rogue River Hwy #873 Grants Pass, OR 97527
Mon-Fri: 9:00am-5:00pm
support@farmhousenetworking.com
© 2016-2026 - Farmhouse Networking. All rights reserved
Terms and Conditions Privacy Policy

Evaluation Signup

Error: Contact form not found.

And God will generously provide all you need. Then you will always have everything you need and plenty left over to share with others. As the Scriptures say,
“They share freely and give generously to the poor. Their good deeds will be remembered forever.”
For God is the one who provides seed for the farmer and then bread to eat. In the same way, he will provide and increase your resources and then produce a great harvest of generosity in you. - 2 Corinthians 9:8-10