How force mailbox disconnection by powershell on Exchange 2010
Hi,
I've some users that connects and disconnects they laptops from our network and sometimes they get stuck to reconnect to the Exchange server as they still have a lot of process open in the exchange server (they didn't disconnect properly). After this, they can't reconnect to the Exchange server, even if I reset the password and put a higher value for the Throttling policy.
So I was wondering if there exists a command in powershell to force the disconnection of a specific user mailbox???
David
I've some users that connects and disconnects they laptops from our network and sometimes they get stuck to reconnect to the Exchange server as they still have a lot of process open in the exchange server (they didn't disconnect properly). After this, they can't reconnect to the Exchange server, even if I reset the password and put a higher value for the Throttling policy.
So I was wondering if there exists a command in powershell to force the disconnection of a specific user mailbox???
David
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The TOE (or Chimney) is used to delegate some workload to the network card. If disabled, you can have some increase in the processor load, for example. I never noted anything when it's disabled. The good thing is that you can quickly enable it if you think it didn't solve your problem.
ASKER
Hi, I didn't had time yet to check that but I'll do it asap and I'll let you know.
thx for the infos.
david
thx for the infos.
david
ASKER
Hi,
I just did the modification, I keep you posted soon if I see any changes.
Kind Regards,
David
PS I added extra memory in the meantime to the server and it seems to be stabilized since then... but we will see if there is any improvement anyway or not.
I just did the modification, I keep you posted soon if I see any changes.
Kind Regards,
David
PS I added extra memory in the meantime to the server and it seems to be stabilized since then... but we will see if there is any improvement anyway or not.
ASKER
Hi,
seems that your solution did the trick for my problem.
Have a good week end.
Kind Regards
seems that your solution did the trick for my problem.
Have a good week end.
Kind Regards
ASKER
In fact, it happens randomly to different users... They can't have access anymore to outlook and the only way to connect them back again is to wait 1h approx... and then, they can have access again.
All users are in a different domain than the exchange (we're merging progressivelly) and they're all in Outlook 2003 SP3. I was wondering if they could be a simple command to close the connectiosn to the server.
if I do a Get-Mailboxstatistics -Identity "username" | fl applicationid
I got a lot of MSExchange RPC connections and the user is not connected anymore... and as soon as they aren't anymore, we can connect it again...
About your suggestion regarding the Chimney, what are the implications by deactivating that??? What is it used for?
David