Administration Videos
newest 100 administration videos / administration widgets / media rss:

Credit Union, Wescom announced plans to cut 80 jobs and will close 11 of their 55 branches. One of the eleven branches includes the Wescom located in Pasadena, California, where the National Credit Administration is keeping a close eye on the branch. Spokesman, John Mckechnie III said that the NCUA is concerned “with some things in Wescom’s mid year numbers. According to the California Department of Financial Institutions and statements from Wescom, its’ Pasadena office is the sixth largest credit union in the state and with 44 branches left… hold $3.69 billion dollars in assets. Workers should not fear for their money because just like banks, credit unions are also insured up to $100,000 by the NCUA.

Join Errington for the latest in national politics and sports! Topics include Russia-Georgia conflict and the response of the US what is going on? Isaac Hayes, and more! This week, I decide that I would like to review the famous August 6th Presidential Daily Brief and the Downing Street Memo. I invite 2 great guests to discuss these important papers Greg Mitchell from Editor and Publisher and Faiz Shakir at thinkprogress.org. Also, note how I freeze when Faiz gives me a compliment. I m not use to that. Great show. Enjoy!

Just wanted to drop a quick note that we have now released a version of Exchange 2003 Exchange System Manager (ESM) that runs on Windows Vista. this has been a frequent request so - now it is here! You can download the package and related release notes here: http://www.microsoft.com/downloads/details.aspx?familyid=3403d74e-8942-421b-8738-b3664559e46f&displaylang=en - Nino Bilic Share this post :

Former US Under Secretary of State for Arms Control John Bolton talks about the Bush administration's stance on North Korea and Iran and how he's still waiting for evidence of Saddam's WMDs to come to light. Author: AlJazeeraEnglish Keywords: Inside USA John Bolton Bush administration North Korea Iran Iraq WMD Added: August 16, 2008

Former US Under Secretary of State for Arms Control John Bolton talks about the Bush administration's stance on North Korea and Iran and how he's still waiting for evidence of Saddam's WMDs to come to light. Author: AlJazeeraEnglish Keywords: Inside USA John Bolton Bush administration North Korea Iran Iraq WMD Added: August 16, 2008

This August 2008, Microsoft has released an update to the Outlook Time Zone Update Tool. This new version (Version 3.0) offers, amongst others, better support for Israel and Brazil with regards to time zone handling and rebasing of calendars. The Exchange Calendar Update Configuration Tool utilizes the Time Zone Data Update Tool for Microsoft Office Outlook for rebasing operations, which is why version 2.0 of the Exchange Calendar Update Configuration Tool included the Time Zone Data Update Tool for Microsoft Office Outlook, in a redistributable format, as part of the package. A new version of the Exchange Calendar Update Configuration Tool was not released along with the release wave of DST updates in Aug 2008, but instead the redistributable version of the Time Zone Data Update Tool for Microsoft Office Outlook V3.0 was made available for download. The OutlookTimeZoneMoveLibRedist.exe is a redistributable installer that installs the assembly file Tzmovelib.dll in C:Program FilesMsExTmz. Third-party calendar rebasing tools can use the assembly file to programmatically update calendars that are displayed incorrectly because of daylight saving time. With this assembly, developers can use the same APIs that Outlook and Exchange Server use in their calendar rebasing tools. The below steps will allow you to utilize the added support in the Time Zone Data Update Tool for Microsoft Office Outlook V3.0, from the Exchange Calendar Update Configuration Tool V2.0: Install the Exchange Calendar Update Configuration Tool from here: http://support.microsoft.com/kb/941018 Go to the control panel, and using Add/Remove programs (found in Programs and Features in Windows Vista) and remove the Time Zone Data Update Engine for Microsoft Office Outlook. Install the Time Zone Data Update Tool for Microsoft Office Outlook V3.0 - redist package http://www.microsoft.com/downloads/details.aspx?FamilyID=ee0af8fd-bbb7-44de-be4d-f33cb1b59563&DisplayLang=en - This download contains the following file: OutlookTimeZoneMoveLibRedist.exe Rebase as appropriate Links: Exchange Calendar Update Configuration Tool: http://support.microsoft.com/kb/941018 Outlook Time Zone Update Tool V3.0 - redist package Outlook tool: http://www.microsoft.com/downloads/details.aspx?FamilyID=ee0af8fd-bbb7-44de-be4d-f33cb1b59563&DisplayLang=en Time Zone Data Update Tool for Microsoft Office Outlook: http://support.microsoft.com/kb/931667/ - The Exchange Team Share this post :

