Uncategorized

Remove Active Directory Domain Controller Metadata

Advertisements
Exchange

Exchange 2010 ActiveSync Autodiscover Issue

This post does not cover the entire OWA config, that will be pre-requisite for this specific  Autodiscover for ActiveSync problem This fix will apply  if you have a different internal local UPN Domain to your Email domain. If you have a Multi-Tenant Exchange that setup is out of scope from this fix and may not apply.

Pre-reqs >

  • Make sure OWA is working correctly from the internets =)
  • Verify a manual setup of Active Sync on a smartphone works ok
  • Verify your Public DNS record for “Autodiscover”
  • Verify you have a SAN or Wildcard SSL Cert installed on your CAS server with “Autodiscover” included if you have a SAN SSL Cert.

OWA setup resource > Beginner’s Guide to Exchange Server 2010 ActiveSync

Symptoms / Error / Scenario >

After checking my OWA config, the URLS, my SAN Cert and my public DNS records for Autodiscover; Active-Sync  with Autodiscover  would not work. Outlook Anywhere Autodiscover worked like a charm for me, this was the big clue =)

Resolution>

 (Verify you are NOT connected to your internal Wi-Fi, to make sure you  go hit your public DNS Autodiscover record )

Lets now add your internal local UPN Domain to your OWA in IIS

  1. Open IIS on your CAS server, navigate to “Autodiscover” unser Default Web Site.
  2. Image
  3. Edit “Authentication” and then edit the “Basic Authentication” a window will pop up and enter ” \ ” or in theory you can use enter
  4. your internal domainImage
  5. Next add the backslash ” \ ” to the Microsoft-Server-ActiveSync directory.Image
  6. Finally I restarted IIS service ( not sure if this is required….caution you will take down OWA)
  7. Image
  8. Time to test! You should now be able to setup your smartphone by only using email address and password.

            ( You can also test here testexchangeconnectivity.com )

Uncategorized

How to verify Exchange 2010 version and Service Pack

Before I installed SP2 on Exchange2010, I wanted to know how to check my build number and most importantly the meaning of my build number. This is how you can find the build number from the EMC. Select Server Configuration>Mailbox and you will see the “Version” of your Exchange servers.

My favorite way to check is via PowerShell, here is the code


Get-ExchangeServer | select name,admindisplayversion | ft 

Finally you can match your build number with the Product name

Microsoft Links—–

Exchange Server and Update Rollups Build Numbers (en-US)

How to determine the version number, the build number, and the service pack level of Exchange Server

VMware

Failed to enable software iSCSI ESX4 U1

“Failed to enable software iSCSI  

ESX4 U1, From the VI Client I received this error,“Error during the configuration of the host: Failed to enable software iSCSi”

From a Putty session to the ESX host I ran  “esxcfg-swiscsi –e” to enable software iSCSI and it failed with this error:

“vmkload_mod: Cannot load module iscsi_vmk: Bad parameter Exec of command ‘/usr/sbin/vmkload_mod iscsi_vmk iscsi_max_lun_queue’ succeeded, but returned with non-zero status: 1”

Resolution:

  1. Launch a SHH Putty session to your ESX host
  2. Enter cmd, “vmkload_mod iscsi_vmk”  this will load the iscsi module file. You should see a return with, “Module iscsi_vmk loaded successfully
  3. Next run cmd “esxcfg-swiscsi –e” to enable software iSCSI.It  should say, “Enabling software iSCSI…”
  4. Now run “esxcfg-swiscsi –q” and it should say “Software iSCSI is enabled”

If not, Enable iSCSI via from the VI Client GUI

  • Click on the ESX host> Configuration>Storage Adapters>

  • Select the iscsi adapter and click properties>

>Iscsi initiator dialog box will open > from the General Tab – Click Configure>

 

  • Now check Enable.

Verify that the task completes under Recent Tasks.

Done!