Outlook searching extremely slow after Windows 10 Update / Búsquedas en Outlook lentas después de actualizar Windows 10

Fuente: https://social.technet.microsoft.com/Forums/ie/en-US/307ea5ea-1417-4c1f-b40d-ee2e9881f47f/outlook-completely-missing-from-indexed-locations

When having issues searching on Outlook 2007 after Windows 10 Updates you must open a Elevated Command Prompt and run:

REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{0077B49E-E474-CE11-8C5E-00AA004254E2}” /t REG_DWORD /d 1 /f

REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{4154494E-BFF9-01B8-00AA-0037D96E0000}” /t REG_DWORD /d 1 /f

REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{70fab278-f7af-cd11-9bc8-00aa002fc45a}” /t REG_DWORD /d 1 /f

REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{C0A19454-7F29-1B10-A587-08002B2A2517}” /t REG_DWORD /d 1 /f

REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{c34f5c97-eb05-bb4b-b199-2a7570ec7cf9}” /t REG_DWORD /d 1 /f

you can copy and paste each of them and press Enter at the end

Greetings

B.

Renew expired Exchange Outlook Web App and Microsoft Outlook Certificate Este certificado ha expirado o no es válido todavía, "La fecha del certificado de seguridad es válida", "El nombre del certificado de seguridad no es válido o no coincide con el nombre del sitio"

Spanish Keywords:

 

Trabaja para Exchange 2010 también en Windows Small Business Server 2011.

 

Si están usando un certificado autofirmado estos pasos no son necesarios pues el mismo servidor de Exchange va a autorenovar los certificados.  Y es más probable qué los errores de certificados sean por qué el nombre del certificado no coincide con el publicado externamente.

 

Por ello es necesario verificar si el certificado expiro o sí el nombre de publicación no coincide.

 

Si usamos entidades certificadoras para verificar si el certificado expiró:  

• En el sitio de owa, al dar clic en "error de certificado" obtienes algo similar
• "Este certificado ha expirado o no es válido todavía"

 

• Cuándo usas Microsoft Outlook para conectar al servidor de Microsoft Exchange obtienes algo similar:  Error junto a "La fecha del certificado de seguridad es válida"

 

Para reparar este error en una sesión del servidor Exchange

1. Abre la consola de Exchange
2. Navega en el árbol de la consola y da clic en "Configuración de Servidor" 
3. En la parte inferior se puede identificar el certificado expirado marcado con una x roja

• Das botón derecho en el certificado y das clic en "Renovar Certificado"

• Se da un nombre a la solicitud de certificado 
• 
• El archivo se creará en la carpeta qué indiquemos después de dar clic en renovar

Una vez qué tengamos el archivo se abre el sitio web de la entidad certificadora y se pega el texto dentro del archivo siguiendo las instrucciones de:
Cuarto Paso: Crear el certificado a partir de la solicitud en la siguiente entrada de este blog
Exchange 2007 and Exchange 2010 Issue a Certificate with a Windows 2008 CA and enable RPC over HTTP

Sin embargo es más sencillo utilizar el siguiente comando de Exchange Management Shell:

1. (para Windows 2008) Clic en Inicio, "Todos los Programas", "Microsoft Exchange 200x", abre el que dice "Exchange Management Shell"
2. Cuándo tengas acceso al Shell de Exchange, ejecuta el siguiente comando:
   [PS] C:\Windows\System32> certreq -submit -attrib "CertificateTemplate:WebServer"

inmediatamente se solicita el path del archivo generado cert2016.req o el nombre qué le hayan puesto

A continuación les solicita la entidad certificadora a la cuál se va a renovar el certificado,

 

 

Una vez que seleccionamos la entidad certificadora (mismo Servidor de Exchange o algún servidor dentro del dominio) se genera un archivo nuevo .cer

 

 

Se regresa a la consola de Exchange y aparecerá el nuevo certificado, sin embargo es necesario dar clic derecho en el mismo y asignar los servicios IIS, POP, SMTP e IMAP.



 



Al dar clic en asignar habrá 4 confirmaciones diciendo qué se va a reemplazar el certificado a todas debe responder "sí" reemplazar o "sí a todo"

Una vez terminado los errores de OWA y Outlook desaparecerán.  Reiniciar el caché del navegador o un reinicio del PC permitirá quitar los errores

Si el error es provocado por un error en el nombre, el mensaje será como el que sigue: "El nombre del certificado de seguridad no es válido o no coincide con el nombre del sitio"

 

Para resolverlo hay que ejecutar a partir del "Tercer Paso: Crear el certificado de Exchange para que funcione con un nombre principal y varios alias internos/externos" de la siguiente entrada de este blog Exchange 2007 and Exchange 2010 Issue a Certificate with a Windows 2008 CA and enable RPC over HTTP

Con estos procedimientos evitas los mensajes de error de certificado de Microsoft Outlook cuándo se conecta a un servidor de exchange que también tiene Outlook Web App, Outlook Anywhere y donde el nombre del equipo y el del dominio interno no coincide con el del alias de internet.

