force GPUPDATE on all domain computers

Issue: You need to force group policies to refresh on all domain computers immediately rather than waiting the default 90 minutes. Solution: You can use PSEXEC to accomplish this feat. 1) Download PSTOOLS from Microsoft, extract and copy to c:PSTOOLS 2) Open a Command Prompt as administrator: To update group policies on all domain machines: psexec \\* gpupdate /force PSEXEC queries Active Directory for the computer names to run the command against, thus it will likely run against Read more [...]

Frozen Exchange Server? How to shut it down safely

Here is what I do on a frozen unresponsive Windows Server to help protect any active database application services that may be running on the server, like Microsoft Exchange or SQL.  These steps are worth trying before you initiate a dirty shutdown (turn off the server w 'the power button') 1) Open services.msc on a different server, then connect to the server that is going to be shutdown. Stop critical database services like the Information Store (it may get stuck in a stopping state, but its Read more [...]

How to enable archiving for a user on Exchange 2013

The following steps will show you how to enable archiving for a users mailbox on Exchange 2013 Note: This process assumes you have already created an archive database. 1) Open Exchange Admin Center 2) Click Recipients > Select Recipient > Click Edit (pencil icon) 3) Click mailbox features > scroll down > click Enable under “Archiving: Disabled” 4) Click “browse”, you know you want to. 5) Select the Archive Database you created previously, and click Ok 6) Read more [...]

How to create an Archive Database on Exchange 2013 / 2010

Mailbox archives can be stored in any database on the Exchange server.  An 'Archive' Database is just like any other Exchange Database, nothing special.  That said, I advice you create a dedicated Database for the archive and name it something like "Archive 01".  Note: depending on your environment you may opt to store the Archive DB on less expensive storage than your primary production databases. Here is the command to create the Archive Database using Exchange Management Shell: New-MailboxDatabase Read more [...]

Exchange “452 4.3.1 Insufficient system resources” Bounce NDR

Issue: Senders report receiving bounce messages containing "452 4.3.1 Insufficient system resources" Diagnosis: Check the free disk space on your Exchange server disk volumes. The volume where Exchange was installed has likely fallen below the free disk space threshold.  The threshold values depend on your version of exchange and range from 500MB to 4GB depending on the version of Exchange, volume size and the formula's being used. Immediate Solution: Either enlarge your volume, free some Read more [...]