37 C
Dubai
Sunday, May 4, 2025
Home Blog Page 81

How to Create Internet Calendar sharing in Exchange 2013 with Gmail (Non-Exchange Organizations )

Sharing Calendar to other Exchange Organizations or Office 365 . We would share using Organizational Relationships

if we need to share our Exchange 2013 Calendar to Non-Exchange Organizations like gmail or zimbra.

Or we need to have public calendars for our organizations in the internet . which his accessible via URL.

We can use sharing policies to achieve it . Let see how to achieve this .

image

Step 1 :

Note: This is done on Mailbox Servers

First we need to Make sure InternetWebproxy URL’s have been set in Exchange 2013 Servers

To Check The status of the URL’s

Get-ExchangeServer | fl inter*

image

To Set InternetWebProxy URL’s

Get-ExchangeServer | Set-ExchangeServer -InternetWebProxy https://mail.careexchange.in/owa

image

 

Step 2 :

Now Make sure OWA external URL is set . And CalendarEnabled is set to True

Get-OwaVirtualDirectory | fl Externalurl,CalendarEnabled

image

 

Now to set OwaVirtualDirectory ExternalUrls use the below shell command.

Set-OwaVirtualDirectory -Identity "CAS01" -ExternalUrl "<URL for CAS01>" -CalendarEnabled $true

Step 3 :
We need to create a sharing policy in order to allow anonymous calendar sharing
Its always recommended to create a new sharing policy . So that we can customize the policy as per our wish . when its required.
To Create New Sharing Policy 

New-SharingPolicy -Name "Internet" -Domains 'Anonymous: CalendarSharingFreeBusySimple' -Enabled $true

Note:
Sharing policies have below options where we can have different type of customizations to specific domains .
-Domains
  • CalendarSharingFreeBusySimple   Share free/busy hours only
  • CalendarSharingFreeBusyDetail   Share free/busy hours, subject, and location
  • CalendarSharingFreeBusyReviewer   Share free/busy hours, subject, location, and the body of the message or calendar item
  • ContactsSharing   Share contacts only
'Contoso.com: CalendarSharingFreeBusySimple', 'Fabrikam.com: CalendarSharingFreeBusyDetail, ContactsSharing'

image
By Default AnonymousFeaturesEnabled is set to True. you can cross check it .
Get-OwaVirtualDirectory | fl anon*
image

Note : if you don’t want to create a new sharing policy and want to mess up with the default  policy

Run

Set-SharingPolicy -Name "Default Sharing Policy" -Domains 'Anonymous: CalendarSharingFreeBusySimple' -Enabled $true

Step 4 :
Apply the newly Created Sharing policy on the mailbox which needs this feature

Set-Mailbox CEO -SharingPolicy Internet

Now Login to OWA of CEO

Choose Calendar – Choose Share
image
Enter the Gmail Address or any non exchange organization email address
image

Now the other End .We have got the details of this calendar .
image

Now the calendar is visible via URL in browser
image

It can be added to Gmail .
Sample URL
webcal://mail.careexchange.in/owa/calendar/f50971bcbb3f48aa9a3ed2ea3b4c61c7@careexchange.in/c52ec0559e1b42f1a91cc3443faea4196601531922852437333/S-1-8-3585576920-3738051497-2994629991-3072103521/reachcalendar.ics

 

 

 

 

 

 

 

 

image

Note these URL’s can be used from Outlook as well .

image

 

 

 

 

Hope you have found this article useful .

Thank you .

Quick Tip – Purpose of Microsoft Exchange Shared Cache Service

image

 

Microsoft Exchange Shared Cache Service is not used by any Exchange 2013 Component currently .  (This is true till Exchange 2013 CU 5)

Service is available now . Just to meet future Architecture requirements

Purpose – Service will eventually improve overall system performance through caching of system information

Exchange Server 2013 Cumulative Update 5 Released

image

 

Fixes / Improvements  –

*Improvements to OAB management for distributed environments
*Frequently restarting the Microsoft Exchange Shared Cache Service

Note :

The Microsoft Exchange Shared Cache Service is a new service that is added to Exchange Server 2013 Cumulative Update 5 to meet future needs of the product.

 

Download Link –

http://www.microsoft.com/en-us/download/details.aspx?id=43103

How to Configure Check_mk monitor with Exchange 2013

Had to work with a Open Source monitoring tool. and they want to monitor Exchange 2013 using it .

Which is Called as Check_mk Monitoring

Below Link shows up their open source monitoring website.

http://mathias-kettner.de/check_mk.html

Downloaded their Check_mk agent  and installed in Exchange 2013 Servers

Download link for Check_mk agents for windows

https://mathias-kettner.de/check_mk_download.html

Download the Scripts

Basic Exchange 2013 Scripts for Check_mk

