Finally RSAT for Windows 7 released !  Don’t forget to go to add/remove programs, select windows components, and install the tools.
Remote Server Administration Tools for Windows 7

Version: 1.0
Date Published: 8/11/2009
Language: English
Download Size: 215.1 MB – 437.2 MB*

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d
amd64fre_GRMRSATX_MSU.msu 222.1 MB
http://download.microsoft.com/download/4/F/7/4F71806A-1C56-4EF2-9B4F-9870C4CFD2EE/amd64fre_GRMRSATX_MSU.msu

x86fre_GRMRSAT_MSU.msu 215.1 MB
http://download.microsoft.com/download/4/F/7/4F71806A-1C56-4EF2-9B4F-9870C4CFD2EE/x86fre_GRMRSAT_MSU.msu

“Researchers at a University in Melbourne, Australia have come up with a "five dimensional" disc capable of storing 2000 times more data than a conventional DVD.”

http://www.pcworld.com/article/165291/researchers_unveil_discs_that_could_store_2000_dvds.html?tk=nl_tex_t_crawl

I was impressed how easily my system upgraded without a hitch.  The only incompatibility was with ATI’s CCC, which it happily disabled.  System response feels much snappier than before, but I am running it on a quad with hyperthreaded 64-bit edition with 6 Gigs of RAM. 

The first large change is the start menu.  Quicklaunch is now gone; however, in a way it was combined with the tasks running.  As before you can create ‘quicklaunch’ icons on your taskbar, but these also double as an indication there is an open window.  It simply has a box around it, up to three.  When you hover over the icon, a small-preview of all windows with that task type are opened.  This includes multiple tabs in an IE session.  There is a way to add quicklaunch back, but it’s a little complicated.  Let me know and I can send you the instructions, but I think you will learn not to need it anymore

I miss Dreamscene; apparently the feedback was it was a feature that took up processing for a low-res moving desktop that was never seen.  Since I run multiple monitors, it was nice to have this moving background.

My system has been rock solid since I installed it, and performance is much improved.  Perhaps Microsoft got it right this time?

Gartner is estimating a decline of nearly 12% drop in sales in 2009 over last year, due to the economy and other factors.  This is reported to be the biggest dip in sales in history.  This means windows 7 will be released in a recession just like its older brother Windows XP.

http://www.microsoft-watch.com/content/desktop_mobile/grim_reaper_gartner_taunts_windows_7.html?kc=MWRSS02129TX1K0000535

I’ve been using IE 8 beta 2 since it’s September release.  There are a ton of features that make it a worthy upgrade, but it has it’s share of problems.   One bug that is particularly annoying is certain sites that want to do a pop-up due to a security change cause a flood of new IE windows.  The only resolution I have found is to open task manager, sort by CPU used, and kill the top IE process.  This closes all IE windows, which is a pain but at least the problem is resolved.   I’d wait for the next release if you haven’t already installed it, but if you want to, here is a link to try it.

The IE team posted an update saying a new release candidate is due in the first part of 2009.  I look forward to the release.  read more here: http://bink.nu/news/ie8-what-s-after-beta-2.aspx

Original post: https://presson.wordpress.com/2008/10/30/sprint-severs-peering-with-cogent-tens-of-thousands-of-users-effected/

Now what I don’t understand is why Sprint Didn’t notify it’s customers they were doing this?

“SPRINT STATEMENT TO CUSTOMERS ON ITS DEPEERING

WITH COGENT COMMUNICATIONS

Dear Valued Customers,

On Thursday, October 30^th, Sprint Nextel completed a disconnection of its network from Cogent Communications. This action was taken by Sprint after Cogent breached its contract and failed to pay for its ongoing connection to the Sprint network, despite repeated collections attempts by Sprint.

Until this issue is resolved, Sprint will continue to work tirelessly to the extent within our control to mitigate the effects on customers. As part of an interim solution, Sprint initiated a temporary reconnection to the Cogent network on Sunday, November 2^nd so that customers would have temporary access while longer-term alternate and permanent access options are explored.

We emphasize that this reconnection is temporary only, as the core issues in this dispute have not changed. Cogent was notified in advance of the November 2^nd reconnection; therefore, any access disruptions occurring during this temporary period are the sole result of a negative reaction instigated by Cogent against the customers of both parties.

Sprint deeply regrets any inconvenience caused by this issue and we do not take our actions lightly given frustrations experienced by customers of both parties.

