Skip to main content

How to record everything you do inside Exchange Management Shell

Let's presume you are working for the company that offers IT services to other companies. One of the things you can do with Exchange 2007 is you can record everything you do in Exchange Management Shell not just for your own records but also in case you need to prove what you did on Exchange server if there is a need for that. We all know how hard sometimes cutomers can be ;)

So, to start recording everything you do in Exchange Management Shell you use following command:

Start-Transcript C:\SOMEFOLDER\WhatYouDid.txt -Append

As you can see, we start the transaction recording by creating WhatYouDid.txt file in one of the folders on C: drive. After that we can start executing commands inside Exchange Management Shell. To finnish recording we just simply execute

Stop-Transcript

You can than browse to and open WhatYouDid.txt file. Sample output of the file:

**********************
Windows PowerShell Transcript Start
Start time: 20070722225904
Username  : DOMENA\Administrator
Machine      : HUB1 (Microsoft Windows NT 5.2.3790 Service Pack 2)
**********************
Transcript started, output file is c:\transcript\WhatYouDid.txt
[PS] C:\Documents and Settings\Administrator>get-transportconfig

ClearCategories                : True
GenerateCopyOfDSNFor           : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
InternalSMTPServers            : {0.0.0.0}
JournalingReportNdrTo          : <>
MaxDumpsterSizePerStorageGroup : 18MB
MaxDumpsterTime                : 7.00:00:00
MaxReceiveSize                 : unlimited
MaxRecipientEnvelopeLimit      : unlimited
MaxSendSize                    : unlimited
TLSReceiveDomainSecureList     : {}
TLSSendDomainSecureList        : {}
VerifySecureSubmitEnabled      : False
VoicemailJournalingEnabled     : True
Xexch50Enabled                 : True

[PS] C:\Documents and Settings\Administrator>Set-TransportConfig -InternalSMTPServers 10.10.0.4
[PS] C:\Documents and Settings\Administrator>Stop-Transcript
**********************
Windows PowerShell Transcript End
End time: 20070722225950
**********************

From the file you can see that I executed Get-TransportConfig and Set-TransportConfig -InternalSMTPServers commands.

Recording works for current (the window you start transaction in) Exchange Management Shell window only.

Comments

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.