- Delete Failed DCs from Active Directory
- How to remove data in Active Directory after an unsuccessful domain controller demotion
- (SCRIPT) Remove Active Directory Domain Controller Metadata
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.
- 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 =)
(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
- Open IIS on your CAS server, navigate to “Autodiscover” unser Default Web Site.
- Edit “Authentication” and then edit the “Basic Authentication” a window will pop up and enter ” \ ” or in theory you can use enter
- your internal domain
- Next add the backslash ” \ ” to the Microsoft-Server-ActiveSync directory.
- Finally I restarted IIS service ( not sure if this is required….caution you will take down OWA)
- 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 )
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
Dcdiag.exe is a great way to check if your domain controllers are healthy.
What does DCDIAG actually…do? [Amazing MS post on DCDIAG]
Handy DC troubleshooting commands:
Dcdiag /v /f:c:\Dcdiag_verbose_output.txt Dcdiag /v /test:dns /f:c:\DCDiag_DNS_output.txt Dcdiag /v /test:topology /f:c:\DCDiag_Topology_output.txt
” Free NFR Licenses for Evaluation and Demonstration Use available to VMware vExperts, VMware Certified Professionals, VMware Certified Instructors VMUG members, Microsoft Most Valuable Professionals, and Microsoft Certified Professionals “
Links to the official VMworld TV Youtube Playlist. Tons of great Sessions, enjoy!
“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”
- Launch a SHH Putty session to your ESX host
- Enter cmd, “vmkload_mod iscsi_vmk” this will load the iscsi module file. You should see a return with, “Module iscsi_vmk loaded successfully”
- Next run cmd “esxcfg-swiscsi –e” to enable software iSCSI.It should say, “Enabling software iSCSI…”
- 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>
Verify that the task completes under Recent Tasks.