Exchange your Mind

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

Lync 2010/2013 Set-cswebserver don’t works on Lync 2010 with Lync 2013 cohabitation

Posted by Teruin laurent le octobre 20, 2014


Issue Description

Hi today I cope with an issue of Lync Mobile cohabitation. The goal is to enable Lync 2010 Mobile communication (Mcx) with Lync 2013 Mobile cohabitation Web API (UCWA). Contrary to migration cases, my customer this time wants to keep some users on Lync 2010 pool and some users on Lync 2013 pool. Thus, some users will have to use Lync 2010 Mobile App and other Lync 2013 Mobile App.

The original Lync 2010 pool is not set originally with Lync Mobile Application (Mcx) and when we tried to set the Mobility service by following the technet and other articles we encountered an error message.

http://blog.schertz.name/2011/12/deploying-the-lync-2010-mobility-service/

I search some information about more a cohabitation path than a migration path for mobility service but without any success for the moment;

When we try to set the mcx port on the Lync 2010 pool we encountered this error

 

Set-cswebserver –identity –McxSipPrimaryListeningPort 5086 –McxSipExternalListeningPort 5087


 

The goal is also to know how it works actually with a Lync 2013 front end pool in the middle. In my view,

  1. The Lync discover A record point to a reverse proxy who send the url request mobile client on port 4443 to the Lync 2013 Webservices load Balanced Vip.
  2. The Load Balanced send the request to one of the Frontend pool

When we set that, the Lync 2013 Mobile application can log on successfully rom External. But Lync 2010 can’t. We verify 3 times all the certificate the root ant the intermediate certificate all is ok from this side.

In my perspective ; but I’m not sure, the Lync 2013 should send to the Lync 2010 External web services to the Lync 2010 Mobile client, and in this case the Lync 2010 client should be able to directly access to the Mcx virtual directory. But in our case we are not able to set it on Lync 2010. See the error message above. Our Lync 2010 webservices works well and are correctly published externally. Because our team also manage the Denyall reverse proxies infrastructure we are capable of viewing the incoming requests from outside.

Resolution Acceptance condition

The case will be considered by our team as resolved when Lync 2010 Mobility service run correctly on Lync 2010 Frontend

Technical articles

http://blogs.technet.com/b/lync/archive/2013/03/12/why-is-lync-2013-mobile-asking-me-to-use-lync-2010.aspx

Lync 2013 Mobile relies on Unified Communication Web API (UCWA) that comes with February 2013 Cumulative Update for Lync Server 2013 or later, which Lync Server 2010 does not provide. If you are connecting to a Lync 2010 or Lync 2013 RTM Server you will see the message « You can’t sign in with this version of Lync. Please install Lync 2010″. On the other side, Lync 2010 Mobile relies on Lync Mobility Service (MCX) which is included on Lync 2010 and Lync 2013 Servers. This allows Lync 2010 Mobile users to sign into either version of Lync Server

http://blogs.technet.com/b/nexthop/archive/2012/04/25/lync-server-2010-mobility-deep-dive-autodiscover-service.aspx

Actions

On a test environnement i try to remove on one 2010 frontend server all cu and tried to install the CU4. The uninstall operation works fine but when i tried to apply the CU4 i encountered the same issue.



On the same environnement with a Lync 2010 Server with the most recent CU i have tried to perform the following command :

Set-cswebserver –identity –McxSipPrimaryListeningPort 5086 –McxSipExternalListeningPort 5087 and same issue as encountered in the production environnement

 

Technical informations

 

Frontend 2010 Operating system version


 

Get-csservice-webserver

 

Identity : WebServer:front-eu.xxxx.com

FileStore : FileStore:nce17nt.eu.xxxx.com

UserServer : UserServer:front-eu.xxxx.com

PrimaryHttpPort : 80

PrimaryHttpsPort : 443

ExternalHttpPort : 8080

ExternalHttpsPort : 4443

PublishedPrimaryHttpPort :

PublishedPrimaryHttpsPort :

PublishedExternalHttpPort : 80

PublishedExternalHttpsPort : 443

ReachPrimaryPsomServerPort : 8060

ReachExternalPsomServerPort : 8061

AppSharingPortStart : 49152

AppSharingPortCount : 16383

McxSipPrimaryListeningPort :

McxSipExternalListeningPort :

LIServiceInternalUri : https://frontweb-eu.xxxx.com/locationinformati on/liservice.svc

ABHandlerInternalUri : https://frontweb-eu.xxxx.com/abs/handler

ABHandlerExternalUri : https://front-eu.groupexxxx.com/abs/handler

