anyweb

have you verified that the network access account works (perhaps locked ?)

hi Ray, if you cannot pxe boot due to network issues (what issues are they ?) did you know that you can create standalone media (cd) to handle that part of the boot process and the rest will be performed as normal ? the suggestions i offer are only one way of doing things, you could of course do it differently and use some HTA frontend which links to variables in your task sequence which in turn decides what gets migrated and when hth cheers niall

this is a good way (there are many) http://www.windows-noob.com/forums/index.php?/topic/1166-fully-automated-application-groups/

updated the link, thanks !

First off, if you have not downloaded the beta or seen some of the exciting information on Configuration Manager v.Next, Check out these links: * System Center Configuration Manager Site * System Center Configuration Manager: vNext Beta Site * Configuration Manager v.Next Beta Download on Connect * The System Center Team Blog * Configuration Manager v.Next VHD Test Drive Hierarchy wide Bootable or Prestaged media. One of the most requested features/capabilities around operating system deployment in Configuration Manager 2007 is the ability to have bootable media that is not tied to a specific site. A large portion was restrictions within the Configuration Manger 2007. In Configuration Manager v.Next we have spent time modernizing the infrastructure. The new hierarchy (based on SQL replication), is flatter, shares more data across sites and requires less infrastructure. As part of the hierarchy redesign, we focused on ways to update Bootable media to be dynamic and not require a specific disc per site. Let’s go over some of the details. How it works today: * In ConfigMgr 2007, an admin creates Bootable media. * During the creation, the media is generated with information specific to the site. * The computer is booted to media and contacts the default site Management Point for information about Optional and Mandatory Advertisements. How it works in v.Next: What needs to be setup: * A v.Next Hierarchy containing: o A Central Administration Site o Two or more primary sites (No need for hierarchy wide media if there is just one site =) * Boundaries defined for the Primary sites * Distribute the Boot Image that is needed for the media to one or more Distribution Points Steps to Create Task Sequence Media: * Select Create Task Sequence Media. * Select Bootable Media (or Prestaged media) * A this point you now have an option for Dynamic Media or Site Based Media. o Dynamic Media gives you the option to use one piece of media for the entire hierarchy. It will redirect the client based on its current location. o Site based Media keeps the parity with ConfigMgr 2007. It remains tied to a specific site. * When you select Dynamic Media, you now receive fields to select a Management Point. You can specify several Management Points for the media. This gives you a fallback if the first Management Point in the list is not available. When specifying the Management Points, keep in mind all clients using the media will contact the Management Points in the order specified for the initial request. The initial request is only a couple KB. How does it all work? * Client boots to the Bootable Media and the Management point you selected for the media is used for an initial request. * The client send the Management Point a request takes networking information about the client. * The Management Point performs a server side look up based on defined boundaries to determine the correct site for the client. * The Management Point returns the default Management Point of the correct site for the client. * The client contacts the default Management Point for the correct site for available or required deployments (formerly Advertisements). * The client processes all further communication with the correct site to process its deployments. John Vintzel Microsoft Corporation | Program Manager | System Center Configuration Manager | twitter: jvintzel via > http://blogs.technet.com/b/inside_osd/archive/2010/08/18/v-next-beta-1-feature-hierarchy-wide-bootable-media.aspx?utm_source=windows-noob.com&utm_medium=twitter

yes it will re-appear as soon as the discovery kicks in, did you Delete or Delete Special ?

