User Profile
Ivarious90
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Re: Exchange 2013 -> Hybrid migration to EXO
Simo_baz elieelkarkafi Thanks for the quick responses! So first upgrade and migrate to Exchange 2019 and then to EXO. The goal is to completely remove the on-prem Exchange environment. Is it also possible to install only new Exchange 2019 VM. Make it a member of the current Exchange 2013 and run the Hybrid setup on the Exchange 2019? Then migrate the mailboxes to EXO and then uninstall the on-prem environment? Thank you in advance again!1.6KViews0likes2CommentsExchange 2013 -> Hybrid migration to EXO
Hi all, We have 2 Exchange 2013 servers with a DAG group configured. We would like to migrate to Exchange Online. As we know the Exchange 2013 is end-of-life. Can we still configure the HCW or do we receive errors or is this still possible?1.7KViews0likes5CommentsSet password policy (with hybrid sync to M365 enabled)
Hi there, We have an on-premise environment with the users synced to Azure AD (by using Azure AD Connect). MFA+SSPR is configured and users are used to work with it. Traditional, the AD password policy settings in the default domain policy have the following settings: Enforce password history 3 passwords remembered Maximum password age 0 days Minimum password age 0 days Minimum password length 6 characters Password must meet complexity requirements Disabled The management wants to tighten the password policy by setting the following; Enforce password history 3 passwords remembered Maximum password age 60 days Minimum password age 0 days Minimum password length 10 characters Password must meet complexity requirements Enabled When I change this setting now, I suppose everyone in the organization is forced to change their password immediately (because we change the maximum password age value from 0 to 60). Besides this; I would like to know your thoughts on this (2022 wise). Because M365 don't require to change passwords by default.... Thanks in advance!1.3KViews0likes0CommentsMove on-prem environment to Azure migration
Hi there, I'm working on a customer with a traditional Windows AD domain. The customer wants to have all their Windows VMs (now running on VMWare) to Azure. For the clients we recently managed to make all devices Azure AD Joined only. M365 suite is used for Teams/SharePoint/ExchangeOnline, Defender for endpoint and Endpointmanager for client management. We have no domain joined computers anymore. All the users are still in Azure AD Connect that syncs to Azure AD. Printers are on universal print and files to Teams/SharePoint. We now have a large file share that we could not migrate to sharepoint. We would like to have this on Azure Files. Right now we are in the start of creating an Azure subscription. What should be the best route to take for this? On-prem there are a couple Windows (apps) VMs that we would like to 'lift and shift' to Azure. These app servers are used for legacy/history checking... If there is any clear path or documentation that we can consult, would like to know. Thanks in advance!3.6KViews0likes3CommentsRe: Autodiscover (public) DNS record in hybrid setup [Public Folders]
ThomasStensitzki-MVP As soon as all client components that require AutoD are migrated to EXO, you can change the external DNS to use the EXO CNAME target. -> Clear, thanks Does EXO reference the on-premises public folder hierarchy as "external" and do EXO users have access to that hierarchy? In that case, you cannot change the external AutoD DNS resource record. -> How can I check this? When I'm in outlook and navigate to the public folder structure, I see Public Folders - email address removed for privacy reasons. For the migration I found this: https://docs.microsoft.com/en-us/exchange/collaboration-exo/public-folders/batch-migration-of-legacy-public-folders 2 of my public (root) folders are 100GB+. These are 2 root folders but have lots of sub folders.... Everyone in the organization have access to this folders (+/- 100 users). What is the best way to migrate these? (I already asked to clean-up the folders, but they have to keep this data..)1.3KViews0likes0CommentsAutodiscover (public) DNS record in hybrid setup [Public Folders]
Hi all, We have a client with an Exchange 2013 hybrid setup. All the mailboxes are already in O365 (for already 2 years). I see that the autodiscover record is still pointed to the on-prem Exchange server instead of M365. Can we safely change this from on-prem to M365? The only thing the Exchange 2013 server is used for are the public folders. The company have 2 'large' email folder (100GB+). Core question is; can we safely change the autodiscover record from on prem to M365 (or what things should we consider)? And if someone have a good idea for the public folders so we can phase out the old Exchange 2013 environment, we would like to know 🙂 Thanks in advance!1.4KViews0likes2CommentsRe: Setup Exchange 2013 hybrid environment
We had an internal discussion and would like to set the Exchange 2013 in Hybrid. Migrate all the mailboxes etc. to Exchange Online. After that we would like to upgrade the Exchange 2013 (hybrid) environment to Exchange 2019 (hybrid). Is this a supported and possible option? In this case we don't need to have 2 mailbox migrations but 1 instead. Would like to know your thoughts on this. Thanks!1.9KViews0likes3CommentsRe: Setup Exchange 2013 hybrid environment
oliwer_sundgren Thanks for your awnser Oliwer! Then we go for a new Exchange 2019 Server solution with the hybrid connection. Is there (best practice) documentation/implementation steps to add a new Exchange 2019 server to an existing environment? Anything you could recommend in this? Thanks in advance!1.9KViews0likes4CommentsSetup Exchange 2013 hybrid environment
Hi there, We have an on-premise Exchange 2013 server and would like to migrate to Exchange Online. We have an internal discussion if we first must migrate the current Exchange 2013 to Exchange 2019 and then setup the hybrid environment to Exchange Online or just go with Exchange 2013 and setup hybrid directly. After the Exchange Online migration we would like to keep the on-premise server as administration server. We would like to know what is the best approach for this. Thanks in advance!2.1KViews0likes6Comments
Recent Blog Articles
No content to show