anyweb

An Internet Explorer 9 Release Candidate build has leaked onto the Internet ahead of its public debut. Internet Explorer 9 RC build 9.0.8073.6003 appeared on a number of file sharing sites on Friday, shortly before Microsoft is expected to unveil its latest public preview. The build is an escrow version of Internet Explorer 9 RC and is not expected to represent the final shipping build version of Internet Explorer 9 RC. Screenshots of a more recent escrow build surfaced on Friday, version 9.00.8073.6018 (WIN7_IE9_Partner.110121-2300). The screenshots revealed that Microsoft is planning a location privacy feature for IE9. WinRumors understands the builds are Microsoft’s escrow near final builds of Internet Explorer 9 RC. Microsoft’s release candidate of Internet Explorer 9 will include a number of new enhancements from the previous public beta build. According to sources familiar with Microsoft’s plans, the software giant is currently building copies of Internet Explorer 9 that include an “ActiveX filter” feature. The filter will allow users to control what ActiveX elements are displayed on sites they visit, furthering Microsoft’s commitment to security within its browser. Microsoft is expected to ship the feature inside Internet Explorer 9 Release Candidate (RC). Microsoft has also improved the UI of the browser tabs and buttons in Internet Explorer 9 RC. The build features square tabs and minor UI enhancements to the address bar buttons in Internet Explorer 9. Microsoft has also updated its download manager so that it now displays the transfer speed without the need to hover over individual downloads. Microsoft announced earlier this month that the beta version of Internet Explorer 9 has surpassed 20 million downloads, making it the most downloaded beta release of Internet Explorer ever. The download rate of Internet Explorer 9 beta has grown by 5 million each month since its release on September 15, 2010. Internet Explorer 9 RC is expected to include UI tweaks and minor changes to some functions in Internet Explorer. Microsoft will also introduce a new Tracking protection feature in Internet Explorer 9 RC that will allow consumers to address their concerns about being tracked on the web. via > http://www.winrumors.com/internet-explorer-9-rc-escrow-build-leaks-ahead-of-public-debut/?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed%3A+WinRumors+%28WinRumors%29&utm_content=Twitter

Solid-state drives are wicked fast. SSDs start and shut down fast, and they perform read operations (especially random reads) at speeds that blow the doors off conventional hard drives. In the first installment of this series, I gathered the numbers to show just how much faster you can expect an SSD to perform in the real world. But you might need to jump through some setup hoops to get top performance out of an SSD-equipped PC running Windows 7. That’s because Windows has evolved over many years with features that specifically target the behavior of conventional hard disks. Features like Superfetch and Prefetch and ReadyBoot are designed to monitor files you access at startup and when you launch programs and then arrange them on the disk for optimal access. Because SSDs don’t have motors and spindles and platters and magnetic heads, they don’t benefit from those features and need to be handled differently. In fact, there are a series of steps that must be performed before an SSD can perform to its full potential on a Windows PC. Skip any of those steps and the results can be disappointing. My own personal experience bears this out. Back in October 2009, I bought a Dell Latitude XT2 with a 256GB SSD. One of the first things I did was to replace the Dell-supplied copy of Windows XP Professional with Windows 7 Professional. Disk performance was reasonably fast, but it certainly wasn’t jaw-dropping, and the disk score in the Windows Experience Index was stuck stubbornly at 5.9. I did a little research last summer and learned that a lot of Dell customers were experiencing the same disappointment with this particular hardware combination. The problem was that the hardware—a Samsung PB22-CS3—needed a firmware update to work properly with the advanced disk-handling features in Windows 7. That update had to come from Dell, and as of last July, it wasn’t available. A third-party utility, CrystalDiskInfo, confirmed that this disk did not offer support for the TRIM command, which is one of the key requirements for proper SSD operation. (Using the TRIM command allows the system to properly erase blocks of data in the background; for an explanation, see this excellent article by Anand.) Windows 7 supports the TRIM command natively; earlier Windows versions don’t. Over the holidays, I decided to check again and was pleasantly surprised to learn that Dell had released a firmware update for this drive several months earlier. Because the firmware update wipes out all data on the drive, I had to do a clean install of Windows 7. The performance difference was like night and day. And benchmark results show why. Here are the Windows System Assessment Tool (WinSAT) results from July 2010 (original OEM configuration) and then from December 2010 after updating the SSD firmware and installing the latest Intel storage drivers: Disk throughput (bigger=better) Original Optimized Sequential Read (MB/s) 151.9 219.39 Random Read (MB/s) 10.77 130.25 IO/Responsiveness (smaller=better) Original Optimized Average IO Rate (ms/IO) 4.29 1.14 Grouped IOs (units) 15.43 8.94 Long IOs (units) 36.69 2.65 Overall Responsiveness (units) 566.01 23.72 Disk score capped at 5.9? Yes No With the new setup, the disk subscore in the Windows Experience Index jumped from 5.9 to 7.4, and the difference is noticeable. The system is 13 12 times faster in random reads, which is what makes the most profound difference in everyday operation. Updating the firmware was the key that unlocked the performance of this device, but it isn’t the only crucial step. On the next page, I list the steps you need to go through to ensure that an SSD performs properly with Windows 7. via ZDNet > continue to page 2

