tag:blogger.com,1999:blog-54398368907965852752024-03-22T12:16:24.024+01:00Exploring Microsoft's UCExploring UChttp://www.blogger.com/profile/03144479339271968966noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5439836890796585275.post-15643114185954122732009-05-27T16:51:00.006+02:002009-05-27T19:03:14.648+02:00How to add a MSN contact to your communicator contactlistIf your company had an OCS edge server deployed, one of the possible options is use Public Instant Messaging Connectivity (PIC).<br /><br />PIC enables your company to chat with MSN, Yahoo & AOL users. I don't have contacts using Yahoo or AOL, but I do have msn-contacts.<br /><br />When you add a contact outside your domain (MSN or federated) OCS will see this address as a federated contact and start a search for the according domain. This works fine if the contact uses federation or when you MSN-contact is registered with a hotmail.com, Live.com or MSN.com domain. But it will fail if the contact is registered with another (mail)address.<br /><br />In order to fix this, you need to change the address, i.e.:<br /><a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk@thenetherlands.com</a> has to be changed into <a href="mailto:Pietje.puk@microsoft.com)@msn.com">Pietje.puk(thenetherlands.com)@msn.com</a><br /><br />The domain MSN.COM will translate this back into the original address and warns the msn-contact that somebody wants to chat.<br /><br />By default, the contact you add will get Access Level 'Public'.<br /><br />Completing the list:<br /><a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk@thenetherlands.com</a> --->> <a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk(thenetherlands.com</a>)@msn.com<br /><a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@hotmail.com">@hotmail.com</a> --->> <a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@hotmail.com">@hotmail.com</a><br /><a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@live.com">@live.com</a> --->> <a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@live.com">@live.com</a><br /><a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@msn.com">@msn.com</a> --->> <a href="mailto:Pietje.puk@thenetherlands.com">Pietje.puk</a><a href="mailto:msncontact@msn.com">@msn.com</a><br /><br />Suc6Exploring UChttp://www.blogger.com/profile/03144479339271968966noreply@blogger.com8tag:blogger.com,1999:blog-5439836890796585275.post-40447811412935277442009-04-24T21:48:00.008+02:002009-04-24T22:51:36.399+02:00Access Edge service terminated with service-specific error 3286842466 (0xC3E93C62)This morning, a friend of me and former colleague deployed an OCS 2007 R2 environment with an OCS Edge.<br /><br />The customer should take care of the according firewall rules.<br /><br />After completing the deployment, he was unable to start up all the OCS Edge services. He got the following error:<br /><ul><li><span style="color:#ff0000;">Failed starting the protocol stack. The service has to stop<br />Error code is:0xC3E93C62 (SIPPROXY_E_NO_DEFAULT_OUTGOING_CERT).Cause: Check the previous entries in the event log for the failure.</span></li></ul>In the Event log he found the corresponding error:<br /><ul><li><span style="color:#ff0000;">The Office Communications Server Access Edge service terminated with service-specific error 3286842466 (0xC3E93C62).</span></li></ul>When he studied the corresponding certificate, he found the path to the Certificate Revocation Lists Url: <a href="http://crl.geotrust.com/crls/secureca.crl">http://crl.geotrust.com/crls/secureca.crl</a><br /><br />He tried to open the page from the Edge as well from the ISA firewall, but failed.<br /><br />After re examin the firewall rules he learned that the customer did not set the outbound firewall rule to download certificate revocation lists.<br />The rule has the be configured as:<br /><ul><li>External</li><li>Local Port: 80 HTTP.</li><li>Direction: Outbound (to download certificate revocation lists).</li><li>Remote Port: Any.</li><li>Local IP: The external IP address of the Access Edge service.</li><li>Remote IP: Any IP address.</li></ul>When he applied the rule, he was able to start the Access Edge service and tested with success Open Federation.Exploring UChttp://www.blogger.com/profile/03144479339271968966noreply@blogger.com2tag:blogger.com,1999:blog-5439836890796585275.post-22572430343560028842009-04-24T09:59:00.003+02:002009-04-24T21:48:03.243+02:00OCS CertifiedLast week I went for my OCS Exam TS: 70-638 and I was able to pass the exam. :-)<br /><br />It took a while, but finally i'm OCS certified.<br /><br />Next week I will follow the Voice Ignite training in Amsterdam (NL), which will be given by Steven van Houttum.<br /><br />Let´s hope they will do a lot of R2 features.Exploring UChttp://www.blogger.com/profile/03144479339271968966noreply@blogger.com0tag:blogger.com,1999:blog-5439836890796585275.post-36194091064784725432009-02-10T20:57:00.001+01:002009-02-10T22:42:19.575+01:00Import-Mailbox cmdlet gives statuscode -2147221219<span style="font-size:85%;">For a customer I had to create a method for importing multiple PST-files into a new Exchange Server 2007 Environment. The PST-files were already exported with ExMerge from Exchange Server 2003.</span><br /><span style="font-size:85%;"></span><br /><span style="font-size:85%;">If you want to import mailboxes I usualy use the cmdlet 'Import-Mailbox'. This cmdlet is part of the Microsoft Exchange Server 2007 Management Shell. For more information on how to use this cmdlet, visit <a href="http://technet.microsoft.com/en-us/library/bb629586.aspx">this site</a>.</span><br /><br /><span style="font-size:85%;">When I started the import, it throws me the following error:</span><br /><span style="font-family:verdana;font-size:85%;color:#ff0000;">StatusCode : -2147221219<br />StatusMessage : Error occurred in the step: Approving object. An unknown error has occurred.<br />ReportFile : C:\Program Files\Microsoft\Exchange Server\Logging\MigrationLogs\import-Mailbox20090209-103301-5655000.xml<br /></span><br /><span style="font-family:verdana;font-size:85%;">I tried to import another PST-file but I got the same error as mentioned above. I figured out is was a consistent error. To troubleshoot this i checked the following possibilities:</span><br /><ul><li><span style="font-family:verdana;font-size:85%;">I can open the mailbox on the server with an Outlook-client</span></li><li><span style="font-family:verdana;font-size:85%;">I have the correct credentials on the users mailbox</span></li><li><span style="font-family:verdana;font-size:85%;">I have the correct credentials on the Exchange Server having the MailboxRole. </span></li><li><span style="font-family:verdana;font-size:85%;">I googled the error. Plenty of hits with many solutions, but none according to the above error.</span></li><li><span style="font-family:verdana;font-size:85%;">I looked at the ReportFile. A lot of XML-code and the same error as mentioned above, but it explains nothing.</span></li><li><span style="font-family:verdana;font-size:85%;">I exported the empty mailbox and I imported again. No errors.</span></li></ul><span style="font-family:verdana;font-size:85%;">Non of the above gave me a clue.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Then I ran the cmdlet with the '-debug' option so I could figure out at wich step the import went wrong. This opens my eyes.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">During the step 'Approving object' the cmdlet opens the PST-file and tries to get access to the objects (mail/calender/etc.) within the PST-file. If the action succeeds, the objects wil be moved (read copied) to the mailbox on the server. For some reason, the PST-file couldn't be opened.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Opening the PST-file with my Outlook-client shows an empty mailbox (the file is about 800MB) and I was not questioned to give up a password.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Than, I decided to import my own PST-file into the mailbox and it gave no error.</span><br /><span style="font-family:verdana;font-size:85%;">Ok. Let's put password protection on my own PST-file and start the import again.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Bingo! I got the same error as above. It looks like the PST-files were exported with the option 'with user password'.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">After I got a new export the import did not give any errors anymore.</span>Exploring UChttp://www.blogger.com/profile/03144479339271968966noreply@blogger.com1