Friday, January 7, 2011

How to Solve Event 465 in Exchange Server?

An Exchange public store or mailbox store of a storage group can be mounted using Exchange Management Console or Exchange Management Shell. This makes the databases ready for use. For any reason, if the process fails, it leads to data inaccessibility. Database mount failure primarily suggests that one or more storage group components are faulty. However, if one or more databases are corrupted, you should use eseutil utility to repair it. Alternatively, you can apply the last good backup or use a powerful EDB Repair utility to repair the corrupted database.

For instance, suppose you try to mount public or mailbox store in Exchange Server. The operation fails and the application event log reports the below information message:

Event ID: 465
Source: Ese98
Type: Error
Computer: Server1
Information Store (2184) Corruption was detected during soft recovery in logfile C:\Programme\Exchsrvr\mdbdata\E00000E8.log. The failing checksum record is located at position 6531:471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable.
For more information, click http://search.support.microsoft.com/search/?adv=1.

Error 465 is usually accompanied with error 477 that informs checksum mismatch and suggests you to restore the logfile from backup.

Cause

The prime cause of error 465 to occur is transaction log file corruption, specifically Edb00000E8.log file.

Solution

You should remove the corrupted log file to achieve recovery. To do so, you must first find out the storage group, which is affected from this corruption and then follow these steps:

  1. Dismount all the databases of affected storage group and perform its offline backup.

  2. Run eseutil /mh tool to make sure if the databases exist in consistent state.

  3. If all the databases report 'Clean Shutdown' state, move out all the log files from Exchsrvr\Mdbdata folder.

  4. But if databases exist in 'Dirty Shutdown' state, perform soft database recovery using eseutil /r

  5. On unsuccessful attempt of soft recovery, you can restore the database from last Exchange backup

  6. In cases when no valid backup is available, you can try repairing the database using eseutil /p, which performs hard repair.

  7. The hard repair of Exchange database causes corrupted pages to delete. Thus, it is suggested to use a third-party EDB Repair Tool for more effective and safe database repair. EDB Repair software employ advanced scanning algorithms and provide you easy-to-implement user interface.

Stellar Phoenix Mailbox Exchange Recovery is a full-featured tool to perform systematic repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It is a safe EDB Repair Tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

Read more: http://www.articlesbase.com/data-recovery-articles/how-to-solve-event-465-in-exchange-server-1391633.html#ixzz1ALSaDh8p
Under Creative Commons License: Attribution

Continue Reading »

Exchange Server 2007 File Structure

Exchange Server 2007 File Structure

Exchange Database Files:-

  • E00.chk checkpoint file marks up to where database has been committed to the database files
  • E00.log –the current log file with transactions waiting to be processed.
  • E00res00001.jrs
  • E00res00002.jrs
  • E00000000A.log
  • Mailbox Database.edb. EDB file is the one which stores all mailbox database information. The size of this file increases significantly since it stores rich text and attachement. .STM files are no longer in use.
  • tmp.edb
  • Enn000000000x.log logs that have already been processed (Max log file size is 1 MB, also maximum number of log files has been raised from 1 million to 2 billion)

http://www.techpeoples.net/

The other files are in the locations C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue are specified below:

  • Trn.chk - The checkpoint file.
  • Trn.log - The current transaction log file.
  • Trntmp.log - The next provisioned transaction log file that is created in advance.
  • Trnnnn.log - Other transaction log files that are created when Trn.log reaches its maximum size.
  • Trnres00001.jrs - The Reserve log file.
  • Trnres00002.jrs - The Second Reserve log file.
  • Temp.edb – Temp DB used to verify database schema on start-up.

http://www.techpeoples.net/

Requirements of Installing Exchange Server 2007 on Windows Server 2003

Follow below steps to install Exchange Server 2007 on Windows Server 2003

1.       Administrative rights

2.       Window 2003 service pack 1 or later

3.       Install MMC.

4.       Install Net Framework2.0

