MAPI tool

http://mfcmapi.codeplex.com

https://support.microsoft.com/kb/2679568

tail for windows

https://logexpert.codeplex.com/documentation

Logexpert

troubleshooting vmware issues

check the resource usage on the VM

Check the resources on the VM host

check for snapshots

esxtop (top of esx)
check latency

less vmkernel | grep -i module (or what ever you are looking for)

ping between VMs on the same host, ping between VMs on different hosts and compare can highlight a network issue

How to troubleshoot BGP issues

http://www.techrepublic.com/article/how-to-use-ip-and-bgp-to-troubleshoot-internet-connectivity/

http://www.analogx.com/contents/download/network/htrace/freeware.htm

http://www.visualware.com/demo/index.html

http://www.traceroute.org/

Nslookup on the website gives us the IP 108.162.200.103

Traceroute shows us that we go to next gen -> equinx -> web server (notice that number 13335 in the equnix datacentre)

AAPT have a looking glass here http://looking-glass.connect.com.au/lg

show ip bgp 108.162.200.103

See below also
http://www.routeviews.org/

It gives the results below

look for the route with "best" this is the one that is used

The second path in red is used. The AS numbers go from source to destination so we went from

1221 (Telstra Australia) -> 10026 (pacnet Hong Kong) -> 13335 (Cloudflare US)

If we didn’t see any route or a route to the wrong AS number we could see a problem. It’s also a good idea to check with another looking glass (this one is in Canada)

852 (telus Canada) -> 13335 (Cloudflare US) -> 13335 -> 13335

Get the public IP of the site you have an issue with.
Use network tools and route views to see if its working

On your router
sh ip bgp sum

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
1.1.1.1      4        55555 2206452 12134255 72040489    0    0 18w4d           4
2.2.2.2  4         4444  103782      47 72040260    0    0 00:38:24   600792
3.3.3.249  4        1234   17399   31813 72040260    0    0 00:56:51    91673
3.3.3.250  4        1234   20209     172 72040260    0    0 02:29:59    91672

We want to see a number there. If its switching between Active/Idle its bad. Try ping the neighbor contact the other end.

sh ip bgp nei 3.3.3.250 advertised-routes
We should see the same networks that are in the BGP config for that neighbor. If we see 0 prefixes we have an issue.

You can also do a debug ip icmp on the router and ping the public IP to see if traffic is hitting the router.

You should have a neighbor with the other router or via a failover cable but not both.

Filter lists are for controlling routes advertised
Look for "filter-list" and "ip as-path"
Prepends are for controlling paths in
BOGONS are usually a list for blocking IP ranges commonly used for IP spoofing

Using Auth Login to Troubleshoot Exchange

http://www.tomsitpro.com/articles/exchange_server-smpt-telnet,2-134-3.html

searching message tracking logs in exchange

Searching message tracking logs

Get-MessageTrackingLog -Recipients clowe@davies.com.au -Start 08/12/2014 | ft MessageSubject,MessageID

Get-MessageTrackingLog -MessageID XXXXXXX.domain.com | fl

change font sizes in outlook 2010

Changing font size in 2010

The folders

Right click on Mail -> Navigation Pane Options ->

Click the font button

The email list

View tab -> View Settings -> Other settings

Other settings button

The text in emails inside the reading pane

You have some options

You can use the zoom in the bottom right

Change DPI settings in windows

Make all emails plain text and select the font

See http://www.howto-outlook.com/howto/fontsizecolor.htm#reading_pane

issues with winRM and windows remote assist

Having some issues with it just storing some information here

Remote assist uses DCOM it must be enabled
HKEY_LOCAL_MACHINE\Software\Microsoft\Ole
EnableDCOM = Y

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
AllowTSConnections = 1

If you enable this policy you should also enable firewall exceptions to allow Remote Assistance communications. The firewall exceptions required for Offer (Unsolicited) Remote Assistance depend on the version of Windows you are running

Windows vista and later
Enable the Remote Assistance exception for the domain profile. The exception must contain:
Port 135:TCP
%WINDIR%\System32\msra.exe
%WINDIR%\System32\raserver.exe

Windows XP with Service Pack 2 (SP2) and Windows XP Professional x64 Edition with Service Pack 1 (SP1)

Port 135:TCP
%WINDIR%\PCHealth\HelpCtr\Binaries\Helpsvc.exe
%WINDIR%\PCHealth\HelpCtr\Binaries\Helpctr.exe
%WINDIR%\System32\Sessmgr.exe

For computers running Windows Server 2003 with Service Pack 1 (SP1)

Port 135:TCP
%WINDIR%\PCHealth\HelpCtr\Binaries\Helpsvc.exe
%WINDIR%\PCHealth\HelpCtr\Binaries\Helpctr.exe
Allow Remote Desktop Exception

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
fAllowUnsolicited = 1
fAllowUnsolicitedFullControl = 1

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
davies\domain admins = davies\domain admins

WinRM

Configuring WinRM using Microsoft Group Policy

If running winrm quickconfig on every XenApp server is not efficient for your site, you can configure WinRM using Microsoft Group Policy.
Note: Settings configured by Group Policy overrides the configuration changes made by the installer or configuration changes made locally on the desktop.
 

Complete the following procedure to configure WinRM using Group Policy:

1. Set the WinRM service to auto start:
   a.    In the Group Policy Editor, navigate to Computer Configuration> Policies > Windows Settings > Security Settings> System Services.
   b.    Double-click Windows Remote Management (WS-Management) and set it to Automatic.
   
   
2.   Create the WinRM listener:
   a.    In the Group Policy Editor, navigate to Computer Configuration >Policies > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM  Service.
   b.    Double-click Allow automatic configuration of listeners and configure the IPv4 filter to *.
    
3. Create a firewall exception for WinRM:
   a.    In the Group Policy Editor, navigate to Computer Configuration> Policies > Windows Settings > Security Settings> Windows Firewall with Advanced Security.
   b.    Create an Inbound Rule for WinRM for port 5985.
4. After configuring the preceding three group policies, restart the server to update the group policies and start the WinRM service.