Skip to content
Lambert Consulting

Artificial Intelligence: A Cross-Functional Offering

Results first. Infrastructure second.

An assistant for your documents, end-of-line verification, a platform for multiple services. Where artificial intelligence is applied is determined by your data, not by a catalog.

See all solutions
4Comparing Architectures, Criterion by Criterion
2 fieldsSoftware and hardware under one roof
All Use CasesUse cases first, technology last

Our first department

This is what needs to work every morning.

Your servers, your workstations, your phone systems, and your identities. The foundation that no one notices as long as it holds, but that everyone notices the day it fails.

View the department
Multi-siteNational and international projects
3Branches in French-speaking Switzerland
View our client projectsCase Studies and References
Let us know how you're doingGetting a quote is free

How We Work

A piece of advice, not a sales pitch.

Our approach is consultative: we tell you what we think, even when it’s not in our best interest. That’s what makes projects succeed.

About Us
1995First project, using Microsoft SMS
Family-orientedOn a human scale and sustainable

Our Branches

Vaud, headquarters9 Avenue des Baumettes, 1020 Renens+41 21 806 37 15
Valais134 Oscar-Bider Street, 1950 Sion+41 27 552 00 22
FribourgChemin de Montmoirin 18a, 1618 Châtel-Saint-Denis+41 26 322 59 05
Monday through Friday8:00 a.m. – 6:00 p.m.
Contact UsFirst 30-minute consultation, with no obligation
Publication Date
1 minReading time
Microsoft 365 and collaborationBlog Archive

I hope you are familiar with Exchange Preferred Architecture (PA). In short it , which is Microsoft’s recommendation on how clients should deploy Exchange. There is a PA for Exchange 2016 and another for 2019. PA is quite controversial, because it assumes physical commodity servers with built-in disks (DAS and without SAN), while many companies have invested heavily in SAN and virtualized environments and now believe that the days of physical servers are over. The second surprise is that PA does not require backup Exchange databases; instead, it , relies on massive redundancy and delayed copies of the data.

As Microsoft consultants, we usually mention PA, but in reality—with few exceptions—we would implement virtualized Exchange farms protected by enterprise- Backup systems such as Veeam or NetBackup.

Here are the references to Exchange 2016 PA: https://blogs.technet.microsoft.com/exchange/2015/10/12/the-exchange-2016-preferred-architecture/

And Exchange 2019 PA: https://docs.microsoft.com/en-us/exchange/plan-and-deploy/deployment-ref/preferred-architecture-2019?view=exchserver-2019

The change between two version can be shortly described as adding planning support for SSD and bigger RAM, CPU.

While we're on the subject of Exchange 2019, we’d like to mention that the UM "Role" (voicemail for Skype) feature was removed in this version. If you need voicemail and do not have Cloud Voicemail, you should keep Exchange 2016.

Microsoft Exchange 2019
After reading

What an article Can't Know

An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.

You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.

If the topic has changed

Check what is still true

Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.

Search for a topic in the blog