Tag: Exchange

Exchange Sizing Calculator & Backup Configuration

I see a lot problems with to small log disks. Sizing Exchange is a very imported thing!! Today there a lot of problems with Thiry-Party Devices. They can create a lot of log files if you run a oudated Exchange Server. Transaction logs are truncated when backup software successfully backs up an Exchange server. The ‘Backup/Truncation Failure Tolerance’ field in the Backup Configuration section, allows a value to be set that specifies how much capacity will be available for logs in the event of backup failures or issues with Thirth party devices. The default value is 3 days. Change This!! This ensures that the server will continue to function and you have the ability to restore from transaction logs for x days, if the backup fails & and if some thirth party device give some trouble. Logs disk & backup should be monitored to ensure that they are successful.

Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V2.5

I love Powershell <3.

Configure & maintaining your Exchange 2013 can be a hell… I do the most things with powershell…

I have a lot of standard scripts to configure an Exchange 2013 server or DAG cluster.

So i created a freaky nice script i my say so!! :

Updated to V2.5

Change List:
# V1.0 Begin
# V1.1 Added Some New Options 12-10-2014
# V1.2 Added Hyper-V Best Practise & NTFS Partition Offset
# V1.3 Added KB2995145 .NET Framework 4.5 garbage collector heap Fix
# V1.4 Added Set Minimum Disk Space Warning level (180GB Default CU6 200GB CU5)
# V1.5 Added Some new features
# V1.6 Changed the Layout & Add Move Arbitration Mailbox
# V1.7 Added PST Export & KB2990117
# V1.8 Added Full backup, Database in GB and Mailbox Size in GB Export CSV
# V1.9 Added Outlook AnyWhere & SafetyNetHoldTime
# V2.0 Added Check DatacenterActivationMode, Get-DatabaseAvailabilityGroupNetwork, Add Static Route, Disable Replation Network on DAG, Database Copies Per Volume (AutoReseed)
# V2.1 Added Edge Subscription
# V2.2 Added Check Transaction Log Growth
# V2.3 Changed the Menu to Submenu’s
# V2.4 Added Check Database White Space
# V2.5 Added MAPI HTTP External URL & Fixed some things

Save the Script as configure-Exchange2013.ps1

Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6

Microsoft Ignite first things about Exchange Server v.Next & Skype for Business

Microsoft Ignite will be hell add may 4-8. The session catalog contains 275 sessions, covering products like Exchange (49), Office 365 (85) and Skype for Business (26). It will be the first major Microsoft event where details will emerge on the next version of Exchange, Exchange v.Next.

The next version of Exchange Server is arriving in the second half of 2015. A short heads-up as the session catalog for Microsoft Ignite has been published. So, if you are still undecided or already want to pick ‘must see’ sessions for your schedule, you can check the session catalog here.

I will not attend Ignite. But i hope the sessions wil be publishd on Channel 9 here.

Short List of sessions:
Tools and Techniques for Exchange Performance Troubleshooting
Meet Exchange Server v.Next
Choosing between Server, Online and Hybrid with Skype for Business
Deploying Exchange Server v.Next
Deep Dive into How Microsoft Handles Spam and Advanced Email Threats
Exchange Server Preferred Architecture
Experts Unplugged: New Exchange Scenarios
Exchange on IaaS: Concerns, Tradeoffs, and Best Practices

Moved al mailboxen to Office 365 & Still using dirsync! Can you remove the last Exchange 2010/2013 Server. Yes It Can! Just don’t do it!! You will have a support issue when you have problems!!

After a customer migrated  to Exchange Online some time ago.
They wanted not a hybrid situation. but they are using still DirSync!

After reading: Decommissioning your Exchange 2010 servers in a Hybrid Deployment a I read its not a real problem.

Changed DirSync & After that Uninstalling Exchange 2013 was very easy.

I had only to disable the Arbitration mailboxes: I did that with the following powershell command:

Get-Mailbox -Arbitration | disable-Mailbox -arbitration -RemoveLastArbitrationMailboxAllowed

I did not publish this article because i has still some doubts!!

I had still a question: Do want to remove the last Exchange Server? Have you a supported Environment without a local Exchange Server and still using DirSync??

