Build: 6.0.6001.16642 - Service Pack 1 v.258 Vista News Discuss Build: 6.0.6001.16642 - Service Pack 1 v.258 in the Windows Vista forums; Released ? Sunday, August 26th, 2007 There are rumours about yet another internal release of Vista SP1 that was made available to testers on 18th august. Build: 6.0.6001.16642 (...

[Snuffy]

Released ?
Sunday, August 26th, 2007
There are rumours about yet another internal release of Vista SP1 that was made available to testers on 18th august.

Build: 6.0.6001.16642 (longhorn.070818-16xx)
Version: Service Pack 1 v.258

The rumours says that this release is 3MB bigger than the 16633 version, and that would be 687MB.

No screens has surfaced yet, but I’ll make an update as soon as I know more.

Posted in Sebastian Foss

[ProCookie]

Intresting cant wait till this thing goes public. The severs will be swamped when it does come out as the full region version is a 1gb file Hopefully i can avoid the rush if im super fast.

[Snuffy]

Windows Vista SP1 Pre-Beta v.249 Leaked
Yet again, another pre-beta version of Windows Vista Service Pack 1 has been leaked to the public. So, what's different in this version compared to the last leak?

Well first, this version carries a build tag of 6.0.6001.16633.longhorn.070803-1655. Unlike v.165 which was integrated with Vista RTM into an ISO image, v.249 is now a standalone installer and weighs approximately 684 MB. This does not require a clean install for those users running the RTM version. The setup wizard requires several reboots and atleast 30 minutes for installation.

Besides bug fixes, overall v.249 does not differ much from the last leak. However, users claim this version to be buggier and not as stable as the last leak.

Screen shots: http://www.jcxp.net/forums/index.php?showtopic=20633

[Snuffy]

Today, September 02, 2007, 12 hours ago | ch46
@ Nick
As for user wanting to use SP1 Beta I would hold off. I just went to a Microsoft TechNet even with them using Vista with SP1 and the system Crashed hard in the middle of the presentation. I must admit this is something I have been waiting for, for some time. I never laughed so hard.

Remind me (Snuffy) of the presentation when Bill Gates plugged in several USB devices and the entire system went up in SMOKE....

guess the only other issue I may have is DX10 issues. All of these games coming out with DX10 with the biggest boy on the block for a GPU in SLI and 10FPS? I think I will stick with DX9 if that is the case.

What I dont understand is Microsoft DEV team is stating we will not release SP1 in its final stages until it is released. Why not do the same with your O/S instead of cutting corners to push something out. There is a lot of features that was never included in Vista that was dropped so it could be rushed out. What makes me think any differntly about SP1. It will be rushed ready or not when Server 2008 or Longhorn is relased 1Q.

I am glad that bandwith issues getting corrected with SP1. I can tell you, this is the biggest reasson we are not using Vista right now due to the fact of bandwith consumption on our network for shared drives. It slowed everything to a crawl even for the users on XP.

[Snuffy]

Microsoft seems to want to emphasize that Windows Vista SP1, slated for release to manufacturing in the first quarter of 2008, is not meant to be about new features, but about already existing components gaining new functionality. Over at Geek.com, Brian Osborne explains what he has learned about the first major update to the software giant's latest OS. Apart from performance, security and reliability, including all previously released updates, SP1 will incorporate additional support for hardware and standards including an Extensible Firmware Interface (EFI) and an Extended File Allocation Table (exFAT).

In SP1, BitLocker Drive Encryption will be able to encrypt other local volumes besides the C drive. Disk Defragmenter will give administrators the ability to control which volume the program defragments. The Network Diagnostics tool has been expanded to help diagnose common file sharing problems and issues associated with printing to local printers from a Windows Terminal Services session. Group Policy tools are also being updated in SP1 to simplify policy management. Nick White, Microsoft Product Manager, also notes that laptop users will be happy to know that SP1 will offer a number of performance improvements, including: “optimization to improve power consumption when the display is not changing by managing the processor so it consumes less energy; single sign-on (SSO) for authenticated wired networks; and improvements in the method used to determine which network interface to use (e.g., should a laptop use wireless or wired networking when both are available).”

Brian’s Opinion

I don’t expect service packs to be what they once were now that Windows Vista is released. Microsoft is taking full advantage of Windows Update to push patches and enhancements. That’s why I don’t think Windows Vista SP1 will be one of those things folks will just have to get their hands on.

If you’re an administrator, then you definitely have a lot more to look forward to when it comes to SP1. One thing that caught my eye was the additional ability in BitLocker to encrypt extra local volumes. Many enterprises still partition their workstations and laptops into a C and D drive. Since users are usually instructed to use the D drive to store their data, this means data was at risk if the enterprise also used BitLocker as a security measure, since D couldn’t be previously encrypted.

Though it doesn’t have a ton of new stuff in it, SP1 does help Microsoft in one significant way. Many enterprises make it a point not to roll out a new version of Windows until the first service pack is released. Therefore, SP1 may open the door for adoption of Windows Vista by more enterprises.







http://www.geek.com/windows-vista-sp...-means-to-you/

[Vistanoob]

To me that's kind of a relief. When SP2 for XP came out in 2004, I was barely into my first year of computer experience and was petrified to upgrade, even though it was strongly urged. So much of what I read scared me, about compatibility issues with programs etc. (I had not discovered forums yet.)
Even though I have a lot more experience now I still go by the adage, "If it aint broke, don't fix it". So for now it looks like nothing to worry about. That's only my opinion, I know there are many who may disagree, including me later on.

[Snuffy]

I like your quote, only you forget part of it..

I still go by the adage, "If it aint broke, don't fix it".

my Granddaddy told me.
"If it aint broke, don't fix it, unless you make it better".
then my dad told me
"Them that can brag without lying, let them brag."

[Vistanoob]

I'll remember that!
I like the adage in your signature too, so true. I'm totally into questions (even at the risk of seeming none too bright some times.)

[Snuffy]

Microsoft has been touting Windows Vista as the most secure Windows ever. Backing up that claim, Microsoft has included a number of new security features in the operating system. Thanks to pacpis for this news.





These new features are designed to address some of the common vectors by which previous versions of Windows have fallen to anonymous miscreants and other criminals.

One such new feature in Windows Vista is known as Windows Service Hardening. In older versions of Windows, services did not necessarily run with the least possible privileges. In fact, Windows services often ran under accounts with very high level of access, such as the LocalSystem account. Further, users are often not aware of the services running on their systems, and do not realise that some services are safe to disable. Finally, services and user applications ran in the same space, which could result in inappropriate access. As a result of services running with privileges that did not match necessity, and services running that users did not require, Windows desktops were left more vulnerable to attack.


What's Windows Service Hardening?
Vista's Service Hardening is designed to mitigate some of these shortcomings. The feature uses four methods to achieve its goals:

* Service isolation
* Least privilege
* Restricted network access
* Session 0 isolation

We'll talk about each of these security methods in some detail.


Service isolation
Before Windows Vista, when a service needed access to an object that required a high level of security, one of two approaches could be taken:

* The service could be run using an account that granted a high level of rights to the system. The LocalSystem account, for example, would provide this level of service. This is the approach that was most commonly taken but unnecessarily opened up the system to possible attack.
* The security configuration for the object to which access was required could be reconfigured to allow access from a special account with fewer privileges. Besides creating an administrative nightmare (imagine having to create a service account for every account and then maintaining passwords for those accounts), this approach would provide an attacker with another vector by which to attack a system.

Enter service isolation. Service isolation is a method by which a Vista service can access a required object without having to jump through administrative hoops or use a super-administrator account like LocalSystem. Service isolation works by securing a target object — such as a registry key — with an access control entry that contains a security ID. This ID is referred to as a "service identity", "per-service SID" or, in some documentation, just "SID", which should not be confused with the phrase "security identifier" (also known as the SID) used by Windows and Active Directory. This SID is unique to the service and is derived from the service name.

Once the SID is created and assigned for use by a service, an object's (for example, a registry key to which a service needs to write information) access control list can be modified to include the new SID, thus allowing the service to access the object without giving away the privilege farm.

http://resources.zdnet.co.uk/article...9288962,00.htm

[ProCookie]

Wise words Snuffy but i would say I'm more of a "if it gets boring, change it! and if it breaks i have something to do"