we are migrating a server from UCX 1.2 to UCX 7.0(2a). It is not a big system, few call handler, and less then 100 users.
The first import was succesfull even if all the users got the the option "user cannot change phone password" selected. We selected the option to override default for "user cannot change phone password" leaving it unflagged, and "user must change password at next logon" this one flagged, but it seems that the software did exactly the opposite. This was not a big issue, because we did not have many users we could change it manually.
After this we found a worse issue with the messages. basically the messages could not be imported. I read everything is written in the manual regarding the SMPT, and firewall to be stopped and antivirus....
In my last try I used my PC (before I was forced to use the customer PC, and indeed that une was subject to several microsoft Policy), connected to the same VLAN of the Unity server, but still got the error message
The first issue (reversed logic on the must/can't change) is fixed in the latest version of the import posted out there currently.
The WAV file upload - this isn't messages, it's greetings. MEssages come in via IMAP, the wav upload throwing that error is going through an HTTP POST (HTTP GET on an export) to move greetings and voice names off and on to the server. Make sure there's not an HTTP proxy or something blocking the ports listed under the HTTP section in the help - the messaging section your're referring to doesn't come into play here.
...again, though, the error message noted in the first post has nothing at all to do with email or SMTP. It's an error uploading a WAV file via HTTP. But anti-virus can, of course, still be at play there.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.