Yes & No!!

After reading Concerning Trends Discovered During Several Critical Escalations

Microsoft Says:
You may remove the last Exchange Server locale when you move totally to Office 365/Exchange Online, but change Exchange Attribuuts trough ADSI is not supported.

If you don’t have a third party tool for that. The only way is trough ADSI and that is not supported.

My Conclusion:

You have a support issue when you dropped a Call at Microsoft and they investigate your environment.
Don’t remove the last Exchange Server even when all mailboxen exist in Office 365/Exchange Online and keep them up to date!
You can always install a Exchange Server but most of the times it will be always to late!

Public Folder Move Script to Exchange 2013

Move Public Folder script from 2007/2010 to Exchange 2013 Script created by Ward Vissers www.wardvissers.nl

THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER

Please Select the Choice You Want

Prepare for Migration (Legacy Exchange Server)
01) Take a snapshot of the original source folder structure
02) Take a snapshot of public folder statistics such as item count, size, and owner.
03) Take a snapshot of the permissions
04) Locate public folders that have a backslash in the name
05) Rename Public Folder
06) Checks the public folder migration status.
07) Set PublicFolderMigrationComplete to False

Check Exchange 2013
08) Get-PublicFolderMigrationRequest
09) Get-Mailbox -PublicFolder
10) Get-PublicFolder

Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server)
11) Export-PublicFolderStatistics PFSizeMap.csv
12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv

Create the public folder mailboxes on the Exchange 2013 server
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)

Migrating the Public Folders
15) BadItemLimit (Exchange 2007 Only)
16) Migrate Exchange 2010 public folders
17) To verify that the migration started successfully (AutoSuspend is Compleet)

Lock down the public folders on the legacy Exchange server for final migration (downtime required)
18) Lock the legacy public folders for finalization

Finalize the public folder migration (downtime required)
19) Finalize the public folder migration (downtime required)

Test and unlock the public folder migration
20) Add Public Folder to Test User
21) Unlock the public folders for all other users
22) Public Folder Migration Complete (Legacy Exchange Server)
23) Public Folders Enabled Local

Final Check
24) Take a snapshot of the original source folder structure.
25) Take a snapshot of the public folder statistics such as item count, size, and owner
26) Take a snapshot of the permissions

99) Exit

Download the script here: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Move-Script-49126418

Exchange & Patching!!!

Microsoft recommends adopting a software update strategy that ensures all software follows N to N-1 policy, where N is a service pack, update rollup, cumulative update, maintenance release, or whatever terminology is used by the software vendor. Microsoft strongly recommend that our customers also adopt a similar strategy with respect to hardware firmware and drivers ensuring that network cards, BIOS, and storage controllers/interfaces are kept up to date.

Software patching is not simply an issue for Microsoft software. You must also ensure that all inter-dependent solutions (e.g., Blackberry Enterprise Server, backup software, etc.) are kept up-to-date for a specific release as this ensures optimal reliability and compatibility.

Customers must also follow the software vendor’s Software Lifecycle and appropriately plan on upgrading to a supported version in the event that support for a specific version is about to expire or is already out of support.

For Exchange 2010, this means having all servers deployed with Service Pack 3 and either Rollup 7 or Rollup 8 (at the time of this writing). For Exchange 2013, this means having all servers deployed with Cumulative Update 6 or Cumulative Update 7 (at the time of this writing).

For environments that have a hybrid configuration with Office 365, the servers participating in the hybrid configuration must be running the latest version (e.g., Exchange 2010 SP3 RU8 or Exchange 2013 CU7) or the prior version (e.g., Exchange 2010 SP3 RU7 or Exchange 2013 CU6) in order to maintain and ensure compatibility with Office 365. There are some required dependencies for hybrid deployments, so it’s even more critical you keep your software up to date if you choose to go hybrid.

Moving to Office 365/Exchange Online? A good idea?

Reducing IT costs: Especially in challenging economic times, organizations need to cut costs wherever possible—but without reducing capabilities.

Increasing predictability of IT costs: Replacing or upgrading on-premises IT systems can require significant one-time capital expenditures.

