anyweb

does this help ? Dell SCUP

sccm will configre wds to do the multicasting, just make sure wds is installed first and see here How to Enable Multicast for Operating System Deployment and here's another guide for setting up MultiCasting in SCCM 2007 http://blogs.msdn.com/steverac/archive/2008/10/19/setting-up-multicasting-in-sccm.aspx

what OS is on the HP laptops windows 7 Professional or ?

This guide assumes you have integrated MDT within SCCM, once done, startup your ConfigMgr console. Disable the MDT Boot Wizard Note: When creating the HTA FrontEnd boot.wim below, we will use the a Media Hook and those Media hook files are copied from your MDT installation folder, eg: C:\Program Files\Microsoft Deployment Toolkit\SCCM. If you want to disable the MDT wizard which prompts you for a MININT-xxxxxxxx computername, then do as follows:- Locate the folder, and find a file called SCCM_Bootstrap.ini, Open the file in notepad and change [settings] Priority=Default [Default] SkipWizard=NO to [settings] Priority=Default [Default] SkipWizard=Yes save the file Create boot image using Microsoft Deployment Expand the OSD section of ConfigMGr and right click on boot images, choose Create Boot Image using Microsoft Deployment Enter the UNC path and make sure the folder you point to is Empty otherwise the wizard will fail fill in the General Settings for Image options select Add Media hook files to enable deployment Wizard for this boot media in the Extrafiles field point to your ExtraFiles folder, in mine I have copied Trace32.exe and also point to the UNC path to your custom background review the summary and click Next this takes some time so be patient Enable Command Support (F8) Once done, enable command support by right clicking on your new Boot.wim file in boot images, select the Windows PE tab Distribute your Boot image Finally don't forget to update your HTA FrontEnd boot.wim to your distribution points, once done you can immediately add that boot image to an existing task sequence or create a new task sequence which will use the HTA frontend boot image we created above.. To see how to display your HTA within a task sequence, click here.

The Windows® 7 operating system and its default browser, Windows® Internet Explorer® 8, offer many exciting new features and benefits. However, organizations may find that some of the older applications they rely on are not yet functional or supported in the new Windows 7 operating system. Microsoft provides several alternate ways to create a virtual operating environment on which you can run earlier versions of Internet Explorer. This white paper provides information to help you select the virtualization alternative that is appropriate for your organization. System Requirements * Supported Operating Systems: Windows 7 For your convenience, this document has been provided in both Microsoft XML Paper Specification (XPS) format and Adobe Portable Document Format (PDF). Please ensure you have installed the appropriate viewer for the format you choose to download. Instructions Download this document to learn about Internet Explorer virtualization alternatives that are appropriate for your organization. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=495934c8-5684-451c-a16e-5ceb50706a42#QuickInfoContainer

how odd, you are the second person in less than a week with the exact same problem, what version of windows 7 is this and tell me more about what you've done to get it to this stage, please include your SMSTS.log file

as you guys are having so many problems with capturing windows 7 I will try and do a webcast to explain it better, watch this space....

and make sure that 'allow this program to be run whether or not it is advertised' is selected, the task sequence will need that step removed, then yuo can save the ts, then edit the ts again to re-add the corrected package, unfortunately it doesn't refresh on the fly

Advertising the Task Sequence to a collection Under the Computer Management node in SCCM ConfigMgr, right-click the collection we made earlier (Build and Capture (Vista)) and choose advertise task sequence fill in the description 'Build Task Sequence', ..... the task sequence should then be selected by clicking on Browse, and finally 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 next set your interaction settings and security settings review the summary and click close once complete. continue on to Part 5 For extra reading, checkout the following blog with detailed info on adding 3rd party Gina, troubleshooting tips, Intel ICH8USB drivers explained and lots more digg it !

correct the data is only as good as the last scan, you can always force a scan on a client to get up to date data

very odd, are you logged on when you do this ?, ive tested it in IE and Firefox and no problem logged on or off