Background

In 2006, Cogent sought a peering trial agreement in the hopes that it would lead to settlement-free peering status with Sprint. Settlement-free peering is a contractual relationship in which two companies exchange Internet traffic without charging each other. This arrangement is only fair if the two parties exchange roughly equal volumes of traffic across the two networks. Prior to this trial period, Cogent utilized third parties for full Internet connectivity.

Following a three-month commercial trial agreement during June – September 2007, the peering trial data indicated that Cogent did not meet the minimum traffic exchange criteria agreed to by both parties. As a result, settlement-free peering was not established and Cogent was notified in writing of these results. Despite this fact, and after repeated discussions, Cogent failed to disconnect itself from the Sprint network or compensate Sprint for the ongoing connection.

Sprint has repeatedly notified Cogent in writing of payment past due and our intent to take action if the issue was left unresolved. On September 2^nd of this year, Sprint filed a lawsuit against Cogent for breach of contract. Sprint also notified Cogent in writing of our intent to begin disconnect procedures if Cogent did not pay for services or voluntarily disconnect and make arrangements with one of many alternate providers. Throughout this period, which includes the initial disconnect activities, Cogent did nothing to mitigate the potential effects of Sprint’s pending disconnect to its customers.

Fact and Fiction

On October 30^th, Cogent issued a press release and has made subsequent statements to the media that contain a number of distortions regarding the relationship between Sprint and Cogent. The following is intended to clarify these misstatements:

Cogent press release: “On October 30 at 4:30 pm Sprint-Nextel severed its Internet connection to Cogent thereby partitioning the Internet.”

FACT: The events of October 30^th related only to disconnection of the final two interconnects (of 10 original interconnections) between Sprint and Cogent. In addition to notifying Cogent 30 days in advance of our intent to disconnect, Sprint’s first disconnect action took place on October 7^th, 2008. Between October 2^nd and October 30^th, Sprint disconnected one or two ports each week with Cogent’s full awareness. During this period, Cogent failed to take any action in support of its own customers’ ongoing Internet reachability even though such actions were fully under its control.

Cogent press release: “Sprint [severed its Internet connection to Cogent] in violation of a contractual obligation to exchange traffic with Cogent on a settlement free peering basis.”

FACT: At no time did Sprint and Cogent enter into a contract for settlement free peering. In 2006, Sprint and Cogent formed a commercial trial agreement that ended in September 2007. Cogent was unable to satisfy the agreed-upon traffic exchange criteria within the trial agreement, yet refused to pay Sprint or disconnect from Sprint’s network.

Cogent press release: “Sprint and Cogent are engaged in litigation over this matter. Cogent regrets that Sprint chose to take this unilateral action rather than await a determination by the court as to the rights of the parties.”

FACT: Sprint filed a lawsuit on September 2^nd in Fairfax County, VA Circuit Court against Cogent for breach of contract due to Cogent’s refusal to pay Sprint for the ongoing connection to our network. Sprint also provided Cogent with 30 days advance written notice in the hope that Cogent would take action to mitigate the impact of this action on our respective customers.

Cogent press release: “Cogent remains ready to reestablish, on the same settlement free basis as previously existed, the connections that Sprint has severed.”

FACT: As noted above, Sprint and Cogent did not enter into a settlement free peering agreement. Instead, the two companies entered into a commercial trial agreement, upon which Cogent did not meet the minimum traffic exchange criteria agreed to by both parties.”

Amazing! At 3:00pm Central Sprint broke legal agreement with Cogent and severed their peering. Folks on Sprint network are unable to get to Cogent IPs, and Cogent folks are unable to get to Sprint. Apparently talks broken down, and Spring is playing hard-ball.

You can see the outage clearly here: http://internetpulse.net/

Read more here:http://www.marketwatch.com/news/story/Sprint-Nextel-Severs-Its-Internet/story.aspx?guid=%7B2971C78E-2F27-4B28-8878-F750FEA999C3%7D

from: http://www.realtechnews.com/posts/6151

“Patch Tuesday is the second Tuesday of each month, and that’s when Microsoft typically releases security and other updates for their products. Sometimes an emergency requires an “out-of-band” patch. And today, October 23rd, Microsoft is pushing out a critical Windows security patch.

