0 Hi, Recently on of our companies decided to implement Exchange 2013, all went smooth server is up and running but: 1. It being to be irresponsive after a undefined period of time 2. Ping replies are increasing from 1 ms to even 65 ms 3. There is no errors in logs 4. Can not log in by RDP or by VMWare console 5. Server is not installed on DC 6. Certificates are signed by dc trusted CA 7. I suspect there is issue with Network Cards on server but now I'm not sure as on host is another VM working - secondary DC 8. HW - HP DL 360 G6 1 proc 28 GB Ram 9. When exchange stop respond processor is used on 100% Anyone noticed same behavior or its just me

Hi, Have you tried to run windows Performance monitor, so that it can identify the root cause. If you see processor used is 100% then see which .exe file is consuming the cpu? Let us know your findings? ------------------------------------------------------------------------------------------------------------------ If this post is useful, please hit the green arrow on the left. Thanks

I haven't seen anything strange on Perf mon, And regarding 100% CPU consumption I can see this from VMware vSphere client, I'm not able to get into server to see what is going on - server is unresponsive.

For me it took more than 5 hour with 4 GB ram in vmware , how much memory you have assigned to the server

I have assigned 18 GB :) and 3 CPU cores

For me it took more than 5 hour with 4 GB ram in vmware , how much memory you have assigned to the server You should be assigning a minimum of 4 threads and 8GB of memory for an Exchange 2013 server. If you try it with anything less, then you are going to see problems. IMO take whatever you would have configured for and Exchange 2010 server and double it for Exchange 2013.

Well I disagree, it can be installed on vm with 4 GB and i CPU thread as I did it on vSphere infrastructre, and server worked without any problems, the problem I see is that on another host exc 2013 is hanging without reason and without any information in logs, the question is why is so. What a f. bug could be that software cut off os and whole host ? I understand that server can be over used or what ever but WHY hell it is not responding ... why it hangs ?

Hi According to your saying, exchange 2013 consume all memory and cut off os.Terence Yu TechNet Community Support

Nah, it consumes processor 100% and cuts off

What if you restart the E2K13 (since it is not accomplishing anything anyway). Can you access it right after reboot? Does it start to consume 100% processor right away? If not, I'd get into Task Monitor ? Resource Monitor and try to identify the process that is using all the processing power. I think your resources, on paper at least, should be sufficient - certainly enough where you shouldn't be at 100% for the processor. Why don't you try assigning an even number of cores to the Exchange guest? The number 3 jumped out at me and it may be OK but here I see someone saying "provided the OS could recognize it (odd number of CPU cores). http://communities.vmware.com/message/1379415 Then again... 1 CPU would be an odd number too...Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

I'd check this too, notably processor ratio section: http://technet.microsoft.com/en-us/library/jj619301(v=exchg.150).aspxPlease mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.