anyweb

Part 2. Download and install Webdav for IIS 7 Note: If you are using Server 2008 R2 which has Webdav 7.5 then read this post first An important note from Microsoft:- pick your version below Microsoft WebDAV Extension for IIS 7.0 (x64) or Microsoft WebDAV Extension for IIS 7.0 (x86) Accept the license agreement and let it install itself Once we have installed Webdav, we need to Enable WebDAV Publishing Using the IIS Manager. Enabling WebDAV Publishing Using the IIS Manager. Startup IIS Manager and in the Connections pane, expand the Sites node in the tree, then click the Default Web Site, then double-click the WebDAV Authoring Rules icon. Click enable webdav in the Actions pane on the right side Once you've clicked it it will then say 'Disable webdav' so be sure not to click there again, now we need to click the Add Authoring Rule task in the Actions pane and set your options as below That's it, you've now enabled WebDAV authoring in IIS 7. We will return to Webdav later in the guide, if you want to do them now then read Step 1 of this post or just continue with the below as we will get to it later anyway.

here's a working SIF and here's the install.bat file referenced in the SIF to install apps/drivers that can't be installed via the SIF

here's a working SIF file and here are the contents of the install.bat file referred to in the sif

The following Step by Step 3 part guide to Deploying Windows Server 2008 using SCCM 2007 covers all the steps necessary to get you up and running in no time at all, screenshots and helpful text show you how to do IT including preconfiguring roles such as Active Directory (ADDS) and DNS. This 3 part guide is aimed at those of you who can succesfully deploy applications (such as Microsoft Office or Firefox) and Operating Systems (such as Windows Vista SP1 and Windows XP sp3. You'll need to be familiar with Microsoft SMS or SCCM and understand what packages, advertisements and collections mean, the guide will however link you to other guides to bring you every step of the way down the entire path. Part 1. * Add new Operating System Install Package * Import new Task Sequence Part 2. * Create and then Update distribution points for the MDT Server packages * Editing the Task Sequence * Adding Server Roles and Features Part 3. * Create a new collection * Advertise the Task sequence to a collection * Add server to collection * Set the IP address as a variable * The Deployment * Troubleshooting PXE errors The guide above has taken a lot of time to document and I'm quite sure that you will find it helpful (lots of screenshots of every step..) good luck, cheers anyweb

With all Windows PE problems and errors that you may (most likely will..) encounter during SCCM OSD Deployment, you'll want to enable the F8 feature in your Windows PE boot images, which allows you to do some basic testing by giving you access to a CMD prompt within the Windows PE session So how do you enable this troubleshooting feature ? locate your boot images in the Operating System Deployment section of SCCM right-click on your chosen boot image (for example 32 bit) and choose Properties Select the Windows PE tab from the properties, and place a checkmark in Enable command support then click apply Don't forget to re-distribute your boot images to their Distribution Points after making this change, and give them some time for doing so. Once distributed, when you PXE boot your clients and you want to troubleshoot any Windows PE deployment issues, press F8 once Windows PE has loadedand you'll get a command prompt. In addition this will keep Windows PE operational in situations where whatever error you were getting would cause Windows PE to reboot with no warnings thereby giving you a chance to read the logs and perform troubleshooting. SMSTS Log File location If the task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\Logs If the task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %Temp%\SMSTSLOG If the task sequence completes when running in Windows PE: <largest fixed partition>\SMSTSLOG Note: In addition, the logs for SCCM (during the Windows PE phase) are stored in X:\Windows\Temp\SMSTSLog\ and C:\SMSTSLog and C:\_SMSTaskSequence. More often than not, the Log file you need to be reading is the smsts.log file to see what is going wrong in your deployment... After Windows PE is done and Windows installation is complete you can find the logs elsewhere such as C:\Windows\System32\CCM\Logs or C:\Windows\SysWOW64\CCM\Logs for 32bit and 64bit respectively. In those directories you'll find a log file named (for example) smsts-20081125-122856.log, the actual name of the file will change based on the date/time that you do the deployment. I've enabled Command Prompt Support, now what ? Once command prompt support is enabled you've got lots of options for troubleshooting. network testing (ipconfig/ping...) or map a share such as net use h: \\servername\share If the user you are trying to logon with is a DOMAIN user then use this format Enter the user name for 'servername': DOMAIN\domainuser disk testing (diskpart...) read LOGS to look for errors that explain why the deployment is failing... using notepad Troubleshooting Links List of Custom Error Codes for Configuration Manager 2007. Troubleshooting tips on Technet see here Troubleshooting made easy > http://blogs.msdn.co...e-easy-way.aspx Sample Troubleshooting Session The Below is taken from a real troubleshooting session... During the Windows PE phase of a Windows Server 2008 Deployment I got an error In the example above it's complaining about a Validate issue in the Task Sequence deployment of Windows Server 2008, looking at the log file located at X:\Windows\Temp\SMSTSLog\ztivalidate I can see that it's complaining about the speed of the processor (because this is a Virtual Machine) so to fix this problem required editing the Validate section of the Task Sequence and removing the check for CPU speed

You need to have completed Part 1 and Part 2 before starting this part. Create a new collection In ConfigMgr right click on Collections and choose new collection for collection name call it Deploy Windows Server 2008 and fill in the comments for membership, click next and ok to the warning, for advertisements and security click next also click close once done and you should see your new empty collection listed. Advertising the Task Sequence to a collection Under the Computer Management node in SCCM ConfigMgr, right-click the collection we have just made (Deploy Windows Server 2008) and choose advertise task sequence fill in the description Build Task Sequence, ..... the task sequence should then be selected by clicking on Browse, select the Server Task Sequence we made earlier select Make this task sequence available to both media and PXE Alternatively, right click the task sequence itself and choose 'advertise' to get to this same step. Schedule Set your schedule depending on whether you are in a Lab or Production Environment. For a Lab Environment Make the Task Sequence mandatory by clicking on the yellow star and select As soon as possible. Select ignore maintenance windows when runing program and allow system restart, set the program rerun behaviour to always rerun program so that we can rerun the task sequence over and over as we require for testing. For a Production Environment In a Production environment set the advertisement from Mandatory to Optional, this gives us less risk of an accidental deployment but also introduces the possibilty of choice. if you want to remove choice then keep the advertisement mandatory but change the program rerun behaviour to never rerun (see below screenshot). Distribution Points set to Access content directly from a distribution point as we will be wiping the hard disc as our first task in the task sequence Interaction adjust interaction to suit your needs Security and security review the summary and click next to proceed, then verify that all went well in the confirmation window. at this point right clicking on our chosen collection and clicking on the Advertisements tab will list the Task Sequence we just added. Add server to collection Under Operating System Deployment, right click on Computer Association and choose import computer information, select Import Single Computer (if you want to import multiple computers select using a file instead) in the example below i'm just giving the server a name and using it's MAC address click next to the data preview and then for Choose Target Collection, hit browse and select the collection we made above click next until the wizard is complete

You need to have completed Part 1 before starting this part. Create and then Update distribution points for the MDT Server packages Now that we have created the Task Sequence, packages files and folders necessary to support the Server deployment we need to make sure to create and then update distribution points for each MDT Server package, the Configuration Manager Client Installation package has already been pushed out to the distribution points so we don't need to do that again. Expand Microsoft MDT Server Settings files and right click on distribution points, click new distribution points and when the wizard starts click next. Select the standard distribution point only and click next, then close when done. Right click the Distribution point and choose upadte distribution points, answer yes at the confirmation screen Repeat the above (create distribution points and then update them) for Microsoft MDT Server Source Files.

Please note that this guide is designed to get you Deploying Windows Server 2008 with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums. In a production environment please consult Technet for best practise, see below links: Operating System Deployment: Operating System Deployment in Configuration Manager Overview of Operating System Deployment Configuration: System Center Configuration Manager 2007 Best Practices: Configuring Configuration Manager Sites for Best Performance Checklist for Security Best Practices Best Practices for Central and Primary Site Hardware and Software Configuration Best Practices for Operating System Deployment Add new Operating System Install Package We will make an Operating System install package, this package will contain the files necessary to support the installation of the Windows Server 2008. In SCCM ConfigMgr expand the Operating System Deployment node and select Operating System Install Package from the list of available options., right click and choose Add Operating System Install Package point to the UNC path of the root of our Windows Server 2008 DVD (which we copied to a network share earlier) eg: \\WIN-AE2V1IRN067\iso\Server 2008 fill in the details click next and review the summary and then click close now that we've added this package, we again need to distribute it to our distribution point, however we will add it only to the normal distribution point and not the pxe one. Expand the Operating System Install Package node we've just added, right click on Distribution Points and choose New Distribution Points. click next when the wizard appears and select the first of the two dist points, then next again click close when done.

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