The NEW 2008 version of SEPTEMBER CLUES Hi-def: http://www.thesocialservice.it/ The 9/11 tragedy was all about hijackings. The TV airwaves were hijacked in order to insert false images into everyone's television set. The very same handlers of this monstrous hoax then hijacked the core of the 9/11truth movement and to this day have spent a fortune pushing half-truths, confusion and cheap divide-and-conquer tactics. Conspiracy films à la Michael Moore were no threat to the 9/11goons - so long as the 9/11 TV broadcasts remained unquestioned. We now know that the #1role of the mainstream media is to mould the news to suit the powers that be. This is a global truth, not confined to the USA. We all have the power to switch that box OFF. If you just can't do it - for any reason - train your brain to stay ON as you watch the Television News. TV is the weapon of mass distraction ; it's high time for all to expose it for what it is. I have a dream : 500 MILLION TV SETS TURNED OFF ON SEPT 10,11,12 - 2008. Anyone on board? I wish you all a happy viewing of September Clues - the 'happy' word meant in this sense : we--the-small-people should be glad and proud to have uncovered the 9/11hoax (thanks to many sharp researchers -- you know who you are) in a relatively short time span. Short indeed : State-sponsored terror and false-flag operations have a history of being exposed (if ever) only after decades, by which time they have slipped into oblivion. This is NOT the case with 9/11 : most folks who planned it are still ALIVE. Yet scores of innocents on both sides keep DYING in war zones born out of the 9/11 lie. This has to stop. SEPTEMBER CLUES is dedicated to all of the victims of 9/11. I dearly wish that families who lost loved ones would bring these findings to light with the comfort that they now - at last - have court-admissible evidence to identify and indict the culprits. Let's face it.: No one believes in "Al-Quaeda" anymore. The "War on Terror" will become folklore material to our sons and daughters ; our generation will go down in history as a foolish lot if we fail to expose this transparent scam. And now relax and rejoice : it's game over for the great hijack. The most common reaction people have after watching September Clues : " How could such an undoubtedly well-funded operation be handled with such staggering ineptitude ? " Let me suggest two responses to this question : 1 : We all fell for this hoax for many years, didn't we ? 2 . Have you ever heard of 'the perfect crime' ? Well, I have not. from simonshack Author: AnonymousCommentator Keywords: 9/11 911 WTC lies propaganda nwo new world order illuminati hologram fake war on terror free masons wwIII CFR Skull Bones Bilderberg hoax scam exposed money banks prior knowledge Patriot Act Victory boeing american airlines no plane missile bombs detonations TV fakery smoke WTC7 explosion controlled demolition Giuliani Bush Cheney administration media news mind control brain perceptions Added: August 14, 2008

Author: YoungTurksShow Added: Tue, 12 Aug 2008 13:54:12 -0800 Duration: 263Watch more at http://www.theyoungturks.com

NASA EDGE features the Last Mission to Hubble with an Inside and Outside Hubble Quiz, an interview with a Hubble Engineer and insight from the STS-125 Crew.

We have always recommended that customers prepare formal server build documentation for their Exchange environments. Until now, we've not provided any formal guidance around what that documentation should look like. We now have build documentation templates and instructions for preparing a build automation DVD. You can use these templates as a starting point for formally documenting your Exchange server builds. Preparing a build automation DVD can help streamline the installation of Exchange 2007 on both Windows Server 2003 and Windows Server 2008. The templates and build automation guidance can be found here: http://technet.microsoft.com/en-us/library/cc533547(EXCHG.80).aspx. Thanks to Ross Smith IV, with Exchange Center of Excellence, for his extensive help with this release. Thanks,Tom Di Nardo Share this post :

