Exchange 2010 (CAS) conversion from Physcial to VM
last weekend i successfully converted my CAS server from physical server to a Vmware VM. I then renamed my old CAS server and changed it IP to something else. I assigned the same name and IP to the new VM and added it back to the domain. I made sure the DNS is updated and was able to ping MAIL server with DNS name for connectivity. However my exchanged service wont start or they would go to starting mode and then stop. My clients were not able to connect so after several reboots and service restarts i gave up and reverted back to my old CAS and renamed it back to its original name and IP all clients were able to connect. What am i missing here and doing wrong? If a server has the same name and IP as the old CAS it should work right? I did the same for my fileserver(DC) and it worked fine with no issues.
Thanks for your input guys. I am just trying to understand the architecture how MAIL talked to CAS. So even if I cloned the P2V the new virtual server should have all the settings and SSL as the old one. Once the old CAS is taken offline and the new CAS is given the same name and IP as the old one shouldn't MAIL server be able to communicate with the new CAS. I We have internal applications and firewall policies based on the CAS server DNS name and IP so I wanted to avoid all that mess and keep the same name and IP on the new VM.I am not an expert in exchange so pardon me if I am asking basics here but I will appreciate your feedback.
With all that said what I get from all the feedback its better for me to build a new server from scratch.