1
Mitel Software Applications / MiCC - Cannot login Ignite(update fails) /CCMWeb/Contact Center
« on: August 07, 2017, 10:40:49 AM »
Hello,
I am relatively new to the world of Mitel and was hoping for some help as our vendor is out of ideas and Mitel is not helping very much ("Its your PC/Network/Group Policy").
Basically, I've installed MiCollab and Client Component pack on about 15 machines with no issues. I took a two week vacation and now any machine that I load the client component pack has the same issues.
- I can ping our micollab server but cannot navigate to CCMWeb, getting page cannot be displayed error.
- I can ping 127.0.0.1 but IIS page does not load when navigating to it. The Microsoft IIS page displays properly on PCs that are working properly.
- MBG is connected and cert approved, but MiCC apps such as Ignite fail to update and then fail to authorize the user due to a webclient exception.
The user accounts load on other PCs, pointing me to some setting or service that is not enabled or an update that the working PCs didnt take. These PC's are on the same subnet, same OU, same GPOs, same image, but any new clients I try to set up after our initial rollout are not working. Anyone seen this before?
Please help and feel free to ask questions.
Thanks!
I am relatively new to the world of Mitel and was hoping for some help as our vendor is out of ideas and Mitel is not helping very much ("Its your PC/Network/Group Policy").
Basically, I've installed MiCollab and Client Component pack on about 15 machines with no issues. I took a two week vacation and now any machine that I load the client component pack has the same issues.
- I can ping our micollab server but cannot navigate to CCMWeb, getting page cannot be displayed error.
- I can ping 127.0.0.1 but IIS page does not load when navigating to it. The Microsoft IIS page displays properly on PCs that are working properly.
- MBG is connected and cert approved, but MiCC apps such as Ignite fail to update and then fail to authorize the user due to a webclient exception.
The user accounts load on other PCs, pointing me to some setting or service that is not enabled or an update that the working PCs didnt take. These PC's are on the same subnet, same OU, same GPOs, same image, but any new clients I try to set up after our initial rollout are not working. Anyone seen this before?
Please help and feel free to ask questions.
Thanks!