Not much has been said about the release, however. They are planning to release the Windows patch at 10 AM PDT, with a Webcast to cover specifics of the patch at 1 PM PDT. However, Webcast registration is already full.

Microsoft hasn’t offered many details about the patch, other than to say it is critical and should be applied immediately to Windows 2000, Windows XP, and Windows Server 2003 systems. For Windows Vista and Windows Server 2008, the patch is only deemed (only) “important” rather than critical.

The last time Microsoft released an “out-of-band” patch was April 2007, according to a Microsoft representative.

Update: It’s this one and it looks pretty bad. Remote code execution could allow an attacker to take over your system.

Bulletin Identifier
Microsoft Security Bulletin MS08-067

Bulletin Title

Vulnerability in Server Service Could Allow Remote Code Execution (958644)

Executive Summary

This security update resolves a privately reported vulnerability in the Server service. The vulnerability could allow remote code execution if an affected system received a specially crafted RPC request. On Microsoft Windows 2000, Windows XP, and Windows Server 2003 systems, an attacker could exploit this vulnerability without authentication to run arbitrary code. It is possible that this vulnerability could be used in the crafting of a wormable exploit. Firewall best practices and standard default firewall configurations can help protect network resources from attacks that originate outside the enterprise perimeter.

Maximum Severity Rating

Critical

Impact of Vulnerability

Remote Code Execution

Detection

Microsoft Baseline Security Analyzer can detect whether your computer system requires this update. The update requires a restart.

Affected Software

Microsoft Windows. For more information, see the Affected Software and Download Locations section.

The Microsoft Security Response Center said the following:

This security update resolves a vulnerability in the Server service that affects all currently supported versions of Windows. Windows XP and older versions are rated as “Critical” while Windows Vista and newer versions are rated as “Important”. Because the vulnerability is potentially wormable on those older versions of Windows, we’re encouraging customers to test and deploy the update as soon as possible. To help you better understand the details around the vulnerability, my colleagues over at the Security Vulnerability Research & Defense blog have provided some more information here. Also, Michael Howard has provided some background on the vulnerability from the Security Development Lifecycle perspective here.

In addition, to releasing a security update to address the vulnerability, we’ve also taken steps to help enable broader protections for customers. Specifically, our colleagues in the Microsoft Malware Protection Center have released updated signatures that can enable Microsoft Forefront and Microsoft OneCare to protect against current attempts to exploit the vulnerability (Exploit:Win32/MS08067.gen!A). You can read about what they’re doing to help protect here. We have also provided information to our security partners in our Microsoft Active Protections Program and our Microsoft Security Response Alliance Program. We encourage all customers to update the signatures for their security protection products to help provide protections while they’re testing and deploying these updates.

We discovered this vulnerability as part of our research into a limited series of targeted malware attacks against Windows XP systems that we discovered about two weeks ago through our ongoing monitoring. As we investigated these attacks we found they were utilizing a new vulnerability and initiated our Software Security Incident Response Process (SSIRP). As we analyzed the vulnerability in our SSRP process, we found that this vulnerability was potentially wormable on Windows XP and older systems. Our analysis also showed that it would be possible to address this vulnerability in a way that would enable us to develop an update of appropriate quality for broad distribution quickly. Based on those two factors, we felt that it was in the best interest of customers for us to release this update before the regular November release cycle.”

The long awaited SQL server 2008 is now available for download if you have MSDN.  Expect to see a lot of buzz about this release..

“Dan Kaminsky from IOActive Inc. discovered the flaw,  said he hopes the patches will be broad enough that hackers won’t be able to reverse-engineer them.”  http://www.upi.com/Top_News/2008/07/09/Experts_discover_major_Internet_flaw/UPI-83691215616576/

What is even more interesting is the collaborative effort that was put into getting patches released for all platforms at the same time.  I don’t recall a collaborative effort going so far for anything on the Internet. Check out this link, and note on the sidebar is a way to check if your DNS cache is vulnerable to poisoning.

http://www.doxpara.com/?q=node/1156

The initial release of AVG had a feature that would pre-scan websites you search. AVG finally agreed to disable the ‘feature’ which significantly increased Internet traffic.  In a post from their team, “The latest update for AVG free edition has addressed and rectified the issue.”  whirlpool.net.au was one of the hardest hit, and their independent testing shows the latest release fixed the problem.  I for one am still unimpressed with the added bloat-ware AVG 8 is now.  I would recommend looking at Avast instead.