<div>
You need to set the actual -ID in the command... you have set it to &quot;$_&quot;<br />
<br />

<blockquote>
<br />
set-mailbox -id <b>$_</b> -type:shared <br />

</blockquote>
<br />
It would be safer to do something like this:<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-41414307-1"><span>$userslist = Get-Content C:\usernames.csv</span>
<span>foreach($user in $userlist)</span>
<span>{</span>
<span>   set-mailbox -id $user -type:shared</span>
<span>}</span>
</code></pre>
<br />
Save the above code to a ps1 file and run it from the Exchange Admin PS Console.<br />
<br />
Dan
</div>


<div>
If you want some console feedback, I've added a write-host to show which mailbox is being worked on.<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-41414315-1"><span>$userlist = Get-Content C:\usernames.csv</span>
<span>foreach($user in $userlist)</span>
<span>{</span>
<span>   write-host &quot;Working on Mailbox:  &quot; $user</span>
<span>   set-mailbox -id $user -type:shared</span>
<span>}</span>
</code></pre>
<br />
<b>PS: &nbsp;please use this code, there is a typo in the first script I submitted.</b><br />
<br />
Dan
</div>


<div>
I wish it was that easy but that does not work. Even if I was to run the command set-mailbox -identity username -type:regular I still get the error. Believe me I wish it was syntax but its not.
</div>


<div>
Can you post some of the contents of your username.csv file?<br />
<br />
Dan
</div>


<div>
its just the following below in &nbsp;CSV file. If I am on the server where the user resides this works. If I am on a remote server this does not work and produces the following message I provided earlier. The problem appears to be with the servers ability to proxua<br />
<br />
<br />
info in the csv file..These are the aliases and like I said it works for some and others this works for.<br />
<br />
userone<br />
usertwo<br />
userthree<br />
userfour
</div>


<div>
This appears to be a known issue with a workaround. &nbsp;Article is posted below.<br />
<br />
Link:<br />
- <a href="http://blog.skysoft-is.com/?p=270" rel="ugc">http://blog.skysoft-is.com/?p=270</a><br />
- <a href="http://www.tachytelic.net/2013/10/office-365-convert-shared-mailbox-user-mailbox/?doing_wp_cron=1452870132.5674960613250732421875" rel="ugc">http://www.tachytelic.net/2013/10/office-365-convert-shared-mailbox-user-mailbox/?doing_wp_cron=1452870132.5674960613250732421875</a><br />
<br />
Essentially you need to setup a PS Session and specific the target server. &nbsp;You should be able to run this from any workstation.<br />
<br />
As for working for some accounts and not others, do the accounts that the set-mailbox doesn't work for, actually exist?<br />
<br />
Dan
</div>


<div>
On the users where the set-mailbox fails, if you run a &quot;Get-ADUser&quot; command... do you get a valid output with AD Object info?<br />
<br />
Dan
</div>


<div>
Here is the bad part. We are a large environment with over 300 servers. So I would have to run this command for each server correct?
</div>


<div>
No. You run it against the Exchange servers. &nbsp;You users are in AD nit on each server. &nbsp;Exchange requires AD to operate.<br />
<br />
Run it from 1 exchange server and you should be down. &nbsp;Unless you have multiple separate Exchange instances.<br />
<br />
If you a DAG, run it on 1 if the servers in the DAG.<br />
<br />
Dan
</div>


<div>
This is a multi-dag environment. I just ran this on a bunch of users using the code on the sites your provided and the only ones it hit was the users who were on the target server. So one thing is I do not have to logon to each server but I do have to remote powershell into them.
</div>


<div>
Ok, then you will have to run the script on a server in each DAG.<br />
<br />
Dan
</div>


<div>
<div class="content wysiwyg-content">
I am attempting to convert some shared mailboxes back to regular and then some to shared. I received this while running the following command<br />
<br />
get-content c:\usernames.csv | foreach {set-mailbox -id $_ -type:shared }<br />
<br />
Error on proxy command 'Set-Mailbox -Identity:'USERNAME' -Type:'Regular' -Confirm:$False -Force:$True' to server<br />
servername FQDN: Server version 15.00.1130.0000, Proxy method RPS:<br />
The operation couldn't be performed because object 'USER NAME' couldn't be found on 'FQDN AD SERVER'..<br />
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: NotSpecified: (:) [Set-Mailbox], CmdletProxyException<br />
&nbsp; &nbsp; + FullyQualifiedErrorId : Microsoft.Exchange.Configu<wbr />ration.Cmd<wbr />letProxyEx<wbr />ception,Mi<wbr />crosoft.Ex<wbr />change.Man<wbr />agement.Re<wbr />ci<br />
&nbsp; &nbsp;pientTasks.SetMailbox<br />
&nbsp; &nbsp; + PSComputerName &nbsp; &nbsp; &nbsp; &nbsp;: REMOTESERVERLOGGEDINTOPERF<wbr />ORMING THIS OPERATION
</div>
</div>


I am attempting to convert some shared mailboxes back to regular and then some to shared. I received this while running the following command

get-content c:\usernames.csv | foreach {set-mailbox -id $_ -type:shared }

Error on proxy command 'Set-Mailbox -Identity:'USERNAME' -Type:'Regular' -Confirm:$False -Force:$True' to server
servername FQDN: Server version 15.00.1130.0000, Proxy method RPS:
The operation couldn't be performed because object 'USER NAME' couldn't be found on 'FQDN AD SERVER'..
    + CategoryInfo          : NotSpecified: (:) [Set-Mailbox], CmdletProxyException
    + FullyQualifiedErrorId : Microsoft.Exchange.Configuration.CmdletProxyException,Microsoft.Exchange.Management.Reci
   pientTasks.SetMailbox
    + PSComputerName        : REMOTESERVERLOGGEDINTOPERFORMING THIS OPERATION

Exchange 2013 error proxy on server

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.