Hi, I have a situation where on one of my AWS if I try to run script editor it does not start, I get an hourglass for a split second but nothing else happens. The other AWS is fine and both were fine earlier today (and for some time). Any idea what is stopping it, I have looked for locks but do not see any held.
I can remember an incident, whenever i did try to open the script editor, it showed an error related registry. I deleted my windows profile from AW being local admin, and logged in again with my domain user and found the issue resolved.
A client Admin Workstation has to join the ICM domain. It makes perfect sense that you should log in on the domain. In ICM, you can create users which are pushed up to the DC (have to obey password rules) and are created therein. Now they are domain logins. Why not use them?
Back to the original problem. The script editor can do this whether it's on a Client AW or even a Distributor AW. There is no rhyme or reason - it just happens. When it does, do as Chad suggested - find scripted.exe in the task manager and bump it off.
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...