Author: YoungTurksShow Added: Thu, 07 Aug 2008 00:34:20 -0800 Duration: 324Watch more at http://www.theyoungturks.com

Lately, we've been getting a lot of questions related to Exchange 2007 memory consumption and why Exchange uses so much of the paging file. Well, there are some valid reasons why and some misconceptions that need to be corrected. Comparing memory usage between Exchange 2007 and Exchange 2003First, let's start with why Store.exe uses so much RAM. If we take a step back in time to the Exchange 2003 era, this blog was quite active on how to tune memory on an Exchange 2003 server. I am not going to go in to specifics or great detail, but one thing to call out is that on the 32-bit architecture, we were limited to addressing 4GB of virtual memory on any given server. So essentially, any 32bit program could address up to 4GB of virtual memory. This address space is typically split so that applications could address 2GB of memory and 2GB would be for the Windows Executive. By adding the /3GB switch in the boot.ini, applications could now access up to a 3GB virtual address space and lower the Executive down to addressing only 1GB, essentially halving the memory that is can be addressed or is available for kernel drivers, paged/non-paged pool memory, PTE's etc. The larger the load that you put on a server has the potential to exhaust important resources on the server which eventually causes a failure or server outages. Any type of memory leak in these areas could be detrimental to the stability of the server. With the numerous posts on this blog regarding the /3GB, /USERVA and /PAE switches, what drivers to update, how to tweak memory to allow Exchange to run optimally, etc., it was always a juggling act to try to keep Exchange servers online. Cluster servers were especially touchy as http.sys will start rejecting HTTP connections when non-paged pool hit a certain level, thus causing cluster failovers. Due to these constraints of the 32-bit architecture, we needed a way to balance I/O based applications on the server. Essentially, there are two types of I/O for the Windows operating system, Buffered and Unbuffered I/O. For Buffered I/O, only portions of the working set can be contained in memory; those portions not in use are retained in the page file. For Unbuffered I/O, the entire working set can be contained in memory. On any given system, we needed to maintain a balance so that each would get the right resources that they need. This is one of the main reasons why we needed to put a maximum on the ESE database cache to leave us enough room for the system cache.In most implementations, the default of 900MB of database cache was used which was sufficient for most deployments, but some implementations had the need for more cache increasing it to a maximum of 1.2GB of memory on systems of 2GB or more of physical RAM. This maintained the balance that was necessary so that the system cache could perform efficiently.So you may ask, why did I go through all of the above to explain how Exchange 2003 worked? Well, one of the aspects of Exchange 2007 that people ask about is the difference between Exchange 2007 memory usage to Exchange 2003. Indeed, the memory usage is much higher,and there are very good reasons for this. Let me explain further.Exchange 2007 Design ConsiderationsDuring the design phase of Exchange 2007, we needed to find a way to scale out servers further than Exchange 2003 did due to the rising demands of email usage in companies. For many companies, email is their life line and if an exchange server should go down, they could be losing money at an astronomical rate. One of the performance bottlenecks in Exchange 2003 was disk latencies which was mostly due to the memory constraints of the 32-bit platform. Ultimately, -, we had to read more from disk than what was available in memory. This required a well performing disk subsystem to handle the sustained I/O necessary to respond to client requests in a timely manner. In many cases where disks were the underlying problem, a re-design of the disk subsystem was necessary to allow the current amount of IOPS that were being generated on the server to be handled by the disks. This could range from adding more spindles to the disk arrays, rebuilding different RAID solutions to provide enough sustained throughput based on current user load.Why we learned to love the 64-bit PlatformWith the 64-bit architecture being available, we made a conscious decision that Exchange 2007 would only be supported in production on 64-bit hardware. This was mainly done to overcome the limitations that the 32bit platform had. The design goal here was to reduce cost of Exchange deployments in which storage turned out to be the number one driver of cost and support overhead. By moving to the 64-bit platform, we are able to reduce our I/O requirements thus bringing us back to easier balancing of I/O and capacity requirements. Now, one of the results of being able to address more memory is the capability to cache more memory for each application. To allow this to happen for Exchange, the ESE Database Cache Size limit was removed to allow Exchange the ability cache more pages in memory. Accessing pages in memory is extremely fast, so the more data we cache in memory, the less we actually have to read andwrite from the disk. When following our best practice guidance around storage group deployment and memory sizing, Exchange 2007 reduces the amount of I/O required overall. This gave us rather huge performance gains. For more information regarding I/O improvements on the 64-bit platform for Exchange, see the following blog post http://msexchangeteam.com/archive/2006/09/08/428860.aspx. With no limitation in Database Cache for Exchange 2007, the memory usage for the store process will naturally be much higher compared to what Exchange 2003 used due to the many benefits discussed earlier. Memory allocation for the ESE cache is dynamic, so Jet will use all available memory on a system and return it as needed. For example, if a server had, let's say, 16GB of physical RAM installed, the database cache could consume approximately 14GB of memory, roughly 2GB less than the total amount of physical RAM in the server, leaving enough memory for the system cache or other applications running on the server. The algorithm is relatively simple for the ESE Database Cache. The DBA (Dynamic Buffer Allocation) will grow the cache by comparing the amount of I/O the databases are doing with the amount of I/O the system is doing in terms of hard page faults (MemoryTransition pages repurposed/sec). So if the database is doing more I/O, and Exchange is hitting hard page faults, we will increase the cache. If the database is doing less I/O than the hard page faults, then we will decrease the cache. The goal is to keep the ESE cache in balance with the disk cache so we don't end up paging ourselves to death. In some cases, on larger servers, Online maintenance during the night could cause up to a 4GB swing in memory for the Database cache alone due to the aggressive nature of how we touch pages during this process. (It may also be prudent to stagger your OLM schedules to assist with this.) Each server configuration is different, so it is important to have a monitoring solution in place or a Performance monitor log to track memory usage over time if memory pressure is occurring. If memory usage gets to a point where some driver or application attempt to allocate a large block of contiguous memory, and there is not one available, then the OS may decide to start trimming working sets which is a really bad thing performance wise. I've discussed this on my own blog http://blogs.technet.com/mikelag/archive/2007/12/19/working-set-trimming.aspx and possible remediation's to work around those type scenarios if you fall in to this bucket.Other Server Memory ConsiderationsSo we've talked a lot about memory usage for ESE database cache, but this cache alone is not the only significant consumer of memory on an Exchange server, it is just the majority. From an Exchange perspective, we have other processes going on such as Content Indexing, log shipping in continuous replication and underlying .NET applications that Exchange makes use of now. Most of Exchange has been rewritten in managed code using the .NET framework except for Store, DAV, and DSAccess. Managed code offers some significant advantages over non-managed code such as the ability to compile applications in real-time so that you don't have to worry about running your application on different architectures or platforms and the ability to manage memory efficiently. .NET applications use the Common Language Runtime (CLR) to allow easier coding in different languages because they share the same runtime. Any code that you develop with a language compiler that targets the runtime is called managed code as mentioned here: http://msdn2.microsoft.com/en-us/library/ddk909ch.aspx.Reasons for Memory PagingOne of the primary reasons for memory paging in Exchange 2007 is Content Searching, which uses the system cache since this is buffered. Performing more searches increases the file cache you have which in turn reduces the amount of IOPS that are generated. Content Indexing itself does not make use of the file cache as this is designed to work on a memory structure that is not affected by the file cache. Master merges of index data does use a small amount of the file cache, but it very short lived. Database I/O is actually unbuffered, so this not affected by the system cache. This is why the ESE cache doesn't continuously grow (ESE cache I/O is less than the system cache I/O). It's being balanced out by the content searching I/O (and potentially other applications that use buffered memory I/O) and thus the system cache. CCR log shipping is also unbuffered while log files are being copied over SMB, so this is also not affected by the system cache.Now couple all of this memory management with other 3rd party applications and drivers that are installed on the server which are all competing for the same resources, you can see that this is vastly different than what Exchange 2003 used to be. There is actually no comparison at all.How Exchange makes use of the Paging File So this brings up the second part of this document where I will now talk about the paging file. So you may ask, if I have so much memory in the server, why is a paging file needed at all? Our system requirements talk about needing one for getting a memory dump on the server, but what does Exchange really use it for? I get this very question asked very frequently. In certain cases, it is true that Windows 2003 does not require a paging file. It is however completely incorrect that Exchange does not need a paging file for normal runtime operations when running on top of that OS. There is always going to be a need to page out unused or rarely used memory to the page file so that we can make maximum use of RAM. For example, there could be a large amount of VM pages used during system startup that are not useful under main load. Unexpected transient conditions could cause large upward swings in memory that could cause us to spill pages of memory in to the paging file. There are enough processes outside of the cache manager that consume a significant amount of memory in Exchange 2007 (e.g. ESE and all processes that utilize the CLR) that there is a need for a substantially sized paging file as the system balances the memory footprint of the competing processes. Without a paging file (or with one that is too small) there is a very high chance that applications will encounter OOM (out of memory) conditions and both the performance and the functionality of the server will suffer and may lead to a possible blue screen.The cost of having a 32GB paging file on a server with 32GB of physical RAM on disk is pretty minimal, so having a properly configured paging file (RAM+10MB) will be able to sustain any unexpected growths in memory where we need more commit charge to handle current load. The other benefit is that if we should get ourselves in to a working set trimming issue, we would at least have the ability to flush these pages out to the paging file and then page them back in when a particular page needs to be accessed again. Excessive working set trimming on an Exchange 2007 server is not normal and should be investigated. Again, check out my blog post on working set trimming problems and why this is bad for performance.Why does Exchange allocate so much memory in the paging file?Another question that generally comes up is why does Exchange allocate so much memory in the paging file? Depending on the amount of memory that is consumed for the store process, we will need to at least allocate enough memory in the paging file to match the current working set that is in RAM on the server. If a system wide working set trim should occur, we would be able to page the current pages in the store working set out to the backing store or paging file. It is important to monitor MemoryPages/sec on the server to detect if this working set trimming problem is causing any performance related problems on the server. You should be able to see by adding ProcessWorking Sets a sharp decline in this value along with a sharp increase in MemoryPages/sec. With the other processes on the server possibly using parts of the system or file cache, there is always a balancing act trying to compete for memory on any given server. The good news is that Windows 2008 has made some significant changes in memory management to help prevent these system wide working set trims and to manage memory more efficiently. With server applications having the need for using more RAM as technology advances, it is imperative that memory management works effectively to prevent any negative performance problems on any given server. For more information on some of these memory management changes in Windows 2008, see http://www.microsoft.com/whdc/system/sysinternals/memmgt.mspx. I hope this helps clarify some of the reasons why Exchange uses more memory overall and provide clarity for these most common questions.A special thanks goes to Andrew Goodsell, Matt Gossage, and Ross Smith IV for their invaluable information in this area and Nick Basile for tech reviewing this document.Mike LagaseSupport Escalation Engineer Share this post :

