anyweb

Welcome to Engineering Windows 7 Welcome to our first post on a new blog from Microsoft—the Engineering Windows 7 blog, or E7 for short. E7 is hosted by the two senior engineering managers for the Windows 7 product, Jon DeVaan and Steven Sinofsky. Jon and Steven, along with members of the engineering team will post, comment, and participate in this blog. Beginning with this post together we are going to start looking forward towards the “Windows 7” project. We know there are tons of questions about the specifics of the project and strong desire to know what’s in store for the next major release of Windows. Believe us, we are just as excited to start talking about the release. Over the past 18 months since Windows Vista’s broad availability, the team has been hard at work creating the next Windows product. ... We’re excited about this blog. As active bloggers on Microsoft’s intranet we are both looking forward to turning our attention and blogging energies towards the community outside Microsoft. We know the ins and outs of blogging and expect to have fun, provide great information, and also make a few mistakes. We know we’ll misspeak or what we say will be heard differently than we intended. We’re not worried. All we ask is that we have a dialog based on mutual respect and the shared goal of making a great release of Windows 7. Our intent is to post “regularly”. We’ll watch the comments and we will definitely participate both in comments and potentially in follow-up posts as required. We will make sure that members of the Windows 7 development team represent themselves as such as well. While we want to keep the dialog out in the open, please feel free to use email to steven.sinofsky@microsoft.com should you wish to. In particular, email is a good way to suggest topics we might have a chance to discuss on the blog. With that, we conclude our welcome post and ask you to stay tuned and join us in this dialog about the engineering of Windows 7. Steven and Jon The full article > http://blogs.msdn.com/e7/

The Windows 7 craze is barely over, and yet the internet is already buzzing with the next big thing from Microsoft: a project called Midori. The SD Times claims to have seen internal Microsoft documents detailing what Midori actually is, and they say it's the clean-break from Windows many of us have been waiting for. The SD Times article is heavy on the details, and quite technical, but luckily Ars Technica provides a more accessible summary of what Microsoft has in store for Midori. via osnews.com

what steps did you follow to setup DHCP in ipv6 mode ? if it was a guide then give me a link and i'll check it out do your vista clients have a firewall enabled ?

Part 2. Run the SCCM 2007 SP1 installation wizard. Click Next to continue and choose the default option which is to 'Upgrade...'. accept the license and click next decide if you want to participate in the CEIP let the wizard check for updates.... create a new local directory and then give that path to the wizard for the local updates to be stored... updates are downloaded (89 in my case...) you'll be told the update download is complete, and you'll get an upgrade summary clicking next will run the pre-requisite checker again ! but now you'll see a new button, Begin Install Clicking that will start the actual process (how long winded can it all get ?) and this process can take some time (no kidding...) so go make a cup of coffee... or 10 after what seems like an eternity the process will finish and you have to click next... if you liked this guide and would like to see more Free guides, then please DIGG it.

when you try to upgrade SCCM 2007 to SCCM 2007 SP1 by first running the pre-requisite checker, you may see a warning which states:- If you open the file ConfigMgrPrereq.log and look at the errors within, just before the above statement will be a line which reads something like this:- <08-10-2008 21:04:57> Failed to connect to registry for KB940848 with 203. If you have already applied the hotfix from Microsoft then you might need this workaround. The reason for the pre-requisite test getting confused appears to be that it is looking for a string in the REGISTRY but it doesn't match what it's expecting to find Using RegMon from sysinternals I logged the entire process while doing the pre-requisite checks and sure enough it fails to find some keys in the registry even though we have installed the correct hotfix (KB940848), the checker looks for the following key(s) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848 HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848\DisplayName However they are not found because when we installed the hotfix it placed them at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848-v3 as a workaround I created a new regedit file with the exact same info as the v3 one (I exported that key in regedit). Here's the file, rename by removing .txt and run to add this key to the registry. uninstallkb.reg.txt I then did a search and replace, and replaced -v3 with blank. Running the resulting reg file and then starting the pre-req checker again now finally removes the MMC warning from the list ! cheers anyweb