5.       Power Shell (exchange command based tool….new feature)

6.       Install .Net Framework Update (74469)

7.       IIS

8.       Active Directory (Functional level-Native Mode)

9.       Run Exchange Setup

10.   Install Exchange Server Service Pack

Read more: http://www.articlesbase.com/online-education-articles/exchange-server-2007-file-structure-2300119.html#ixzz1ALRCYOKD
Under Creative Commons License: Attribution

Continue Reading »

Getting Started With Exchange 2010

As most know Exchange 2010 is the latest version of Microsoft's email server.  I wanted to write a short description of the software and outline its features. 

Like its predecessor Exchange 2010 requires that you run it on an x64 platform.  32-bit processing is surely but slowly becoming a thing of the past.  In 2010 however you must also be running Windows 2008 SP2 or 2008 R2.  One of the major decisions you'll have to make is whether to select the standard or enterprise edition.  This basically boils down to how many stores you need.  Standard supports 5 stores per server as to where Enterprise you can do 50+.   As far as the client side CAL's are concerned you must purchase the 2008 enterprise CAL's if you wish to do unified messaging.  There is not however a limitation in the software.  It is simply a licensing issue.  Which means you'll still have the ability to access unified messaging but it will not be licensed correctly.   Another feature Microsoft has decided to keep is the JET EDB database.  It has been rumored in the past that Microsoft would start using SQL server to house the Exchange database.  This is not the case. 

If you ever worked with recovery storage groups in Exchange 2003 or 2007 you will no longer find those in 2010.  As well you will not be able to find routing groups.  All of the Exchange 2010's routing is done through active directory sites and services.  So you must make sure that you have properly configured your sites before moving forward with Exchange.  It is essential to Exchange 2010 functioning properly.  As with Exchange 2007 Microsoft still is trying to deemphasize public folders.  Their goal is to eventually replace these with their Sharepoint product. 

Another major feature of Exchange 2007 and 2010 is their ability to reject email at the gateway.  The Edge transport server allows you to configure ADAM and active directory lightweight services to query AD.  This allows you to get a list of valid email address and push them out to the border of your network.  If the edge server detects that someone is trying to send email to the inside of your organization and the user does not exist it is dropped immediately.  This saves on memory and processing power internally so that you don't have to deal with spam. 

Additionally with Exchange 2007 and 2010 you get the ability to create UNC direct file access paths.  This way in OWA when a user needs a file on a network share they can grab it without needing a cumbersome VPN client.  Outlook anywhere also remains widely the same in 2007 and 2010.  It basically encapsulates your RPC packets into https packets.  This allows you to traverse your firewall without opening any additional ports.  Therefore giving users access to their email from Outlook wherever they may travel. 

One of the greatest new features of Exchange 2010 in my opinion is database availability groups or DAG.  This is essentially the same thing as CCR in Exchange 2007.  Anyone who has tried to configure CCR, LCR, or SCR in Exchange 2007 knows that it can be quite the process.  Microsoft simplified this with DAG's in 2010.  It allows you to keep 16 copies of a users mailbox for redundancy and disaster recovery.  It does this through a process called log shipping.  Where 1MB files are created and then played into the database.  This allows you to keep a backup of your server at another physical location for disaster recovery or have two Exchange servers running next to each other.

Another nice feature in 2010 is the fact that the client access server or CAS redirects your client to their database server that houses their mailbox.  You no longer need to specify the location of your server in Outlook.  The CAS parses AD and redirects them automatically.  Therefore there is no hard coding.  This makes the transition for failover a lot easier. 

As most of you know who have used Exchange 2007 the GUI is simply a front end to Microsofts command line utility called EMS or Exchange Mangement Shell.  Anything you do in the GUI is converted to a command and executed against your server.  I would personally say you have about 90% functionality in the GUI as opposed to EMS.  However, EMS definitely makes the process a lot easier if you need to apply a setting to multiple objects at the same time. 

