Regular update will take about 1 hour. I had a lot of issues either while trying to update from 3.1 to 3.2, the only way I got it work is doing a backup with avvid backup utility and download the 3.2.2(c) CD-Boot-Image (not the cco download, thats for upgrade only, You have to know somebody who can give you this image), then restoring the backup.
Try stopping the IIS Admin service prior to the upgrade. There have been times when the IIS service will not stop correctly during the upgrade. I've seen where this causes an error and the upgrade will fail. I don't know for sure if this applies to you, but 36 hours is too long.
We just did the same upgrade. We have a five server cluster and the upgrade went really well. Got a few new minor bugs of which most have been resolved. It took us the better part of about 12 hours to upgrade the whole system.
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 ...