HtmlToText
contacter l'auteur envoyer à un ami derniers messages continuum et équivalent android avec chromecast oab not available in exchange 2013 active directory replication fails with error target principal name incorrect active directory : replication error target principal name incorrect faire fonctionner genymotion et ses machines android sur windows 10 released: june 2015 exchange cumulative update and update rollups comment se débarrasser de dridex? vmware vsphere 6 : le lancement en ligne! nettoyer le répertoire winsxs de windows 2008 r2/windows 7 désactiver sslv3 sur les serveurs windows avec iis veeam backup & replication 8 availability suite disponible! outil de sauvegarde gratuit des postes clients à venir chez veeam changement de méthode exchange 2010 mailbox database creation error access denied votre ipad sous ios 8 est lent ? trop tard pour revenir sous ios 7 newsletter archives juillet 2016 janvier 2016 décembre 2015 août 2015 juin 2015 février 2015 janvier 2015 novembre 2014 octobre 2014 septembre 2014 toutes les archives transfert de connaissances pole conseil expertise maintenant architecture et intégration de proservia, par jean-charles demarque accueil du blog recommander ce blog créer un blog avec canalblog 05 juillet 2016 continuum et équivalent android avec chromecast continuum est une fonctione très intéressante des smartphones windows 10 mobiles de microsoft. il est possible d'utiliser un client rdp/remote app depuis son téléphone sur un écran d'ordinateur ou une tv en hdmi ou en miracast. mais windows phone /windows 10 mobile est une niche, peu de modèles sont disponibles. android d'un autre côté est ouvert et permet beaucoup de choses. de la une question m'est venue, comment utiliser mon smartphone android lg g2 et une clé chromecast comme un pseudo pc sur une tv? j'ai trouvé mon bonheur sur le play store avec l'application andromium os, mais il serait possible de juste utiliser le client remote desktop de microsoft sur le store. https://play.google.com/store/apps/details?id=com.microsoft.rdc.android&hl=fr https://play.google.com/store/apps/details?id=com.andromium.os&hl=fr il faut bien entendu un cable micro usb vers usb "otg host" pour pouvoir brancher un clavier et une souris, ou aller sur un kit bluetooth, mais le prix n'est plus le même. https://www.amazon.fr/c%c3%a2ble-micro-usb-fiche-prise-femelle/dp/b005jdetza/ref=sr_1_8?ie=utf8&qid=1467721762&sr=8-8&keywords=micro+usb https://www.amazon.fr/rii-ultra-mince-bleutooth-inoxydable-rechargeable/dp/b01873xdic/ref=sr_1_2?ie=utf8&qid=1467721796&sr=8-2&keywords=clavier+bluetooth bien entendu je me sers du chromecast v2 pour caster sur la tv et son application google cast sur android... et hop je peux caster mon écran sur la tv, je lance le client rdp et je me connecte sur mon serveur rds et je peux travailler avec mon word, outlook, client vsphere etc depuis mon téléphone! de même il est possible de piloter une présentation sans fil et sans ordinateur mais c'est une autre histoire... des explications sur andromium: http://andromiumos.freeforums.net/thread/6/setting-andromium-os-chromecast-miracast posté par jcdemarque à 14:33 - divers - commentaires [0] - permalien [ # ] tags : 10 , android , chromecast , continuum , google , mobile , phone , rdp , remote apps , remote desktop services , windows 19 janvier 2016 oab not available in exchange 2013 a client had errors in outlook after migrating to exchange 2013, and outlook did not show the oab url in autodiscover information. here is what we did : get-offlineaddressbook | fl webdistributionenabled,virtualdirectories,identity if you have webdistributionenabled set to false and/or no value defined for virtualdirectories (as shown below) this is why you have the issue to solve this issue, run the following command get-clientaccessserver | get-oabvirtualdirectory | fl identity to get oab virtual directory identity (this will be required for the next command) set-offlineaddressbook -virtualdirectories "<oab vdir identity from the previous command>" –identity <oab identity> wait a little bit and try a new autodiscover check; you should now have oab url parameter and value. http://blog.hametbenoit.info/lists/posts/post.aspx?id=443 i recently saw the same problem at a customer...no oab url in autodiscover. looking around a bit, i noticed that webdistributionenabled was set to $false which was very odd since that is value that can't be changed and the oab was missing many of the virtualdirectories (this was 5 multi-role servers). below you see the steps i took to solve my customers problem: 1) new-offlineaddressbook "new offline address book" -addresslists "default global address list" 2) set-offlineaddressbook "new offline address book" -virtualdirectories "server1\oab (default web site)", "server1\oab (exchange back end)","server2\oab (default web site)", "server2\oab (exchange back end)" -isdefault $true (added all five servers of course) 3) get-mailboxdatabase | set-mailboxdatabase -offlineaddressbook "new offline address book" 4) restart-service msexchangemailboxassistants (on all servers) 5) recycled the application pool msexchangeautodiscoverapppool in iis (on all servers) 6) remove-offlineaddressbook "default offline address book" https://social.technet.microsoft.com/forums/exchange/en-us/dc286338-a37e-4a1e-a426-ecec7ba38c87/exchange-2013-not-returning-oab-url-issue?forum=exchangesvrclients posté par jcdemarque à 14:19 - exchange - commentaires [0] - permalien [ # ] tags : 2013 , exchange , microsoft , missing , oab , offline address book , server 16 décembre 2015 active directory replication fails with error target principal name incorrect i recently had a problem with a client's active directory 2 active directory sites were unable to connect during a few days, and in the meantime the domain controllers changed their computer's account password (see murphy 's law) when the network came back, the active directory replication tools gave the following error : dcdiag reports that the active directory replications test has failed with error -2146893022: “the target principal name is incorrect." this oriented me towards this microsoft kb : https://support.microsoft.com/en-us/kb/2090913 after checking all the information, here is what i did : the "netdom resetpwd /server:<dc to direct password change to> /userd:<user name> /passwordd:<password> command executed from an admin-privileged cmd prompt on the console of the dc needing a password reset can be used to reset dc machine account passwords. this command must be executed on the different dcs crossing sites, dc1sitea towards dc1siteb and dc1siteb towards dc1sitea after cascading reboots, replication started again correctly! posté par jcdemarque à 11:10 - active directory - commentaires [0] - permalien [ # ] tags : active directory , incorrect , microsoft , netdom , principal name , replication , resetpwd , server , target , windows active directory : replication error target principal name incorrect lors d'un dépannage client, j'ai du résoudre un problème de réplication active directory assez particulier. 2 sites active directory ont été coupés pendant plusieurs jours, et durant ce laps de temps, les contrôleurs de domaine ont changé le mot de passe de leur compte ordinateur (cf loi de murphy ) après la coupure, le client n'a pas tout de suite remarqué que les réplications ne se faisaient plus. au bout d'un temps, il a lancé des outils de diagnostique qui ont retourné l'erreur suivante : dcdiag reports that the active directory replications test has failed with error -2146893022: “the target principal name is incorrect." en français : le nom principal de la cible est incorrect ce message d'erreur m'a orienté vers ce kb microsoft : https://support.microsoft.com/en-us/kb/2090913 je vous épargne les traces réseau, on avance sur la solution qui a fonctionné sur l'environnement de mon client : the "netdom resetpwd /server:&l
Informations Whois
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
Domain Name: CANALBLOG.COM
Registry Domain ID: 94428638_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2019-03-22T09:40:34Z
Creation Date: 2003-01-27T21:30:48Z
Registry Expiry Date: 2020-01-27T21:30:48Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: A1-69.AKAM.NET
Name Server: A12-64.AKAM.NET
Name Server: A20-65.AKAM.NET
Name Server: A28-66.AKAM.NET
Name Server: A3-67.AKAM.NET
Name Server: A7-64.AKAM.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-07-11T03:20:22Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
REGISTRAR Gandi SAS
SERVERS
SERVER com.whois-servers.net
ARGS domain =canalblog.com
PORT 43
TYPE domain
RegrInfo
DOMAIN
NAME canalblog.com
CHANGED 2019-03-22
CREATED 2003-01-27
STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
NSERVER
A1-69.AKAM.NET 193.108.91.69
A12-64.AKAM.NET 184.26.160.64
A20-65.AKAM.NET 95.100.175.65
A28-66.AKAM.NET 95.100.173.66
A3-67.AKAM.NET 96.7.49.67
A7-64.AKAM.NET 23.61.199.64
REGISTERED yes
Go to top
poleexpertise.canalblog.com rapport :
Visitez le site