El conocimiento al alcance de todos.

thank to:  Exchange 2010 Owa Client Access issues login This is the code I ran on the 2008R2 server: Import-Module ServerManager then Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart

Thank to http://forevergeeks.com Stuff you need before installing the BES server. 1. Exchange 2010 needs to be up and running 2. Domain admin access rights 3. A Windows Server 2003 SP2 or Windows 2008 box already setup with at least a 100GB hard drive ( I know many people will say this much hard drive space would be a waste, but believe me those logs in the BES server get big really fast, especially when you have many users ) 4. A fast Internet connection to download the BES server software, and some Microsoft stuff. step 1. Setup the BESADMIN account in AD. the account does not need to be added to any admin groups. once the account is created in AD, add it to the local administrator group on the Windows 2003 or Windows 2008 server where you are planning to install the BES server on. Step 2. Setup the permissions on exchange. open the Exchange management shell in exchange 2010 and type these commands: * _Get-MailboxDatabase | Add-ADPermission -User "BESAdmin" -Acce

Thanks to http://www.vkernel.ro/blog Yes, you can have your own Certification Authority (CA), and issue certificates for clients. The bad news is that certificates issued by your internal CA are trusted only by you internal clients, or by clients that have your root certificate imported. For internal applications, sites etc this is gold, because you don’t have to by a commercial certificate, but if you have a public HTTPS site you will need a commercial certificate. Certification authorities can have multiple ramifications or levels, like Root CA, then a Subordinate CA, and the last one is the Issuing CA. Bellow I created a diagram for a better visualization. Root CA will issue certificates only for Subordinate CA, and the Subordinate CA will issue certificates only for Issuing CA. The Issuing CA is the one that will issue certificates for internal clients. You can, off course create more than three ramifications, but even those commercials Certification Authoriti

Thanks to Crypt.Gen.NZ   Introduction There are a number of good reasons for companies to deploy proxies for user access to the Internet. Amongst these are Monitoring of web sites and traffic volumes Restricting web access - by user, web sites, time of day, etc. Using caching to reduce traffic volumes Managing bandwidth There are also a number of challenges faced when implementing proxies. Probably the top one is the job of configuring all of the web browsers to use the proxy, and then comes the problem of what to do if the proxy fails. This article proesents a solution of web proxying which is transparent to the end-user - it requires no browser configuration. It is also resilient to failure, in that if the proxy server fails then web access continues to be provided without disruption. A Basic Network and Web proxy In the network drawing below I show a basic network with access to the Internet, this is a very common configuration for small business networks.

Tecnoloxía xa: Manual de clonezilla: creación de imágenes... : Como algunos ya sabréis, clonezilla es un programa que nos permite crear imágenes de nuestro disco duro, de modo que después podamos volca...