A school where there aren't any rules and practical jokes are praised, what could be better.

A little trick from Jeffrey Snover over on PowerShell team blog: Speeding Up PowerShell Startup. Running the script mentioned by Jeffrey speeds up PowerShell startup times. Yes, hard to believe at first, but after having run this on a few servers, as Jeffrey says - the reaction is "Wow!" Paste the following in notepad and save it as Update-Gac.ps1 (or whatever you want to call it): Set-Alias ngen @(dir (join-path ${env:windir} "Microsoft.NETFramework64") ngen.exe -recurse |sort -descending lastwritetime)[0].fullName[appdomain]::currentdomain.getassemblies() | %{ngen $_.location} Note: On x86 systems; replace Framework64 in the second line of this script with Framework. [Optional] Close all open windows [Optional] Start the Exchange Management Shell and note the time it takes to start up Run the script: .Update-Gac.ps1 (or whatever you saved it as) Quit all open windows, start the Shell. Notice the difference? As Jeffrey says in his blog post, the PowerShell team had a problem in Windows PowerShell v1, that caused the binaries not to be NGENed. What's NGEN?Managed code exists in Common Intermediate Language (CIL). The Just In Time (JIT) compiler takes that and converts it into native code for a particular processor/platform - a process also referred to as "jitter". If you don't want this translation to happen at runtime, you can use NGEN.exe - the Native Image Generator - to convert managed code from the CIL to native code. Native code does not need to be compiled at run time, and thereby avoids jitter. So how does speeding up PowerShell help Exchange?The Shell is built on Windows PowerShell technology, and under the hood, the Exchange Management Console also executes PowerShell cmdlets. If you're running Exchange Server 2007 on Windows Server 2003, you're likely to see performance gains in shell start-up times after running this script. On one of my Exchange 2007 servers, EMS now starts up in as little as 2-3 seconds. Disclaimer: Your mileage may vary. Feel free to leave feedback about results you're seeing with this. - Bharat Suneja Share this post :