Increasing user productivity: Users face growing volumes of email, and need tools to help them manage it more efficiently.
Enhancing collaboration: Increasingly mobile and distributed workers need technology that helps them work together wherever they are.

Reducing IT administration: IT can be stretched thin and spend too much time managing hardware, updates, and upgrades.
Increasing reliability and availability of email: Email is a business-critical application, and many organizations face challenges keeping it running—especially with shrinking IT budgets.

Staying up-to-date with the latest technology: To stay competitive and recruit the next generation of talent, businesses need to have the latest functionality. But, upgrading on-premises software can be a significant undertaking.

1 Simplified Administration

Managing corporate email can be complex. With Exchange Online, many of the most time-consuming tasks are taken care of by Microsoft, including the management of hardware, updates, and upgrades. Additionally, Exchange Online delivers a streamlined administration experience, making it easier for IT administrators to configure and manage email services in ways that benefit the business.

2 Conclusion

The benefits of moving email to the cloud are clear; including lower costs, increased agility, simpler management, and higher-quality services. Exchange Online meets these expectations by delivering a wide-range of features and capabilities that support anywhere access, protection and compliance, and simplified administration.

But now the real world experience with Exchange Online

If your organization is using google DNS servers. You will be redirected to the Exchange Online servers in America not Dublin if you live in The Netherlands.

Exchange Online works the best if you use cached mode.

The Question is do you want is you using Microsoft Remote Desktop Services or Citrix XenDesktop or VMware Horizon (View)

Cached Exchange Mode in a Remote Desktop Session Host environment: planning considerations
Limits to using personal folders (.pst) files over LAN and WAN links.

My Conclusion:
Exchange Online is great for most organizations. Lower costs, increased agility, simpler management, and higher-quality services.

But is your organization using Microsoft Remote Desktop Services or Citrix XenDesktop or VMware Horizon (View). You need think twice for you migrate.

As IT admin you don’t want ost files locally on Remote Desktop or XenDesktop or VMware View Servers & Desktops or on your file server.

Saving money can mean angry & complaining customers….

Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V2.2 Added Check Transaction Log Growth

I love Powershell <3.

Configure & maintaining your Exchange 2013 can be a hell… I do the most things with powershell…

I have a lot of standard scripts to configure an Exchange 2013 server or DAG cluster.

So i created a freaky nice script i my say so!! :

Updated to V2.2 Added Check Transaction Log Growth
Configure-Exchange2013

Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6

Exchange 2013 Managed Availabilty and why do I need 200GB free space

I  like the Managed Availability and the “self healing” aspect of Exchange 2013.
But about SpaceMonitorLowSpaceThresholdInMB is nothing about to read. 

If you check your serverhealt with:
get-serverhealth -identity servername -HealthSet Diskspace | ? AlertValue -ne unHealthy | ft -autosize

You can get lots of Databases which are in an unhealthy state because the LowLogVolumeSpaceMonitor is configured to check if you have 200 GB of free space. That would be an great idea, if you have a large organization and you have lots of disks whith a huge amount of free space. But in smaller company it would be great to change this value.

With Exchange 2013 SP1 you should now be able to configure this. Go to all of your Mailbox Servers and in regedit go to the following path:

HKLM\Software\Microsoft\ExchangeServer\v15\ActiveMonitoring\Parameters

If you have an DWORD called SpaceMonitorLowSpaceThresholdInMB then you’re lucky. If not, create a DWORD with the name and then you can change it to an Value which suits you more. But, as the dword is mentioning, its in MB not GB 😉

Updated 15-03-2015

No Reg Setting but Add-GlobalMonitoringOverride is better!!

SpaceMonitorLowSpaceThresholdInMB.ps1
write-host = “Default 175GB CU7”
$diskspace = Read-Host ‘What is the Minimum Free Disk Space in MB?’
Add-GlobalMonitoringOverride -Item Monitor –Identity MailboxSpace\StorageLogicalDriveSpaceMonitor -PropertyName MonitoringThreshold -PropertyValue $diskspace

Exchange Administrator’s toolkit

There are lots of tools for Exchange Server available, you can find most of them at the Exchange Server Wiki (some of the tools listed are for previous versions of Exchange).

Here is a short selection from the vast collection available:

Translate »