Voici un lien pratique
1. Logon to Exchange 2013 CAS Server.
2. Open IIS 7.0.
3. Locate virtual directories for Autodiscover and EWS (Exchange Web Services) under default website.
4. Select EWS.
5. Select authentication.
6. Set status DISABLED for Anonymous authentication.
7. Select Windows authentication, click ADVANCED SETTINGS, select ENABLE KERNEL-MODE AUTHENTICATION. Click OK.
8. Repeat Steps 5-7 for Autodiscover.
9. Go to command prompt, run IISRESET.
10. Close and re-open Outlook client.
Les clés pour ces applications sont dans le registre sous la rubrique :
- CONF.EXE ==> NetMeeting
- DIALER.EXE ==>Numéroteur Téléphonique
- HELPCTR.EXE ==> Centre d’Aide et de Support
- HYPERTRM.EXE ==>HyperTerminal
- ICWCONN1.EXE ==> Assistant de Connexion Internet
- IEXPLORE.EXE – Internet Explorer
- INETWIZ.EXE ==> Configuration de la Connexion Internet
- INSTALL.EXE – User’s Folder
- MIGWIZ.EXE ==> Assistant de Transfert de Fichiers et de Paramètres
- MSCONFIG.EXE ==> Utilitaire de Configuration Système
- MSIMN.EXE – Outlook Express
- MSINFO32.EXE ==> Informations Système
- MSMSGS.EXE – Windows Messenger
- MSN6.EXE – MSN Explorer
- PBRUSH.EXE – Paint
- WAB.EXE ==> Carnet d’Adresses
- WABMIG.EXE ==> Outil d’Importation de Carnet d’Adresses
- WINNT32.EXE ==> Dossier Utilisateur
Les fichiers EXE qui suivent se trouvent dans les dossiers « C:\Windows\System32\ » ou « C:\Windows\ » sont pour la plus part dans le panneau de configuration et dans les outils admin ou système avec l’extension « EXE ».pas besion de taper l’extension celle-ci sont automatiquement reconnus
- ACCWIZ.EXE ==> Assistant Accessibilité
- CHARMAP.EXE ==> Table des Caractères
- CLEANMGR.EXE ==> Nettoyage de Disque
- CLICONFG.EXE ==> Utilitaire Réseau du Client SQL Server
- CLSPACK.EXE ==> Liste/Export Packages Installés
- CMSTP.EXE ==> Installation de Profils Connexion Manager
- CONTROL.EXE ==> Panneau de Configuration
- DCOMCNFG.EXE ==> Propriétés de Configuration de Distributed COM
- DDESHARE.EXE ==> Agent Net DDE – Partage DDE
- DRWATSON.EXE ==> Doctor Watson v1.00b
- DRWTSN32.EXE ==> Réglages Dr Watson
- DXDIAG.EXE ==> Outils de Diagnostic DirectX
- EUDCEDIT.EXE ==> Éditeur de Caractères Privés
- EVENTVWR.EXE ==> Observateur d’événements
- EXPLORER.EXE ==> Explorateur Windows
- FXSCLNT.EXE ==> Console Fax
- FXSCOVER.EXE ==> Éditeur de Page de Couverture Fax
- FXSEND.EXE ==> Envoi Fax
- LOGOFF.EXE ==> Déconnexion Système
- MAGNIFY.EXE ==> Loupe Microsoft
- MMC.EXE ==> Console d’Administration
- MOBSYNC.EXE ==> Gestion Éléments à Synchroniser
- MPLAY32.EXE ==> Media Player
- MSTSC.EXE ==> Connexion Bureau à Distance
- NARRATOR.EXE ==> Narrateur Microsoft
- NETSETUP.EXE ==> Assistant de Configuration Réseau
- NSLOOKUP.EXE ==> Recherche Adresses IP
- NTSD.EXE ==> Debugger pour Windows 2000
- ODBCAD32.EXE ==> Administrateur de Sources de Données ODBC
- OSUNINST.EXE ==> Désinstallation de Windows
- PACKAGER.EXE ==> Gestionnaire de Liaisons
- PERFMON.EXE ==> Analyseur de Performances
- PROGMAN.EXE – P / Gestionnaire de Programmes
- RASPHONE.EXE ==> Annuaire Téléphonique
- REGEDIT.EXE ==> Éditeur du Registre
- REGEDT32.EXE ==> Éditeur du Registre
- RESET.EXE ==> Reset Session
- RSTRUI.EXE ==> Restauration du Système
- RTCSHARE.EXE ==> Session de Partage
- SFC.EXE ==> Contrôle des Fichiers Système
- SHRPUBW.EXE ==> Créer un Dossier Partagé
- SHUTDOWN.EXE ==> Arrêt Système
- SIGVERIF.EXE ==> Vérification des Signatures des Fichiers
- SNDREC32.EXE ==> Magnétophone
- SNDVOL32.EXE ==> Contrôle Volume Son
- SYNCAPP.EXE ==> Créer un Porte-Documents
- SYSEDIT.EXE ==> Éditeur de Configuration Système
- SYSKEY.EXE ==> Protection de la Base de Données des Comptes Windows
- TASKMGR.EXE ==> Gestionnaire des Fichiers de Windows
- TELNET.EXE ==> Client Telnet
- TSSHUTDN.EXE ==> Arrêt du Système
- TOURSTART.EXE ==> Lancement du “Tour Windows”
- UTILMAN.EXE ==> Gestionnaire Utilitaires Système
- USERINIT.EXE ==> Mes Documents
- VERIFIER.EXE ==> Gestionnaire du Vérificateur de Pilotes
- WIAACMGR.EXE ==> Assistant Scanner et Appareil Photo
- WINCHAT.EXE ==> Conversation
- WINHELP.EXE ==> Moteur d’Aide de Windows
- WINHLP32.EXE – / Aide
- WINVER.EXE ==> À Propos de Windows – Vérification Version
- Wscrïpt.EXE ==> Paramètres de Windows scrïpt Host
- WUPDMGR.EXE ==> Mise à Jour de Windows
Les applications du Panneau de Configuration que l’ont peut lancées à partir de la commande extension CPL« Exécuter ». Qui sont elles dans le dossier « C:\Windows\System32 » taper extension« CPL ».
- ACCESS.CPL ==> Options d’accessibilité
- APPWIZ.CPL ==> Ajout/Suppression de Programmes
- DESK.CPL ==> Propriétés de l’Affichage
- HDWWIZ.CPL ==> Assistant Ajout/Suppression de Matériel
- INETCPL.CPL ==> Propriétés d’Internet Explorer
- INTL.CPL ==> Options Régionales
- JOY.CPL ==> Options de Jeu
- MAIN.CPL ==> Propriétés de la Souris
- MMSYS.CPL ==> Propriétés des Sons et du Multimédia
- NCPA.CPL ==> Connexions Accès Réseau à Distance
- NUSRMGR.CPL ==> Comptes d’Utilisateurs
- ODBCCP32.CPL ==> Administrateur de Sources de Données ODBC
- POWERCFG.CPL ==> Propriétés des Options d’Alimentation
- SYSDM.CPL ==> Propriétés Système
- TELEPHON.CPL ==> Options des Modems et de Téléphonie
- TIMEDATE.CPL ==> Propriétés de Date/Heure
Ce qui suit sont des applications de la Console d’Administration Microsoft qui peuvent être ouvertes à partir de la commande « Exécuter » Elles ont l’extension « MSC ». Taper l’extension.
- CERTMGR.MSC – / Certificats
- CIADV.MSC ==> Service d’Indexation
- COMPMGMT.MSC ==> Gestion de l’Ordinateur
- DEVMGMT.MSC ==> Gestionnaire de Périphériques
- DFRG.MSC ==> Défragmenteur de Disques
- DISKMGMT.MSC ==> Gestion des Disques
- EVENTVWR.MSC ==> Observateur d’Événements
- FSMGMT.MSC ==> Dossiers Partagés
- LUSRMGR.MSC ==> Utilisateurs et Groupes Locaux
- NTMSMGR.MSC ==> Stockage Amovible
- NTMSOPRQ.MSC ==> Demandes de l’Opérateur de Stockage Amovible
- PERFMON.MSC ==> Analyseur de Performances
- SERVICES.MSC – / Services
- WMIMGMT.MSC ==> Infrastucture de Gestion de Windows (WMI)
So you can’t login to the Sophos UTM WebAdmin interface anymore. It happens. Perhaps you’ve made a configuration change and locked yourself out, or perhaps you’ve just forgotten your password. I locked myself out a couple of times when playing around with the new 2 Factor Authentication feature in the Sophos UTM 9.2 Beta. Don’t worry, here’s the steps to reset your password.
You’ll first need a direct console into Sophos UTM. For hardware appliances, plug in a monitor and keyboard, or for Virtual Appliances open up your virtualization system’s management console for the Virtual Machine.
Once you have a console open, try to login as the root user.
Yep, locked out alright! So lets go ahead and reset the root user password. Then we can go about resetting the password for the WebAdmin user as well. If you can login as root, jump to Resetting the Web Admin Password below.
Reset Sophos UTMs Root User Password
To reset the root password:
- Ensure you have a monitor and a keyboard connected to the Sophos UTM and restart the UTM.
- Press the ESC key as the Sophos UTM starts to boot. You’ll soon see the GNU GRUB screen:
- Ensure the current Sophos UTM version is highlighted (should be the top option). Do NOT select the ones that say ‘previous’ or ‘rescue’.
- Press the ‘e‘ key (don’t press Enter!).
- Use the arrow keys to highlight the second option that starts with the word ‘kernel‘:
- Again, press the ‘e‘ key on the keyboard
- The cursor should be at the end of a string of text. Add this to the end:
- Press Enter to return to the previous screen, then press the ‘b‘ key on the keyboard to reboot the Sophos UTM.
- Once the UTM boots, the cursor will be at a command prompt
- Now we finally get to reset the password. Type: passwd loginuser
- Enter and re-enter a new password for the ‘loginuser’ account.
- Type: passwd root
- Enter and re-enter a new password for the root account.
- Press Ctrl+Alt+Del to reboot the Sophos UTM.
You have now reset both the loginuser and root passwords. Once the UTM has rebooted, check that the root password works by logging in as the root user.
Reset Sophos UTM WebAdmin Password
Now we have regained access to the root user login, we can reset the WebAdmin password.
- Ensure you are still logged in as root as per the last step above.
- Type cc at the prompt. This will take you to another prompt starting with 127.0.0.1 MAIN >
- Type RAW. This will switch you to RAW mode.
- Type system_password_reset
- Browse to the WebAdmin Interface. You will notice it is now asking you to set the password.
- Enter your new password into each box and hit Apply. You’ll then be directed to the usual WebAdmin login page
- Enter your shiny new credentials, and if everything went to plan, you should be logged in!
source : Fastvue Sophos Reporter
- Users cannot authenticate with a vCenter Single Sign-On (SSO) 5.5 system that is installed on Windows Server 2012 when this system is joined to an Active Directory domain controller also running on Windows Server 2012.
- Users receive this error message when trying to log in through the vSphere Web Client:
Cannot Parse Group Information
- This issue occurs only in environments where BOTH of these conditions apply:
- vCenter SSO 5.5 is running on Windows Server 2012, and
- vCenter SSO 5.5 joined an Active Directory Domain with a Domain Controller that is running on Windows Server 2012.
- This article does not apply if:
- The vCenter SSO 5.5 machine is running on Windows Server 2008 or Windows Server 2008 R2 joined to any supported Active Directory Domain version.
- The vCenter SSO 5.5 machine is running on Windows Server 2012 and the Active Directory domain is running on Windows Server 2008 (and R2).
- The vCenter SSO 5.5 machine is installed as the vCenter Server Appliance joined to any supported Active Directory Domain version.
- You are running vCenter SSO versions earlier than 5.5.
To work around this issue on vSphere 5.5 GA (Build Number 1312298), replace the %WINDIR%\System32\idm.dll file on all systems running vCenter SSO 5.5 with the idm.dll file attached to this KB article.
To replace the idm.dll file on the Windows Server 2012 running SSO 5.5:
- Ensure that you are logged in as an administrator
- Stop the VMware Identity Management Service on the vCenter SSO server. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Note: This step also stops the VMware Secure Token Service.
- Back up the existing idm.dll by copying %WINDIR%\System32\idm.dll to %WINDIR%\System32\idm.dll.orig.
- Download the idm_patch09252013.zip attached to this article. It contains the replacement idm.dll.
- Run md5 checksum on the downloaded idm_patch09252013.zip. The md5 checksum should match the MD5 checksum in the note below.
- Decompress the zip file to a temporary location then copy the idm.dll to %WINDIR%\System32\.
- Confirm that you have both new (idm.dll) and old (idm.dll.orig) in the %WINDIR%\System32\ Directory.
- Start the VMware Secure Token Service on the vCenter SSO server. For more information, see Stopping, starting, or restarting vCenter services (1003895).x
Note: This step also starts the VMware Identity Management Service.
Was unable to start the VMware vSphere Web Client after upgrading from 5.1 to 5.5 (it’s same after restore a vcenter 5.5)
Noticed that the VMware Vsphere web client service wasn’t started.
Tried manually via Services.msc got the following error;
Windows could not start the VMware Vsphere web client service on local computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
I realized that the folders in the new version installation had changed and for that reason paths should be changed also.
Check your Registry value for hkey_local_machine\system\currentcontrolset\services\vspherewebclientsvc:
“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME=C:\Program Files\VMware\Infrastructure\vSphereWebClient\server set.default.JMX_PORT=9875
Look at these value and confirm that the WRAPPER file is located and accessible on the path mentioned above.
Always backup your registry before making changes.
For me I had to change the port (see below) for it to work, for others I have seen it is due to the path being incorrect or inaccessible. (with quote because Program Files have a space in name)
“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME= »C:\Program Files\VMware\Infrastructure\vSphereWebClient\server » set.default.JMX_PORT=9877
Restart the server.
How’s that for the title of a blog article! Apparently I’ve been reading too much Huffington Post or something. For the record, I never read that website. I have standards, as low as they may be.
So back to the title and the point of this post. Are there actually hidden log files that could cause some unintended problems with your Lync 2013 environment? Absolutely. I am assuming you are already aware that IIS logs could fill up your local hard drive. It is also a good idea to keep an eye on the trace files created by OCS Logger and Snooper.
However, there are some hidden logfiles that are created by Windows Fabric that could very much fill up your hard drive and it would be a decent challenge to find them. If you are unaware, Lync 2013 sits on top of a technology called Windows Fabric. For a nice overview, check out this Technet blog article as well as this article on masteringlync.com.
By default, Windows Fabric is set to create log files in this hidden system directory:
Once a log file reaches 128MB, it creates a brand new log file. Over time, all of these 128MB log file will fill up your hard drive. When the hard drive gets full it’s very likely that you will see some issues with Lync – yes, even including the potential of one of your Lync servers to crash.
Here is a screenshot of one of my lab servers where I have done nothing to address this potential issue.
According to Windows Explorer, that is 810MB of disk space taken up in my Lab by Windows Fabric log files. Note that these are binary log files so it’s not as if I could read these log files to see what is happening. As such, these log files are only useful to Microsoft when troubleshooting a potential issue. You know, an issue like your hard drive has filled up! I don’t think there is a point in keeping a years worth of Windows Fabric log files.
So how do we keep these log files from eating up our drive space? For the paranoid, create a scheduled task on all of your Front End Servers (and Directors and SBAs/SBSes) to move the logs to some other server that has disk space you want to waste. For the rest of us looking for an easy, one time fix, run this command from an elevated command prompt (this is not a PowerShell command):
Logman update trace FabricLeaseLayerTraces -f bincirc --cnf
This will change the logging to circular. According to this Technet article, –cnf is used to “create a new file when the log size has been exceeded”. I imagine this is added as a parameter so that logging doesn’t stop once the initial 128MB file size has been reached. Rather, it will go back to the beginning of the same file and continue logging.
So there you go. Either keep an eye on this directory or run the Microsoft-recommended command to make sure these hidden log files don’t cause you unnecessary heartache.
source : http://flinchbot.com/2014/02/28/the-hidden-logs-that-could-crash-your-lync-servers/
What is SPF?
Sender policy framework (SPF, RFC 7208) is an authentication process that ties the 5321.from (also known as the mail from,envelope from or return path) to authorized sending IP addresses. This authorization is published in a TXT record in DNS. Receivers can check SPF at the beginning of a SMTP transaction, compare the 5321.from domain to the connecting IP address and determine if that IP is authorized to transmit mail.
What does a SPF record look like?
At its simplest, the SPF TXT record contains a version indicator, allowed IPs and an authorization type.
In the example
"v=spf1 ip4:198.51.100.26 -all":
- v=spf1 is the version indicator
- 198.51.100.26 is the allowed sending IP
- -all means only this IP is authorized to send mail for the domain.
Of course, there are other ways to define authorized IP addresses. Using
"v=spf1 mx -all" authorizes any IP that is also a MX for the sending domain. Other SPF records can be included using the include: command; for instance
include:_spf.google.comincludes Google’s SPF record. IPs can be in either IPv4 space or IPv6 space by using either the ip4 or ip6 qualifiers:
"v=spf1 ip4:198.51.100.26 ip6:2001:db8:8:4::2 -all". SPF records can also contain IP ranges in the form
"v=spf1 ip4:198.51.100.128/25 -all".
Domain owners are also allowed to publish different types of authorization.
|+all||pass||Allow all mail|
|-all||fail||Only allow mail that matches one of the parameters (IPv4, MX, etc) in the record|
|~all||softfail||Allow mail whether or not it matches the parameters in the record|
|?all||neutral||No policy statement|
What’s the difference between ~all and -all
Given many receivers are not actively bouncing mail based on SPF pass/fail, there isn’t a strong argument for either -all or ~all in SPF records. For a while, Hotmail was advising that senders who published a -all record would have better delivery. This led to -all became a de-facto standard for a lot of ESPs and bulk senders. More recently, there does not seem to be any benefit to publishing -all even at Hotmail (Outlook.com, live.com, etc).
What should I publish?
I generally recommend publishing ~all records for my clients. There’s not a huge benefit to publishing -all and sometimes mail gets forwarded around. The one time I recommend a -all record is when a domain is getting forged into spam. Domain forgery can cause a lot of bounces. The amount of bounces can be bad enough to take down a mail server, particularly those with a small userbase. Many ISPs will check SPF before sending back a bounce and so a -all record can decrease the amount of blowback the domain owner has to deal with.
Do I have to publish SPF records?
No, there is no requirement for publishing SPF in order to send mail. You don’t even need to publish SPF to get inbox delivery. Gmail will even do a “best guess SPF” for domains not publishing SPF and authenticate off that. However, large volume senders should be publishing SPF records on principle.
Want to check your SPF record?
We provide a SPF checker on our Tools page.