To start, the Exchange module only requires installation on the Source machine. It will do a remote installation on the Target. this explains why you do not necessarily see any module software ont he Target.
Since the customer you have had v1 of the RepliStor Exchange module, this means that their Active Directory was changed in order to accommodate for it.
You will need to use adsiedit.msc in order to go to the Exchange object in Configuration container in AD. When you go to the Porperties of the object, there is a paramter called attribute called "networkAddress". If you review the values, you will see the "ncacn_ip_tcp" entry still contains the virtual account name (Not the hostname of the machine, which Exchange was installed upon. This is the same one seen via Exchange System Mngr). This value was changed when the v1 module was activated and is how the module used to work.
Therefore, you will need to do the following: - Deactivate the Alias. - Modify the ncacn_ip_tcp value in AD. - Remove the RepliStor Exchange module. - Start Exchange and validate connectivity via an Outlook client. At this point, you are essentially back to the way you before ReplIStor entered the picture. - If you are implementing the v2 of the the module, proceed with the steps used to install it as it is documented.
NOTE: There are several other objects changed as a result of the Alias such as homeMDB, homeMTA, & msExchHomeServerName. After you Deactivate the Alias, check a few users in the Domain partition via adsiedit.msc to ensure the Exchange server name in use is the original. Deactivating the Alias is supposed to change these particualr parameters back to the original. If it does not, you would potentially have to change these values for all users.
Keep in mind that when modifying Active Directory, you are taking speacial care. A backup should be taken before proceeding to ensure you have protected the environment in the event you inadvertently make a mistake. If you have any doubts about the above, I recommend you open a support case with EMC to assist with this work.
To answer your questions: 1. An installation at this point could be more destructive. 2. You may have to manually uninstall the module. Ensure you have Deactivated the Alias and have validated the AD changes before proceding. 3. Do not remove adsiedit.msc to remove the Exchange instance from AD as this was created by the Exchange install itself. Doing this work could cause a lot of damage and your Exchange instance would be corrupted.
Let me know if the above is consistent with the issues you are seeing in your environment and if you have any other questions after reviewing.
Thank you very much for your response. Your answer is what I suspected must be done from reading several Powerlink articles prior to posting. Thank you for pointing out the ramifications of the other ways I asked about as well.
Is this the correct Key? Are the attributes you mentioned, "networkAddress" only created when Replistor is installed? I am headed to customer site this evening and looking at our Exchange AD Attributes currently and do not see those attributes you mentioned anywhere.
That is the correct key, but you have to drill further down to the Exchange server name. When you right-click and look at the properties of the server name, the attribute is located there.
This value is created by the Exchange installation. The RepliStor Exchange module v1 updates this field as mentioned earlier in this string.
CN=Configuration>CN=Services>CN=Microsoft Exchange>CN= (Name Given in Exchange Server Manager)>CN=Administrative Groups>CN=(Container from Exchange Server Manager Servers are in)>CN=Servers>CN=Server Name
dramjass
151 Posts
0
February 13th, 2009 11:00
Since the customer you have had v1 of the RepliStor Exchange module, this means that their Active Directory was changed in order to accommodate for it.
You will need to use adsiedit.msc in order to go to the Exchange object in Configuration container in AD. When you go to the Porperties of the object, there is a paramter called attribute called "networkAddress". If you review the values, you will see the "ncacn_ip_tcp" entry still contains the virtual account name (Not the hostname of the machine, which Exchange was installed upon. This is the same one seen via Exchange System Mngr). This value was changed when the v1 module was activated and is how the module used to work.
Therefore, you will need to do the following:
- Deactivate the Alias.
- Modify the ncacn_ip_tcp value in AD.
- Remove the RepliStor Exchange module.
- Start Exchange and validate connectivity via an Outlook client. At this point, you are essentially back to the way you before ReplIStor entered the picture.
- If you are implementing the v2 of the the module, proceed with the steps used to install it as it is documented.
NOTE: There are several other objects changed as a result of the Alias such as homeMDB, homeMTA, & msExchHomeServerName. After you Deactivate the Alias, check a few users in the Domain partition via adsiedit.msc to ensure the Exchange server name in use is the original. Deactivating the Alias is supposed to change these particualr parameters back to the original. If it does not, you would potentially have to change these values for all users.
Keep in mind that when modifying Active Directory, you are taking speacial care. A backup should be taken before proceeding to ensure you have protected the environment in the event you inadvertently make a mistake. If you have any doubts about the above, I recommend you open a support case with EMC to assist with this work.
To answer your questions:
1. An installation at this point could be more destructive.
2. You may have to manually uninstall the module. Ensure you have Deactivated the Alias and have validated the AD changes before proceding.
3. Do not remove adsiedit.msc to remove the Exchange instance from AD as this was created by the Exchange install itself. Doing this work could cause a lot of damage and your Exchange instance would be corrupted.
Let me know if the above is consistent with the issues you are seeing in your environment and if you have any other questions after reviewing.
Duncan
jerry.reddick
51 Posts
0
February 16th, 2009 08:00
Thank you very much for your response. Your answer is what I suspected must be done from reading several Powerlink articles prior to posting. Thank you for pointing out the ramifications of the other ways I asked about as well.
I am going to use this article as the method of manually uninstalling 6.2. https://solutions.emc.com/emcsolutionview.asp?id=esg59512 Please let me know if you suggest a different one.
Thanks again!
Jerry
dramjass
151 Posts
0
February 16th, 2009 08:00
Duncan
jerry.reddick
51 Posts
0
February 27th, 2009 09:00
To make sure I am looking in the correct place in ADSIEdit.
Configuration[domain name] >CN=Configuration>CN=Services>CN=Microsoft Exchange ?
Is this the correct Key? Are the attributes you mentioned, "networkAddress" only created when Replistor is installed? I am headed to customer site this evening and looking at our Exchange AD Attributes currently and do not see those attributes you mentioned anywhere.
Jerry
dramjass
151 Posts
0
February 27th, 2009 10:00
This value is created by the Exchange installation. The RepliStor Exchange module v1 updates this field as mentioned earlier in this string.
jerry.reddick
51 Posts
0
February 27th, 2009 12:00
Full path is...
CN=Configuration>CN=Services>CN=Microsoft Exchange>CN= (Name Given in Exchange Server Manager)>CN=Administrative Groups>CN=(Container from Exchange Server Manager Servers are in)>CN=Servers>CN=Server Name
Thanks!