04. November 2015 · Comments Off on Check Whether the Exchange Server is an Open SMTP Relay using a Telnet Test · Categories: Microsoft · Tags: , ,

Check Whether the Exchange Server is an Open SMTP Relay using a Telnet Test

A Telnet test involves establishing a Telnet session from a computer that is not located on the local network to the external (public) IP address of the Exchange server. You need to carry out the test from a machine at home, or from another office. Doing the test from a machine on your own network will produce useless results.

  1. Start a command prompt.
    Either click start, run and type CMD
    or Choose Command Prompt from Start, Programs, Accessories, Command Prompt
  2. Type “telnet” (minus quotes) and press enter.
  3. At the Telnet prompt, type

    set localecho

    (minus quotes) and press enter. This lets you see what is going on.

  4. Still in the telnet prompt, enter the following command and then press enter

    open external-ip 25

    where external-ip is your external IP address eg:

    open 111.222.333.444 25

  5. You should get a response back similar to the following:

    220 mail.server.domain Microsoft ESMTP MAIL Service, Version: 6.0.2790.0 Ready at

  6. Type the following command in to the telnet windows:

    ehlo testdomain.com

    and press enter (note “testdomain.com” can be anything that isn’t a domain that the Exchange server is responsible for.

  7. After pressing OK you should get a response back

    250 OK

  8. Type the following command in to the telnet window:

    mail from:address@testdomain.com

    and press enter (again where address@testdomain is an email address that is not on the Exchange server. Note the lack of space between from and the first part of the address).

  9. After pressing OK you should get a response back:

    250 2.1.0 address@testdomain.com….Sender OK

  10. Type the following command in to the telnet window:

    rcpt to:address@anotherdomain.com

    and then press enter (where address@anotherdomain.com is not either an address you use internally or the address you entered earlier as the from. Once again note the lack of space between to and the first part of the e-mail address).

  11. After pressing enter you will get one of two responses.
    If you get

    550 5.7.1 Unable to relay for address@anotherdomain.com

    then you are relay secure.
    However if you get

    250 2.1.5 address@anotherdomain.com

    Then you are an open relay.

21. June 2013 · Comments Off on How to Manually Remove Exchange 2007 · Categories: Microsoft · Tags: , , , , ,

How to manually remove an Exchange 2007 that got hosed.

Uninstalling exchange was also unsuccessful because some objects were missing from Active Directory. I also wanted to avoid reinstalling the OS as I have critical software that needs to remain.  So I tried removing exchange manually.

  1. Run setup /m:uninstall (From Exchange 2007 Media)
  2. Stop and disable all the Exchange 2007 services
  3. Use Registry Editor (Start->Run->Regedit) to remove these Exchange related registry keys:
    • HKLMSOFTWAREMicrosoftExchange
    • HKLMSYSTEMCurrentControlSetServicesMSExchange* (all the keys starting with “MSExchange”)
    • HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstallMicrosoft Exchange
  4. Remove the entire Web Server role (don’t forget to reinstall afterwards as it’s a prerequisite for E2K7!)
  5. Remove the Exchange 2007 server from Active Directory. I ended up deleting the entire “Microsoft Exchange” branch from ADSIEdit (Configuration Container > Services > Microsoft Exchange) as my domain only has one server.
  6. Use Windows Explorer to delete:
    • C:Program FilesMicrosoftExchange Server
    • C:ExchangeSetupLogs
  7. Use Windows Installer CleanUp Utility to remove all the exchange related info from the installer database.
  8. Remove the security groups created by Exchange setup from AD

Note: Manually removing Exchange 2007 is not supported by Microsoft! Official guidance for removing Exchange 2007 can be found in this TechNet article.

22. April 2013 · Comments Off on The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process · Categories: Office365 · Tags: , , , ,

I”m working on a Office365 Migration for a client that has an Excahange 2010.  Encountered some some migration issues.  I ran the testexchangeconnectivity.com test for RPC over HTTP, and everything was just fine, excpet for the last test, which returned the dreaded:

“The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.”

===================================================================
More »

25. March 2013 · Comments Off on How can I stop users from using PST files · Categories: Microsoft · Tags: , , ,

PST files are a burden in many environments. They’re hard to manage, hard to perform discovery on, and prone to loss when stored on local machines. Many companies now use archiving solutions at the mail server, such as the Exchange 2010 archiving functionality, to avoid the need for user PST files.

Briefly, these are some of the problems with PST files:

  • Microsoft does not support using PST files over a LAN or WAN network (KB267019). Using PST files located on network shares can slow down Outlook and can cause corruption of the PST file.
  • Anti-virus countermeasures cannot be implemented on PST files as easily as Exchange Server mailbox databases.
  • It is difficult to accurately report on PST file use, making reporting on organizational mail storage and planning for future growth difficult.
  • Managing content of PST files is difficult.  Exchange Server provides tools to manage the content of mailboxes (such as Messaging Records Management) and to export or remove data from mailboxes (such as the Export-Mailbox cmdlet) but there are no such tools to manage the content of PST files.
  • Local PST files are difficult to back up, making them vulnerable to data loss.

To phase out PST files, take a two phase approach. First, you can stop users from writing to PST files but still allow them to read from then. You can then totally block PST files.
More »

21. January 2013 · Comments Off on Exchange 2010 EMC “initialization failed” error execution of scripts is disabled on this system · Categories: Microsoft · Tags: , ,

1-21-2013 10-41-20 AM

The reason for this error is the security setting on your pc that does not allow you to execute a script.  This is the so-called Execution Policy. By default, the Execution Policy is set to Restricted. This setting means that you may not run any PS1 script at all.

An overview of the policy levels:

Restricted: Individual cmdlets can run, but not saved Powershell scripts. This is the default setting.
AllSigned: Scripts can run, but must have a digital signature even if written on the local computer. Prompts you before running scripts from trusted publishers.
RemoteSigned: Scripts written on the local computer do not need a digital signature, but any script downloaded from outside (email, IM, Internet) must have a signature to execute.
Unrestricted: Any script can run, but scripts downloaded from outside will run with a warning.
More »

05. November 2012 · Comments Off on Stop|Start|Restart Exchange 2010 services · Categories: Microsoft · Tags: , ,

Restarting the Exchange services:

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
@Echo Off
Echo 'Stopping Microsoft Exchange Services'
net stop MSExchangeAB
net stop MSExchangeADTopology
net stop MSExchangeAntispamUpdate
net stop MSExchangeEdgeSync
net stop MSExchangeFBA
net stop MSExchangeFDS
net stop MSExchangeIS
net stop MSExchangeMailboxAssistants
net stop MSExchangeMailboxReplication
net stop MSExchangeMailSubmission
net stop MSExchangeProtectedServiceHost
net stop MSExchangeRepl
net stop MSExchangeRPC
net stop MSExchangeSA
net stop MSExchangeSearch
net stop MSExchangeServiceHost
net stop MSExchangeThrottling
net stop MSExchangeTransport
net stop MSExchangeTransportLogSearch
Echo 'Starting Microsoft Exchange Services'
net start MSExchangeAB
net start MSExchangeADTopology
net start MSExchangeAntispamUpdate
net start MSExchangeEdgeSync
net start MSExchangeFBA
net start MSExchangeFDS
net start MSExchangeIS
net start MSExchangeMailboxAssistants
net start MSExchangeMailboxReplication
net start MSExchangeMailSubmission
net start MSExchangeProtectedServiceHost
net start MSExchangeRepl
net start MSExchangeRPC
net start MSExchangeSA
net start MSExchangeSearch
net start MSExchangeServiceHost
net start MSExchangeThrottling
net start MSExchangeTransport
net start MSExchangeTransportLogSearch
End

More »