While users are adding additional distribution groups to the contact list in Lync, they receive the following message: “Cannot add contact group. The Contacts list already contains the maximum number of distribution groups.” (ten groups)
This happens if you already have 10 groups and you add more groups.
You can change this default setting to a maximum of 64 groups by using the Set-CsClientPolicy powershell commandlet
| MaximumDGsAllowedInContactList | Optional | Integer | Indicates the maximum number of distribution groups that a user can configure as a contact. MaximumDGsAllowedInContactList can be set to any integer value between 0 and 64, inclusive. The default value is 10. |
To change the value to the maximum of 64 groups, fire up the lync server management shell and type this command by running the following cmdlet:
Set-CsClientPolicy –MaximumDGsAllowedInContactList 64
If you logoff and logon the policy is applied and your users can add more groups :^)
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
After moving/migrating all mailboxes from Exchange 2003 to Exchange 2010, you have to update several objects to Exchange 2010 level. One of these types of objects are mail contacts. If you see the error message :
“the object must be upgrade to the current Exchange version. After the upgrade the object cannot be managed by an earlier version….”
You can solve this by typing in one of the next commands in powershell, (actually you fill in the customattribute1 field with ‘nothing’)
Get-MailContact -resultsize Unlimited | Set-MailContact -CustomAttribute1 $null
or
Get-MailContact -resultsize Unlimited | Set-MailContact -CustomAttribute1 Update
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
There lots of reasons why someone would like to run an Exchange powershell .ps1 script as a scheduled task. For example scheduling a delta PST export during a migration.
In this post I will share with you how to achieve this on both Microsoft Exchange 2007 and Exchange 2010. Obviously you should start by creating your .ps1 script for this article we will assume the script location is c:\pcs\YourScript.ps1
The idea is to run the powershell.exe add pass to it the Exchange powershell console as parameter and then finally specify the desired .ps1 script.
You should notice the difference in the path of the Exchange powershell console between Exchange 2007 and Exchange 2010.
Exchange 2007 exshell.psc1 is located at “”C:\Program Files\Microsoft\Exchange Server\Bin\exshell.psc1″”
Exchange 2010 exshell.psc1 is located at “”C:\Program Files\Microsoft\Exchange Server\V14\Bin\exshell.psc1″”
Notice the extra V14 in Exchange 2010 ?
So the full command to run would be
For Exchange 2007
PowerShell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\BinExShell.psc1″ -Command “. ‘c:\pcs\YourScript.ps1′”
For Exchange 2010
PowerShell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\V14\Bin\ExShell.psc1″ -Command “. ‘c:\pcs\YourScript.ps1′”
Many thanks to zero
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
In Microsoft Exchange Server 2010 since Service Pack 1 (SP1), the Start-ManagedFolderAssistant cmdlet has been changed. In the Exchange 2010 release to manufacturing (RTM) and Exchange Server 2007 versions, the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process.
In Exchange 2010 SP1, the Mailbox parameter has been removed, and the Identity parameter now accepts the mailbox or mail user to process.
e.g. : Start-ManagedFolderAssistant -identity JohnDoe
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
I want to show you 2 cool videos about Polycom and Lync:
The first one is from Graham Walsh on the user experience in Lync and Outlook when integrated to the Polycom RealPresence platform. :
http://www.graham-walsh.com/blog/?p=499
The second video is from Jan Zoetemelk who is demonstrating how you can magically turn you flatscreen TV into a smartboard with a new polycom device! The video introduces the Polycom UC Board. This is an electronic whiteboard tool using current screens, open standards and directly integrates into the Polycom Video Conference Systems
http://www.youtube.com/watch?v=Mdt9S9ThJCk
Thanks guys for the cool videos!!
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
This poster shows each workload in Lync Server 2010, describing relationships, dependencies, the servers that initiate connections, and certificate requirements. Relationships between Microsoft Lync 2010 communications software, Microsoft Lync 2010 Phone Edition, Microsoft Office Live Meeting 2007, Microsoft Lync Web App, and other communications software are also described. SIP and XMPP connection patterns are shown for Yahoo!, MSN, AOL, Gmail, and Jabber. The latest update is version 5.10. This version incorporates Mobility Services and corrections in the IM and Presence workload.
You can download the poster here!
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.
Well this is a very basic troubleshooting step. With these commands you will see immediately what error your server is throwing and why your server not accepting mail :
• Open a command prompt and type in the following command: telnet <servername> 25
C:\Users\admin>telnet mail.xs4all.nl 25
• Identify yourself by typing: helo <your domain name><enter>
helo exchangedude.net
Disclaimer: This posting is provided AS IS with no warranties. It is based on the personal opinion of the author.




