Updates from Rayan Hanoudi Toggle Comment Threads | Keyboard Shortcuts

  • Rayan Hanoudi 2:23 pm on November 21, 2011 Permalink | Reply
    Tags:   

    Lessons Learned with Office 365 

    Lessons learned

    1. We noticed very slow performance when accessing a secondary mail file from Outlook 2007.  Upgrading to Outlook 2010 corrected the problem.
    2. Upgrade of Office 365 from the professional version to enterprise version is not easy.  See Lisa’s Blog for details.
    3. We noticed two problems with both Outlook 2007 and 2010:
      1. Calendar reminders do not show up.
      2. Unread email messages with the following information:

    11:37:00 Synchronizer Version 14.0.6025

    11:37:00 Synchronizing Mailbox ‘Rayan Hanoudi’

    11:37:00 Synchronizing local changes in folder ‘Drafts’

    11:37:00 Uploading to server ‘CH1PRD0402.mailbox.outlook.com’

    11:37:01 Synchronization of some deletions failed.

    11:37:01                         [80040115-514-80040115-130]

    11:37:01                         Network problems are preventing connection to Microsoft Exchange.

    11:37:01                         Microsoft Exchange Information Store

    11:37:01                         For more information on this failure, click the URL below:

    11:37:01                         http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80040115-514-80040115-130

    11:37:01           1 item(s) deleted in online folder

    11:37:01 Done
    I found a fix on the office 365 community forum: http://community.office365.com/en-us/f/160/p/11060/48912.aspx

    We had to:

    1. Quit Outlook, delete the OST file and start Outlook again and have it rebuild the file.
    2. Quit Outlook, Turn off “Use Cached Exchange Mode”, start Outlook.  Exit Outlook and enable “Use Cached Exchange Mode” again.
    3. There is still on outstanding issue with an unread email that shows up all the time:

    9:49:36 Synchronizer Version 14.0.6109

    9:49:36 Synchronizing Mailbox ‘Rayan Hanoudi’

    9:49:36 Synchronizing local changes in folder ‘Drafts’

    9:49:37 Uploading to server ‘CH1PRD0402.mailbox.outlook.com’

    9:49:37 Synchronization of some deletions failed.

    9:49:37                   [0-130]

    9:49:37    1 item(s) deleted in online folder

    9:49:37 Done

    Many people are having this same exact issue, see this blog post:  http://community.office365.com/en-us/f/146/t/3437.aspx

     
    • A B 10:33 am on March 5, 2013 Permalink | Reply

      Will try the options 1&2 soon as I have the identical error message. Will confirm if it works so that you know it is a deffinet fix. Thanks, this website is the only one on which I could find the answer.

  • Rayan Hanoudi 1:16 pm on October 27, 2011 Permalink | Reply
    Tags: ,   

    Part 2 of 3: Steps to finalize the upgrade to Office 365 

    After following the pre-migration steps, we followed these steps to finalize the upgrade:

    1. Verify that Office 365 is working correctly and we can send and receive emails.

    2. Create forward rules from Lotus Notes to Office 365. We still have many Lotus Notes applications that were not migrated at the time of the email migration. We setup a forward rule in Lotus Notes’ address book to forward to office 365 addresses.

    3. Import external contacts from Lotus Notes directory to Office 365 using PowerShell script. The external contacts are clients or vendors email addresses and phone numbers that we share between the team. Since there is no UI tool to allow us to do import the contacts in Office 365, we had to write a PowerShell script to import the contacts.

    4. Previous calendar entries had to be manually created in Outlook for each user.

    5. Configure the Outlook/mobile device client for each user

    6. Setup user signature in Outlook

    7. Setup rules in Outlook

    8. Import/manually enter personal contacts that were created in Lotus Notes.

     
  • Rayan Hanoudi 8:13 am on October 19, 2011 Permalink | Reply
    Tags:   

    Part 1 of 3 – Migration from Lotus Notes to Office 365 

    Migration from Lotus Notes to Office 365

    I wanted to document our process that we followed to migrate from Lotus Notes to Office 365. We have had to do quite a bit of research on how this process should go. Since we have found bits and pieces all over the internet. These are the step that we took pre-migration.

    1. In our case, we changed the company name from Ebiz Technology to TractionCRM. We ended up purchasing a new Internet domain to be used in Office 365

    2. Purchase new office 365 accounts from http://www.office365.com

    3. Setup all mail files ahead of time on Office 365

    4. Enable IMAP on the Lotus Notes server

    5. Update firewall rules to allow IMAP from the Internet to access Lotus Notes IMAP.

    6. We used the IMAP connector to synchronize the email messages between Lotus Notes and Office 365.

    7. Calendar entries do not migrate when using POP/IMAP. We had to make a copy of the calendar entries and manually create those entries in Outlook.

    8. Turn off out office agent and rules from Lotus Notes

    9. If the end user used mail rules. Those rules had to be manually created on the Outlook side

    10. Setup “Connected Account” in Office 365 to fetch emails every hours from Lotus Notes. In our case, customers still sent emails to our ebiz email address and the connector fetched those emails automatically every hour.

    11. On migration day, we delegated DNS to office 365 name servers

     
    • Murali V 2:45 am on July 16, 2013 Permalink | Reply

      Hi Rayan

      please provide more information on IMAP connector to synchronize the email messages between Lotus Notes and Office 365, as need to understand more on this

  • Rayan Hanoudi 4:35 pm on March 7, 2011 Permalink | Reply
    Tags:   

    Microsoft CRM 2011 Top 10 New Features 

    I’m excited about CRM 2011. There are a lot of new features that I’m looking forward to using. I wanted to blog about top 10 new features, but it like other bloggers beat me to it. See this blog site: http://crmrocks.net/?p=64

    I will follow up with features still lacking in CRM 2011.

     
  • Rayan Hanoudi 4:21 pm on February 2, 2011 Permalink | Reply
    Tags:   

    Microsoft CRM 4 is a great CRM system, however there are a few things about how Microsoft implemented some key aspects of it makes me wonder if the engineers at Microsoft spent enough time thinking through the architecture.

    A perfect example of this is CRM Plugin for Outlook. The basic design assumes that each user will install and configure the Plugin to work correctly. Here are a few problems with this design:

    1. Client Side Calendar Sync: One of our clients have many internal staff that create calendar entries on behalf of their sales staff. The calendar sync does work, however Outlook has to be open in order for the calendar entries to sync. This is in my opinion is a major design flaw. In today’s world people rely on their mobile device to see their calendars and asking sales staff to have Outlook open all the time does not always seem like a good solution. Exchange and CRM are both Microsoft products why can’t we have a server side calendar sync tool?

    2. Email sending. There are two options here, but each has its own flaws. The CRM for Outlook has the same client send problems described above. The CRM router is a better solution, however it relies on manual intervention for adding and removing users. Again both CRM and Exchange are Microsoft products. Why can’t the email part be seamless?

    3. CRM Plugin installation. The CRM Plugin can be installed through the web site. On a recent client engagement they wanted all their clients to have the latest plugin. Some of the users had rollup 3 (don’t get me started on the build numbers instead of the a simple version number) installed, which is a very old version. I tried to upgrade the clients directly to rollup 15 however rollup 7 is prerequisite. So instead of just doing one update I had to do two. For the clients that did not have the CRM Plugin I couldn’t use the rollup 15 directly. I had to install rollup 3 first, 7 then 15. What a pain. The CRM Plugin should be a simple installation and it should just work…

     
  • Rayan Hanoudi 3:12 pm on November 23, 2010 Permalink | Reply
    Tags:   

    We had a project to migrate a Domino server from a dedicated host to new Virtual Machine (VM) host.  We typically don’t do much server administration.  Having migrated over a hundred Domino servers in my previous job, I didn’t think this would be any different than any other Domino migration.

    The requirement for this project was a migration instead of a move.  The customer wanted a clean server install without any legacy installs from years of previous Domino installs, plus the new OS was newer and it was running 64 bit.  There were a couple of complications, the customer is running all of these services:  DAOS, Transaction logging, BES, Traveler, ReplicAction, SMTP.  Having all these services running on the one Domino server.  We decided to move BES to a new host and replace ReplicAction with another tool.

    I setup the new Domino server with a new name, setup transaction logging, DAOS then started replicating the databases over to the new server.  At this point everything worked great.  I had a user switch to the new Domino server and everything worked fine.  To minimze distrubtion with having users switch to the new server name, we opted to switch server ID files and updated DNS.  The next day we started hearing from users that they couldn’t open certain files.  We then realized that the DAOS encrypts the files with server ID, the attachments replicated during the setup period of the new server were encrypted with the temporary ID we used to setup the new server and the original server ID could not decrypt the attchments.  I found a good article here that explains DAOS encryption:

    http://www-10.lotus.com/ldd/dominowiki.nsf/dx/daos-best-practices#Encryption

    Luckily we were able to copy the encrypted DAOS NLO files and corrected the problem.  For anyone reading this, remember to turn off DAOS encryption (DAOS_ENCRYPT_NLO=0) when swapping servers.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel
%d bloggers like this: