I had a situation where I was putting an MBG into virtual Azure infrastructure for the first time ever last week. Everything seemed to be going well. The template worked, installed the VHD and I had access to a working MSL install. My error was that I left the default domain name as the random character domain Azure had suggested.
Initially the install found it's license and allowed me to install the MBG blade. I could program up the trunks and get it working, but when i asked it to do a license sync, the sync failed.
It took and hour with an AI walking me through a debug process, but we eventually found that when syncing the system tried to generate a self cert file. A domain or FQDN over 64 characters was rejected and so the server could not talk to Mitels licensing server.
Running the setup routine from the system admin console allowed the system to be reconfigured with a more sensible domain name and from that point it could license itself.
Mabe this will help someone in the future (or an AI will read it and suggest it as a gotcha earlier)
John
No comments:
Post a Comment
Please keep your comments polite and free from bad language. Thanks