Last night I tried to upgrade our 3.1(4) Unity server and had two major problems.
1) I had a problem upgrading my MSDE to any version. (I'm currently on MSDE2000 SP1) I have been reading the many posts and workarounds for upgrading MSDE, none of them helped me. I am getting the same errors as many people do "Invalid instance name", "Product not found".
2) Since I was already at MSDE2000 SP1 (I met the requirements for Unity 3.1(5)) I elected to proceed and tackle MSDE at a later point. I ran SETUP on the 3.1(5) cd, it went all the through with no errors and then requested a reboot. After reboot and logging back in, the setup continued with the Message Store configuration screen. I was prompted to enter the password for the service account used by the Unity to log into the message stores. I verified the password many times, and it still would not proceed any further. I eventually had to cancel the setup process.
I know for certain I was using the right password. I verified it by logging into the server with that account and password. I was successful.
After all this, Unity was upgraded to 3.1(5), and it appeared to work properly. MWI's wouldn't work even though all the Unity services started without error.
After a long night and trying the upgrade twice, we reverted back to the baclkup we had. (I pulled one of the mirrored hard drives before the upgrade and did a switcharoo to get back to 3.1(4))
Has anyone who has upgraded from 3.1(4) to 3.1(5) seen this?
There used to be a similar issue if the account did not have the "act as the operating system" and "log on as a service" rights. I believe that should have been fixed by 3.1.5, but you could check to see if the account that's going to run the AvMsgStoreMonitor has those rights.
If that still doesn't work, look for a hidden file called tempu.log and post it here. That's a log of the install/upgrade process that might help us out.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
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 ...