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

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi...

Apple iPhone Text responses go to wrong country code

A user wrote: Recently I went to Portugal and when I was there I bought a sim card and put it in my iPhone 11 Pro, with my primary e-sim still in it. When I got home to Australia, I deactivated the Portugal sim-card, deleted it and took the sim card out. Now when someone call me I respond with text, my iPhone changes the calling numbers country code to +31. I had the same problem. Despite turning "Dial assist" on/off, checking Country, Language and all the suggested stuff it did not work for me. What I did at the end was deleting country prefix from contact numbers --> Save --> Added country prefix again . It works now.