About Us

EzcloudInfo is a team of well experienced IT Professionals specialized in Messaging platforms Microsoft Exchange, Office 365 Suite products, Azure Infrastructure services , Powershell automations , Azure bot services through node.js & Microsoft Teams with telephony integration services.

Any Queries or Concerns feel free to reach us on services@ezcloudinfo.com

18 thoughts on “About Us”

Gulab May 9, 2013 at 1:53 am Reply

All the best and Good luck with your initiative guys 🙂

LikeLike

James Jackson January 22, 2014 at 12:57 pm Reply

Very insightful information…enjoy reading your post….could you guys assist with an OWA issue I’ve been fighting with for about two weeks now. I performed an Exchange 2013 install and all was working fine until one day my owa access just stopped letting me in. I get the login screen but when I enter the credentials I’m get the 😦 something went wrong error. I’ve tried a host of fixes, resetting the virtual directories, offloading SSL, and to many other to name. Also my Outlook client won’t connect but I think that maybe of a certificate issue. Any guidance would be greatly appreciated. I’m a exchange IT consultant in Washington DC and I’m preparing for my 2013 exams. Thanks.

LikeLike

sathishveerapandian January 23, 2014 at 8:54 pm Reply

Hi
Mostly looks like this is host (A) issue.You can check the below things
Just check of the mail host (A) record is created on internal DNS server and ensure its pointed to new Exchange 2013 server.

If the mail host (A) record is pointing to old exchange 2007 server just modify it and make it to point to new Exchange 2013 server

Check the DWS directory in edit binding if loopback 127.0.0.1 is added if not add them

Please follow the below article to follow http to https redirect below creating the SRV records

http://support.microsoft.com/kb/975341/en-us

Try correcting the Correcting Autodiscover and DNS settings http://help.outlook.com/140/dd875725.aspx

Good Luck !!!
Feel free to get in touch with me if in case of any queries with regards to the same

LikeLike

James Jackson January 30, 2014 at 8:44 am Reply

Hello, Thanks for your response but I began to experience other problems in my lab so I decided to do a compete rebuild using CU3. Hopefully this will go a bit smoother, but I’ll reach out if I have any questions. Thanks again for your response.

LikeLike

sathishveerapandian February 5, 2014 at 2:22 am Reply

Thanks for your response james.
feel free to get in touch with me if in case of any issues

LikeLike

James Jackson February 9, 2014 at 9:46 am Reply

Hello Sathish….sorry to bother you but I’m not experiencing an IIS issue. It seems to become corrupt after a period of time, I haven’t been able to identify a specific pattern as yet. But I can access ECP/OWA (Exchange 2013) on a regular basis for maybe a week and then all of a sudden I try to access and I receive an Http internal server error. The fix I’ve been using is replacing the applicationhost.config file from the history folder located in inetpub directory. But I’d like to find the root cause/permanent fix before my temporary fix doesn’t work any longer. Thanks in advance for your response.

LikeLike

sathishveerapandian February 10, 2014 at 2:07 am Reply

Looks like this could be an permission issue after upgrade to CU3
Just check if all the Exchange services are running
Run prepare AD and most likely this will fix this issue

LikeLike

James Jackson February 10, 2014 at 2:48 am Reply

Thanks for the prompt response…I ran AD Prep prior to the install of CU3..are you suggesting I run it again? Thanks…

LikeLike

James Jackson February 10, 2014 at 2:49 am Reply

Thanks for the prompt response…I ran AD Prep prior to the install of CU3..are you suggesting I run it again? Thanks…

LikeLike

sathishveerapandian February 10, 2014 at 6:18 am Reply

Hi James Yes please run AD prep once again as we could miss few permissions which can be replaced

LikeLike

J. Jackson September 11, 2014 at 11:55 am Reply

Good Evening,
I have a quick question for you? I am rebuilding my exchange 2013 lab which I have three exchange servers installed on Windows 2012 and Windows 2012 R2. I cannot get the Windows 2012 R2 server to successfully join the Dag. I’ve removed and reinstalled the failover clustering feature a few times and have tried to join the cluster from the EAC and from the Failover Clustering Utility. Do you know if there’s an issue with a Windows 2012 R2 server joining a Cluster along with Win2012. Thanks in advance for your response.

JJ in Wash, D.C.

LikeLike

J. Jackson September 11, 2014 at 12:03 pm Reply

Sorry its JJ in Wash, D.C. again. Below is the error I receive:

Cluster service on node XXXXXX did not reach the running state. The error code is 0x5b4. For more information check the cluster log and system event log from the node xxxxxxx. This operation returned because the timeout period expired.

Thanks. again…

LikeLike

sathishveerapandian September 11, 2014 at 12:34 pm Reply

Are your Domain controllers VMs in the cluster, the cluster service will not start unless it can reach a domain controller.
You could destroy your cluster and recreate from scratch. Ensure that no cluster entries are present in AD and DNS before rebuild.
Once a cluster is destroyed, you should be able to simply rebuild

LikeLike