if you want to store the data on the network then you use a State Migration Point (SMP) and there are some samples of that (task sequence) here http://www.windows-noob.com/forums/index.php?/topic/1633-sample-xp-to-windows-7-task-sequences/

I havn't tried it, but this is similar, http://www.deployvista.com/Default.aspx?tabid=36&EntryID=65

Test Drive App-V via Online labs Overview: The following scenarios are used to show the end-to-end process of creating, publishing and delivering a virtual application: * Sequence * Publish * Deliver a Virtual Application using the App-V Full Infrastructure https://www.microsoft.com/resources/virtuallabs/step1-technet.aspx?LabId=42fc6d00-05d4-48a9-92fa-71bedf5572ca&BToken=reg

can you bring up a command prompt and verify that you actually have a valid ip address during the build and capture and at the point it fails,

looks like dns or network issues - see below:- are you capturing this in a lab or on a production network ? can you verify if network access is still working at this point (command prompt, ipconfig etc...)

can you post your logs here please ? including the windowsupdates.log

that's your problem, in package status or in the Task Sequences references tab, find out what package that is (DC100008) and verify that you have it updated to your distibribution points.

please attach your log files here

have a read of this post for ideas http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/4c87b3e9-0520-443a-b5fd-c6e466477655/ namely:- 1) Did you set up the reporting point correctly? Does it show any errors? 2) Is the account you are using a member of the SMS Admins and/or the SMS Reporting Users Group? 3) Does the account (direct or via group membership) have at least read permission on the Report class? 4. have you also added "read" rights for the site object?

it's probably just an Obsolete record (when a computer is reimaged the old record is marked as obsolete), obsolete records are deleted automatically by the delete aged discovery data under site maintenance/tasks

you need to remove any gpo's that are pointing to a wsus or even a sccm sup, the installation of the sccm client will take care of updating the registry on the client with the address of the active sup

welcome, great to see the lurkers joining in

what do the ClientLocation.log and locationservices.log files say

no you dont, but with MDT integration you can utilise the MDT scripts folder and the scripts therein, very useful

With Microsoft well at work on the next version of Windows — more specifically with Windows 8 M2 development underway — many are hoping for a build to escape Redmond and leak upon us. The build may very well have escaped Redmond, but not to the general public, but through a chain of under-the-table passing from one trustee to the next. DeviantArt user Misaki2009 with ties to the Russian leaking community has published the following screenshots of 6.2.7867.0.101020-1800 on his dA page: While there is a chance that these shots may be forged, GeekSmack strongly believes that they are legitimate screenshots of Windows 8 Build 7867, which was the build demonstrated at CES. As you can see, a build of IE9 allowing tabs to be situated beneath the address bar is present in these shots, as Microsoft are compiling internal IE9 builds with such functionality. The dA user who published the shots is not willing to leak or share the build with anyone, stating that we must “wait ’till will leak on the web from Zukona or Canouna”. While 7867 is a very early build with barely any visual changes, the significance of this news is that builds are starting to escape the grasp of Redmond. For leak enthusiasts, this news means that unofficial 8 builds may begin to surface on the Internet from the usual sources shortly. Stay tuned for updates. via > http://www.geeksmack.net/microsoft/windows-8-build-7867-screenshots-surface-hint-at-impending-leak?utm_source=twitterfeed&utm_medium=windows-noob.com

please take a look at this post from Jason as well - http://myitforum.com/cs2/blogs/jsandys/archive/2011/01/17/configmgr-client-hotfix-queries.aspx which references a recent blog from Microsoft about the client hotfixes - http://support.microsoft.com/kb/2477182 are you getting any further ?

its receiving the policy but nothing much more read this post for troubleshooting advanced client installation http://support.microsoft.com/kb/925282

doesnt look like it's run yet, how long have you waited and have you succeeded in deploying anything to this client yet ?

well have you seen the guides here, they are specifically for WDS in Windows Server 2008 http://www.windows-noob.com/forums/index.php?/forum/65-windows-deployment-services/ I need the full error that you are receiving, can you please post it here

is the client on the same vlan as the dhcp server ? did you configure any DHCP scope options ? did you configure WDS ?

take a look at this post, does it give you some ideas ? could be that the update worked and your still looking at old data, have you verified the client version ON a client (not from the server)

nice, did it work ? and did you do this on the primary or central ?

can you post the script you are testing with ?