Netwacky87 Posted February 9, 2011 Posted February 9, 2011 Hi All, Just incase some of you missed this: SP1 for Windows 7 and Server 2008 R2 will be out on the 22nd Febuary, and for you lucky TechNet and MSDN subscriptions you get it on 16th Feb!... All Credit and news source to: Neowin.net - Windows 7 SP1 confirmed for Feb 22nd release Enjoy ! 2
FN-GM Posted February 9, 2011 Posted February 9, 2011 I assume this is american time, so it will be probably late on in the day for us.
EduTech Posted February 10, 2011 Posted February 10, 2011 Nice use of the TechNet Sub now i've finished playing with the recently added SBS2011
Arthur Posted February 10, 2011 Posted February 10, 2011 For some reason, a lot of the news sites seem to have missed Microsoft's other announcement... Microsoft also used the service pack announcement to describe Windows Thin PC, a benefit for Software Assurance customers that will become available next year. Windows Thin PC is a special, locked-down version of Windows 7 designed to be used as a thin client. Unlike other thin clients, systems running Windows Thin PC will not need a virtual desktop access (VDA) license to access services provisioned using VDI desktops. In conjunction with RemoteFX, this should allow older PCs to obtain the full richness of the Windows 7 desktop experience. (Source) 2
SYNACK Posted February 10, 2011 Posted February 10, 2011 And me with a bunch of servers that need to be installed this week.
sted Posted February 10, 2011 Posted February 10, 2011 wonder if they will also have sp1 integrated isos up on technet?
Arthur Posted February 11, 2011 Posted February 11, 2011 Good news for those of us with Exchange servers... Windows Server 2008 R2 SP1 general availability and what it means for Exchange Now that you might have seen the announcement for general availability of Windows 2008 R2 SP1, we wanted to get ahead of the inevitable question: "Is Exchange supported running on Windows Server 2008 R2 SP1?" We wanted to let you know that we've completed testing with Windows 2008 R2 SP1 and the following versions of Exchange are supported to run on Windows 2008 R2 SP1 (the RTM version of SP1): Exchange 2010 SP1 Exchange 2010 RTM Exchange 2007 SP3 Please note that Exchange 2007 was not supported to run on Windows 2008 R2 at all before Exchange 2007 SP3 release. (Source) 1
Gatt Posted February 11, 2011 Posted February 11, 2011 Looks like thats me spending some time with SCCM - clearing all the updates that will get superceded as a result.. Was going to go through them on Monday.. but prob best waiting for SP1 now..
Netwacky87 Posted February 16, 2011 Author Posted February 16, 2011 Its on technet NOW :-) You beat me to it!...Downloading
AngryTechnician Posted February 16, 2011 Posted February 16, 2011 (edited) The dozy idiots have forgotten to put the ISO for Enterprise SP1 x86 on TechNet. x64 is there, but no x86. It is on the VL download site though. Edited February 16, 2011 by AngryTechnician It is on the VL site after all.
Gatt Posted February 16, 2011 Posted February 16, 2011 The dozy idiots have forgotten to put the ISO for Enterprise SP1 x86 on TechNet. x64 is there, but no x86. It is on the VL download site though. As in MVLS ?! If it is I can't see it ...
AngryTechnician Posted February 16, 2011 Posted February 16, 2011 Look under the Software Assurance category. For some insane reason it's not listed in the Windows category. I made the same mistake at first.
Arthur Posted February 17, 2011 Posted February 17, 2011 Microsoft have also released an update to the Windows Automated Installation Kit (AIK) which adds support for Windows 7 & 2008 R2 SP1. This is just a supplement, so you need to have the previous AIK installed beforehand (KB3AIK_EN.iso). Download: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en ReadMe: http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx Direct Link (1.25GB): http://download.microsoft.com/download/8/E/9/8E9BBC64-E6F8-457C-9B8D-F6C9A16E6D6A/waik_supplement_en-us.iso SHA-1: 3B0627003AC43B93199F521A1472C8747CDAFE41 To install, burn/mount or extract the files from the ISO and run the command below from an elevated command prompt (where X: is the root of the disc). xcopy X:\ "C:\Program Files\Windows AIK\Tools\PETools" /ERUY 2
mrbios Posted February 17, 2011 Posted February 17, 2011 Just installed SP1 on a freshly installed 2008R2 server with no prior updates.......took 2 hours to complete!
Gatt Posted February 17, 2011 Posted February 17, 2011 Installed successfully on my 2 home PCs, Terminal Server and DC....
FreeWill Posted February 17, 2011 Posted February 17, 2011 Installed OK on Windows 7.. took 90+ minutes on a 2.4GHz Core 2 Duo with 4GB of RAM. Only downside so far is it lost the registry setting for the custom logon wallpaper.
Gatt Posted February 17, 2011 Posted February 17, 2011 Odd.. still got my custom logon screen background on my home PC..
mrbios Posted February 17, 2011 Posted February 17, 2011 Run this command from a command prompt to free up about 2.5GB of space, once your happy you won't want to be rolling back: dism /online /cleanup-image /spsuperseded Only really needed for people running windows 7 on 40/80GB SSDs but handy nonetheless 2
Arthur Posted February 19, 2011 Posted February 19, 2011 Something else to watch out for... http://forums.mydigitallife.info/threads/24666-The-Windows-7-SP1-USB-Driver-Bug-(what-it-is-and-how-to-fix-it) The Windows 7 SP1 USB Driver Bug (what it is and how to fix it) This was a bug that was first noticed by a member of this forum, burfadel, in another thread. At first, I thought that this was just a minor bug in the SP installer, nothing to get too excited about. But then this bug bit me hard... Who is affected by this bug? Anyone who updates Windows 7 to SP1 using the executable installer (i.e., windows6.1-KB976932-???.exe). Who is NOT affected by this bug? Anyone who installed a new copy of Windows 7 SP1 using an official integrated ISO (and it looks like homemade slipstreamed integrated ISOs are okay, too). What does this bug do? Of the several USB-related driver files updated by SP1, three files, usbport.sys, usbehci.sys, and winusb.sys were only partially updated; i.e., the SP1 installer only updated the "repository" copies of these files i.e., the copies found in WinSxS and DriverStore. The "active" copies, found in System32\Drivers, are not updated (this is a bug with the installer). People who did a new installation using an integrated ISO are not affected (both the "repository" and "active" copies are 7601) (so this only affects a 7600->7601 update), and other USB-related driver files seem to be unaffected (e.g., the SP1 installer updates both the "repository" and "active" copies of usbhub.sys). What is the impact of this bug? For most people, this bug just means that they keep using the old 7600.16385 version of usbport.sys, usbehci.sys, and winusb.sys instead of the newer 7601.17514 version. So, for most people, it's not a very big deal. However, there is a scenario where this would result in your USB2 (EHCI) controller becoming unsigned, which may result in all your USB2 devices being downgraded to USB 1.1. This particular scenario happens when (1) you have KB976972 installed (this hotfix was distributed via Windows Update to anyone with a NVIDIA USB controller, such as people with nForce boards or first-generation ION) and (2) you ran the DISM cleanup command ("DISM /Online /Cleanup-Image /spsuperseded") after installing SP1. The cleanup operation removes all the hotfixes that had been superseded by SP1, so it deletes the KB976972 security catalog and all the "repository" copies of the KB976972 usbehci.sys. But the "active" copy of usbehci.sys is still the KB976972 version (the cleanup operation only deletes obsolete security catalogs and obsolete copies in the repository--it never touches the "active" copies of files because the SP1 updater should have replaced those already), so you are still using the KB976972 usbehci.sys (thanks to the installer bug) but the corresponding security catalog is gone (due to the cleanup), so Windows no longer has a signature for the file. The device manager does not immediately notice the problem (in my case, it flagged the controller as unsigned only after I plugged in a new USB device and rebooted), but once it sees the problem, it disables the EHCI (USB2) controller, thus forcing all the USB2 devices to use the legacy OHCI or UHCI (USB1.1) controller. This scenario can play out in other ways too, of course. If you installed "private" hotfixes (those not released to WU), then you might have a hotfixed version of usbport.sys, in which case, installing SP1 and then doing a cleanup will result in ALL of your USB controllers becoming unsigned, which will basically disable USB on your system. To the best of my knowledge, I think usbehci.sys was the only driver affected by the SP1 installer bug that had a hotfixed version on WU (and that hotfix was not offered to everyone; my systems with Intel controllers never got that hotfix). 2
IanT Posted February 20, 2011 Posted February 20, 2011 Installed on 4 Servers, 1 Desktop and 1 Laptop so far, all installed fine but takes a while.
SYNACK Posted February 20, 2011 Posted February 20, 2011 I wish I had Technet, stupid faulty MVLS SA portal.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now