maybe the files themselves are blocked (exe's) to unblock them right click and choose unblock or copy all the drivers to a FAT file system then back to the drivers folder and then repackage them. there is one other option, in the Apply Drivers package step, select 'Do unattended installation of unsigned drivers on Versions of Windows where this is allowed@ but at least you are getting somewhere,

i dont see any pictures, just mht files...

did you have to change any perms on the xml file ?

did you see that ^

hmm i simply used the IRRT step (instead of both) and it installed all drivers perfectly on a Dell E4200 here device manager i didn't do Jason's step but it may help you, i don't have the same hardware as you so cannot test that model. during the install a c:\_SMSTasksequence folder is created as normal and in there was drivers, along with several other folders number 1 to 31 or so, in addition there was a TEXTMODE folder with some iastor drivers *inf sys etc* and a TextSetup.OEM file which contained the following text

did you create a package from definition for the client package ? did you define a network access account with full local administrative permissions on those clients ?

Hello everyone, we wanted to get this information to you as soon as possible. We now have released a fully configured virtual machine for ConfigMgr v.Next Beta 1. Based on a Windows Server 2008 R2 x64 OS, this is a fully built virtual machine ready to import into your Hyper-V environments. This is something the ConfigMgr team has done for a few major releases, starting back at the ConfigMgr 2007 RTM timeframes. We are really excited to get you guys this type of access, to help you evaluate the latest and greatest ConfigMgr v.Next release. We are also in the process of uploading the hands on labs for ConfigMgr v.Next as well, look for that announcement soon. Some resources for you: * VHD Test Drive - System Center Configuration Manager v.Next on Windows Server 2008 R2 – link * VHD Test Drive - System Center Configuration Manager 2007 R2 - link * Configuration Manager vNext Beta 1 evaluation download – link via > http://blogs.technet.com/b/systemcenter/archive/2010/08/18/configuration-manager-v-next-beta-1-now-on-vhd-test-drive-program.aspx?utm_source=windows-noob.com&utm_medium=twitter

in the system management container in AD, do you see that it has populated with site info ?

can you post the smsts*.log files please ?

ok assuming you have added ALL those drivers into the package as per the link (had to re-read your post, sorry) do you see the drivers listed anywhere on c:\drivers\? i'll try and do a test here in my lab but it may be tomorrow before I post a result

well you could pull the capture task out of a build and capture task sequence, that is essentially taking a wim backup of a system

you could script a full backup (to wim file), not hard to do but requires a lot of storage for the wim file and/or network speed. You should be able to deploy sp3 without having to do this though so why do you think it will fail ?

interesting result and thanks for confirming

check in c:\windows\temp

post the smsts.log file here and we'll check it

try this out http://www.microsoft.com/downloads/details.aspx?FamilyId=B9FB478A-EC98-47F2-B31E-57443A8AE88F&displaylang=en

you shouldnt be hard specifying the path to the msi like so try something like this instead msiexec.exe /qn /i "Tools.msi"

Microsoft's web browser, Internet Explorer, today celebrates its fifteenth birthday as the Redmond-based giant prepares to unveil the next version, Internet Explorer 9. The web browser, the world's most used (but arguably most hated) according to recent NetApplications figures, was born on the 16th of August, 1995 when version 1.0 was made available to the public. The first version of IE was based off Spyglass's Mosaic application -- which Microsoft originally licensed but was eventually used to form the code basis for future versions of IE. It wasn't until version 3.0, released on August 13, 1996 that Microsoft first began bundling the web browser into Windows, making it the default web browser and exponentially growing the browsers market share, pushing out market leader Netscape Navigator. Since the debut of Mozilla Firefox in 2004, it's been a tough old slog for IE, which is now facing an increasingly competitive browser field with competitors such as Google Chrome, Opera and newer editions of Firefox, that has left the browser facing a slowly eroding market share. And just last year Microsoft was also faced with a European Union decision to force the company to stop making IE the default Windows web browser in Europe last year, with the company now showing users a "browser ballot" when they turn on newly purchased Windows computers for the first time. The future is looking better for IE however, with version 9 of the browser widely expected to be released later this year with a possible beta as soon as September 15. IE 9 is expected to better conform to web industry standards such as CSS, and will reportedly feature a user interface similar to that of Google Chrome alongside for the first time a downloads manager. via > http://www.neowin.net/news/microsoft-celebrate-internet-explorers-15th-birthday

i havnt tried it yet, so please tell us how it goes,