Loading ...

Category: Email

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.

Exchange User Calendar Adding Permissions

Had a request to allow all users access to the new hires Exchange user calendar and some researched determined that this was not a job for the Exchange Managememt Console GUI. Instead it required a bit of PowerShell scripting to get the job done. It is best to run Get-MailboxDatabase before editing the script to retrieve the [Database Name] and [Username]. Here is the final product for accomplishing this task:

Add Exchange User Calendar Permissions via Powershell

$mailboxes = Get-Mailbox -Database “[Database Name]”
$AccessRights = “Reviewer”
$newusername = “[Username]”

foreach ($mailbox in $mailboxes) {

$calendar = (($mailbox.SamAccountName)+ “:\” + (Get-MailboxFolderStatistics -Identity $mailbox.SamAccountName -FolderScope Calendar | Select-Object -First 1).Name)

Write-Host “Updating calendar permission for $mailbox…” -ForegroundColor Yellow

add-MailboxFolderPermission -User $newusername -AccessRights $AccessRights -Identity $calendar

}

If your company is using on-premise Microsoft Exchange User Calendar or needs any help migrating to Office 365, then contact us for assistance.

Test SMTP Connectivity via Telnet

Had issues recently with another tech setting up a SMTP relay to Google Apps that didn’t work correctly and during the process of correcting their setup there came a need to test SMTP connectivity. Time to use a telnet connection to the SMTP server over port 25 method to test via my favorite telnet/ssh/console program PuTTY:
1. Open PuTTY and type in the Host Name of the SMTP server.
2. Choose Connection type of Telnet and change the Port to 25 then click the Open button.
3. Type EHLO [hostname] and then press ENTER.
4. Type MAIL FROM:[authorizeduser@domain.com] and then press ENTER.
5. Type RCPT TO:[anotheruser@domain.com] and then press ENTER.
6. Type DATA and then press ENTER. You will receive a response that resembles the following:

354 Start mail input; end with .

7. Type Subject: [Test Subject] and then press ENTER.
8. Press ENTER. RFC 2822 requires a blank line between the Subject: header field and the message body.
9. Type [Test Message Body] and then press ENTER.
10. Press ENTER, type a single period character and then press ENTER. You will receive a response that resembles the following:

250 2.6.0 Queued mail for delivery

11. To disconnect from the destination SMTP server, type QUIT and then press ENTER. You will receive a response that resembles the following:

221 2.0.0 Service closing transmission channel

12. Check the [anotheruser@domain.com] mailbox to see if the message arrived successfully.

This allows testing of the connection without end user intervention or the creation of a test account to send from. If there is SMTP authentication or encryption then there are other commands that will need to be entered.
If your company is in need of help troubleshooting or needs to test SMTP connectivity on your email servers, then contact us for assistance.

Google Apps SMTP Relay

Install Windows Server 2012 SMTP Relay Feature

1. Login as an administrator.
2. Go the the start screen and type “Server Manager”. Click on Manage and choose “Add roles and Features”.
3. Click “Next >” (Check the box to skip this in the future)
4. Make sure “Role-based or feature-based installation” is selected then click “Next >”
5. Choose the appropriate server then click “Next >”
6. Make no changes to the “Roles” page then click “Next >”
7. On the “Features” page scroll down and check the box by “SMTP Server”
8. Click “Add Features” (required for SMTP Server) then click “Next >”
9. Click “Install” then wait for the install to finish then click “Close”.

Configure Windows Server 2012 Google Apps SMTP Relay

