Damien writes:

“There are some excellent reasons for willing to use SQL 2012 with Microsoft Lync like the support of the new availability model (Always On). However, Lync 2010 is using a feature called DMO (Distributed Management Objects) that was introduced in SQL 7.0 (a long time ago !).

SQL 2012 does not support this feature anymore as it is indicated in this article : http://msdn.microsoft.com/en-us/library/ms131540.aspx so SQL 2012 will not be a supported platform for Lync 2010 as it is now.”

Full post over here.

/Tim

/Tim

The popular mobile app for the Lync service has an anticipated update for Windows Phone.

There is no changelog published to detail what, if anything, is changed. If you notice anything different, comment below so we all keep posted about the changes!

/Tim

Microsoft®Lync™ Server 2010 Multitenant Pack for Partner Hosting is a unified communications (UC) solution for telecom and hosting providers. Unified communications is a way for telecom and hosting providers to expand their service offering to their current customers.

The Deployment Guide can be downloaded here

Note: Please be aware that some features such as Call Park and Public IM is not supported!

Features Comparision:

/Tim

If your using your own domain with Office 365 or on one of the higher plans check these guides… Set up Lync mobile devices and Set up your network for Lync Online.

Start the Lync mobile client

Enter your username as: <name>@<domain>.onmicrosoft.com

Enter your password:

Specify a username in the same format: <name>@<domain>.onmicrosoft.com

Toggle the “Auto-detect services” & enter the following as the “External Discovery URL”
https://meet.lync.com/Autodiscover/autodiscoverservice.svc/Root

Chances are you’ll never be “internal” to the Office 365 network so we can probably leave the internal one clear for now..!

It looks like some clients doesn’t work if you don’t give them an “internal URL” too, so just repeat the process for the Internal Discovery URL:

You should now be able to connect & enjoy having a play around.

/Tim

After looking in eventviewers and message tracking logs, all emails were delivered without a problem. I tried disabling outlook-rules and using various outlook switches like cleanviews and cleanrules, only to see them vanishing from the sent items folder. 

Another odd thing was, that the sent items were only disappearing if the user requested a read receipt.

After troubleshooting for some hours, I found that the affected users were all using a different DelegateSentItemsStyle.  These users were sending emails on behalf of other users and wanted the sent items to appear in the mailbox of the user and not in the mailbox of the delegate.  According to MS KB articles http://support.microsoft.com/kb/953803 and http://support.microsoft.com/kb/953804 this involved installing a Outlook 2003 hotfix package and adding a registry key.  Which I configured some weeks ago for a set of users.

After some more googling I found there was a bug in the Outlook hotfix package office2003KB953803GLB.

This bug is fixed in Outlook hotfix package office2003KB959628GLB

http://support.microsoft.com/kb/959628

After installing this hotfix all new sent emails showed again in the users sent items folder.

Grtzzzz

/Frederik

As the main theme is “Microsoft Cloud”, I’ll go and present a session on “Integrating your Exchange 2010 on-premise platform with Office365”

As always, I’ll share my experiences of this event in a couple of daily update blog posts when I’m there.

So stay tuned for some news and the end of October.

See yah,

/Peter

More details can be found at their website:

http://blogs.technet.com/b/exchange/archive/2011/08/23/released-update-rollup-5-for-exchange-2010-sp1.aspx

The RU6 is also announced, being available somewhere round October.

Would this mean a monthly rollup update is coming our ways as of now?

Cheers, Peter

http://www.lynctip.be/

/Tim

Please keep in mind that the names and ip’s are fictive in this documentation.

In this setup I choose to install Archiving and Monitoring on seperate hardware. Also keep in mind that you first have to prepare thes servers the way I described in part 1.

If you need more information or if you have questions please send an e-mail to tim.peeters@ictinus.be and I will reply or help you as soon as possible.

Prepare Active Directory Domain Services for Lync Server 2010

The next area for preparation is Active Directory Domain Services. Preparing AD DS for Lync Server 2010 consists of three steps:

· Schema Preparation

· Forest Preparation

· Domain Preparation

Each of these steps can be performed by using the Lync Server Deployment Wizard or the Lync Server Management Shell cmdlets directly.

Install Topology Builder and define Topology for Lync Front-End Pool

Now we have all of the infrastructure preparation complete, so it’s time to move on to defining the topology for Lync 2010 Enterprise Edition in Topology Builder.

1. Log on to Lync Front-End server

2. Go to Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.

3. On the Topology Builder dialog box, select the New Topology option, and then click OK.

4. On the Save New Topology As dialog box, enter a name in the File name field, and then click OK.

5. On the Define the primary domain page, enter the primary SIP domain, and then click Next.

6. On the Specify additional supported domains page, click Next.

7. On the Define the first site page, enter a site name into the Name field, enter a description into the Description field if desired, and then click Next.

8. On the Specify site details page, enter the location details, and then click Next.

9. On the New topology was successfully defined page, ensure the Open the New Front End Wizard when this wizard closes option is selected, and then click Finish.

10. The Define the New Front End Pool wizard opens. Click Next.

11. On the Define the Front End pool FQDN page, type pool1.domain.local into the Pool FQDN field, ensure the Enterprise Edition Front End Pool option is selected, and then click Next.

12. On the Define the computers in this pool page, enter lyncserver.domain.local into the Computer FQDN field, click Add, and then click Next.

13. On the Select features page, check all options you need and then click Next.

14. On the Select collocated server roles page, collocate A/V Conferencing service, and then click Next.

15. On the Associate server roles with this Front End pool page, select all options, and then click Next.

16. On the Define the SQL store page, select the Define a new SQL store option, enter the specified into the SQL Server FQDN field, ensure the SQL Instance option is selected, enter the specified name into the Named Instance field, and then click Next.

17. On the Define the file share page, select the Define a new file share option, enter the specified name into the File Server FQDN field, enter the file share name into the File Share field, and then click Next.

18. On the Specify the Web Services URL page, click Finish.

19. On the Select an Archiving Server page, click New.

20. On the Define the fully qualified domain name page, enter the specified name into the FQDN field, and then click Next.

21. On the Define the SQL store page, select the Use a previously defined SQL store option, enter the specified name into the SQL Server FQDN field.

22. On the Define the file store page, select the Use a previously defined file share option, select the the specified file share from the drop down, and then click Next.

23. On the Select an Archiving Server page, click Finish.

24. On the Select a Monitoring Server page, click New.

25. On the Define the fully qualified domain name page, enter the specified name into the FQDN field, and then click Next.

26. On the Define the SQL store page, select the Use a previously defined SQL store option, enter the specified name into the SQL Server FQDN field, and then click Finish.

27. On the Select a Monitoring Server page, click Finish.

28. You will be presented with the Lync Server 2010, Topology Builder page, which is where you can view and modify the topology that was just created.

/Tim

Next part (part 3) will be Publishing the Topology and Setup the Lync 2010 Front-End server and Front-End pool.