We had a problem upgrading from Unity 2.4.105 > 2.4.120. The upgrade process completed normally, but seemed to completely trash the exchange server local to the Unity box. I couldn't even open up the exchange administrator after this. <br><br>Also, if you look in the event log we see failure audit errors event id 1023 category logons.<br><br>The error reads:<br>XXXXX\Exchange was validated as /o=XXXX/ou=YYYY/cn=Recipients/cn=Unity_XXXXX but was unable to log on to /o=XXXX/ou=YYYY/cn=Recipients/cn=XXXX/cn=123456<br><br>I talked to tech support and they said this is normal. Is there anything in the works for a future release of Unity to fix this?<br><br>
Im having an extremely difficult time believing our upgrade could have been responsible for trashing your Exchange server. The upgrade process has had other problems along the way, but nothing that would harm the local Exchange server in any way. The upgrade between 105 and 120 doesnt even have to upgrade the directory at all as opposed to, say, an upgrade from 2.3.4 to 2.4.0 where we have to walk the directory and add new collections (for instance the new notification devices added between those releases).
Theres nothing our upgrade process would be doing that could hurt Exchange. Ive never got a report before this that anyone had any trouble with Unity damaging their local Exchange server. Theres no fix in the works for this since I dont think we have a problem.
Whats the error you get when you try to open the administrator? Did someone in support really tell you this was normal or were they just talking about that event log error? Is this part of a larger Exchange site or is it a stand alone POV install (based on the event log error Im assuming theres at least one other Exchange server in the site)? Any chance the Exchange admin account was toasted somewhere along the way? Ive seen that before at another site they also pointed the finger at Unity, however the logs revealed another admin accidentally deleted that account. It happens.
Is Unity running?
The event log you mention looks to be normal. When Unity is in one Domain and a subscriber is in that Exchange site but a member of a different domain, youll see that error in the event log. We log into each box to monitor its inbox activity (for lamps, notification events and the like). Each one of these logins will result in an entry in the log. Theres nothing we can do to prevent it, however its not a problem. If everyone is in the same domain, something else is going on along those lines.
Im very curious to know more about why you think we trashed your Exchange server and whats happening when you try to open the administrator.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...