ERRO NA HORA DE MUDAR WIN 1O HOME PARA PRO

Quando é feito uma instalação do Windows 10 e ela ativa automaticamente com Windows 10 home e quando tentamos mudar para o Windows 10 PRO ele apresenta erro e não aceita a sua chave mesmo sendo válida.

USAR: VK7JG-NPHTM-C97JM-9MPGT-3V66T    obs. sem estar conectado na internet.

Após ele atualizar para o Windows 10 Pro, trocar a chave do Windows colocando a chave válida.

ZCS OSE cannot start after upgrade to 8.8.15

       

        amavis                  Running
        dnscache                Running
        ldap                    Running
        logger                  Running
        mailbox                 Stopped
                zmmailboxdctl is not running.
        memcached               Running
        mta                     Running
        opendkim                Running
        proxy                   Running
        service webapp          Stopped
                zmmailboxdctl is not running.
        snmp                    Running
        spell                   Running
        stats                   Running
        zimbra webapp           Stopped
                zmmailboxdctl is not running.
        zimbraAdmin webapp      Stopped
                zmmailboxdctl is not running.
        zimlet webapp           Stopped
                zmmailboxdctl is not running.

        zmconfigd               Running


1. error in /opt/zimbra/log/mailbox.log

ERROR [main] [] Versions - DB Version Mismatch: ours=111 from DB=109
FATAL [main] [] system - Data version mismatch. Reinitialize or upgrade the backend data store



zimbra@zimbra:cd /opt/zimbra/libexec/scripts/
zimbra@zimbra:~/libexec/scripts$ ./migrate20190401-ZimbraChat.pl
Wed Jul 31 10:56:53 2019: Verified schema version 109.
Wed Jul 31 10:56:55 2019: Verified schema version 109.
Wed Jul 31 10:56:55 2019: Updating DB schema version from 109 to 110.
zimbra@zimbra:~/libexec/scripts$ ./migrate20190611-ZimbraChat.pl
Wed Jul 31 10:57:04 2019: Verified schema version 110.
Wed Jul 31 10:57:06 2019: Verified schema version 110.
Wed Jul 31 10:57:06 2019: Updating DB schema version from 110 to 111

2. update zmlocalconfig 

zimbra@zimbra:zmlocalconfig -e mailboxd_java_options="-server -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djava.awt.headless=true -XX:+UseG1GC -Dsun.net.inetaddr.ttl=${networkaddress_cache_ttl} -Dorg.apache.jasper.compiler.disablejsr199=true -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=15 -XX:G1MaxNewSizePercent=45 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:-OmitStackTraceInFastThrow -verbose:gc -Xlog:gc*=info,safepoint=info:file=/opt/zimbra/log/gc.log:time:filecount=20,filesize=10m -Djava.net.preferIPv4Stack=true -XX:+HeapDumpOnOutOfMemoryError -XX:CompileCommandFile=.hotspot_compiler -XX:HeapDumpPath=/opt/zimbra/log -XX:ErrorFile=/opt/zimbra/log/hs_err_pid%p.log"


 zmcontrol stop
 zmcontrol start

CentOS Linux release 7.7.1908 (Core)

fonte: https://forums.zimbra.org

Como melhorar a performace do FireBird

Como melhorar a performace do FireBird

                 Para melhorar o desempenho do FireBird é preciso ajusta algumas configurações.

                 No servidor, localize o arquivo firebird.conf, ele fica na pasta onde foi instalado o FireBird (Ex.: C:\Program Files\Firebird\2.5\). Dependendo da configuração do servidor a configuração do FireBird pode mudar.

                 A baixo seguem alguma configurações que podem ser usadas para melhorar o desempenho.

 

 

• Configuração para servidor com processador dual-core, e pelo menos 4GB memória:

  DefaultDbCachePages = 4096
  FileSystemCacheThreshold = 67108864
  FileSystemCacheSize = 70
  CpuAffinityMask = 3

• Configuração para servidor com processador dual-core, e pelo menos 8GB memória:

  DefaultDbCachePages = 8192
  FileSystemCacheThreshold = 134217728
  FileSystemCacheSize = 70
  CpuAffinityMask = 3

• Configuração para servidor com processador quad-core, e acima de 8GB memória:

  DefaultDbCachePages = 16384
  FileSystemCacheThreshold = 268435456
  FileSystemCacheSize = 80
  CpuAffinityMask = 3

          Para complementar o ideal é fazer um Backup/Restore da base de dados com o parâmetro Page Size igual a configuração usada no parâmetro DefaultDbCachePages, definido no firebird.conf.

https://datalansistemas.blogspot.com.br

Download Windows 10

Pessoal segue o link para baixar o Windows 10 / atualizar, assim não precisa esperar o agendamento.

https://www.microsoft.com/pt-br/software-download/windows10

só escolher 32 ou 64.

Instalação e configuração de certificados SSL no seu servidor Zimbra

/opt/zimbra/bin/zmcertmgr createcsr comm -new -keysize 2048 -subject "/C=BR/ST=SIGLADOESTADO/L=NOME DA CIDADE/O=NOME DA EMPRESA/OU=TI/CN=seudominio.tld"

Uma vez recebido seu e-mail com os arquivos de certificado você receberá os seguintes arquivos:

1. AddTrustExternalCARoot.crt
2. SSLRSAAddTrustCA.crt
3. SSLSADomainValidationSecureServerCA.crt
4. seudominio_tld.crt

Efetuando a instalação do certificado

