That's good news?
That's good news?
...and there's more
The HT came to me today to ask if it might be possible to get this done by the end of term - as Easymail are going to enforce a better password policy in Sept so everything will have to change and I will be back to square one..
I pointed out that I hadn't been allowed to get the SLT and Office passwords so I would not be able to say whether or not they will have the same issues as all the others. I can get the MX record changed over and easymail left alone so we will have parallel systems for a while.
Really though - why wait till now? He is also about to put in an order for a new IT suite to be installed at the back end of the summer (depending on my availability - hmmmm - term-time only, no overtime.....)
I do have a question though. Looking at my email migration, I notice that it has stopped and if I restart it, it only does it once and stops again. I was led to believe that it would keep syncing until I stopped it myself.
It is a pain as I will have to keep starting it to make sure things are all migrated. Have I done something wrong? Can anyone help?
It gets worse
Because the migration will need to be restarted multiple times I have now amalgamated all 55 users into one csv. I had done them separately so that I could see at a glance which ones failed - but now they all work I can put them into one synchronisation - or so I thought...
I have had the csv file checked over by microsoft - it looks fine and when I queue up the job it states "55 mailboxes"
I have come in this morning to find it saying "synced" but with 0 mailboxes and 0 failures - no error message of any kind.
This is all way above my pay grade - has anyone any ideas please?
Have you deleted other batches? Can't have more than one migration with same user.
Delete all the individual ones and start it again
The other batches all have different names and according to microsoft, that is fine - but yes, I have deleted them all anyway (which will be a complete pain if I have to reinstate them )
Name doesn't matter. It's the account names with the batch that matters.
Hit the refresh button as sometime they show as deleted but then show as removing and you need to wait for it to be fully removed
Definitely everything is gone and the new batch won't work
Tried to connect to exchange online using Powershell on the instructions of my brilliant Microsoft tech. Kept erroring out (see attached)
Spoke to SWGfL who said "if you can connect to Office 365 then there isn't a problem and we don't support Office 365 anyway"
Delete all te batches and start again with your new 55 user one.
On your powershell error should it be ConnectionURL no uri?
And you hit the refresh button to fully ensure all batches were not in a removing state?
I have been doing this for %^&*^% months now
I removed everything last night
refreshed it this morning
Rang Microsoft guy (who got me through before)
He tried to connect to exchange servers via powershell
Never seen this before, apparently
Google Apps for Education????has anyone any ideas please?
All the Office 365 schools I know have had issues migrating, they got there but not without issues. Not very helpful for you but hay ho.
Ok @witch, try this as it might be a proxy server issue
Code:$proxysettings = New-PSSessionOption -ProxyAccessType IEConfig $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://ps.outlook.com/powershell/" -Credential $cred -Authentication Basic -AllowRedirection -SessionOption $proxysettings
There are currently 1 users browsing this thread. (0 members and 1 guests)