[cisco-voip] RE: Unity showing up as Exchange 5.5

Marc Hering mhering at reval.com
Thu Mar 10 15:13:32 EST 2005


I forget which one it is...it's ether the message store configurator or the permissions wizard..but if I recall..one of those should allow you to see the list of servers...then you uncheck it to remove it....it's been a while but I THINK that is what I had to do....
HTH

________________________________

From: Aaron Kent [mailto:Aaron.Kent at apptis.com] 
Sent: Thursday, March 10, 2005 3:14 PM
To: Marc Hering; cisco-voip at puck-nether.net
Subject: RE: [cisco-voip] RE: Unity showing up as Exchange 5.5



Yes, but I do not recall that.

 

________________________________

From: Marc Hering [mailto:mhering at reval.com] 
Sent: Thursday, March 10, 2005 3:11 PM
To: Aaron Kent; cisco-voip at puck-nether.net
Subject: RE: [cisco-voip] RE: Unity showing up as Exchange 5.5

 

Did you run the message store configuration to rehome the Unity box????  If I recall correctly it should allow you to remove unity extensions from a specific server...

 

 

 

________________________________

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Aaron Kent
Sent: Thursday, March 10, 2005 2:34 PM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] RE: Unity showing up as Exchange 5.5

Good afternoon,

 

I have a Unity 4.0 on Server 2000 with is fully integrated into our AD2003 forest. It was initially a Unity 2.4 install with Exchange 5.5 on-box server. We upgraded to 3.1 and moved the message store off-box about 3 ½ years ago when we were still a NT domain. Then 6 months ago we moved to 4.0 and did all the schema changes for Unity to work correctly in AD. Our Exchange administrator has been working for the last 6 months on decommissioning all the Exchange 5.5 servers in hopes to run in a native Exchange mode. Last night anxiously made the change and was promptly alerted that there was still an Exchange 5.5 box (Unity) active and he had to continue to run in hybrid mode until that was removed. 

 

My question is with the above taken into consideration, "How do I accomplish the task of decommissioning Unity as a 5.5 server without disrupting operation of the Unity server function?" We have no failover capabilities to utilize for uptime considerations and have 99.9% uptime SLAs to meet for a very picky customer. 

 

We have regular maintenance windows between 10PM and 5AM every night so time is not an issue, it is availability. We have a managed service and we are only allowed to reboot the server or down the unity services from 10PM Sunday night to 3AM Monday morning. Any input you can offer would be greatly appreciated.

 

Thanks,

Aaron

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050310/7d343888/attachment-0001.html


More information about the cisco-voip mailing list