Outlook : Prevent connecting to the https autodiscover url

Sometimes you don’t want Outlook to connect to the autodiscover URL’s. For example: if your internal DNS zone differs from your external one, and you don’t have a split DNS zone setup.

If you want to prevent Outlook 2010 to lookup to connect to the autodiscover URL’s you can deploy these registry keys :

You can read more in this technet article

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Autodiscover] “ExcludeHttpsRootDomain”=dword:00000001

“ExcludeHttpsAutodiscoverDomain”=dword:00000001

“ExcludeHttpRedirect”=dword:00000001

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Lync 2010 – Polycom CX 7000 : The far site requires encryption ( AES )

If you see the errormessage :  The far site requires encryption. Please enable encryption on your system on your polycom video conferencing device like below, you have to enable encryption on your device.

 

 

 

 

 

Enable encryption by choosing :

admin settings -> securrity -> security settings -> AES encryption -> when available , after the change restart your Polycom device!

 

 

 

 

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

NTVDM error – NTVDM has encountered a problem and needs to close

This one has nothing to do with UC, but I wanted to share this because a lot of people still use MS-DOS programs on Windows XP SP3.

Suddenly MS-DOS programs stopped working after running Windows update (June 2012). After starting the applications, Windows shows this error message :

 

 

 

 

 

 

in my case the error in the eventviewer with event ID 1000 was :

Faulting application ntvdm.exe, version 5.1.2600.5512, faulting module unknown, version 0.0.0.0, fault address 0x0ff82e63.

To solve this you need to uninstall the KB 2707511 update for XP , because this interferes with ntvdm.exe

*** UPDATE ***

This fixed, read http://support.microsoft.com/kb/2732488

(tnx to simon :D)

 

*** UPDATE ***

 

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Outlook 2010 : run autodiscover unattended/silent/suppressed without any user intervention

When Outlook 2010 is started for the first time in an Active directory environment that has Exchange 2007 or 2010 servers, the autodiscover wizard – which is basically a Next Next Finish operation – becomes unnecessary, because all the information to configure the outlook client is right there in the background.

Some customers want to run the autodiscover wizard in the background without asking the user to click next next finish to configure and create the outlook profile, if that is your case just add the following registry key to your clients and the wizard will run in the background without showing the wizard for the end user

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\AutoDiscover
Value name: ZeroConfigExchange
Value type: REG_DWORD
Value data: 1

OR

Of you want to do this using a GPO group policy object, enable this Outlook 2010 Policy on your domain :

User configuration / Policies / Administrative templates / Microsoft Outlook 2010 / Account Settings / Exchange

Automatically configure profile based on Active Directory Primary SMTP address

which also auto creates a users Outlook profile at first logon without the need for the user to enter any settings.

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Increase number of groups in lync client

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 : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

update mail contacts to Exchange 2010

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 : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Exchange create .ps1 script powershell scheduled task

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 : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.