As with Exchange 2007 you still have the same five roles edge transport, hub transport, client access server, mailbox, and unified messaging.  Inside of these five roles only the edge transport server must be installed separately from the rest of the servers.  Everything else can be ran on one box.  Although this is not recommend for performance reasons.  The reason why the edge server is standalone is it was meant to sit in your DMZ or on the border of your network.  Absorbing the hits so your internal servers are not affected.  It has features such as safelist aggregation where Outlook client rules are brough outside to it so that it can apply those rules before the message ever enters your internal network. 

The hub server still is the same as Exchange 2007 it routes your messages internally and holds compliancy rules.  You can also run a command against it to install antispam featureset.  This way if you don't have an edge transport server you can use it to receive outside mail directly.  Although this is not recommended by Microsoft.

The CAS server or client access server is meant to interface with your internal and external clients.  As stated before it automatically redirects your Outlook clients so that you don't need to hardcode their mailbox server.  It also accepts connections from smart phones, OWA, etc.  It is basically your clients interface to your Exchange infrastructure.

If you wish to monitor your Exchange 2010 infrastructure Microsoft has made a plugin for their SCOM or system center operations manager.  This is Microsoft's MOM replacement that allows you to montior your servers.

In Exchange 2010 you will no longer see SCR, LCR, or CCR.  They have been superceded by DAG or database availability groups.  This makes configuring database replication a lot smoother.  DAG's also allow for your data to reside across multiple servers.  You can also have multiple DAG's.   This is a great feature because if half of your users are in one DAG group and it goes down the other half are not even affected.  Other benefits are reduced restore time since you're not restoring all of your users' data only the ones in that DAG.  You can also have separate exchange policies for different DAG's.  So if your management is in one and your regular users are in another you can change the rules that apply to them.  This is a great way to mitigate risk by distributing your load. 

As far as the enterprise and standard software go they are both installed from the same media.  It is just different license keys that you input that determine what version you are installing.  It is also upgradable.  You can go from trial to standard to enterprise.  However, you cannot downgrade backwards from enterprise to standard or standard to trial. 

In order to install Exchange 2010 your domain and forest functional level must be at 2003.  Also each site which contains Exchange 2010 must also contain a 2003SP2 domain controller or 2008 domain controller.  We recommend you have your domain running 2008R2 domain controllers however. 

Exchange still uses EAS or exchange active sync for mobile devices.  This way your contacts, calendar, email, etc. are all tightly integrated with your Windows mobile devices.

One common misconception that people have is Exchange enterprise must be installed on server enterprise software.  Or that server enterprise software cannot have Exchange standard installed on it.  Both of these are fallacies. 

When you begin your Exchange installation you should give serious consideration to how you configure your arrays.  Exchange is a very read/write intensive application.  Therefore you should separate your OS, log files, and database all on separate arrays.  If this is not possible it is then recommended that you at least put yoru OS and log files on one array and your database files on another.  The reason for this is simple.  The log files are write intensive and the database files are read intensive.  Separate these two out can speed up your disk I/O.

Memory requirements in Exchange 2010 have pretty much gone unchanged.  Start your server with 2GB of memory and then 5MB for every mailbox user.  I would also personally recommend to have a minimum of 4GB.  Memory is cheap enough these days that the benefit of having more of it outway the cost.

Although the databases in Exchange can grow very large we do not recommend that you go over 100GB.  This can become cumbersome to work with and decrease performance on your server.

If you wish to remotely manage your Exchange server you can install the management tools.  They will install on Vista SP2 and higher or server 2008 SP2 or higher.  This way you do not have to remotely login to your Exchange server to make all of your changes.

As far as your site layout goes you should also plan on having a global catalog server in every location that contains a mailbox server.  This is recommended by Microsoft and will reduce WAN traffic. 

Exchange has also setup a new permissions setup which they refer to as RBAC or role based access control.  From this you get 5 roles to manage your exchange infrastructure.  They are Organization management, view only organization management, recipient management, records management, and GAL synchronization management.

