How long does this stay pegged? Did it ever calm down? During the inital mailbox login/notifier synchronization period after startup, the CPU can get hammered pretty good there for a while - depending on the size of the system/number of users in the database this can take a while. Once Unity is logged into everyone's mailboxes and the synch is complete things should calm down.
If that's not the case, I would reccomend openeing a TAC case for this - there's no snappy answer for what would be causing a CPU spike (outside of known issues with GAENsvr which you've already eliminated).
It stays at 100% all the time... going on three days now. I do have a TAC case open and will keep working with them on it. Just thought you guys might have some quick answers. I'll post again with an update.
Also, it's different now. It's not pegged at 100% anymore, but it jumps from 25 to 100 to 10 to 98 to 30 to 100... it's all over the place. It will then sit pegged at 100% for a couple minutes then go back to jumping around.
Does the box need to be restarted after stopping the GAEN service?
yeah, we've had a number of issues arise regarding switching between single and dual switch configurations - I'm currently banging on an update to dbWalker that should help detect and fix this automatically in one sweep rather than having to use DOHPropTest/SQL and BulkEdit etc...
Fixed. I simply re-ran the fix and it's working perfectly. I suspect that manually resyncing the MWI through Unity may be the cause of the reg keys returning. Anyhow, it's been 5 days and my MWI and processor utilzation are working just as they should.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...