DLExpansionInternalUri : https://frontweb-eu.xxxx.com/groupexpansion/se

rvice.svc

DLExpansionExternalUri : https://front-eu.groupexxxx.com/groupexpansion

/service.svc

CAHandlerInternalUri : https://frontweb-eu.xxxx.com/CertProv/CertProv

isioningService.svc

CAHandlerInternalAnonUri : http://frontweb-eu.xxxx.com/CertProv/CertProvi

sioningService.svc

CollabContentInternalUri : https://frontweb-eu.xxxx.com/CollabContent

CollabContentExternalUri : https://front-eu.groupexxxx.com/CollabContent

CAHandlerExternalUri : https://front-eu.groupexxxx.com/CertProv/CertP

rovisioningService.svc

DeviceUpdateDownloadInternalUri : https://frontweb-eu.xxxx.com/RequestHandler/uc

device.upx

DeviceUpdateDownloadExternalUri : https://front-eu.groupexxxx.com/RequestHandler

Ext/ucdevice.upx

DeviceUpdateStoreInternalUri : http://frontweb-eu.xxxx.com/RequestHandler/Fil

es

DeviceUpdateStoreExternalUri : https://front-eu.groupexxxx.com/RequestHandler

Ext/Files

RgsAgentServiceInternalUri : https://frontweb-eu.xxxx.com/RgsClients/AgentS

ervice.svc

RgsAgentServiceExternalUri : https://front-eu.groupexxxx.com/RgsClients/Age

ntService.svc

MeetExternalUri : https://front-eu.groupexxxx.com/Meet

DialinExternalUri : https://front-eu.groupexxxx.com/Dialin

CscpInternalUri : https://frontweb-eu.xxxx.com/Cscp

ReachExternalUri : https://front-eu.groupexxxx.com/Reach

ReachInternalUri : https://frontweb-eu.xxxx.com/Reach

WebTicketExternalUri : https://front-eu.groupexxxx.com/WebTicket/WebT

icketService.svc

WebTicketInternalUri : https://frontweb-eu.xxxx.com/WebTicket/WebTick

etService.svc

McxServiceExternalUri : https://front-eu.groupexxxx.com/Mcx/McxService

.svc

McxServiceInternalUri : https://frontweb-eu.xxxx.com/Mcx/McxService.sv

c

AutodiscoverServiceExternalUri : https://front-eu.groupexxxx.com/Autodiscover/A

utodiscoverService.svc/root

AutodiscoverServiceInternalUri : https://frontweb-eu.xxxx.com/Autodiscover/Auto

discoverService.svc/root

ExternalFqdn : front-eu.groupexxxx.com

InternalFqdn : frontWeb-eu.xxxx.com

DependentServiceList : {Registrar:front-eu.xxxx.com, ConferencingServ

er:front-eu.xxxx.com}

ServiceId : 1-WebServices-1

SiteId : Site:DATACENTER EU

PoolFqdn : front-eu.xxxx.com

Version : 5

Role : WebServer

 

Identity : WebServer:front2K13-eu.xxxx.com

FileStore : FileStore:nce05im.xxxx.com

UserServer : UserServer:front2K13-eu.xxxx.com

PrimaryHttpPort : 80

PrimaryHttpsPort : 443

ExternalHttpPort : 8080

ExternalHttpsPort : 4443

PublishedPrimaryHttpPort :

PublishedPrimaryHttpsPort :

PublishedExternalHttpPort : 80

PublishedExternalHttpsPort : 443

ReachPrimaryPsomServerPort : 8060

ReachExternalPsomServerPort : 8061

AppSharingPortStart : 49152

AppSharingPortCount : 16383

McxSipPrimaryListeningPort : 5086

McxSipExternalListeningPort : 5087

LIServiceInternalUri : https://front2k13-eu.xxxx.com/locationinformat

ion/liservice.svc

ABHandlerInternalUri : https://front2k13-eu.xxxx.com/abs/handler

ABHandlerExternalUri : https://lyncweb-eu.groupexxxx.com/abs/handler

DLExpansionInternalUri : https://front2k13-eu.xxxx.com/groupexpansion/s

ervice.svc

DLExpansionExternalUri : https://lyncweb-eu.groupexxxx.com/groupexpansi

on/service.svc

CAHandlerInternalUri : https://front2k13-eu.xxxx.com/CertProv/CertPro

visioningService.svc

CAHandlerInternalAnonUri : http://front2k13-eu.xxxx.com/CertProv/CertProv

isioningService.svc

CollabContentInternalUri : https://front2k13-eu.xxxx.com/CollabContent

