Home

Regional settings default setting for all mailboxes

%3CLINGO-SUB%20id%3D%22lingo-sub-63887%22%20slang%3D%22en-US%22%3ERegional%20settings%20default%20setting%20for%20all%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-63887%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20command%20to%20run%20to%20set%20all%20my%20current%20migrated%20mailboxes%20in%20the%20cloud%20to%20the%20correct%20timezone%20but%20that%20only%20seems%20to%20apply%20to%20all%20current%20existing%20mailboxes.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20use%20the%20%22%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd351103(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-MailboxRegionalConfiguration%3C%2FA%3E%22%20command%20then%2010%20minutes%20create%20a%20new%20user%20then%20I%20need%20to%20run%20the%20command%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20set%20a%20permanent%20default%20rather%20than%20having%20to%20run%20the%20powershell%20over%20and%20over%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-64776%22%20slang%3D%22en-US%22%3ERe%3A%20Regional%20settings%20default%20setting%20for%20all%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64776%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-63902%22%20slang%3D%22en-US%22%3ERe%3A%20Regional%20settings%20default%20setting%20for%20all%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-63902%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20just%20one%20of%20the%20examples%20why%20many%20companies%20use%20%22mailbox%20provisioning%22%20scripts.%20Other%20examples%20include%20disabling%20protocols%20(POP%2FIMAP%20usually)%2C%20configuring%20quotas%2C%26nbsp%3Benabling%20Auditing%2C%20even%20putting%20mailboxes%20on%20hold.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20might%20consider%20adding%20this%20as%20a%20step%20in%20your%20provisioning%20workflow%2C%20or%20simply%20scheduling%20a%20task%20that%20runs%20PowerShell%20to%20periodically%20update%20mailbox%20settings.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-63892%22%20slang%3D%22en-US%22%3ERe%3A%20Regional%20settings%20default%20setting%20for%20all%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-63892%22%20slang%3D%22en-US%22%3E%3CP%3ENo%2C%20there%20is%20no%20way%20to%20set%20a%20default%20regional%20configuration.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Mike Rowland
Occasional Contributor

I have the command to run to set all my current migrated mailboxes in the cloud to the correct timezone but that only seems to apply to all current existing mailboxes.  

 

If I use the "Set-MailboxRegionalConfiguration" command then 10 minutes create a new user then I need to run the command again.

 

Is there a way to set a permanent default rather than having to run the powershell over and over?

 

 

3 Replies
Highlighted

No, there is no way to set a default regional configuration.

Highlighted

That's just one of the examples why many companies use "mailbox provisioning" scripts. Other examples include disabling protocols (POP/IMAP usually), configuring quotas, enabling Auditing, even putting mailboxes on hold.

 

You might consider adding this as a step in your provisioning workflow, or simply scheduling a task that runs PowerShell to periodically update mailbox settings.

Highlighted

Great thank you!