Installation of ADS-MS exchange and OCS.
It was on one hot summer afternoon we have got a dell server power edge 2900 with xeon 2.45 GHz quadcore CPU, 500 GB SAS hard disk and 8 Gigs of memory. The intended use was to install office communication server on it and test the application developed. And also enable hyper -V and have some guest OS in it with 64 bit architecture for testing.
All the things started with a dim mind as my concept of MS Hyper -V was similar to that of VMware ESX . But I did not find the client which can connect to the baremetal installation so that I can create the virtual Machines.
Later with the guidance I understood that It is actually a different way, you can install win 2008 RTM first and then add the role as hyper-V. With this knowledge I emulated/virtualized 4 guest OS both 64bit and 32 bit on it. ( why it is hyper- V and not Esxi...? the answer is simple I have been asked to do that way.. :P)
Well later Surendra and Nagesh started installing ADS, it was easy cake, configured some domains and policies, moved on to install exchange 2007. It did not starting Transport Agent. After some time we found out it is just because of IPV6 was disabled on the network. Once IPV6 is enabled exchange server installation was smooth.
But in this trial and error excercise we have already formatted and reloaded win2k8 and installed DC again :P. Interestings things are yet to follow.
Then we started installing OCS with loads and loads of dependencies and again it got struck at starting the services. Earlier we thought it is an issue with network/certificate or some stupid trivial thing we missed out... And finally figured that it was messge queing server. We added that feature and tried to start the services, It was not starting.... :P :P . this time it was the case that MSMQ has to be added even before promoting the machine to DC.
Again we formatted and reloaded win2008 / ADS /Exchange and now it started moving. This time it is already 5 hours since we started working from scratch and we are still waiting at a place where the certificate and auth as tls was giving error. Atlast once we made auth through tcp OCS communicator client was able to login to the server .
A geek performance by Surendra. Hats off to him....
ಮುಂದ.....?
No comments:
Post a Comment