CollabContentExternalUri : https://lyncweb-eu.groupexxxx.com/CollabConten

t

CAHandlerExternalUri : https://lyncweb-eu.groupexxxx.com/CertProv/Cer

tProvisioningService.svc

DeviceUpdateDownloadInternalUri : https://front2k13-eu.xxxx.com/RequestHandler/u

cdevice.upx

DeviceUpdateDownloadExternalUri : https://lyncweb-eu.groupexxxx.com/RequestHandl

erExt/ucdevice.upx

DeviceUpdateStoreInternalUri : http://front2k13-eu.xxxx.com/RequestHandler/Fi

les

DeviceUpdateStoreExternalUri : https://lyncweb-eu.groupexxxx.com/RequestHandl

erExt/Files

RgsAgentServiceInternalUri : https://front2k13-eu.xxxx.com/RgsClients/Agent

Service.svc

RgsAgentServiceExternalUri : https://lyncweb-eu.groupexxxx.com/RgsClients/A

gentService.svc

MeetExternalUri : https://lyncweb-eu.groupexxxx.com/Meet

DialinExternalUri : https://lyncweb-eu.groupexxxx.com/Dialin

CscpInternalUri : https://front2k13-eu.xxxx.com/Cscp

ReachExternalUri : https://lyncweb-eu.groupexxxx.com/Reach

ReachInternalUri : https://front2k13-eu.xxxx.com/Reach

WebTicketExternalUri : https://lyncweb-eu.groupexxxx.com/WebTicket/We

bTicketService.svc

WebTicketInternalUri : https://front2k13-eu.xxxx.com/WebTicket/WebTic

ketService.svc

McxServiceExternalUri : https://lyncweb-eu.groupexxxx.com/Mcx/McxServi

ce.svc

McxServiceInternalUri : https://front2k13-eu.xxxx.com/Mcx/McxService.s

vc

AutodiscoverServiceExternalUri : https://lyncweb-eu.groupexxxx.com/Autodiscover

/AutodiscoverService.svc/root

AutodiscoverServiceInternalUri : https://front2k13-eu.xxxx.com/Autodiscover/Aut

odiscoverService.svc/root

ExternalFqdn : Lyncweb-eu.Groupexxxx.com

InternalFqdn :

DependentServiceList : {Registrar:front2K13-eu.xxxx.com, Conferencing

Server:front2K13-eu.xxxx.com}

ServiceId : 1-WebServices-9

SiteId : Site:DEU

PoolFqdn : front2K13-eu.xxxx.com

Version : 6

Role : WebServer

 

Identity : WebServer:hon11im.xxxx.com

FileStore : FileStore:hon11im.xxxx.com

UserServer : UserServer:hon11im.xxxx.com

PrimaryHttpPort : 80

PrimaryHttpsPort : 443

ExternalHttpPort : 8080

ExternalHttpsPort : 4443

PublishedPrimaryHttpPort :

PublishedPrimaryHttpsPort :

PublishedExternalHttpPort : 80

PublishedExternalHttpsPort : 443

ReachPrimaryPsomServerPort : 8060

ReachExternalPsomServerPort : 8061

AppSharingPortStart : 49152

AppSharingPortCount : 16383

McxSipPrimaryListeningPort : 5086

McxSipExternalListeningPort : 5087

LIServiceInternalUri : https://hon11im.xxxx.com/locationinformation/l

iservice.svc

ABHandlerInternalUri : https://hon11im.xxxx.com/abs/handler

ABHandlerExternalUri : https://front-as.groupexxxx.com/abs/handler

DLExpansionInternalUri : https://hon11im.xxxx.com/groupexpansion/servic

e.svc

DLExpansionExternalUri : https://front-as.groupexxxx.com/groupexpansion

/service.svc

CAHandlerInternalUri : https://hon11im.xxxx.com/CertProv/CertProvisio

ningService.svc

CAHandlerInternalAnonUri : http://hon11im.xxxx.com/CertProv/CertProvision

ingService.svc

CollabContentInternalUri : https://hon11im.xxxx.com/CollabContent

CollabContentExternalUri : https://front-as.groupexxxx.com/CollabContent

CAHandlerExternalUri : https://front-as.groupexxxx.com/CertProv/CertP

rovisioningService.svc

DeviceUpdateDownloadInternalUri : https://hon11im.xxxx.com/RequestHandler/ucdevi

ce.upx

DeviceUpdateDownloadExternalUri : https://front-as.groupexxxx.com/RequestHandler

Ext/ucdevice.upx

