Exchange your Mind

"La connaissance ne vaut que si elle est partagée" / "An effective Knowledge is a shared one"

Archives d’Auteur

New-owavirtualdirectory Exchange 2013 sp1 : An error occurred while creating the IIS virtual directory

Publié par Teruin laurent le avril 16, 2014


I all

hI all After noting that no one have the possibility to connect to OWA (Invalid User name and password) on the default web site I decided to delete the OWA Web Site and try to recreate it. After a IISreset My wonderful New Exchange Server running SP1 on Windows 2012 display this error message .

[PS] C:\Windows\system32>new-owavirtualdirectory -websitename "Default Web Site" An error occurred while creating the IIS virtual directory ‘IIS://SRVEXC02.mrsaero.loc/W3SVC/1/ROOT/owa’ on ‘SRVEXC02′ + CategoryInfo : InvalidOperation: (SRVEXC02\owa (Default Web Site):ADObjectId) [New-OwaVirtualDirectory] , InvalidOperationException

+ FullyQualifiedErrorId : [Server=SRVEXC02,RequestId=6c73332e-6c1f-4e13-a47b-f9bf35c1b9b3,TimeStamp=4/16/2014 12:3 2:26 PM] [FailureCategory=Cmdlet-InvalidOperationException] D30125EB,Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory

+ PSComputerName : srvexc02.mrsaero.loc

The fun is that I have a second server who I made the same thing without any issue

I can note that when ti try to recreate this vitual directory I have this error in the eventlog


Laurent TERUIN

Publié dans Non classé | Leave a Comment »

Lync 2013 : Mise à jour d’avril 2014

Publié par Teruin laurent le avril 11, 2014


Bonjour

Microsoft vient de sortir les cumulative update d’avril pour Lync 2013 disponible ici : http://support.microsoft.com/kb/2880474

Les bugs corrigés sont les suivants :

2941631 Cannot drag a distribution group to change position in your contact list in Lync 2013

2941639 Call forwarding to the Response Group fails in Lync 2013
2941640 Desktop sharing session stops in Lync 2013 when all screen data is updated
2941643 Caller cannot close the window of a transferred call in Lync 2013
2941654 Update sorts and searches contacts by Furigana in Lync 2013
2941658 CTRL+TAB does not work when you switch between conversation windows in Lync 2013
2941682 Instant message appears using incorrect text format when the DisableRTFIM setting is enabled in Lync 2013
2941659 Callee’s name and detailed information is missing from the conversation history of a Lync 2013 outgoing call
2941636 Search fails in Lync 2013 when non-Latin characters are used in a different case from the AD DS attributes
2941635 Can’t sign in to Lync 2013 when Office 365 account UPN differs from domain account UPN
2954951 Slow screen update in application sharing or desktop sharing session in Lync 2013
2955577 Lync 2013 takes a long time to sign in after reconnect to the network
2955579 Lync 2013 displays un-encoded texts in a toast notification or an instant message sent to another messaging client
2955580 Update adds a button to show details about limited functionalities when Lync 2013 connects to a backup pool

Cordialement
Laurent Teruin

Publié dans 2- LYNC-2013 | Leave a Comment »

Exchange 2013: A fatal alert was generated and sent to the remote endpoint Windows SChannel error state is 10 [Pending]

Publié par Teruin laurent le avril 9, 2014


Hi all

Today from two fresh Exchange 2013 SP1 (Version 15.0 (Build 847.32)) installed servers i have to cope with this error message:
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10.

Because this error message is almost laconic is it a little bit difficult to find the reason.

After searching on the Web I found nothing relevant. Find a workaround (no proud of this…)

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL : EventLogging=0

In another server I try this Group Policy Editor (run: gpedit.msc), Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enabled "allow local activation security check exemptions" Disabled.


Work and a little bit better.

Regards
Laurent Teruin


 

Publié dans Non classé | Leave a Comment »

SCOM 2012 R2 enable to connect on SQL Server 2012 X64 SP1 and SP1 CU9 [Solved]

Publié par Teruin laurent le mars 27, 2014


HI

On 27 March 2014 morning , we have just install a fresh Windows 2012 R2 french Standard version with only Microsoft components, Disabling firewall, install Sql Server 2012 (SQL_Svr_Standard_Edition_2012_w_SP1_French_Download_Only_64bit_-2_X18-78138) and try to install Scom 2012 R2 (SCOM_SW_DVD5_Sys_Ctr_2012_R2_French_OpsMgr_MLF_X19-18423)

No Way to connect. All is correct the Sql Browser listen on 1433 ports but no way to connect. Sql Management Studio connect correctly.


15:32:05]:    Error:    :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0×80131509, Exception.Message: Le service spécifié n’existe pas en tant que service installé
[15:32:05]:    Error:    :InnerException.StackTrace:
[15:32:05]:    Warn:    :Could not start the SQL Service W-IMA-1\scom but we will attempt to connect anyway.
[15:32:05]:    Debug:    :Connection was not open. We will try to open it.
[15:32:05]:    Debug:    :SqlConnectionReady returned True.
[15:32:05]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[15:32:05]:    Info:    :SQL Product Level: SP1
[15:32:05]:    Info:    :SQL Edition: Standard Edition (64-bit)
[15:32:05]:    Info:    :SQL Version: 11.0.3000.0
[15:32:05]:    Always:    :Current Version of SQL=11.0.3000.0 Required Version=10.50.2500.0
[15:32:05]:    Always:    :Entering GetRemoteOSVersion.
[15:32:05]:    Info:    :Info: remoteOS = 6.3.9600
[15:32:05]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[15:32:05]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[15:32:05]:    Info:    :The SQL Collation is valid.
[15:32:05]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[15:32:05]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.
[15:32:05]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

We try this on the Sql Server


Same issue.

After that we have installed on our local Sql Server the CU 9 : http://support.microsoft.com/kb/2931078

[18:21:48]:    Always:    :DatabaseConfigurationPage: Attempting to connect to database using server\instance W-IMA-1\scom. If we need it, the port is 1433
[18:21:48]:    Error:    :Error in Forcing Service to Running state.: Threw Exception.Type: System.InvalidOperationException,
Exception Error Code: 0×80131509, Exception.Message: Le service MSSQL$scom est introuvable sur l’ordinateur ‘W-IMA-1′.
[18:21:48]:    Error:    :StackTrace: à System.ServiceProcess.ServiceController.GenerateNames()

à System.ServiceProcess.ServiceController.get_ServiceName() à System.ServiceProcess.ServiceController.GenerateStatus() à System.ServiceProcess.ServiceController.get_Status()

à Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.ForceSqlServiceToRunningState(String sqlServerInstance)
[18:21:48]:    Error:    :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception
Error Code: 0×80131509, Exception.Message: Le service spécifié n’existe pas en tant que service installé
[18:21:48]:    Error:    :InnerException.StackTrace:
[18:21:48]:    Warn:    :Could not start the SQL Service W-IMA-1\scom but we will attempt to connect anyway.
[18:21:48]:    Info:    :Info:Opening/Testing Sql Connection on W-IMA-1\scom, port:
[18:21:49]:    Debug:    :Connection was not open. We will try to open it.
[18:21:54]:    Error:    :
Error opening SQL connection.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0×80131904, Exception.Message: Une erreur liée au réseau ou spécifique à l’instance s’est produite lors de l’établissement d’une connexion à SQL Server. Le serveur est introuvable ou n’est pas accessible. Vérifiez que le nom de l’instance
est correct et que SQL Server est configuré pour autoriser les connexions distantes. (provider: SQL Network Interfaces, error: 26 – Erreur lors de la localisation du serveur/de l’instance spécifiés)
[18:21:54]:    Error:    :StackTrace: à System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
à System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

à System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)

à System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)

à System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)

à System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)

à System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)

à System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

à System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)

à System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

à System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

à System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

à System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

à System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

à System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

à System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

à System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
à System.Data.SqlClient.SqlConnection.Open()

à Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.OpenAndTestSqlConnection(DbConnection sqlConnection, Int32 retries)
[18:21:54]:    Always:    :OpenAndTestSqlConnection: connection string – Data source=W-IMA-1\scom;Integrated Security=true;Connection Timeout=5
[18:21:54]:    Debug:    :Connection was not open. We will try to open it.
[18:21:54]:    Error:    :Error opening SQL connection.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0×80131904, Exception.Message: Une erreur liée au réseau ou spécifique à l’instance s’est produite lors de l’établissement d’une connexion à SQL Server. Le serveur est introuvable ou n’est pas accessible. Vérifiez que le nom de l’instance est correct et que SQL Server est configuré pour autoriser les connexions distantes. (provider: SQL Network Interfaces, error: 26 – Erreur lors de la localisation du serveur/de l’instance spécifiés)
[18:21:54]:    Error:    :StackTrace: à System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