Ever struggled with a 0x0000007B BSOD when deploying a Windows XP SP3 image? Struggle no more, here is a working driver set and sysprep mass storage section for most current hardware models... Instructions for adding the sample files to MDT 2010 Lite Touch In these steps I assume you have a deployment share in the D:\MDTProduction folder, Windows XP Pro SP3 (full source) imported to the D:\MDTProduction\Operating Systems\Windows XP Pro SP3 Eng x86 Unattend folder, and that you created a Task Sequence named Windows XP Pro SP3 Eng x86 Unattend Task Sequence. Step 1 - Download sample files 1. Download and extract the sample files to D:\Setup\Sample Files (http://www.deployvista.com/Repository/tabid/71/EntryId/62/DMXModule/396/Download/attachment/language/en-US/Default.aspx) Step 2 - Disable the builtin add mass storage action 1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence and select Properties. 2. In the Task Sequence tab, configure the Windows XP Pro SP3 Eng x86 Unattend Task Sequence with the following setting, 3. Disable the Capture Image -> Add mass storage drivers to sysprep.inf for XP and 2003 action. 4. Click OK. Step 3 - Configure sysprep.inf 1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence and select Properties. . 2. In the OS Info tab, click Edit sysprep.inf. 3. Edit the mass storage section using the D:\Setup\Samples Files\Sysprep\storage.txt sample Step 4 - Add the drivers 1. Using Explorer, copy the D:\Setup\Sample Files\$OEM$ folder to the D:\MDTProduction\Operating Systems\Windows XP Pro SP3 Eng x86 Unattend folder Step 5 - Build and Capture 1. Run the Windows XP Pro SP3 Eng x86 Unattend Task Sequence on a virtual machine. via Johan @ deployvista.com http://www.deployvista.com/Blog/tabid/70/EntryID/130/language/en-US/Default.aspx

of course, what i havent pointed out is you can mount the wim using imagex and make physical changes to files etc, but, in SCCM the recommended way is always to build and capture, and the entire build process should encompass all changes required before the capture, you can separate build from the capture..... to split up the process

well the first two windows are whats important, the last one is merely your version of windows server MMC, so, in the first screenshot it looks like the SCCM console is reporting as SP1, so whatever computer you are on verify that the CONSOLE is upgraded to SP2

can you show me a screenshot of what you are talking about so we are clear

probably means you are running the sccm console remotely (ie: separate to the sccm server) and the console is still at sp1, you will need to upgrade it to sp2

are you using an unattend.xml file in this deployment ? are you deploying windows 7 via standalone cd ?

got this email today The System Center Configuration Manager team would like to announce that the following has been released and available for download: Configuration Manager 2007 R3 Beta This is the official Beta release for Configuration Manager 2007 R3. Yesterday at the Microsoft Management Summit, Brad Anderson announced during his keynote the release of ConfigMgr07 R3 Beta. Power management is at the core of the R3 release, it addresses the need that many organizations have to monitor and reduce the power consumption of their computers. ConfigMgr07 R3 Power Management leverages the power management features built into Windows to apply relevant and consistent settings to computers in the organization. There are three major components to power management in ConfigMgr07 R3: 1. Monitoring and Planning: Power Management collects information about computer usage and power settings for computers in the origination. Reports are provided to allow the administrator to analyze this data and determine optimal power management settings for computers. 2. Enforcement: Power management allows the administrator to create power plans which can be applied to collections of computers. These power plans configure Windows power management settings on computers, and different power plans can be configured for peak and non-peak working hours. 3. Compliance: After applying power plans to computers in the organization, the administrator can run reports to validate that power settings were correctly applied and to calculate power and carbon footprint savings across collections of computers. In addition to power management, ConfigMgr07 R3 will provide customers with enhanced scale and performance support (scale to 300K managed clients per hierarchy, delta AD discovery, dynamic collection updates), as well as enablement of further capabilities for operating system deployment. A full list of the R3 features can be found on Microsoft Connect at the “What’s new in R3” post. Navigate to Microsoft Connect today and download the ConfigMgr07 R3 Beta. Please review the Release Notes before performing any installation and the help (chm) file for specific deployment and supportability guidance. Feedback and Support: - All registered Open Beta users can submit bugs and make product suggestions using the Feedback tools provided on Microsoft Connect. This feedback is triaged daily by members of the Product Group. It is your feedback that helps drive feature changes and improvements. See the help link on the ConfigMgr MSConnect homepage for more instructions. - Newsgroups are a great way to post questions and receive general support for specific R3 related questions and answers. If you experience any issues with the download or the ConfigMgr Microsoft Connect site please contact, sccmtap@microsoft.com Regards, The Configuration Manager Customer Team

what version of Windows 7 are you trying to deploy ? what media did you use, double check that you havnt included the cd key...

ok from your log so, remove the Windows 7 product key from the task sequence and try again please cheers niall

are you trying to manually sysprep this machine ? it looks like it can't find sysprep.exe, so how did you create this task sequence ? here's your failure from the log

ok so it is not part of an SCCM task sequence ? and you are running it via a script ? if you run the same line as a local administrator does it work ?

the link is being fixed according to Johan Arwidmark, here it is in the meantime trace64.zip Rename trace64.bob to .exe cheers niall

no it doesnt need to be on the pxe share, please post your smsts.log file here and i'll take a look at it

did you redistribute the configmgr client package ? (right click it, choose update distribution points..)