Archive

Archive for the ‘Office 365’ Category

Want to move your Exchange 2010 to Office 365, check these Arabic Episodes

February 19, 2013 Leave a comment

Last week I published around 3 episodes to help you move your Exchange 2010 organization to Office 365, all session are in Arabic helping the Arabic community to move to the latest edges for technologies.

the sessions can be found here:

[Arabic] Office 365 migration – Episode 1 – Registering Domain with Office 365

[Arabic] Migrating to Office 365 – Creating and managing VMs on Windows Azure

[Arabic] Migrating to Office 365 – Episode 3 – Installing and configuring ADFS

Session 4 and 5 are being recorded, so hand on and let me know your feedback about the Episodes

Advertisements

error when migrating users to Live@Edu user UserPrincipalName is not valid SMTP address #msexchange #office365

June 27, 2012 Leave a comment

Symptoms: you are synchronizing users using FIM 2010 and OLSync to Live@EDU domain, everything is configured and when you run the MA you get:

Metaverse object 1%: The expected generated Windows Live ID 2% is invalid. Reason: The UserPrincipalName of MetaVerse object “MV GUID” used to generate a Host WindowsLiveId ‘@domain.edu’ is not a valid Smtp Address.

Solution: make sure that the account used in synchronization is member of domain admin group permissions.

 

The error is 100% not related but that solved the problem.

Mahmoud

you might get an NDR 550 550 5.4.1 Relay Access Denied (state 13). when you move to office 365 #office365 #msExchange #microsoft

June 20, 2012 Leave a comment

you might have seen that error, or you might get it if you deleted your domain from Office 365 and migrated it to a new account, or recently created your domain, or it has been a period of de-activation, the reasons might vary but here is the solution:

– follow the steps here to connect powershell remotely, http://help.outlook.com/en-us/140/cc952755.aspx

 

– issue the following command: set-acceptedomdain <domainname> –outboundonly $True followed by set-acceptedomdain <domainname> –outboundonly $flase

you will have to wait 30-45 minutes for information to propagate to Edge servers cloud @ Microsoft.

have fun.

%d bloggers like this: