[News] Hewlett Packard se divise en plusieurs sociétés

Hewlett-Packard confirmed on Monday that it planned to break into two companies. The company, considered a foundational institution of Silicon Valley, said in a news release that it intended to divide itself into a company aimed at business technology, including computer servers and data storage equipment, software and services, and a company that sells personal computers and printers. Both companies will be publicly traded. The business-oriented company will be called Hewlett-Packard Enterprise, while the PC company will be called HP Inc. and will retain the company’s current logo. The transaction is expected to be completed by October 2015, the end of HP’s fiscal year, the company said.

Les ratés du net : Canalplay

Ce soir j’ai décidé d’inaugurer une nouvelle section : les ratés du net ! Les sites et les applications grand public lancés à grand renfort de publicités aguicheuses et qui une fois chez vous se révèle être un cauchemar.

J’inaugure donc cette section avec Canal Play et son système de vente en ligne.

Ce soir j’ai décidé de loué en film en ligne sur Canal plus en Vod en utilisant un simple PC sous Windows 8.1. Un grand classique en sorte

Première étape : Retrouver le mot de passe perdu de son abonnement Canal Plus. Classique une adresse email et options retrouver le mot de passe. Bon la déjà allez boire un café le mail arrive après 10 Minutes ! Il va falloir qu’il change de serveurs ou qu’il s’achète de la bande passante mais bon passons.

Deuxième étape : Se connecter : pas de souci je choisi le film et une fois que vous avez choisi on vous indique qu’il vous manque le fameux player. La, installation du Player canal. Oups il manque Framework . NET 3.5 téléchargement installation. Prévoyez bien 10 Minutes. Installation du Player et là on vous redemande de vous connectez encore une fois

Troisième étape : Lancement du canal Player et la erreur de script pfoou !!

Bon essai sur un autre PC ! et la erreur de script mais cette fois ci pas la même, il faut bien variez les plaisirs !!.

Bon après avoir attendu environ 20 Minutes j’ai reçu un mail de confirmation avec un lien pour le support. Et là, ça commence fort. On vous demande en anglais…. Une session number qui soit disant vous a été donnée par un moderator ou un consultant. Bon allons jusqu’au bout Cliquons ici !

Je clique ici et la je rempli le formulaire mais…

L’exécution d’un module complémentaire pour ce site Web a échoué.. Du grand du très grand Canalplay !. J’aime aussi les INFORMATION CONCERNANT VOTRE CONFIGURATION. Bon vu que leur système ne fonctionne pas et que leurs modules de support non plus. Je vais m’arrêter la…..

Alors Messieurs de Canal plus au lieu de mourir de peur et de pleurer face au grand NetFlix ; Embauchez des développeurs et testez vos applications !

Vous y arriverez surement !

 

LYNC 2013 – Le Cumulative Update 6 (Septembre) est disponible !

Bonjour,

Microsoft vient de mettre à disposition le Cumulative Update 6 (September 2014) pour Lync Server 2013. Pour rappel, le dernier CU était celui de Aout 2014 (CU5).

Plus d’informations ici : http://support.microsoft.com/kb/2809243

Disponible au téléchargement à l’adresse suivante : http://www.microsoft.com/en-us/download/details.aspx?id=36820

Pour rappel, l’application d’un CU doit être effectuée avec précaution. Il faut privilégier son installation dans un environnement de test/pré-production. Nous ne sommes jamais à l’abri d’une version 2 de ce CU.

Ce dernier inclut bien sûr le Security Update (https://technet.microsoft.com/en-us/library/security/MS14-055) de début septembre. 

Have Fun !

David ANDRE

Exchange 2013 CU5 : Régression fonctionnelle

La venue de Microsoft Exchange 2013 si elle apporte des fonctionnalités nouvelles ne supporte plus certaines fonctionnalités historiques. C’est le cas de la possibilité de mettre en place deux sites Web OWA et ECP qui permettent dans la plupart des architectures, de publier de façon différentes les services Web Utilisateurs selon qu’ils soient accédés de l’extérieur ou de l’intérieur.

La plus regrettable est que l’absence de cette fonctionnalité sur la nouvelle version ne semble pas, selon l’éditeur être documentée. On est donc en droit de s’inquiéter de la façon dont Microsoft compte à l’avenir communiquer ou pas la suppression de certaines fonctions historiques. Le fait de ne pas reconduire certaines fonctionnalités est tout à fait justifiable mais le fait de ne pas le documenter constitue une première depuis plusieurs années. Ce comportement, au mieux cette omission, va par conséquent impliquer un accueil suspicieux des prochaines versions nous obligeant à revalider les fonctions de bases pour vérifier quelle sont toujours d’actualité.

Cordialement
Laurent Teruin

 

 

Exchange 2013 Edge CU5 : Edge Issue with DNS Event Id 2000 and 205. No Dns could be retrieved

It is started with a warning related to edge poor performance. After looking on the fresh edge server I discovered that I have warning in the event viewer

Each day have an exchange 2013 issue. Our both edges have these warning

No DNS servers could be retrieved from network adapter 9f574acc-20d7-45c3-8a75-c967825b6ae4. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.

And

 

Log Name: Application
Source: MSExchangeTransport
Date: 9/19/2014 11:58:01 AM
Event ID: 2000
Task Category: SmtpSend
Level: Warning
Keywords: Classic
User: N/A
Computer: SrvExc04.xxxx.xxxx.loc
Description:
Send connector a826f0d0-76a0-4768-b347-57de55f00571: A DNS failure occurred with the following diagnostic information The DNS query for ‘SmartHostConnectorDelivery':’srvexc01.xxx.loc,srvexc02.xxx.loc':’a826f0d0-76a0-4768-b347-57de55f00571′ failed with error : ErrorRetry.

 

But the configuration with the DNS is correct and the mono Nic edge computer could resolve correctly all internal internet names

Name : Intel(R) 82574L Gigabit Network Connection
DnsServers : {10.100.0.1}
IPAddresses : {192.168.2.201}
AdapterGuid : 9f574acc-20d7-45c3-8a75-c967825b6ae4
MacAddress : 00:50:56:8E:25:3^E
Identity : 9f574acc-20d7-45c3-8a75-c967825b6ae4
IsValid : True
ObjectState : Unchanged

If i perform a Get-transportserver iv got this

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Get-TransportServer | fl | more
WARNING: The Get-TransportServer cmdlet will be removed in a future version of Exchange. Use the Get-TransportService
cmdlet instead. If you have any scripts that use the Get-TransportServer cmdlet, update them to use the
Get-TransportService cmdlet. For more information, see http://go.microsoft.com/fwlink/p/?LinkId=254711.

 

Name : xxxx
AntispamAgentsEnabled : False
ConnectivityLogEnabled : Trueµ
ConnectivityLogMaxAge : 30.00:00:00
ConnectivityLogMaxDirectorySize : 1000 MB (1,048,576,000 bytes)
ConnectivityLogMaxFileSize : 10 MB (10,485,760 bytes)
ConnectivityLogPath : C:\Program Files\Microsoft\Exchange
Server\V15\TransportRoles\Logs\Edge\Connectivity
DelayNotificationTimeout : 04:00:00
ExternalDNSAdapterEnabled : True
ExternalDNSAdapterGuid : 9f574acc-20d7-45c3-8a75-c967825b6ae4
ExternalDNSProtocolOption : Any
ExternalDNSServers : {}
ExternalIPAddress :
InternalDNSAdapterEnabled : True
InternalDNSAdapterGuid : 9f574acc-20d7-45c3-8a75-c967825b6ae4
InternalDNSProtocolOption : Any

And frrm the Edge with cmdline DNS works perfectly!!!!!! So what is wrong with the transport? The Dns is correct and the machine can resolve correctly!

C:\Users\Administrator>nslookup
Default Server: ddi.XXX.loc
Address: 10.100.0.1
> srvexc01.XXXX.loc
Server: ddi.XXX.loc
Address: 10.100.0.1
Name: srvexc01.XXXX.loc
Address: 10.100.20.11
> srvexc02.XXXX.loc
Server: ddi.XXXX.loc
Address: 10.100.0.1
Name: srvexc02.XXX.loc
Address: 10.100.20.12

The Ip configuration is this one

And the Network card are listed here

For how to get this please refer ti this article http://blogs.technet.com/b/danstolts/archive/2010/09/25/how-to-find-a-lost-missing-hidden-or-removed-network-card-nic-or-other-device-and-even-remove-it.aspx

Useless links :

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=16025&EvtSrc=MSExchangeTransport&LCID=1033

http://technet.microsoft.com/en-us/library/bb218662(v=exchg.80).aspx

 

I set the DNS for this server with the following command

set-transportserver -server srvexc04 -ExternalDNSServers 10.100.0.1 -InternalDNSServers 10.100.0.1

Restart the transport service and No Way ! still have the event id 205 !

Do you want to laugh? Change the Ip configuration and ask to the edge to register his record to the DNS Server.

(Not very simple if you use a public one !) Restart your edge server and you will not have the eventid anymore. But on the system log you will have en warning message.
The system failed to register network adapter with settings:

At this time I could not find better!!

Exchange 2013 a so fresh version!

 

 

 

 

 

 

 

 

Exchange 2013 OWA Logging Issue is back ! : Owa the user or password you entered isn’t correct. Try entering it again.

HI All after executing the CU5 on one Exchange 2013; one multirole exchange 2013 Server refuse all OWA connections.

I decided to not lose too much time to search. We have encountered since 2 months some various instabilities with this service, so my script is ready let’s delete the main OWA Virtual directory and recreate it.

Remove-OwaVirtualDirectory -Identity « SRVEXXX\owa (Default Web Site) »
New-OwaVirtualDirectory -WebSiteName « Default Web Site »
set-owavirtualdirectory -identity « SRVEXXX\owa (Default Web Site) » -AdfsAuthentication $False -BasicAuthentication $true -WindowsAuthentication $false -DigestAuthentication $false -FormsAuthentication $true -LogonFormat PrincipalName

And to finalize : IISRESET /noforce

And works again !!

But if you decide to have a second Owa website for a basic authentication the SRVEXXX\owa (Default Web Site) will not works anymore.

I create a second website « ExchangeBasic » and tried to create a second OWA Directory to allow basic authentication

New-OwaVirtualDirectory -WebSiteName « ExchangeBasic »set-owavirtualdirectory -identity « SRVEXCXXX\owa (ExchangeBasic) » -ExternalAuthenticationMethods basic -BasicAuthentication $true -WindowsAuthentication $false -DigestAuthentication $false -FormsAuthentication $false
Issreset
And now you cannot log again on the SRVEXXX\owa (Default Web Site) the user name or password you entered isn’t correct.

The solution is to delete both and recreate the first one.

 

 

 

 

 

 

Exchange 2013 : CU 5 Error installation : Web Management Service ask for an unknow certificat [Solved]

 

Error:

The following error was generated when « $error.Clear();
$keyPath = « HKLM:\Software\Microsoft\WebManagement\Server »;
if (!(Get-Item $keyPath -ErrorAction SilentlyContinue)) {New-Item $keyPath -Force}
Set-ItemProperty -path $keyPath -name « EnableRemoteManagement » -value 0x1 -Type DWORD -Force;
if (Get-Service WMSVC* | ?{$_.Name -eq ‘WMSVC’}) {Set-Service WMSVC -StartupType AutomaticStop-SetupService -ServiceName WMSVC ;Start-SetupService -ServiceName WMSVC}
 » was run: « Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service ‘WMSVC’ failed to reach status ‘Running’ on this server at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService) at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters) at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters) at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed) ».

After searching i disicover that the Web Management Service could not start

PS C:\Windows\system32> Get-Service WMSVC* | ?{$_.Name -eq ‘WMSVC’}
Status Name DisplayName
—— —- ———–
Stopped WMSVC Web Management Service

And the error is the following

Process:WMSvc

User=NT AUTHORITY\LOCAL SERVICE
Event Xml:
<Event xmlns= »http://schemas.microsoft.com/win/2004/08/events/event »&gt;
<System>
<Provider Name= »Microsoft-Windows-IIS-IISManager » />
<EventID Qualifiers= »0″>1007</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<Data>IISWMSVC_STARTUP_UNABLE_TO_READ_CERTIFICATE
Unable to read the certificate with thumbprint ‘31477a6e41f9ae4f8324154a3c9ac82b8feac1a8′. Please make sure the SSL certificate exists and that is correctly configured in the Management Service page.
Process:WMSvc
User=NT AUTHORITY\LOCAL SERVICE</Data>

I ve checked all certificats in this server no service are binded to this expected certificate with the thumbprint : 1477a6e41f9ae4f8324154a3c9ac82b8feac1a8′

I add a certificat in the Management Service and the service start. The CU5 installer could continue. ;-)

 

KEMP Load Balanced can not send email through Exchange 2013 [Solved]

HI all

Today i v to cope with a little issue with my favorite HLB solution. Kemp. I want to set email alerte with 2 Virtuals Load Balancer. To do This i set the Load Balancer to directly send mail to the Ip address of the Exchange server on 25 Port as the picture display.

But when i check the log of the kemp vm i found this : Error Processing MAIL CMD on smtp server. Status Code = 501

BY inspecting the log of the receive connector i found this :

2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,3,10.100.20.11:25,10.100.20.15:32836,<,EHLO SrvHlb01,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,4,10.100.20.11:25,10.100.20.15:32836,>,250-serverexc01.xxxxxxxx.loc Hello [10.100.20.15],
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,5,10.100.20.11:25,10.100.20.15:32836,>,250-SIZE 37748736,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,6,10.100.20.11:25,10.100.20.15:32836,>,250-PIPELINING,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,7,10.100.20.11:25,10.100.20.15:32836,>,250-DSN,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,8,10.100.20.11:25,10.100.20.15:32836,>,250-ENHANCEDSTATUSCODES,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,9,10.100.20.11:25,10.100.20.15:32836,>,250-STARTTLS,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,10,10.100.20.11:25,10.100.20.15:32836,>,250-X-ANONYMOUSTLS,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,11,10.100.20.11:25,10.100.20.15:32836,>,250-AUTH NTLM,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,12,10.100.20.11:25,10.100.20.15:32836,>,250-X-EXPS GSSAPI NTLM,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,13,10.100.20.11:25,10.100.20.15:32836,>,250-8BITMIME,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,14,10.100.20.11:25,10.100.20.15:32836,>,250-BINARYMIME,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,15,10.100.20.11:25,10.100.20.15:32836,>,250-CHUNKING,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,16,10.100.20.11:25,10.100.20.15:32836,>,250 XRDST,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,17,10.100.20.11:25,10.100.20.15:32836,<,MAIL FROM:<INFO-Logger.SrvHlb01@[Unknown Domain]>,
2014-09-05T09:14:04.394Z,serverexc01\Default Frontend serverexc01,08D196FF590038B1,18,10.100.20.11:25,10.100.20.15:32836,*,Tarpit for ‘0.00:00:05′,

The kemp do not use a domain sufix which by default is not allowed in Exchange 2013

I try to add the local domain in the smtp configuration on the kemp interface and it works correctly !

Regards Laurent

 

Lync 2013 Edge : The Buffer supplied to a function was too small [solved]

HI all

Today i cope with a strange behavior on edge server by assigning a public certificat from comodo

By inspecting the log a found this

The cetificat is well imported in the computer certificat container have a private key and the certification path is correct.

By using the following Certutil.exe command i v got this result

 

C:\Users\Adm-teruin>Certutil.exe -v -store my « 4bf5f126f5011c9dad6b737439f4e0b4″
my « Personal »
================ Certificate 2 ================
X509 Certificate:
Version: 3
Serial Number: 4bf5f126f5011c9dad6b737439f4e0b4
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.11 sha256RSA
Algorithm Parameters:
05 00
Issuer:
CN=COMODO High-Assurance Secure Server CA
O=COMODO CA Limited
L=Salford
S=Greater Manchester
C=GB
Name Hash(sha1): fde74a84a2cc6dd61ec4743bfbbf8abe4a38a458
Name Hash(md5): 193edeb04bee0820e2bde6b731cfe1be

NotBefore: 6/11/2014 2:00 AM
NotAfter: 6/12/2015 1:59 AM
Subject:
CN=access01.XXX.BBB
OU=0002 790043954
O=XXXX
Name Hash(sha1): 0b9997d9949687Fe9440f77789a8f1d87a494365eaa
Name Hash(md5): c9052776583d9038fb42d079e1999777d9e846857
Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
Algorithm Parameters:
05 00

 

To solve this issue

1. Export the certificate with PFX format from the Edge server
   
2. import it on Firefox (my machine was Windows 8.1)
   
3. export it from Firefox with the format P12
   
4. Remove on the edge the assignement on the concerned certificat
   
5. Remove the certificat on the edge server from the certificat store
   
6. import the new formated certificat with the P12 format.
   
7. Assign it to the edge
   

It should works

 

Lync 2013 Citrix VDI HDX Engine crash after May 2014 Lync Update

HI all for your information this post describe a update of our attempt to delivered a stable Lync 2013 Citrix Vdi environment to our users on Xendesktop 7.5

A complete history could be found here: https://unifiedit.wordpress.com/category/2-lync-2013/lync-2013-vdi/

Since a while, we try to stabilize the Citrix VDI environment with Lync 2013 on Xendesktop 7.5. The last issue before delivering this solution to our User pilot was to fix the Ctrl Alt Tab issue (for more information see this article). https://unifiedit.wordpress.com/2014/03/07/lync-2013-vdi-citrix-alt-tab-issue-is-back/. For this a Microsoft Case has been opened and the last action was to update the Lync 2013 client with a May 2014 patch (http://support.microsoft.com/kb/2880980). As the following picture display

Figure 1 : Component on the Physical Box

After applying the update we can observe that the Ctrl Tab Issue is no more present
but when the user close the session the Ucvdi.dll of HDx Engine crash.

Figure 2 : Hdx crash when user exit from the session

Regards

Laurent Teruin