à System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) à System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
à System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
à System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
à System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
à System.Data.SqlClient.SqlConnection.Open()
à Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.OpenAndTestSqlConnection(DbConnection sqlConnection, Int32 retries)
[18:21:54]:    Always:    :OpenAndTestSqlConnection: connection string – Data source=W-IMA-1\scom;Integrated Security=true;Connection Timeout=5
[18:21:54]:    Debug:    :SqlConnectionReady returned False.
[18:21:54]:    Info:    :Info:Opening/Testing Sql Connection on W-IMA-1\scom, port: 1433
[18:21:54]:    Debug:    :Connection was not open. We will try to open it.
[18:21:55]:    Debug:    :SqlConnectionReady returned True.

[18:21:55]:    Error:    :Error in Forcing Service to Running state.: Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0×80131509, Exception.Message: Le service MSSQL$scom est introuvable sur l’ordinateur ‘W-IMA-1′.

[18:21:55]:    Error:    :StackTrace: à System.ServiceProcess.ServiceController.GenerateNames()

à System.ServiceProcess.ServiceController.get_ServiceName()

à System.ServiceProcess.ServiceController.GenerateStatus()

à System.ServiceProcess.ServiceController.get_Status() à Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.ForceSqlServiceToRunningState(String sqlServerInstance)
[18:21:55]:    Error:    :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0×80131509, Exception.Message: Le service spécifié n’existe pas en tant que service installé
[18:21:55]:    Error:    :InnerException.StackTrace:
[18:21:55]:    Warn:    :Could not start the SQL Service W-IMA-1\scom but we will attempt to connect anyway.
[18:21:55]:    Debug:    :Connection was not open. We will try to open it.
[18:21:55]:    Debug:    :SqlConnectionReady returned True.
[18:21:55]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[18:21:55]:    Info:    :SQL Product Level: SP1
[18:21:55]:    Info:    :SQL Edition: Standard Edition (64-bit)
[18:21:55]:    Info:    :SQL Version: 11.0.3412.0
[18:21:55]:    Always:    :Current Version of SQL=11.0.3412.0 Required Version=10.50.2500.0
[18:21:55]:    Always:    :Entering GetRemoteOSVersion.
[18:21:55]:    Info:    :Info: remoteOS = 6.3.9600
[18:21:55]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[18:21:55]:    Info:    :Info:Using DB command timeout = 1800 seconds.[18:21:55]:    Info:    :The SQL Collation is valid.
[18:21:55]:    Info:    :Info:Using DB command timeout = 1800 seconds.
[18:21:55]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.
[18:21:55]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

After 9 hours to try to install Scom back home … fucking bad Day !

28 March 2014 (after 9 Hours trying to install SCOM….)

Removing Sql Server / Renaming the windows machine WIMA1 without "–" caracter
Reboot / resinstalling Sql Server . Reboot / Trying to install Scom 2012R2 SP1 FR Non OK/ Verifying SqlBrowser = OK
Installing CU9 on SQL Server 2012 R2 SP1 …….. Rebooting / Trying to install Scom 2012R2 SP1 FR Non OK (Log below)

[10:26:39]:    Always:    :CheckPrerequisites: Return Value 1

[10:26:39]:    Always:    :Entering Page: AdditionalPrerequisitesPage

[10:26:39]:    Info:    :Info:Attempting to get the text for the prereq: memoryCheckTitle

[10:26:45]:    Always:    :Entering Page: InstallScenario

[10:26:50]:    Always:    :Entering Page: EulaPageCleanInstall

[10:26:50]:    Always:    :Displaying localized EULA for localization: fr

[10:26:50]:    Always:    :Displaying Eula: C:\Users\LTERUINEXTADM\AppData\Local\SCOM\Setup\fr\eula_fr_eval.rtf

[10:26:53]:    Info:    :Info:User has agreed to EULA.

[10:26:53]:    Info:    :Not all of the information on the screen is valid, so we’re not going to check disk space.

[10:26:53]:    Info:    :Not all of the information on the screen is valid, so we’re not going to check disk space.

[10:26:53]:    Always:    :Entering Page: FirstServerOperationalDb

[10:26:54]:    Info:    :Not all of the information on the screen is valid, so we’re not going to check disk space.

[10:26:54]:    Info:    :Not all of the information on the screen is valid, so we’re not going to check disk space.