NASA EDGE visits Experience Aviation with Barrington Irving. Jacky interviews Barrington while Blair and Franklin try to compete in their flight simulators.

Author: YoungTurksShow Added: Thu, 31 Jul 2008 08:33:43 -0800 Duration: 316Watch more at http://www.theyoungturks.com

Author: YoungTurksShow Added: Tue, 29 Jul 2008 22:52:49 -0800 Duration: 384Watch more at http://www.theyoungturks.com

PlusBush Administration Projects Record 2009 DeficitBush Administration Projects Record 2009 DeficitThe Associated PressThe next president will inherit a record budget deficit of $482 billion, according to a new Bush administration estimate released Monday. (July 28)This video contains ONLY natural sound. No script is available. Author: AssociatedPress Keywords: budget deficit bush administration projects record 2009 Added: July 28, 2008

Dans cette interview, Eric Répérant, référent du MBA spécialisé Conseil stratégique de l'ISG (http://www.isg.fr/fr/MBA-specialises/etudes-MBA-specialises.html) revient sur les principaux points analysés au cours de cette formation, à savoir, l’ensemble des méthodes de travail, les enjeux, les organisations et les marchés qui constituent le conseil stratégique. Ce MBA spécialisé s’adresse aux candidats ayant validé un bac+4.Author: ISG_PARIS Tags: référent isg mba eric répérant conseil stratégique école commerce paris master bachelor administration Posted: 22 July 2008 Rating: 0.0 Votes: 0

