Search This Blog

Thursday, July 26, 2012

Windows Installer coordinator hangs

You might experience this when you install MSI packages on your RDS/Terminal and XenApp servers.

The installation will hang and display the message:

Please wait while the application is preparing for the first use


I have seen this with the following software packages:
  • Google Chrome (Enterprise)
  • IBM i Access

One way to avoid this issue is to create and set the following dword value to 0:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services\TSAppSrv\TSMSI\Enable

During deployment with MDT 2012 or SCCM 2012 one way to do this is to add it in your task sequence:


You can find more information in this link

Saturday, July 21, 2012

Exchange Schema Version

After you have updated the schema with the Exchange 2010 changes (RTM or service packs), you can check the current version with adsiedit.msc.

First connect to the Schema:


Expand the nodes and drill down to the name CN=ms-Exch-Schema-Version-Pt.

Right click on CN=ms-Exch-Schema-Version-Pt and select Properties.


Now find the attribute rangeUpper


The possible rangeUpper values are listed in this table (so this example is taken from a Exchange 2010 SP1 installation):

Exchange Version rangeUpper value
Exchange 2000 RTM 4397
Exchange 2000 SP3 4406
Exchange 2003 RTM 6870
Exchange 2003 SP1 6870
Exchange 2003 SP2 6870
Exchange 2007 RTM 10637
Exchange 2007 SP1 11116
Exchange 2007 SP2 14622
Exchange 2007 SP3 14625
Exchange 2010 RTM 14622
Exchange 2010 SP1 14726
Exchange 2010 SP2 14732
Exchange 2010 SP3 14734
Exchange 2013 RTM 15137
Exchange 2013 CU1 15254
Exchange 2013 CU2 15281
Exchange 2013 CU3 15283
Exchange 2013 CU4 15292
Exchange 2013 CU5 15300
Exchange 2013 CU6 15303
Exchange 2013 CU7 15312
Exchange 2013 CU8 15312
Exchange 2013 CU9 15312
Exchange 2013 CU10 15312
Exchange 2013 CU11 15312
Exchange 2016 RTM 15317

You will also be able to use DSQuery as shown here:

dsquery * CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=xx,DC=xx -scope base -attr rangeUpper


And PowerShell:

Get-ADObject -Identity "CN=ms-Exch-Schema-Version-Pt,CN=schema,CN=configuration,DC=xx,DC=xx" -properties rangeUpper


Thursday, July 12, 2012

KMS caching

By default a KMS client will cache the KMS host that it was able to activate with and will communicate directly with this host when it is time to reactivate (instead of querying DNS). If the client cannot contact the cached KMS host, discovery with DNS will be used.

You are able to disable the caching with the following command:

slmgr /ckhc (or cscript c:\windows\system32\slmgr.vbs /ckhc)



To enable caching again use the command:

slmgr /skhc (or cscript c:\windows\system32\slmgr.vbs /skhc)

You can verify if caching is active with the command:

slmgr /dli (or cscript c:\windows\system32\slmgr.vbs /dli)


Office 2010 will also cache the KMS server used, but in order to disable this you will need to set a registry key:



Wednesday, July 11, 2012

Disable Internet Explorer Enhanced Security Configuration in unattend.xml

When deploying Xenapp and RDS servers from MDT 2012 or SCCM 2012, you will probably want to disable Internet Explorer Enhanced Security Configuration. If this feature is not disabled, users will see prompts like this:

Content from the website listed below is being blocked by the Internet Explorer Enhanced Security Configuration.


Tuesday, July 3, 2012

.NET Authenticode signature revocation list checking for MMC is currently enabled.

When deploying Xenapp you will see this prompt the first time you start Citrix AppCenter.


To get rid of the prompt you can during the automated deployment also deploy the file mmc.exe.config to the C:\windows\SysWOW64 folder.


Place the following text inside the file:


You can find more information in this link