DeviceUpdateStoreInternalUri : http://hon11im.xxxx.com/RequestHandler/Files

DeviceUpdateStoreExternalUri : https://front-as.groupexxxx.com/RequestHandler

Ext/Files

RgsAgentServiceInternalUri : https://hon11im.xxxx.com/RgsClients/AgentServi

ce.svc

RgsAgentServiceExternalUri : https://front-as.groupexxxx.com/RgsClients/Age

ntService.svc

MeetExternalUri : https://front-as.groupexxxx.com/Meet

DialinExternalUri : https://front-as.groupexxxx.com/Dialin

CscpInternalUri : https://hon11im.xxxx.com/Cscp

ReachExternalUri : https://front-as.groupexxxx.com/Reach

ReachInternalUri : https://hon11im.xxxx.com/Reach

WebTicketExternalUri : https://front-as.groupexxxx.com/WebTicket/WebT

icketService.svc

WebTicketInternalUri : https://hon11im.xxxx.com/WebTicket/WebTicketSe

rvice.svc

McxServiceExternalUri : https://front-as.groupexxxx.com/Mcx/McxService

.svc

McxServiceInternalUri : https://hon11im.xxxx.com/Mcx/McxService.svc

AutodiscoverServiceExternalUri : https://front-as.groupexxxx.com/Autodiscover/A

utodiscoverService.svc/root

AutodiscoverServiceInternalUri : https://hon11im.xxxx.com/Autodiscover/Autodisc

overService.svc/root

ExternalFqdn : front-as.groupexxxx.com

InternalFqdn :

DependentServiceList : {Registrar:hon11im.xxxx.com, ConferencingServe

r:hon11im.xxxx.com}

ServiceId : 2-WebServices-1

SiteId : Site:DAS

PoolFqdn : hon11im.xxxx.com

Version : 5

Role : WebServer

 

 

Resolution

This cmdlet should be runned directly on the Lync 2013 Farm.

 

 

Posted in 2- LYNC-2013, Lync 2013-Mobile-Client | Leave a Comment »

Des nouvelles de Kemp !

Posted by Teruin laurent le octobre 13, 2014



Bon c’est vrai on les aime bien les gens de Kemp. Pourquoi ? La raison est simple, ils sont efficaces, abordables financièrement, réactifs et leurs solutions fonctionnent bien. C’est avant tout ce que cherchent nos clients et les retours que nous en avons depuis quelques temps sont très bons.

L’objectif de ce billet et de vous présenter rapidement les nouveautés fonctionnelles de la nouvelle version. On reviendra surement vers vous lorsque nous les testerons.

Kerberos Constrained Delegation (KCD):

This eliminates the need for users to provide credentials twice
Important feature found in TMG
Prerequisite for SmartCard / CAC Authentication

VMware vCenter Log Insight Manager add-on pack
o    Solves key availability problem for VMware and customers leveraging vCenter Log Insight
•    GEO/GSLB pack enhancements for granular interface control
o    Provides customers with greater granularuity for hybrid environments
o    Several enterprise applications support split DNS which simplifies management

Application Firewall Pack Beta
o    Integration of WAF functionality and security services in LoadMaster

Cordialement
Laurent Teruin

Posted in Non classé | Leave a Comment »

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

Posted by Teruin laurent le octobre 6, 2014


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.

Posted in Non classé | Leave a Comment »

Les ratés du net : Canalplay

Posted by Teruin laurent le septembre 26, 2014


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 !


 

Posted in Non classé | Leave a Comment »

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

Posted by David ANDRE le septembre 24, 2014


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

Posted in 2- LYNC-2013, Lync 2013 Mise à Jour | Leave a Comment »

Exchange 2013 CU5 : Régression fonctionnelle

Posted by Teruin laurent le septembre 24, 2014


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

 


 

Posted in EXCHANGE 2013, Exchange 2013 Issues | 2 Comments »

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

Posted by Teruin laurent le septembre 19, 2014


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:3E
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!

 

 

 

 

 

 

 


 

Posted in Exchange 2013 Issues | 1 Comment »

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

Posted by Teruin laurent le septembre 18, 2014


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.

 

 

 

 

 


 

Posted in Exchange 2013 Issues | Leave a Comment »

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

Posted by Teruin laurent le septembre 11, 2014


 

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. ;-)

 


Posted in EXCHANGE 2013 | Leave a Comment »

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

Posted by Teruin laurent le septembre 5, 2014


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


 

Posted in KEMP HLB | Leave a Comment »

 
Suivre

Recevez les nouvelles publications par mail.

Rejoignez 224 autres abonnés