Eric Répérant, référent du MBA spécialisé Création d’entreprise de l'ISG (http://www.isg.fr/fr/MBA-specialises/etudes-MBA-specialises.html) revient sur les principaux objectifs de cette formation : fournir aux porteurs de projets les bases et les repères méthodologiques indispensables pour les accompagner dans la finalisation, la préparation et le lancement de leur idée. Il est constitué d’interventions de professionnels qui vont tous apporter un retour d’expérience et des conseils judicieux auprès des participants. Ce MBA spécialisé s’adresse à tous ceux qui ont un projet de création ou de reprise d’entreprise.Author: ISG_PARIS Tags: référent isg mba eric répérant création entreprise école commerce paris master bachelor administration Posted: 22 July 2008 Rating: 0.0 Votes: 0

Author: ISG_PARIS Tags: référent mba bernard quéau Logistique Supply chain management isg école commerce paris master bachelor administration Posted: 22 July 2008 Rating: 0.0 Votes: 0

We saw a great post by John Grohol at PsychCentral called Distracted While Driving. He really caught our attention with one thought. We allow ourselves to be distracted while we drive because we think we re playing a race against time. In reality, we re playing against the odds. A study by Virginia Tech Transportation Institute and the National Highway Traffic Safety Administration found that about 80 percent of all crashes and 65 percent of all near-crashes involved someone who was distracted within three seconds of the event. . . I plead guilty as charged. I have to admit to using my car as a roaming second office. I store up phone messages and return calls while I m on the road. . . . I m in the car on a busy, busy day with all these things rolling through my mind. That s one of the distractions that we often don t take into account. I zone out I don t really pay attention like I should. I m in my own world. . . Psychologists have identified four types of distractions, according to Grohol s article. Visual checking out an accident or looking at a billboard Audible cell phone calls, the radio, or another person talking Physical eating, flipping the dial, shuffling your iPod, or putting on make-up Cognitive daydreaming, thinking about other things in your life Of course, a lot of distractions are multi-faceted. For example, talking on your cell phone includes three of these audible, physical, and cognitive. . I really do think it saves time. We have a friend who consults with us. He talks to us when he s on his hour-and-a-half commute home. I can understand why you would use your phone when you have that long drive. . I won t dispute that at all, but I now realize more than ever that I have to recognize the odds of something happening and take measures to try to minimize the distractions. . . Changes we plan to make Leave earlier. When we have a lengthy trip, we usually don t give ourselves the time to stop and eat. We gas, grab, and go eating on the road. Leaving earlier will allow us time to stop and eat. We ll probably eat healthier, too! Ignore the phone. Granted, that s a hard thing to do. So we re going to turn our ringers off when we re only going to be in the car for a short time. Change our greetings. If we re expecting an important call, we ll change the greeting to let them know when we will be checking our messages. Pull over (if we can). For those rare situations where we have to take the call, we ll stop driving momentarily. What s your biggest distraction while driving? Subscribe to The Bigg Success Show in iTunes. Subscribe to the Bigg Success feed. (Image by krilm) ShareThis

