Want to create a default outlook account in windows server 2019

Question

I have a requirement where I want to create a outlook default profile through cmd.

I used outlook.exe /PIM Default

which is fine, but it also automatically open up the outlook GUI.

Is there any flag or any other way by which I can create an outlook profile without outlook GUI opening up?

Answer 1

Hi @Anvay Singh ,

Welcome to our forum and posting your question here.

It is recommended you create an Outlook profile from Control Panel.

1. Go to Control Panel > Mail > Show Profiles
2. Add a new profile name, if you want to set it as the default, select "Always use this profile"
   

---

If the answer is helpful, please click "Accept Answer", this will make answer searching in the forum easier and be beneficial to other community members as well.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

Hi @Anvay Singh

There's no way to perform this action via cmd silently without opening up Outlook.

I do hope this answers your question.

Thanks.

--
--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Hi @Anvay Singh ,

I'm sorry for misunderstanding your needs.
According to my test, you can add profile into registry via command, run the following command:

reg add HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\<name>  
reg add "HKCU\Software\Microsoft\Office\16.0\Outlook" /v DefaultProfile /t REG_SZ /d "<name>" /F  

When I open outlook, it shows as the default profile.

---

If you think my answer is helpful, please kindly "Accept Answer" to thelp others with the same problem.

Answer 4

I just went through this myself and documented my findings, which hopefully will be of use: https://learn.microsoft.com/en-us/answers/questions/1154958/how-to-create-a-blank-34no-email34-outlook-365-pro.html.

In short, I didn't find a way to automate it completely, but after ProcMon sessions/etc., I documented the registry settings that seem to be at play. It doesn't appear to be possible short of some more involved scripting effort (reading in some variable data, writing binary registry values, etc.).