This guide was done on a Windows 2003 Server (sp2) running SCCM 2007 which in turn was upgraded from SMS 2003. As a result, your results may vary, if they do, post them here. Part 1. Run the Pre-requisite checks and fix the warnings/errors reported. First of all download the Service Pack 1 update and then run the EXE file which will unzip it to a folder of your choice (I chose to call the folder sccm2007sp1) Once unzipped you can burn that to a DVD or run the splash.hta file contained in C:\sccm2007sp1\SCConfigMgr07_UPD_EN Once it starts you can run the prerequisite checker to see what you need to fix before continuing... you will be presented with a prerequisite check I left everything as it was and clicked on OK once done you'll get a list of errors that need to be resolved such as below, double click on any one to see what the recommended action is and then action each one My first error told me that I needed to do as follows: as this was a hotfix i was pleasantly surprised to see that Microsoft now allow you to download the hotfix semi-directly, you have to enter your email address twice and input a number displayed on screen, you then get an email with the hotfix download details... So I downloaded the first one and extracted it with the password supplied in the email. While the hotfix installed I clicked OK on the prerequisite checker for SCCM 2007 sp1. Once the hotfix was done installing, it wanted a reboot, so I rebooted. And then I ran the SCCM 2007 SP1 prerequisite checker again by starting at the beginning and running splash.hta... This time however I was down to only 3 warnings Next up I had to do the following:- That brought up a page with 3 download links (xp/windows server and so on).... confusing, inconsistent ? yep.. but I got the following file WindowsServer2003-KB936059-x86-ENU.exe I must have been lucky because when I ran the SCCM sp1 prerequisite checker again, I was only shown 2 warnings (below) Next up was my MMC update Once installed, I ran the SCCM 2007 SP1 pre requisite checker again, it told me i still needed this fix, so I decided to reboot (the hotfix didn't request it), the reboot didn't help it still listed it as a warning... so I viewed the ConfigMgrPrereq.log file (stored in the root of C:\) and it had a line that read Failed to connect to registry for KB940848 with 203 that lead me to this post Using regmon from Sysinternals I found the missing key and made a reg file of it, if you want it make sure you've applied the correct hotfix first then:- As a workaround I've produced the following hack. FQDN Warning. As my SCCM 2007 site is mixed mode I chose to resolve this warning by doing as follows:- To fix the FQDN error try the following: 1. Start SCCM Console 2. Click Site Database 3. Click Site Management 4. Click on Site 5. Click Site Settings 6. Go to Site Systems 7. Click on SCCM Server (where State Migration Point is located) 8. Right click on “Configmgr Site System” 9. Click on Properties 10. In the "Specify a fully qualified domain name (FQDN) for this site system on the intranet” change the Intranet FQDN to something like my example here it was WINDOWS-DOBMTWV I changed it to windows-noob.sccm2007.local and clicked apply, after waiting a few minutes for SCCM 2007 to udpate itself I ran the pre-req checker again and finally, success !

Microsoft Deployment Toolkit (MDT) 2008 Update 1 is now available from here What’s New in MDT 2008 Update 1? MDT 2008 Update 1 includes new capability for OEM preload scenarios, a revised System Center Operations Manager Management Pack, bug fixes, and revised documentation. This updated version provides guidance in the .chm help file format only. If you need the guidance in .doc file format, you can download it here. MDT 2008 Update 1 enables deployment of the following Microsoft products: * Windows Vista Business, Enterprise, and Ultimate (32 and 64 bit) RTM and SP1 * Office Professional, Professional Plus, Enterprise, and Ultimate 2007 * Windows Server 2008 * Windows Server 2003 R2 (32 and 64 bit) * Windows XP Professional with Service Pack 2 and Service Pack 3 (32 and 64 bit) or Windows XP Tablet PC Edition Choosing the Right Version Microsoft Deployment Toolkit 2008 Update 1 is offered in two versions to support Solution Accelerator component installation on x64 or x86 hosts. Select the version that corresponds with your host hardware type. Both versions of Microsoft Deployment Toolkit support deployment of x86 and x64 Windows operating systems. The Quick Start and Getting Started guides for MDT 2008 Update 1 are available as a separate download on this page for those who want to quickly evaluate MDT by viewing condensed, step-by-step instructions for using it to install Windows operating systems. Send questions or feedback to us directly at SATfdbk@microsoft.com I cannot download MDT 2008 !!! Can't find the download any more ? don't worry, it's still available right here

the download (1gb) is available here System Requirements System Center Configuration Manager 2007 installed Please see the Configuration Manager 2007 SP1 System Requirement page for detailed requirements.

i'm sure we could get around this problem without the need to use a cd, have you tried diskpart at all ?