1. Go the the start screen and type “Server Manager”.
2. In the Tools menu select “Internet Information Services (IIS) 6.0 Manager”
3. Expand the tree until [SMTP Virtual Server #1] is shown then right click and choose “Rename” (as appropriate)
4. Right click again and choose “Properties”.
5. Click on the “Access” tab then click the “Connection…” button
6. Select “All except the list below” then click “OK”
7. Click on the “Relay…” then select “All except the list below” then click “OK”
8. Click on the “Delivery” tab then click the “Outbound Security” button
9. Select “Basic Authentication” and type in the username and password of Google Apps user
10. Check “TLS encryption” then click “OK”
11. Click the “Outbound connections” button then change “TCP port” to 587 then click “OK”
12. Click the “Advanced” button then fill in the FQDN of the internal server (add custom DNS for future changes)
13. Fill in “Smart host” with SMTP.gmail.com – the name of the Google Apps SMTP server then click “OK” twice

Warning! You have an open relay now. Use this setup to check the email notification system. When you see it’s fully functional go back to the “Access” tab and narrow down the “Connection” settings to the necessary systems. When no other system needs to relay, just check “Only the list below” and grant “127.0.0.1” access.

Configure Google Apps SMTP relay service

1. Login to Google Apps Admin Console
2. Click on Apps
3. Click on Google Apps
4. Click on Gmail
5. Click on “Advanced settings >>”
6. In “Search settings” type SMTP relay then click the Configure button
7. Give the relay a name
8. Leave the “Only registered Apps users in my domains” option set
10. Select “Require TLS ecryption”
11. Click ADD SETTING
12. Click SAVE CHANGES at the bottom right

If your company is using Google Apps and needs a SMTP relay setup for use by a network device like a multi-function printer, then contact us for assistance.

Office 365 / Active Directory User Changes Name

There is often the case that a female user will have a name change due to change in marital status. Here is the basics of how to change their name in both Active Directory and Office 365.

Active Directory User Changes Name objects

  1. Open Active Directory Users and Computers
  2. Find the user needing the changed name, right click on them and choose the “Rename” option.
  3. Change the user’s name as needed then press Enter then in the window that opens make all the further changes needed and click the “OK” button.
  4. Click on the View menu at the top and check the “Advanced Features” option.
  5. Double click on the users new name to open their Properties. Change the email address if needed in the General tab.
  6. Choose the “Attribute Editor” tab, scroll down the list to “proxyAddress” attribute and double click it. Click on the current SMTP:old.email@company.com and click the “Remove” button then change it to a smtp:old.email@company.com then click the “Add” button.
  7. Type in SMTP:new.email@company.com for the user and then click the “Add” button. Click the “OK” button on this window and the one beneath it.
  8. Make sure to also rename the users Redirected Folder if there is one created via Group Policy
  9. Run a manual sync of the DirSync tool via the Microsoft Forefront Identity Manager console.

Changes to Office 365

  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 to change the username for login to Office 365:

    Set-MsolUserPrincipalName -UserPrincipalName old.email@company.com -NewUserPrincipalName new.email@company.com

  9. Login to the portal as administrator and make sure the changes have take effect.

If your company has an Active Directory user changes name in your domain or Office 365 user changes name, then contact us for assistance.

Problems Reinstalling Office 365 DirSync

This has happened to me countless times in the field and it is time to write up the process on my own. Either the client has an older version of the DirSync tool installed or there is some sort of errors that require reinstalling Office 365 DirSync. Special thanks go to Joseph Turley for the original write up on which this is based.

Uninstall Old AADSync Tool

If the server is running an older version of AADSync then below is a list of applications that are to be removed:

  • Microsoft Azure AD Sync
  • Microsoft Online Services Sign-in Assistant [Restart is required]
  • Forefront Identity Manager Windows Azure Active Directory Connector

There should then be a reboot of the server to finish these uninstallations. Additionally, the Azure AD Sync Scheduler scheduled task needs to be removed from the Task Scheduler to complete the removal of AADSync. There are also several user accounts in Active Directory Users and Computers that will need to be removed either titled something like “AAD…” or “ADSync…” for the reinstall to work properly. Also need to remove the folders named something like “C: > Program Files > Microsoft Azure AD…” before attempting to start the new installer. There might also be some leftovers in the registry that need to be removed as follows:

  • HKEY_CLASSES_ROOT\TypeLib\{1EE655FB-EC8A-4CFE-BFE7-E8D46BC87B6A}
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AD Sync
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Local DB
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOLCoExistence
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MicrosoftAzureADConnectionTool
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{0311B5B5-B05D-47A0-89D8-98AED5A0D204}
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Azure AD Sync Scheduler
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Application\AzureActiveDirectoryDirectorySyncTool
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\DirectorySyncTool_RASAPI32
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\DirectorySyncTool_RASMANCS

Uninstall Newer DirSync Tool

If the server is running a more current version of DirSync then below is a list of applications that are to be removed:

  • Windows Azure Active Directory Sync Tool
  • Microsoft Online Services Sign-in Assistant [Restart is required]
  • Forefront Identity Manager Synchronization Service

There should then be a reboot of the server to finish these uninstallations. There are several user accounts in Active Directory Users and Computers that will need to be removed either titled something like “AAD…” or “ADSync…” or “FIMSync…” for the reinstall to work properly. Also need to remove the folders named something like “C: > Program Files > Windows Azure…” and the database files located in a folder named something like “C: > Program Files > Microsoft SQL Server > MSSQL**.MSONLINE > MSSQL > DATA > FIMSync…” before attempting to start the installer.

Reinstalling Office 365 DirSync Tool

  • Log into the customer’s Office365 portal as a global administrator.
  • Click on the Admin tile
  • Click on the Users item in the left pane to expand it then click on Active Users
  • At the top of the main pane next to “Active Directory synchronization:” click on Manage
  • Make sure the at Active Directory synchronization is activated
  • Download the Directory Sync tool by clicking on Download button
  • Double click the installer
  • Type in your Office365 global administrator credentials then click “Next >” button
  • Type in your domain administrator credentials then click “Next >” button
  • Ignore the page on Hybrid and click “Next >” button
  • Make sure the box next to Active Directory Password Sync is checked and then click “Next >” button
  • Click on Install then on Finish to complete the install

Another handy thing to do after the installation is complete is to make a shortcut on the desktop for the miisclient software that monitors the sync process. It is located at “c: > Program Files > Windows Azure Active Directory Sync > SYNCBUS > Synchronization Service > UIShell > miisclient.exe” (this also allows for manual syncs when needed).
If your company needs help reinstalling Office 365 DirSync or help setting up Active Directory Password Sync for single sign-on, then contact us for assistance.

Outlook Anywhere / Outlook via Proxy / RPC over HTTP

Apply RPC over HTTP to an existing account

  1. If Outlook is open, close it.
  2. Click Start then click on Control Panel.
  3. If Control Panel is in Category view, click the Switch to Classic View link on the left and then double-click the Mail control panel. If Control Panel is in Classic view, double-click the Mail control panel.
  4. Click on the “E-mail Accounts…” button.
  5. Select Microsoft Exchange (or whatever is was named). Click on the “Change…” button.
  6. Click on the “More Settings…” button. Click the Connection tab.
  7. In the Outlook Anywhere section, check the “Connect to Microsoft Exchange using HTTP” box.
  8. Click on the “Exchange Proxy Settings…” button.
  9. In the “Use this URL to connect to my proxy server for Exchange” box, type the external URL of the proxy server.
  10. Make sure the “Connect using SSL only” box is checked.
  11. Check the “Only connect to proxy servers that have this principal name in their certificate” box.
  12. In the Principle name for proxy server box, type msstd:[external URL] where [external URL] is the external URL of the proxy server.
    Note: Be certain that entries from Step 9 and 12 are correct. Do not have a space before or after the entries. In Step 12, after msstd there is a colon ( : ). It is not a semicolon. The text should be in all lower-case as well.
  13. Un-check the “On fast networks, connect using HTTP first, then connect using TCP/IP” box.
  14. Check the “On slow networks, connect using HTTP first, then connect using TCP/IP” box.
  15. At the bottom of the dialog box, in the Use this authentication when connecting to my proxy server for Exchange list, change the setting from NTLM Authentication to Basic Authentication instead.
  16. Click OK. Click Apply. Click OK. Click Next. Click Finish.
    Note: If you get “stuck” at the above step and can’t go forward, you need to double-check the settings in the settings in the Exchange Proxy Settings dialog box.
  17. Open Outlook. You will be prompted for a User name and password.
  18. In the User name box, type: [domainname]\ where [domainname] is the internal domain name of the network and then username. (i.E. FHN\Administrator)
  19. Enter the password for the account. Click OK. In some cases, you may be prompted for the password a second time, please enter it.
  20. Outlook should open normally. You’re done.

If your company is using internal Microsoft Exchange servers and need help configuring Outlook Anywhere via RPC over HTTP, then contact us for assistance.

Configure Server 2012 Office 365 SMTP Relay

Install Windows Server 2012 SMTP Relay Feature

  1. Login as an administrator.
  2. Go the the start screen and type “Server Manager”
  3. Click on Manage and choose “Add roles and Features”.
  4. Click “Next >” (Check the box to skip this in the future)
  5. Make sure “Role-based or feature-based installation” is selected then click “Next >”
  6. Choose the appropriate server then click “Next >”
  7. Make no changes to the “Roles” page then click “Next >”
  8. On the “Features” page scroll down and check the box by “SMTP Server”
  9. Click “Add Features” (required for SMTP Server) then click “Next >”
  10. Click “Install” then wait for the install to finish then click “Close”.

Configure Windows Server 2012 SMTP Relay

  1. Go the the start screen and type “Server Manager”.
  2. In the Tools menu select “Internet Information Services (IIS) 6.0 Manager”
  3. Expand the tree until [SMTP Virtual Server #1] is shown then right click and choose “Rename” (as appropriate)
  4. Right click again and choose “Properties”.
  5. Click on the “Access” tab then click the “Connection…” button
  6. Select “All except the list below” then click “OK”
  7. Click on the “Relay…” then select “All except the list below” then click “OK”
  8. Click on the “Delivery” tab then click the “Outbound Security” button
  9. Select “Basic Authentication” and type in the username and password of Office365 user – this can be different than what is used on the device as long as the alternate address on the device is an alias of this user.
  10. Check “TLS encryption” then click “OK”
  11. Click the “Outbound connections” button then change “TCP port” to 587 then click “OK”
  12. Click the “Advanced” button then fill in the FQDN of the internal server (add custom DNS for future changes)
  13. Fill in “Smart host” with SMTP.office365.com – the name of the Office365 SMTP server then click “OK” twice

Warning! You have an open relay now. Use this setup to check the email notification system. When you see it’s fully functional go back to the “Access” tab and narrow down the “Connection” settings to the necessary systems. When no other system needs to relay, just check “Only the list below” and grant “127.0.0.1” access.

Configure External DNS for SPF protection

Go to the domain registrar’s website to update DNS records. Edit / create a sender policy framework (SPF) record. In the entry, include the external IP address. The finished string looks similar to this, where 10.0.0.2 is your public IP address:

v=spf1 ip4:10.0.0.2 include:spf.protection.outlook.com ~all

Note:
Skipping this step might cause email to be sent to recipients’ junk mail folders.
If your company is using Office 365 and needs an Office 365 SMTP relay setup for use by a network device like a multi-function printer, 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-2024- Farmhouse Networking. All rights reserved
Terms and Conditions Privacy Policy

Evaluation Signup

[contact-form-7 id="452" title="Free Network Evaluation"]
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