LDAP проблема с загрузкой сервера RedHat

 

Проблема:

 

To relevant parts of nsswitch.conf on my system look like this:

 

passwd: files ldap

group: files ldap

shadow: files ldap

 

bind_policy hard

nss_reconnect_tries 3

nss_reconnect_sleeptime 1

nss_reconnect_maxconntries 3

 

 

INIT: version 2.86 booting

Starting the hotplug events dispatcher: udevd

udevd[374]: nss_ldap: could not connect to any LDAP server as (null) -

Can't contact LDAP server

udevd[374]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar:

Can't contact LDAP server

udevd[374]: nss_ldap: could not connect to any LDAP server as (null) -

Can't contact LDAP server

udevd[374]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar:

Can't contact LDAP server

udevd[374]: nss_ldap: could not connect to any LDAP server as (null) -

Can't contact LDAP server

udevd[374]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar:

Can't contact LDAP server

udevd[374]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)

...

If you think the boot takes still to long, you can decrease these values 

further. Another possibility would be to use "bind_policy soft", but if I use 

that option, some other services started after udevd cannot connect to the 

LDAP server correctly.

 

Решение:

 

/etc/ldap.conf

 

bind_policy soft

nss_reconnect_tries 3

nss_reconnect_sleeptime 1

nss_reconnect_maxconntries 3

 

 

 

OWA 2007 configuration tricks to boost performance

Gzip compression is an OWA 2007 option that compresses Web content at the server level before its sent to end users. There are a few things you should know about Gzip.

First, Gzip is enabled by default, but the default compression level is set to Low. Additionally, Gzip can negatively affect your client access server's performance since the server must compress Web content. If you change the Gzip compression level, you'll have to restart IIS before the change takes effect.

Which compression level to use depends on where your biggest performance bottleneck is. If your Internet connection (or your remote user's Internet connection) is the bottleneck, you can improve the end-user experience by setting the Gzip compression level to High.

To do so, open the Exchange Management Shell and enter: Set-OwaVirtualDirectory -Identity "owa (Default Web Site)" -GzipLevel High

However, if there is enough Internet bandwidth, but your client access server is suffering from excessive CPU use you may be able to improve performance by disabling Gzip. To do so, enter: Set-OwaVirtualDirectory -Identity "owa (Default Web Site)" -GzipLevel Off

Reminder: You must restart IIS before your changes will take effect. OWA will be temporarily unavailable during this time. Perform the restart by either rebooting the client access server or by opening a command prompt window and entering:IISRESET /NOFORCE

Отключение SPAM Filters on MS Exchange 2007

Set-Mailbox -Identity tester -SCLDeleteEnabled 0 -SCLQuarantineThreshold 0 –SCLJunkEnabled 0