Another thing you should consider before installing Exchange 2010 is to make sure your domain is setup properly.  You can use tools such as NETDIAG and DCDIAG to verify this.  In order to install Exchange 2010 you're going to need to be a member of domain admins, enterprise admins, and schema admins.  You will also want to add connect.microsoft.com and download.microsoft.com to your trusted sites list in IE.  Other pieces of software that must be installed are .NET 3.5, Windows remote management 2.0, powershell v2, 2007 office converter microsoft filter packs.  If you are installing the mailbox role you must also have AD services remote management tools.

Before starting the install you must prepare your schema by running setup /ps if it fails delete the contents of c:\windows\temp, copy the files from your CD to yoru hard drive and rerun setup /ps.  You must then run setup /prepareAD /OrganizationName:MyCompany where "MyCompany" can be replaced by your organization name.

You must then prepare the prerequisites by running the following commands.

  • ServerManagerCMD -install RSAT-ADDS
  • ServerManagerCMD -install Web-Server
  • ServerManagerCMD -install Web-ISAPI-Ext
  • ServerManagerCMD -install Web-Metabase
  • ServerManagerCMD -install Web-Lgcy-Mgmt-Console
  • ServerManagerCMD -install Web-Basic-Auth
  • ServerManagerCMD -install Web-Digest-Auth
  • ServerManagerCMD -install Web-Windows-Auth
  • ServerManagerCMD -install Web-Dyn-Compression
  • ServerManagerCMD -install Net-http-Activation
  • ServerManagerCMD -install RPC-over-http-Proxy

    Once this is complete reboot your server.  You are now ready to run Setup.com /mode:install /roles:H,C,M the H,C,M install hub cas and mailbox roles.

    Once your install is complete run the Exchange BPA or best practice analyzer.

    In order to install the Edge server you'll want to make sure you're running 2008 standard with SP2.  You'll need .NET 3.5, remote management 2.0, powershell v2, AD LDS (can be installed via servermanagerCMD -i ADLDS).  For the edge server to work in a DMZ you'll need to open ports 50389-50636.  Then run new-EdgeSubscription -filename "c:\temp\EdgeSubscriptionInfo.xml"  Copy that generated file to your hub server you can import it in the GUI and run start-edgeSubscription from EMS.  You can test this once it is imported to verify it is working properly by using test-EdgeSubscription from EMS.

    I would personally recommend using a RBL provider to stop spam from entering your organization.  One example of this is SpamHaus.  This queries the connecting server to a black list of IP's and blocks communcation if it is found on the list.  This one feature can drastically cut down on spam.

    Another item you have to address is purchasing a SAN certificate for your Exchange server.  Exchange has moved to a secure by default mentality.  You will find connecting to OWA or using activesync become very painful if you try to issue your own SSL certificates.

    Another security improvement in Exchange 2007 and 2010 is that all intracommunication is secure and encrypted.  TLS is used for all server to server communication internally.  RPC is used for your Outlook clients to communicate with your servers.  SSL is configured for all external client communication including, OWA, activesync, etc.

    Opportunistic TLS is a new feature where your Exchange server will no long try to send via SMTP by default.  It will first send a STARTTLS command to use TLS to encrypt external SMTP communication with other servers.  If the other server however does not support this it will revert to unsecure communications.

    Still included in Exchange 2010 is the ability to use a journaling mailbox to track all of your emails.  This is required by some organizations.  Keep in mind that this feature can increase your processor and memory usage by 25%.  So you should make sure your server has plenty of resources before turning on this feature. 

    One of the requirements as previously stated is that Exchange 2010 must be running active directory 2003.  Even though 2008 is recommended if you are running Cisco Unified Messaging 4.2(1) or lower it is NOT compatible with active directory 2008. 

    When you upgrade your active directory infrastructure it is recommended that you create a virtual machine using Microsoft Hyper-v or Vmware.  Make the virtual machine an additional domain controller and make it a global catalog.  This way if your upgrade takes  turn for the worst you have data that is intact if you have to downgrade.  Do not forget to unplug it from the network before doing the upgrade.  If you need to revert back you can use NTDSUTIL to seize the roles.

    If for whatever reason you need to create a scratch installation of a domain you can always use the ADMT utility to move users, groups, computers, service accounts, and trusts.

    To migrate from 2003 Exchange to 2010 the overview is as follows.  First you must be running Exchange 2003 with service pack 2.  Your active directory domain and forest functional levels must be 2003 and at least one global catalog has to be 2003 server with SP2.  Instal AD LDIFDE tools on 2008 to upgrade your schema.  Upgrade your Exchange Schema.  Transfer OWA, activesync, and Outlook anywhere to the CAS server.  Install/upgrade hub server.  Transfer the mail flow to the hub transport server.  Install mailbox servers and DAG if required.  Move your public folder replicas using pfmigrat.wsf or PFRecursive.PS1.  Move your mailboxes.  Rehome OAB.  Rehome public folder heirarchy.  Transfer public folder replicas.  Delete 2003 public and private stores.  Delete routing group connectors.  Delete RUS using ADSIEdit.  Uninstall Exchange 2003.

    To migrate from 2007 Exchange to 2010 the process is a little less.  Make sure your Exchange 2007 server is running SP2.  Make sure your domain and forest is at 2003 functional level.  Global catalog server is at 2003 SP2.  Use AD LDIFDE tools to upgrade your schema.  Prepare schema.  CAS server.  Transfer OWA.  Install hub transport.  Transfer mail to hub transport.  Use AddReplicatoPFRecursive.Ps1 to move your public folder replications.  Move your mailboxes.  Rehome OAB.  Transfer public folder replica.  Delete public and private stores.  Uninstall Exchange 2007.

    With Exchange 2010 or 2007 you want to make your co-existance time as small as possible.  The longer you intermingle different versions the more problems you are asking for.

    If you are running Exchange 5.5 unfortunately there is no direct upgrade at this point.  You must first upgrade to Exchange 2003 SP2 then to 2010.  As far as Lotus Notes, Novell Groupwise, or Senmail goes the recommend path is to install a clean environment and then work on importing your data using tools.  There is no upgrade path.

    Database Availability Groups or DAG's are a very important new feature of Exchange 2010.  It gives you the ability to maintain 16 copies of users' mailboxes.  You can also set different databases to failover to different servers and specify in what priority.  The requirements for DAG are Windows Server 2008 enterprise, two nics in your mailboxes servers, Exchange 2010 Enterprise, a file share witness.  We recommend you put this on your hub transport server.  But technically it can be on any file server.  It is very easy to setup as you create a share and then Exchange manages and handles the permissions.

    Steps to create a DAG, Add members, and verify the DAG

    New-DatabaseAvailabilityGroup -Name ExchangeDAG -WitnessServer ExchangeHT -WitnessDirectory “c:\FSW” -DatabaseAvailabilityGroupIPAddresses 172.16.4.5 –Verbose

    Add-DatabaseAvailabilityGroupServer -Identity ExchangeDAG -MailboxServer ExchangeMB -Verbose

    Add-DatabaseAvailabilityGroupServer -Identity ExchangeDAG -MailboxServer ExchangeMB2 -Verbose

    Get-DatabaseAvailabilityGroup -Identity ExchangeDAG -Status

    To see your network settings run

    Get-DatabaseAvailabilityGroupNetwork -identity ExchangeDAG

    We can then add database copies by doing the following

    Add-MailboxDatabaseCopy -Identity ExchangeMB -MailboxServer ExchangeMB2

    Then check the status

    Get-MailboxDatabaseCopyStatus

    To test the health

    Test-ReplicationHealth

    Read more: http://www.articlesbase.com/information-technology-articles/getting-started-with-exchange-2010-1826490.html#ixzz1ALPAHg75
    Under Creative Commons License: Attribution

  • Continue Reading »

    Using Powershell in Windows 7

    For years people that have come from a Unix background have complained about the lack of command line tools that the Windows line of operating systems just did not supply.

    The most recent line of Windows operating systems has a virtual dos based command line but it in no way had the large amount of features that something like the Bash command line had over in Linux.

    Several years ago Microsoft introduced the Powershell command line system to windows. It's purpose was to bring a powerful command line editor similar to what people had over in the Unix family.

    The only thing that was different is that you had to download Powershell separately from the actual operating system. Now with the release of Windows 7, Powershell comes with the operating system ready for action.

    Powershell is not a feature that is meant for most of the Windows user out there. Most people like the graphical interfaces that Windows provides and would hate to be forced to do anything by command line like you are sometimes forced to do in Linux.

    Powershell was not created with that in mind. It was created so that people that were use to working in Linux and other Unix based operating systems felt more comfortable about making the switch over to windows.

    To turn on Powershell in Windows 7 you first have to click on the Start button, then hit All programs.

    After that click on accessories and scroll down until you see the Windows PowerShell folder.

    Click on that and you will see a blue screen pop up waiting for a command to be typed in.

    People who are not used to using a powerful command line tool might be thinking that this no different than using the old version of command line. They are wrong, for one thing you have a feature called pipe lining that is available now. This is a feature that allows you to take the output of one program and input into another program.

    For an example, if you were typing text into notepad and wanted to email it, all you would have to do is type one command into powershell, which would send the text to the email program and the action would be done. Pipelining is a powerful feature once you get used to using it.

    Powershell also comes with a powerful scripting language that is not only object orientated but also is considered a first class citizen of the .Net family. This will allow you to create shell scripts like you can in Unix. The difference is that the scripts will be able to reach out to the .Net framework and make a ton of features easier to access. When you script something in powershell it is called making a cmdlet.

    There is so much that you can do with with the scripting language that we will not be able to cover it all here.

    Another feature that was made particularly for the people that are coming from a unix background is the ability to give Powershell commands aliases. This means that if a command has one name, you can force that same command to be called by another name. For example in windows usually if you want to see the contents of a directory in the command line you would call the "dir" command.

    If you are coming from a Linux background then you would type that same command as "ls". Now instead of getting used to the windows version, they have already created an alias for you where "ls" will do the expected behavior that someone from a linux background would expect. You can also make your own custom aliases as well.

    I hope that we have giving you a good ideal why the Windows Powershell in Windows 7 is such a good thing. even if you are not coming from a Unix/Linux background learning the powershell can make your computing experience a lot easier.

    Read more: http://www.articlesbase.com/operating-systems-articles/using-powershell-in-windows-7-1692410.html#ixzz1ALLejhVy
    Under Creative Commons License: Attribution

    Continue Reading »

    Some tricks for apache security

    Passwords
    I presume you know that having a password like 'Mom' or 'girlfriend' is not a good start for securing your system. I usually prefer passwords with both numerican and alphatbetical characters, plus some extra symbols. This is a good password: ILik3-PeN_gu1nS. Passwords should be complicated as there are a lot of ways someone can get your encrypted password. When we are talking about Linux systems with a webserver, the first thing that comes to my mind are all those numerous buggy CGI scripts that make you get /etc/passwd file from the attacked system. When that is done, a copy of Crack or John The Ripper can be used for cracking the password. Always remember: a good password is harder to crack. If you use some basic word for a password, a good wordlist will make the cracker software spit your en-encrypted password on the screen in no-time.

    File transfer and remote logins

    Think what software packages should run on your system, and remove the ones that you don't need. If you are thinking about transfering files from and to your system shut the FTPd down. There is far more secure way that does the same - SCP. By quickly checking the man pages for SCP, we get: "scp copies files between hosts on a network. It uses ssh for data transfer, and uses the same authentication and provides the same security as ssh. Unlike rcp, scp will ask for passwords or passphrases if they are needed for authentication."
    SCP clients don't have that much good looking GUI frontends, but you can do it all from the shell by using the syntax:
    scp Localfile Username@RemoteServer:RemoteFolder
    I hope you don't use the Telnet Deamon which usually sits on the port 23. If you do, remove it as SSH is a far better way of remotely doing a login into your system. The big difference between telnet and SSH, is that SSH provides significantly enhanced security for your login situations.It provides an encrypted communications path between two untrusted hosts over a potentially insecure network and thus prevents user's passwords and other sensitive data from being transmitted across the network in clear-text form.

    Checking the integrity
    While you can use Tripwire or any other similiar solution for checking the integrity of files that reside on your system, there is another way of doing this. To tell you the truth, it is not as powerful, but it is usable. Let's consider this seven liner:
    ----------------cut-here-------------------
    #!/bin/bash
    for rpmlist in `rpm -qa | sort`
    do
    echo " __ $rpmlist __"
    rpm -V $rpmlist
    done > /tmp/123.out
    cat /tmp/123.out | mail -s "RPM Check `date +%T %A %d.%m.%Y`" admin@yoursystem.net
    ----------------cut-here-------------------
    This shell script basically makes a list of RPM files on your system, sorts them in an easily viewable format and verifies them to see what has changed. After that it mails the whole list to the administrative mailbox. Everything can of course be re-configured to suite your needs the best.

    Also it would be suitable to add this script in CRON, so you can receive a daily snapshot of the RPM's on your system. In this exaple is starts every day at 10 am.

    [admin@pilatus]# crontab -l
    # DO NOT EDIT THIS FILE - edit the master and reinstall.
    # (/tmp/crontab.1759 installed on Tue Apr 16 16:06:48 2002)
    00 10 * * * /usr/local/etc/rpmcheck.sh

    Checking the logs
    Usually you should periodically check the logs on your system. All the vital things about the current status of your system can be seen from the logs. While manually checking all the files takes some time, and time is precious, there are a few tools that help you automate the process of checking your system logs.
    I like to use LogSentry, a freeware product by Psionic Technologies.
    As can be seen from the product description: "LogSentry automatically monitors your system logs and mails security violations to you on a periodic basis. It is based on a program that ships with the TIS Gauntlet firewall but has been improved upon in many ways to make it work nicely for normal system auditing."

    Read more: http://www.articlesbase.com/security-articles/some-tricks-for-apache-security-2330631.html#ixzz1ALL2BW96
    Under Creative Commons License: Attribution

    Continue Reading »

    Thursday, January 6, 2011

    Linux on USB 3.0?

    By 2009, boasted a few specialty sites that Linux is the first new operating system compatible with USB 3.0 ports on computer. Back then I thought wow, that gonna be crazy with this USB 3.0. Indeed it could be, if I think I just told the transfer rate could reach 5.0 Gbps specifications.

    Instead windows at that time said that USB 3.0 will be supported by Windows 7, but only after the appearance of service pack1. And so it happened.

    Meanwhile began to produce disks with USB 3.0 devices, newer device's USB 3.0 only and therefore you grab them or to install on these computers. Because I didn linuxuri Stress plus installing from a time when I started I did not hate bootloaderele more complicated to put my linux computer as a parallel operating system and possibly better than Windows. I am pleased that last. Today instead I wanted to put my linux computer. How did this computer has only USB 3.0, so 2.0 pazua old technology I said to try, can the world smarter, doing a live CD, USB stick on which to install Linux.
    The guys have created tools to pendrive formatted USB sticks for any Linux distribution and therefore we have taken in hand. None refused to install on USB stick because it's 3.0. Start bootloader has different options, but when you install or kernel panic, or drive not found. So is there any idea that you install Linux on a USB stick using a USB 3.0 chipset only?

    You realize that I do not want to look for a CD and give it write or install of windows? Exclusive USB stick.

    Continue Reading »