[10:27:18]:    Always:    :DatabaseConfigurationPage: Attempting to connect to database using server\instance WIMA1\SCOM. If we need it, the port is 1433

[10:27:18]:    Debug:    :MSSQL$SCOM on server WIMA1 is in a running state

[10:27:18]:    Info:    :Info:Opening/Testing Sql Connection on WIMA1\SCOM, port:

[10:27:19]:    Debug:    :Connection was not open. We will try to open it.

[10:27:19]:    Debug:    :SqlConnectionReady returned True.

[10:27:19]:    Debug:    :MSSQL$SCOM on server WIMA1 is in a running state

[10:27:19]:    Debug:    :Connection was not open. We will try to open it.

[10:27:19]:    Debug:    :SqlConnectionReady returned True.

[10:27:19]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:19]:    Info:    :SQL Product Level: SP1

[10:27:19]:    Info:    :SQL Edition: Standard Edition (64-bit)

[10:27:19]:    Info:    :SQL Version: 11.0.3412.0

[10:27:19]:    Always:    :Current Version of SQL=11.0.3412.0 Required Version=10.50.2500.0

[10:27:19]:    Always:    :Entering GetRemoteOSVersion.

[10:27:19]:    Info:    :Info: remoteOS = 6.3.9600

[10:27:19]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:19]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:19]:    Info:    :The SQL Collation is valid.

[10:27:19]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:19]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

[10:27:19]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

[10:27:20]:    Always:    :DatabaseConfigurationPage: Attempting to connect to database using server\instance WIMA1\SCOM. If we need it, the port is 1433

[10:27:20]:    Debug:    :MSSQL$SCOM on server WIMA1 is in a running state

[10:27:20]:    Info:    :Info:Opening/Testing Sql Connection on WIMA1\SCOM, port:

[10:27:20]:    Debug:    :Connection was not open. We will try to open it.

[10:27:20]:    Debug:    :SqlConnectionReady returned True.

[10:27:20]:    Debug:    :MSSQL$SCOM on server WIMA1 is in a running state

[10:27:20]:    Debug:    :Connection was not open. We will try to open it.

[10:27:20]:    Debug:    :SqlConnectionReady returned True.

[10:27:20]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:20]:    Info:    :SQL Product Level: SP1

[10:27:20]:    Info:    :SQL Edition: Standard Edition (64-bit)

[10:27:20]:    Info:    :SQL Version: 11.0.3412.0

[10:27:20]:    Always:    :Current Version of SQL=11.0.3412.0 Required Version=10.50.2500.0

[10:27:20]:    Always:    :Entering GetRemoteOSVersion.

[10:27:20]:    Info:    :Info: remoteOS = 6.3.9600

[10:27:20]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:20]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:20]:    Info:    :The SQL Collation is valid.

[10:27:20]:    Info:    :Info:Using DB command timeout = 1800 seconds.

[10:27:20]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

[10:27:20]:    Info:    :Info:DatabaseConfigurationPage: DB connection attempt completed.

 

Removing Sql Server / Rebooting / Installating Sql Server with Default Option (No Scom Name instance).


The issue is problably due to the instance Name (Scom). Is it too difficult to include in the developpement a verification task to check this fuck..value ?

Laurent Teruin

Publié dans Non classé | Leave a Comment »

Kemp HLB dont send email Alert [PENDING]: Error processing MAIL cmd on SMTP server. SMTP status code = 501

Publié par Teruin laurent le mars 26, 2014


We try to send alert with Kemp HLB LoadMaster Version 7.0-12a The Hlb use on eth0 the same IP address of the Exchange 2013 SP1 Us Smtp transport server. We tried to send email from a telnet from the same vlan through the 25 port and it works! The mail is arrived on Exchange User mailbox
When we try to do this with the HLB with this configuration

We have this error message : Mar 26 16:42:36 SrvHlb01 mailer: Error processing MAIL cmd on SMTP server. SMTP status code = 501 on the system log. We tried to replace the smtp address with a fqdn . Same issue.

Case is openend
Laurent

 

 

 

Publié dans KEMP HLB | Leave a Comment »

Lync Conférence France 2 Avril 2014

Publié par Teruin laurent le mars 11, 2014


Bonjour

Un petit post pour vous informer que la Lync Conférence France se tiendra le 2 Avril 2014 dans les locaux de Microsoft
Pour vous inscrire à la Lync Conférence France : http://www.microsoft.com/france/Office/2013/lync/evenements.aspx


Cordialement
Laurent Teruin