Author: ISG_PARIS Tags: référent isg mba Jean-Philippe Regnault Customer relationship management école commerce paris master bachelor administration Posted: 21 July 2008 Rating: 0.0 Votes: 0

Sen. Clinton says Bush's draft proposal would change the definition of abortion.

Petition: http://sendkarlrovetojail.com Digg: http://digg.com/politics/Send_Karl_Rove_to_Jail This sounds like a dream, doesn't it? Well, it's not. We have a unique opportunity right now to send Karl Rove to jail, but only if we take immediate action. All we have to do is pressure the 40 members of the House Judiciary Committee, make them hold Rove in contempt and send him to jail. We've never had such a direct opportunity to hold Rove accountable. No, this is not enough punishment for his years and years of crimes, but it's a huge start, and will send a very clear message to the entire Bush administration. The specific issue regarding Rove's failure to testify before Congress is a little complicated, so we put together this video that explains exactly why Rove should be held in contempt and sent to jail. Check out Send Karl Rove to Jail, and sign our petition to ensure that the HJC holds Rove in contempt. After you watch the video, sign the petition: http://sendkarlrovetojail.com Author: bravenewfilms Keywords: karl rove jail house judiciary committee contempt congress george bush administration executive privilege testify Added: July 18, 2008

Petition: http://sendkarlrovetojail.com Digg: http://digg.com/politics/Send_Karl_Rove_to_Jail This sounds like a dream, doesn't it? Well, it's not. We have a unique opportunity right now to send Karl Rove to jail, but only if we take immediate action. All we have to do is pressure the 40 members of the House Judiciary Committee, make them hold Rove in contempt and send him to jail. We've never had such a direct opportunity to hold Rove accountable. No, this is not enough punishment for his years and years of crimes, but it's a huge start, and will send a very clear message to the entire Bush administration. The specific issue regarding Rove's failure to testify before Congress is a little complicated, so we put together this video that explains exactly why Rove should be held in contempt and sent to jail. Check out Send Karl Rove to Jail, and sign our petition to ensure that the HJC holds Rove in contempt. After you watch the video, sign the petition: http://sendkarlrovetojail.com

The Red Cross' blood processing method draws criticism from the FDA.