is there any chance you can remove the servers hard disc and replace it with one that DOESN't have grub on it and then re-run the WDS test, just to see if it works ok if it does then we know that we have to find a way to remove grub via WDS and my guess would be that will need to be done via diskpart

this sounds to me like wds is deploying ok but that it is NOT removing grub (the linux boot loader) if you mount one of these server hard discs do you see windows installed on it or not ?

what do people think of Windows Vista ? well..... how about what do people think of Windows when it's The Mojave Experiment

Ben is talking about manually editing a sysprep.inf file in a light touch installation (LTI) of Windows XP using BDD 2007 (Business Desktop Deployment), so this may be different to what you require, what are you trying to do exactly and how ?

hi, according to here its defined by what is in the Syprep section and Sysprep parameters You can use the following optional parameters with the Sysprep command in Windows XP: • -bmsd - Populates all the available mass storage devices in the [sysprepMassStorage] section. • -clean - Clears the critical devices database that is used by the [sysprepMassStorage] section in the Sysprep.inf file. does that help ?

to do this you need to be using Windows Server 2003, Windows XP or Windows Vista (Windows 2000 doesn't support it) open a command prompt and paste this wmic.exe path win32_NetworkAdapterConfiguration get /format:htable > win32_NetworkAdapterConfiguration.html This will create a new file called win32_NetworkAdapterConfiguration.html which you can open in a Web browser (IE please, Firefox won't render this correctly) here's a sample of the file win32_NetworkAdapterConfiguration.html Under the IPAddress column, you'll see the IP address of the current Network adapter, you may see many listed (PPOE and more) here's the same query in text format wmic.exe path win32_NetworkAdapterConfiguration get > win32_NetworkAdapterConfiguration.txt win32_NetworkAdapterConfiguration.txt as you can see from the samples they not only give the ip address but lots more info like MAC address and so on now, this will only reveal your LOCAL ip address, ie: if you are behind a router (or dhcp server) then that ip is the one it will reveal, so if you want your real WAN (internet or wide area network) ip address then you'll need another script... cheers anyweb

sounds like you've mounted it incorrectly can you give me the exact commands you used to mount the wim file using imagex ? please copy paste how you did it here and that should explain why you are getting access denied.... here's an imagex howto here cheers anyweb

hi again yes there are differences (not necessarily restrictions) resulting from what Vista dvd you used, please read this post to see what i'm talking about AND can you confirm that you are or are not seeing the list of available images, or do you just get an error, the more info you give me the better, but for now please consider either using the MSDN vista dvd OR editing the OEM copy and removing that pid.txt then try again cheers anyweb

hi and welcome i'll try and answer your questions, it should work just fine yes but you may need to add additional drivers your actual problem is that 'Windows could not display the images available for installation'' can you confirm what Windows Vista DVD you used to do part one, step one of this post was the Windows Vista dvd msdn, retail, OEM or something else ? cheers anyweb

more info > http://www.channelregister.co.uk/2008/06/2...indows_roadmap/

fast cars, sleepless nights, dumpsters, diggers and more (oh and Windows too) a good intro about how things came together in the early days, worth seeing

Microsoft is busy trying to convince us to use Vista, and rather than have its' userbase wait for Windows 7 it has compiled 5 reasons to deploy Vista (PDF) well at least it's not a docx !

here's a short video of a first look at Windows 7, it demonstrates the ability of Windows 8 to use touch screen technology in an interactive way...

yes the presence of the pid.txt file could indeed be borking things up as you describe, only one way to find out though and that's for you to test it i'm very interested in hearing if this solves the problem ! cheers anyweb

ok are you certain that the dvd you use to create the boot.wim file for this was the Dell Vista DVD or Microsoft's MSDN Vista DVD ? it should be the Microsoft one, of if you don't have access to it delete the pid.txt file found on the dvd as outlined here, you'll have to mount the wim file to do this, then make the change and save the change, the new wim file can then be imported back into WDS and tested... and.... from here if the above doesnt help and you are definetly using a MSDN or Microsoft DVD to create the original wim files then let me know cheers anyweb

in order to get Visual Studio working (for SQL 2005 Sp2) you need to download the following update from Microsoft Once downloaded, extract the file by running VS80sp1-KB926601-X86-ENU.exe. You'll be prompted if you want to upgrade Visual Studio 2005 to Sp1, you'll have to accept the EULA then the process will start... and after a while it'll all be done !