I know you have a busy time ahead! I dont expect you to drop everything and help me...
I just want to know how to do things - there isnt any explanation anywhere
Apparently I deleted that initial one - didnt think I had but its gone now
It can wait till next week but I dont expect you to leap to my side - again -
Ok well if we can I'd like to take a look over teamviewer or similar next week.
Busy? Where? My network is running quite smoothly so I've plenty of time for all out other distractions in the other roles I also do so throwing a few helpful suggestions your way is fine and helps the day pass quicker.
You said you have a lot of accounts still to do, roughly how many.
For my migration I had 100 accounts to generate CSV files for and manually created 10 jobs for the first 10 staff, and every time I got an e-mail confirmation of completion I added the next one to the batch. This was mainly to ensure I did not overload my mail server with imap connections. I did have the luxury of doing the migration after I'd told the staff to only use 365 so I only had to worry about 1 sync per account.
The total time for all 100 accounts was about 9 hours and some of that was out of hours since you can select to run the task later. I connected to the admin page at home and started a few off in between web browsing.
Grab a coffee and some hobnobs and recharge before doing the next batch.
I have created individual csvs for all staff, which is fewer than I had thought - 47 in all
I did a quick google and the advice was that I could run them all together. So I did.
That'll fail then, will it?
I have started to get messages that some of the migrations have finished and that I can download the success report - that's good, is it? :)
I have some failures though and when I click on the error report, I get an error! What do I do about those?
There is nothing wrong with having multiple accounts per csv, but it then does make troubleshooting failures a bit more difficult as you have found.
Separate files means that if JoeBloggs fails, then you can just restart that task, or if they had updated the password in the day or so since they told you, amend the csv and then reapply it to that task.
Success reports is positive as it means that it's all good.
For the failure reports, just restart the task for a second time (assuming it is not already failed twice) If it has failed multiple times it might need more investigation.
I have 16 failures. All error reports are about not being able to contact the server - I have checked 3 or 4 and the passwords are correct. I will start them again and see
Alll 16 have failed again already
I checked more passwords and they are all fine
First thought, can you login successfully to both easymail and 365 as one of the failed users.
Thought it was all going too well - today I logged on with my A2 account and tried to carry out a migration. However, I don't see the same permissions I had in the A3 account (which expires today) - I'm pretty sure I did set the A2 up with the right permissions?
Yep - I logged on successfully to both
Originally Posted by Boredguy
I clicked on "resume" to resync - is this right or is there another way?
You can still login with your main tenancy admin account. Just make sure you give it a A2 faculty license.
Originally Posted by speckytecky
Your other account should have basic permissions unless you have assigned a role to it (such as global administrator which is the same as your tenancy admin account)
That's the right way, or you can delete the task and re-create it. Just seeing if I can get any information for the possible reasons for it not being able to connect to server, since all the others seemed to behave.
Originally Posted by witch
I don't suppose the troublesome account has any e-mails greater than 35Mb in it does it as that can cause issues apparently.
Ok sorted out the permissions bit - now has Global Admin. Next sticking point is on the port. It won't let me change from 993 to 143?
At which point @speckytecky? You can only select the port and encryption level (or none for easymail) when creating the endpoint initially.
Whenever you create a migration task it will bring up the screen with your easymail endpoint and all the other values greyed out. This is fine to ignore and continue.