Publié dans Lync 2013 - Evenements | Leave a Comment »

LYNC 2013 VDI Citrix : HDX Crash with Vd3dplay.dll

Publié par Teruin laurent le mars 7, 2014



Hi just to keep you informed on the VDI Citrix Lync Project

 

We have to cope again with HDX Crash on some thin client. Our platform is composed with these elements.

  • Platform Windows 7 embedded Std : 6.1.76.01
  • Thin Client : HP T610
  • Citrix Receiver version on Thin client: 4.1.2.3
  • Citrix Receiver version in the VM for Xenapp : 4.1.0.56461
  • Operating System : Windows 8.1 64 Fr Bits Build Number : Enterprise 6.3.9600
  • Lync Vdi Version : 15.0.4420.1017 32bit
  • Lync client Version : MSO 15.0.1.4569.1506 Build 15.0.1.4569.1503 (32 bits)
  • Xendesktop version : 7.1

We have deployed around 25 users with this configuration and we have this behavior frequently


Publié dans 2- LYNC-2013, Lync 2013 - Vdi Citrix, Lync 2013 -VDI | Leave a Comment »

LYNC 2013 VDI Citrix: Alt Tab Issue is back

Publié par Teruin laurent le mars 7, 2014



Hi just to keep you inform on the VDI Citrix Lync Project

We have to cope again with the Alt tab on Citrix Vdi environment. Our platform is composed with these elements.

  • Platform Windows 7 embedded Std : 6.1.76.01
  • Thin Client : HP T610
  • Citrix Receiver version on Thin client: 4.1.2.3
  • Citrix Receiver version in the VM for Xenapp : 4.1.0.56461
  • Operating System : Windows 8.1 64 Fr Bits Build Number : Enterprise 6.3.9600
  • Lync Vdi Version : 15.0.4420.1017 32bit
  • Lync client Version : MSO 15.0.1.4569.1506 Build 15.0.1.4569.1503 (32 bits)
  • Xendesktop version : 7.1

With this environment we have the Alt Tab Issue.

The Alt Tab Issue definition: When a user in the VM machine use the alt Tab key combination the user is redirected to the thin client local Interface instead of switching to another application in the VM. see below



TEST1: The Windows 8.1 VM has no Receiver inside (receiver has been uninstalled) and the alt tab issue is still present ;-(

TEST 2: The Receiver 4.1.2.3 has been installed in the VM and the Alt Tab issue is still present ;-(

TEST 3: The Lync VDI-plugin client has been removed in the thin client and the alt Tab issue is when the user use ALT tab he can switch between Apps IN the VM. ;-)

Laurent Teruin


 

Publié dans 2- LYNC-2013, Lync 2013 - Vdi Citrix, Lync 2013 -VDI | Leave a Comment »

Lync 2013 : Kemp Publication Reverse Proxy Lync 2013

Publié par Teruin laurent le mars 6, 2014


Kemp vient de mettre en ligne une documentation sur la publication des services Web Lync 2013 a récupéré ici.

http://kemptechnologies.com/files/downloads/documentation/7.0/Deployment_Guides/Deployment_Guide-Lync_2013.pdf

Vous trouverez également un article Microsoft sur le lien suivant : http://blogs.technet.com/b/nexthop/archive/2014/02/14/configuring-reverse-proxy-access-to-microsoft-lync-server-2013-using-kemp-loadmaster.aspx

Laurent Teruin

 

Publié dans 2- LYNC-2013, Lync 2013 - Documentation, Lync 2013 - Reverse Proxy | Leave a Comment »

Lync 2013: Stress and Performance Tool (LSS)

Publié par Teruin laurent le mars 6, 2014


Microsoft Vient de sortir un outil permettant de recourir à des stress d’infrastructure sur la partie Lync 2013. Nommé Lync Server 2013 Stress and Performance Tool (LSS), il peut simuler toute la charge des différentes activités ou unitairement une charge spécifique IM, Audio Conferencing. Les équipes fournissent un guide sur cet outil qui peut être téléchargé à cet endroit.

http://www.microsoft.com/en-us/download/details.aspx?id=41935

Documentation TechNet : http://technet.microsoft.com/fr-fr/library/jj945609.aspx

Cordialement

Laurent Teruin

 


 

Publié dans 2- LYNC-2013, Lync 2013 - Documentation, Microsoft Lync | Leave a Comment »

 
Suivre

Recevez les nouvelles publications par mail.

Joignez-vous à 223 followers