Saludos
B.

 

Experiencing an OWA HTTP 500 Error?

Source: http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html

I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox.


You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.
So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue.
Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause.
Until later,
Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture

I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox.



You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.
So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue.

Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause.
Until later,
Henrik Walther
Technology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture 

Setup Microsoft Outlook 2007 to open a Office 365 Mailbox

Install this updates:


•For Outlook 2007    
KB2596598 from the July 2012 public update
KB2687404 from the November 2012 public update


Microsoft Online Services Sign-In Assistant for IT Professionals RTW                        
http://www.microsoft.com/en-us/download/details.aspx?id=28177 (escoger 32 o 64 bits)



Configure Outlook with "AutoDetect Settings" and username and correctly changed 1st time password from Outlook Web App

This also applies for Exchange Online Services nor Office 365

ZCS Avoiding Browser (IE, Firefox, Outlook) Certificate Error with Zimbra Web Client

1. on Zimbra with Putty or Terminal run:

openssl x509 -in /opt/zimbra/ssl/zimbra/ca/ca.pem -outform DER -out /var/tmp/ca.cer

2. startx
3. browse to https://mail.tudominio.com/
4. attach and sent your self the the ca.cer file from /var/tmp

Use GPEDIT.MSC (workgroup) or GPO to copy certificates to other domain machines
1. Ve a Policy Object Name/Computer Configuration/Windows Settings/Security Settings/Public Key Policies/Trusted Root Certification Authorities
2. Right clic and click on import
3. Select ca.cer downloaded after.
4. close GPO or GPEDIT.MSC
5. Reboot

Voilá, mensaje de error de certificado CHAO!!!









06-25-2009, 07:59 AM





Source: http://www.zimbra.com/forums/administrators/26641-outlook-users-getting-certificate-warning.html

YetiRick
New Member

Posts: 4

I know this is too late to help any of the old posters, but it may help other with the same question...

Assuming the Zimbra devs don't move the file, the command:

openssl x509 -in /opt/zimbra/ssl/zimbra/ca/ca.pem -outform DER -out ca.der

will generate the CA root certificate you need in order for Windows to import it properly. You can then copy the resulting ca.der file to your Windows box and double-click it (or import it using the wizard.) It will install into the "Trusted Root Certification Authorities" section of your certificates window. Outlook and HTTPS webmail will no longer generate those annoying errors.

Please keep in mind that if the Zimbra CA is pre-generated and not generated at the time of installation, this will open you up to misidentified sites that sign their own certs with the same CA. I don't know if this is the case or not, but would recommend building your own CA if you're unsure.

[SOLVED] Rolling Your Own CA and Installing Certificates in Zimbra

will get that done for you. And you won't have to guess at which ca.pem file to use.


Fuente 2: http://technet.microsoft.com/en-us/library/cc738131(WS.10).aspx
Add a trusted root certification authority to a Group Policy object
Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To add a trusted root certification authority to a Group Policy object

Open the Group Policy object (GPO) that you want to edit.

In the console tree, click Trusted Root Certification Authorities.

Where?

Policy Object Name/Computer Configuration/Windows Settings/Security Settings/Public Key Policies/Trusted Root Certification Authorities

On the Action menu, point to All Tasks, and then click Import.

This starts the Certificate Import Wizard, which guides you through the process of importing a root certificate and installing it as a trusted root certification authority (CA) for this GPO.

Notes

To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as.

ClearOS Adding a second listener port on Postfix (great for closed ISP SMTP ports)

1. Login to your ClearOS as root (use Putty.exe)
2. Edit /etc/postfix/master.cf as follows: find the line that says "smtp inet n - n - - smptd"copy the line or change the line "smtp" to "2525" or whatever port you want the postfix daemon to use.
3. vi /etc/postfix/master.cf
4. to copy line press Y
5. to paste line press P
6. replace on the pasted line the word smtp to 2525
   
7. press Esc
   
8. wq!

Restart postfix "/etc/init.d/postfix restart".

Go to Network- Firewall- Incoming
Add Nickname/port: SMTP2525
Select: TCP
PortBox: 2525
click add

Configure Outlook advanced SMTP options to point to port 2525 instead of default 2525

B

Clear OS - Banned Office 2007 Files - docx, xlsx, pptx

Source: http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,14/func,view/id,15627/

Re:Banned Office 2007 Files - docx, xlsx, pptx 9 Months, 1 Week ago
If you do want to pass these then add them to the list also (note these will be passed as 'clean' regardless of content)

I found the following also worked:-

Create a file called /etc/amavisd/override.conf

Code:
$banned_filename_re = new_RE(
[ qr'(\.xlsx|\.docx|\.pptx|\.xlsm|\.docm|\.pptm)$' => 0 ], # allow all MS Office 2007 (including macro)
);


Then run 'service amavisd restart' - it should now pass these files, the ones to be wary of are xlsm or docm which contain macros.

You can disable the .bin files from being blocked but opens a bit of a security hole for other binary files from admin console

Server- Mail Scanning-Antimalware Uncheck .bin CD Iso image files