Matt Landis: http://windowspbx.blogspot.co.uk/
http://windowspbx.blogspot.co.uk/2012/11/lync-2010-training-resources-list.html?utm_source=dlvr.it&utm_medium=twitter&utm_campaign=Feed:+MattLandisWindowsPbxUcReport+(Matt+Landis+Windows+PBX+%26amp;+UC+Report)
-Lync 2010 Attendant Training: http://www.microsoft.com/en-us/download/details.aspx?id=11472
-Outlook Voice Access/VoiceMail Reference Sheet (choose your languague even!):http://www.microsoft.com/en-us/download/details.aspx?id=20772
-PowerPoint Lync Training: http://www.microsoft.com/en-us/download/details.aspx?id=16547
-How To Video Training for each individual thing:http://office.microsoft.com/client/helpcategory.aspx?CategoryID=CL101833114&lcid=1033&NS=COMM14&Version=14
-Lync Adoption/Training Kit: http://lync.microsoft.com/adoption-and-training-kit/Pages/default.aspx
Tuesday 20 November 2012
Configuring Reverse Proxy for Lync Server 2010 Mobility
http://blogs.technet.com/b/nexthop/archive/2012/11/19/configuring-reverse-proxy-for-lync-server-2010-mobility.aspx?utm_source=dlvr.it&utm_medium=twitter
Monday 19 November 2012
Exclude Contact Folders from Exchange Mailbox in Lync
set-csclientPolicy -identity global -ExcludedContactFolders “Contacts;Suggested Contacts;frequent contacts”
Thursday 15 November 2012
Lync Client Log Files
To turn on Logging
In the Communicator Title bar, click the Menu button, point to Tools, and then click Options.
Click the General tab, and then under Options, select the Logging options that you want to enable.
To locate the Communicator log file
In Windows Explorer, navigate to the <user profile>\Tracing folder. If you have enabled the Turn on Logging in Communicator option, you will see a communicator-uccp-log.uccplog file in the folder. If you are already signed in, you will need to sign out and then sign back in before the log file is created.
Also lync 2011 for mac log files are located:
/Users/username/Library/Logs
In the Communicator Title bar, click the Menu button, point to Tools, and then click Options.
Click the General tab, and then under Options, select the Logging options that you want to enable.
To locate the Communicator log file
In Windows Explorer, navigate to the <user profile>\Tracing folder. If you have enabled the Turn on Logging in Communicator option, you will see a communicator-uccp-log.uccplog file in the folder. If you are already signed in, you will need to sign out and then sign back in before the log file is created.
Also lync 2011 for mac log files are located:
/Users/username/Library/Logs
Windows Live contacts that use a custom (EASI) domain
Symptoms
Consider the following scenario. You add Windows Live, MSN, or Windows Live Hotmail contacts to a Microsoft Lync Online user’s contact list. To do this, you use an E-mail As Sign-In (EASI) ID domain instead of a default @live.com address. In this scenario, you may experience the following issues:
Presence is unavailable, and the status is displayed as Presence Unknown.
Instant messages cannot be delivered or sent.
In the following sections, the following domains are used as placeholder examples:
Lync Online domain: contoso.com
Windows Live EASI domain: live-contoso.com
Cause
Public Internet Connectivity (PIC) in Lync Online supports Windows Live, MSN, and Windows Live Hotmail. However, when you add PIC contacts that use a Windows Live EASI domain such as live-contoso.com, Lync Online cannot resolve the IM Federation server based on the domain suffix.
If you directly add a PIC contact by using the contact’s EASI ID (for example, you use JoeAndreshak.@live-contoso.com), a specific Service (SRV) record is required in the Domain Name System (DNS) for live-contoso.com. This SRV record is required because the Lync Online server uses the domain suffix in the user's EASI ID. In this example, the Lync Online server tries to use the live-contoso.com domain suffix. The Lync Online server tries to identify an SRV record that points to the Instant Messaging (IM) federation server for the domain.
Resolution
To resolve this issue, use one of the following methods.
Method 1
Use the EASI Windows Live ID together with PIC when you add a user to your Lync 2010 contact list. To do this, you must make a change in the search field. A Lync Online user who wants to add the EASI Windows Live ID, such as <username>@live-contoso.com, must add an address that resembles the following to the search field:
JoeAndreshak(live-contoso.com)@msn.com
This method allows for a quick resolution if Lync Online users are only going to add a few PIC contacts.
Method 2
The Lync Online administrator must add the correct SRV Federation records to the DNS host for the Lync Online environment. The Windows Live EASI domain owner must also add an SRV record that resembles the following example to the DNS host for the Windows Live EASI environment:
_sipfederationtls._tcp.live-contoso.com
port = 5061
server hostname = federation.messenger.msn.com
Administrators can let Lync Online users add contacts without having to use the special format in "Method 1" in the "Resolution" section. To do this, administrators must add an SRV Federation record that Lync Online users can access to add contacts to the Windows Live EASI domain.
Consider the following scenario. You add Windows Live, MSN, or Windows Live Hotmail contacts to a Microsoft Lync Online user’s contact list. To do this, you use an E-mail As Sign-In (EASI) ID domain instead of a default @live.com address. In this scenario, you may experience the following issues:
Presence is unavailable, and the status is displayed as Presence Unknown.
Instant messages cannot be delivered or sent.
In the following sections, the following domains are used as placeholder examples:
Lync Online domain: contoso.com
Windows Live EASI domain: live-contoso.com
Cause
Public Internet Connectivity (PIC) in Lync Online supports Windows Live, MSN, and Windows Live Hotmail. However, when you add PIC contacts that use a Windows Live EASI domain such as live-contoso.com, Lync Online cannot resolve the IM Federation server based on the domain suffix.
If you directly add a PIC contact by using the contact’s EASI ID (for example, you use JoeAndreshak.@live-contoso.com), a specific Service (SRV) record is required in the Domain Name System (DNS) for live-contoso.com. This SRV record is required because the Lync Online server uses the domain suffix in the user's EASI ID. In this example, the Lync Online server tries to use the live-contoso.com domain suffix. The Lync Online server tries to identify an SRV record that points to the Instant Messaging (IM) federation server for the domain.
Resolution
To resolve this issue, use one of the following methods.
Method 1
Use the EASI Windows Live ID together with PIC when you add a user to your Lync 2010 contact list. To do this, you must make a change in the search field. A Lync Online user who wants to add the EASI Windows Live ID, such as <username>@live-contoso.com, must add an address that resembles the following to the search field:
JoeAndreshak(live-contoso.com)@msn.com
This method allows for a quick resolution if Lync Online users are only going to add a few PIC contacts.
Method 2
The Lync Online administrator must add the correct SRV Federation records to the DNS host for the Lync Online environment. The Windows Live EASI domain owner must also add an SRV record that resembles the following example to the DNS host for the Windows Live EASI environment:
_sipfederationtls._tcp.live-contoso.com
port = 5061
server hostname = federation.messenger.msn.com
Administrators can let Lync Online users add contacts without having to use the special format in "Method 1" in the "Resolution" section. To do this, administrators must add an SRV Federation record that Lync Online users can access to add contacts to the Windows Live EASI domain.
Lync 2010 Deleting ALL Contacts by User - Using SQL
1. Using the Microsoft SQL Management Studio tools connect LyncServerName\RTC using an account that has full CSAdministrator rights.
2. When connected, under databases right click "RTC" and select "New Query".
3. In the new query entry fieldtype the following:
DECLARE @RC int
DECLARE @_Owner nvarchar(4000)
EXECUTE @RC = [rtc].[dbo].[ImpDeleteContactGroups2] "user@sipdomain.co.uk"
GO
4. Under the Execute command detailed above change the users SIP address to be the desired one. To run this for multiple people at once, add more Execute lines for each person and then click Execute in the tool bar to run the script
5. Once the query has run, log into the Lync 2010 client as the user(s) and ensure their contacts list is now blank.
2. When connected, under databases right click "RTC" and select "New Query".
3. In the new query entry fieldtype the following:
DECLARE @RC int
DECLARE @_Owner nvarchar(4000)
EXECUTE @RC = [rtc].[dbo].[ImpDeleteContactGroups2] "user@sipdomain.co.uk"
GO
4. Under the Execute command detailed above change the users SIP address to be the desired one. To run this for multiple people at once, add more Execute lines for each person and then click Execute in the tool bar to run the script
5. Once the query has run, log into the Lync 2010 client as the user(s) and ensure their contacts list is now blank.
Adium MAC and SIPE Addon for LYNC
http://john.whelans.net/archives/991
The setup is simple:
Make sure you’re running Adium 1.5
Download this plugin: http://db.tt/2yx5wYNt
Install the plugin and restart Adium
Add the new account using Office Communicator for the protocol
It doesn’t do everything (no video chat or screen sharing) – but it’s a huge step in the right direction.
[Update 5/4/12]: One thing Adium doesn’t do (but lync does) is set your status based off your calendar. I’ve addressed this via some AppleScript, as detailed here.
[Update 5/16/12]: The latest beta of Adium (1.5.1b1) uses a different version of libpurple, so the plugin doesn’t work. A quick workaround is to run the following commands in Terminal:
cd /Applications/Adium.app/Contents/Frameworks/libpurple.framework/Versions
ln -s 0.10.5 0.10.0
Plugin is also available on V:\IT Share\IM Clients\MAC\Adium + SIPE Plugin\
The setup is simple:
Make sure you’re running Adium 1.5
Download this plugin: http://db.tt/2yx5wYNt
Install the plugin and restart Adium
Add the new account using Office Communicator for the protocol
It doesn’t do everything (no video chat or screen sharing) – but it’s a huge step in the right direction.
[Update 5/4/12]: One thing Adium doesn’t do (but lync does) is set your status based off your calendar. I’ve addressed this via some AppleScript, as detailed here.
[Update 5/16/12]: The latest beta of Adium (1.5.1b1) uses a different version of libpurple, so the plugin doesn’t work. A quick workaround is to run the following commands in Terminal:
cd /Applications/Adium.app/Contents/Frameworks/libpurple.framework/Versions
ln -s 0.10.5 0.10.0
Plugin is also available on V:\IT Share\IM Clients\MAC\Adium + SIPE Plugin\
Pidgin on Linux with SIPE connect to Lync
http://home.dataforce.org.uk/2012/04/mi ... -on-linux/
Instructions for Ubuntu (using a precompiled deb I've uploaded):
sudo apt-add-repository ppa:pidgin-developers/ppa
sudo apt-get update
sudo apt-get install pidgin
wget http://www.myfileservice.net/pidgin-sip ... 2_i386.deb
sudo dpkg -i pidgin-sipe_1.13.1-2_i386.deb
Once this is done you can then open pidgin, and add an "Office Communicator" account, using teh following settings:
First tab (Basic)
Login: email address
Username: email address
Password: password
Second tab (Advanced)
Server/port: blank
Connection Type: Auto
User Agent: UCCAPI/4.0.7577.314 OC/4.0.7577.314
Auth Scheme: TLS-DSK
Untick Use single sign on, leave everything below it blank
Ignore the other 2 tabs
Instructions for Ubuntu (using a precompiled deb I've uploaded):
sudo apt-add-repository ppa:pidgin-developers/ppa
sudo apt-get update
sudo apt-get install pidgin
wget http://www.myfileservice.net/pidgin-sip ... 2_i386.deb
sudo dpkg -i pidgin-sipe_1.13.1-2_i386.deb
Once this is done you can then open pidgin, and add an "Office Communicator" account, using teh following settings:
First tab (Basic)
Login: email address
Username: email address
Password: password
Second tab (Advanced)
Server/port: blank
Connection Type: Auto
User Agent: UCCAPI/4.0.7577.314 OC/4.0.7577.314
Auth Scheme: TLS-DSK
Untick Use single sign on, leave everything below it blank
Ignore the other 2 tabs
Lync 2010 Prepare for Support of Public IM Connectivity + Video to MSN
http://technet.microsoft.com/en-us/libr ... 98177.aspx
Supporting connectivity with public IM users in your organization requires that the appropriate licensing is in place and that the provisioning process for the public IM services that you want to support is complete. Provisioning can take up to thirty days, so allow sufficient time to complete the process prior to the date on which you want to implement support. For details about licensing requirements and how to complete the provisioning process, see the "Public IM Connectivity Provisioning Guide for Microsoft Lync Server, Office Communications Server, and Live Communications Server" at http://go.microsoft.com/fwlink/p/?LinkId=155970.
If you are implementing audio/video (A/V) federation with Windows Live Messenger, there are two parameters that you need to modify: the Microsoft Lync Server 2010 encryption level and the EnablePublicCloudAccess policy. By default, the encryption level is set to Required. You must change this setting to Supported. The EnablePublicCloudAccess policy is set to false, this needs to be set to true You can do this from the Lync Server Management Shell.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
From the command prompt, type the following commands:
Set-CsMediaConfiguration -EncryptionLevel SupportEncryption
Set-CsExternalAccessPolicy Global -EnablePublicCloudAccess $true -EnablePublicCloudAudioVideoAccess $true
Supporting connectivity with public IM users in your organization requires that the appropriate licensing is in place and that the provisioning process for the public IM services that you want to support is complete. Provisioning can take up to thirty days, so allow sufficient time to complete the process prior to the date on which you want to implement support. For details about licensing requirements and how to complete the provisioning process, see the "Public IM Connectivity Provisioning Guide for Microsoft Lync Server, Office Communications Server, and Live Communications Server" at http://go.microsoft.com/fwlink/p/?LinkId=155970.
If you are implementing audio/video (A/V) federation with Windows Live Messenger, there are two parameters that you need to modify: the Microsoft Lync Server 2010 encryption level and the EnablePublicCloudAccess policy. By default, the encryption level is set to Required. You must change this setting to Supported. The EnablePublicCloudAccess policy is set to false, this needs to be set to true You can do this from the Lync Server Management Shell.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
From the command prompt, type the following commands:
Set-CsMediaConfiguration -EncryptionLevel SupportEncryption
Set-CsExternalAccessPolicy Global -EnablePublicCloudAccess $true -EnablePublicCloudAudioVideoAccess $true
Lync Server 2010 Deployment - blog.schertz.
Wicked guide to Lync 2010 setup: http://blog.schertz.name/
Jeff Schertz Bog:
http://blog.schertz.name/2010/09/lync2010rc-deployment-part1/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part2/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part3/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part4/
Jeff Schertz Bog:
http://blog.schertz.name/2010/09/lync2010rc-deployment-part1/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part2/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part3/
http://blog.schertz.name/2010/09/lync2010rc-deployment-part4/
Subscribe to:
Posts (Atom)