In your Exchange 2013 Mailbox Server

Note – These Exchange 2013 servers are on DAG.

###############
Place .bat files  –

ExchangeHealth.bat
MailQueueHealth.bat

In this location
C:\Program Files (x86)\check_mk\local

##################
Place .ps1 files –

ExchangeHealth.ps1
MailQueueHealth.ps1

Note : Create a folder called scripts – if it doesn’t exist

In this location
C:\scripts

Now login to Monitoring

Select the host – Click on WATO

image

Choose Services

image

 

Click on Full SCAN and Click on Activate Missing

 

Now Monitor would show . Feel free to open the Mail Queue script and set the limits as per your wish.

image

 

Note : Make sure your Execution Policy is set properly on your machines.

For Example to set to Unrestricted – Set-ExecutionPolicy Unrestricted

Exchange 2013 Transport Service is not starting–1067 Error

Exchange 2013 Transport Service doesn’t want to start after server restart.

Windows could not start the Microsoft Exchange Transport service on Local Computer.

Error 1067 The process terminated unexpectedly.”

image

  • Tried putting the Transport Service logon to Local account . No Luck
  • Placed logon back to “Network Service” .No Luck
  • Tried Running Get-Receiveconnector
  • Saw two mysterious connectors in the End

image

Logged in to EAC – Exchange admin center.

Saw that Receive connectors have been created on HubTransport instead of FrontEndTransport

Solution –

Change the Transport role TYPE from HubTransport to FrontendTransport

Set-ReceiveConnector –Identity “EXCH\RELAY” –TransportRole FrontendTransport

Or

Disabled them.

image

Now  able to start Microsoft Exchange Transport Service.

Reference Events –

Log Name: Application
Source: MSExchange Common
Date: 1/24/2015 10:34:29 AM
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Watson report about to be sent for process id: 9280, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, MSExchangeTransport, M.Exchange.Net, M.E.P.WorkerProcessManager.HandleWorkerExited, M.E.ProcessManager.WorkerProcessRequestedAbnormalTerminationException, 5e2b, 15.00.0847.030.
ErrorReportingEnabled: False

Log Name: Application
Source: MSExchange TransportService
Date: 1/24/2015 10:34:29 AM
Event ID: 1046
Task Category: ProcessManager
Level: Warning
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Worker process with process ID 18316 requested the service to terminate with an unhandled exception.

Log Name: Application
Source: MSExchangeTransport
Date: 1/24/2015 10:34:29 AM
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running properly.

Microsoft Exchange 2013 Storage Drives – SMR or PMR…?

Exchange 2013 with regards to storage requirement the focus on choosing the drives is more on getting larger than faster. Exchange 2013 has significantly improved the IOPS requirement as compared to Exchange 2003/2007/2013 over a decade with architectural database changes in the product.

 

Storage

 

There was a constraint from the very beginning on choosing the right storage with drives to deliver required IOPS towards performance of the Exchange, over a decade due to the rapid development in the IT industry regards to storage the Exchange DB architecture has also adjusted to support different storage types and drives.

 

With Exchange 2010 the recommendation was cheap JBOD and multiple databases copies for high availability.  Preceding its lower version and due to the enhanced improvement in architectural changes not only the IOPS numbers is reduced but also the same recommendation follows as JBOD with minimum 7200 RPM disks. Because of this enhanced features in Exchange 2013 like diagnostic loggings / other loggings / current mailbox size trends(50GB min.) the need for the storage space on Exchange Server is in huge demand.

 

Due to the development in storage technologies I would like to highlight two type of drives which are of an interest to known by Exchange Admin/Consultant/Architectures.

 

 

PMR

 

PMR drives has already replaced the LTR drives to meet the increasing demand of storage and performance due to which we’ve been seen seeing the recommendation with Exchange 2010 & 2013 to go with JBOD having minimum 7200 RPM disks as tested. You can have more and more information on the technology how it works

Well here is the animation clip which explains what is PMR, that was fun to see and hear 🙂

 

Perpendicular Magnetic Recording

 

SMR Drives – Shingled Magnetic Recording

SMR

 

The drives getting larger but not faster, Shingled Magnetic Recording (SMR) was named after roof shingles.

With this type of drives the capacity is in huge but with the performance degrade. The Exchange database read/write architecture doesn’t work well the SMR drives and with Jetstress results shared from MEC video there is ~80 reduction in the IO performance. It places constraints on data flow onto disk that are incompatible with the current HDD usage and hence internal HDD data architecture must be changed or operating system modified. Check out the video explaining SMR mentioned below.

 

Shingled Magnetic Recording

 

So in short SMR disk aren’t supported for Exchange Server or neither MS SQL, so keep in mind while choosing the right supported HDD types to not only focusing larger disk but as faster(performance).

× How can I help you?