Crie o bundle dos certificados  CA da seguinte maneria, copie o conteúdo dos arquivos acima 1,2,3 para o arquivo

/opt/zimbra/ssl/zimbra/commercial/commercial_ca.crt

dentro do seu Zimbra.

Copie o arquivoseudominio.tld.crt

para este mesmo diretório ficando da seguinte maneira

/opt/zimbra/ssl/zimbra/commercial/seudominio.tld.crt

Execute como #ROOT o seguinte comando para validar o certificado a ser instalado, lembre-se de estar dentro do diretório/opt/zimbra/ssl/zimbra/commercial

/opt/zimbra/bin/zmcertmgr verifycrt comm ./commercial.key ./seudominio.tld.crt ./commercial_ca.crt

Você deverá receber isto como saída do comando:

** Verifying ./mail_frtec.com.br.crt against ./commercial.key
** Certificate (./mail_frtec.com.br.crt) and private key (./commercial.key) match.
** Valid Certificate: ./mail_frtec.com.br.crt: OK

Uma vez testado, efetue a instalação do certificado da seguinte maneira:

/opt/zimbra/bin/zmcertmgr deploycrt comm ./mail_frtec.com.br.crt ./commercial_ca.crt

A saída do comando deverá ser similar a abaixo:
** Verifying ./mail_frtec.com.br.crt against /opt/zimbra/ssl/zimbra/commercial/commercial.key Certificate (./mail_frtec.com.br.crt) and private key (/opt/zimbra/ssl/zimbra/commercial/commercial.key) match. Valid Certificate: ./mail_frtec.com.br.crt: OK **
Copying ./mail_frtec.com.br.crt to /opt/zimbra/ssl/zimbra/commercial/commercial.crt **
Appending ca chain ./commercial_ca.crt to /opt/zimbra/ssl/zimbra/commercial/commercial.crt cp: `./commercial_ca.crt' and `/opt/zimbra/ssl/zimbra/commercial/commercial_ca.crt' are the same file ** Importing certificate /opt/zimbra/ssl/zimbra/commercial/commercial_ca.crt to CACERTS as zcs-user-commercial_ca...done. ** NOTE: mailboxd must be restarted in order to use the imported certificate. **
Saving server config key zimbraSSLCertificate...done. ** Saving server config key zimbraSSLPrivateKey...done. **
Installing mta certificate and key...done. **
Installing slapd certificate and key...done. **
Installing proxy certificate and key...done. **
Creating pkcs12 file /opt/zimbra/ssl/zimbra/jetty.pkcs12...done. **
Creating keystore file /opt/zimbra/mailboxd/etc/keystore...done. **
Installing CA to /opt/zimbra/conf/ca...done.

Para verificar o certificado instalado, utilize o comando:
/opt/zimbra/bin/zmcertmgr viewdeployedcrt

Endian Firewall Community 3.0.5-beta1 released

Endian Firewall Community 3.0.5-beta1 released Endian Firewall Community 3.0.5-beta1 has been released and is now available for download. This new minor release contains many improvements and closes more than 350 issues. The most prominent improvements in this new release are: "Network types" have been added to the network wizard and uplink editor to be able to distinguish between firewall setups in different network topologies. Support for transparent implementations through a new bridge mode has been added. With the new TPROXY support in the HTTP proxy it is now possible to create firewall rules, routing policies and other rules based on the source IP address even if the proxy is being used. The complete rewrite of the event management engine results in better performance when analyzing log files and sending notifications. The anti-virus engine has been updated. Many security vulnerabilities have been fixed. Hardware support has been improved.

Endian Firewall Community 3.0 BETA 2

Endian Firewall Community 3.0 BETA 2

Endian firewall: 1.363.525 downloads and counting - Be part of our growing community!

Hey folks, Endian is back again!Do you want to be part of this community?
Endian calls for the best and brightest users to enhance its community and make Endian Firewall improving and spreading all over the world. Together we can do more and better!

So join the crew, and become part of our extended team.How? Download the latest, Endian Firewall Community 3.0 Beta 2 version and start making your own tests. (Want to glance at the brand-new features, first? 

…And once I made them? How to share my findings?And here’s the next news of the day. You can easily report the outcome of your trials on Jira, our new bug tracker, finally open to the community!

If you did report some bugs relevant to the previous release on Mantis, don’t panic! It will remain open in read-only mode to everyone, including our developers and QA team.

For those who prefer a stable and tested version, the Endian team reminds that Endian Firewall Community 2.5.2 release dates back to just a few weeks ago.

For upgrades  from the Development Channel (bleeding edge): please note that after the upgrade you may need to re - configure some modules.

This release includes the following changes: Web Security HTTPS filtering E-mail Security SMTP Proxy: Domain Management SMTP Delivery Status Notification configuration Virtual Private Networking IPsec Encryption: Null, 3DES, CAST-128, AES 128/192/256-bit, Blowfish 128/192/256-bit, Twofish 128/192/256-bit, Serpent 128/192/256-bit, Camellia 128/192/256-bit Hash algorithms: MD5, SHA1, SHA2 256/384/512-bit, AESXCBC IKEv2 OpenVPN Support for TUN mode Connections page for VPN users User Management & Authentication User management for OpenVPN Integrated certificate authority External certificate authority support User password and certificate management (two-factor authentication) Logging and Reporting Live network traffic monitoring (powered by ntopng) System status graphs are not lost at every reboot Images for SMTP mail statistics graphs Miscellaneous fixing and improvements Serial port speed is now always set to 115200bps Fixed password changing from the console menu Sanitized logs