anyweb

good stuff, I'm using something similar, what i'd like to see you add to this post is a description of the step(s) in the task sequence where you call this, plus if you can, include the reg files mentioned in the script, cheers niall

Microsoft have released a whitepaper on using the R3 release more info here > White Paper on Power Management Capabilities which is part of ConfigMgr 2007 R3. You can read and/or download the paper from the link below, http://technet.microsoft.com/en-us/library/gg398008.aspx

Step 7. Create the Configmgr Client from Definition Package In Software Library, right click on Packages and choose Import Click Next at the Welcome wizard, and select Configuration Manager Client Upgrade from the list select always obtain files from a source directory enter the client directory of your site server typically \\server\sms_xxx\client where xxx is the sitecode click next at the summary and review the confirmation of wizard completion click close to finish. Now don't forget to Update the Client from Definition Package to the Distribution Points, in Software Library, click on Packages, right click on your Configuration Manager Client Upgrade package and choose Distribute Content click on the Drop down Add menu, select Distribution Point select only the normal DP and click ok

have you made sure the firewall isnt blocking anything ? that the client isn't obsolete ?

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. In Part 4 we configured the client Agents and deployed the vNext Client. In Part 5 we deployed an Application to All Users. In Part 6 we added Windows Deployment Services, added the PSP role, added the Windows 7 Enterprise image, and updated our boot image for Deploying Windows 7. Next we will continue with this process, and as part of that we need to utilise the built in Build and Capture Task Sequence. Step 1. Create Build and Capture Task Sequence Perform the following on the vNext server as SMSadmin In the Software Library, Right-Click on Task Sequences and choose Create Task Sequence from the wizard that appears, choose Build and Capture a reference operating system image Fill in details about the image and select the X86 boot image we udpated previously when the Install Windows Operating System window appears click on browse and select our Windows 7 X64 Enterprise image select Always use the same administrator password and type in an admin password as this is Build and Capture, it's recommended best practise to be a member of a workgroup (don't join the domain) for the Install Configmgr Client step, click on browse and select our ConfigMgr Client Upgrade Package (if you don't have this package see here for details of how to create it) we have not enabled the SUP yet, so do not install software updates leave applications blank as this is Windows 7, no system preparation package needed (it's included with the OS), so just click next fill in some details about the image enter the capture wim file name (path) and user details to save the capture with Click Next, Next and review the confirmation. Step 2. Enable the Network Access Account We need our Network Access Account set in order to copy packages in WinPE. We have already created the user in Active Directory (NAAUser), now lets add it to vNext. In Administration, click on sites, then select your site and right click, choose properties. Click on the Component Configuration tab, software distribution, edit enter the network access account details (click on the network access account tab), and click ok, ok

ok i've mailed you my VBS script, take a look at how it's done and try and replicate it in your environment. cheers niall

short answer, you don't. use the best practise method of Build and Capture Windows 7 to build (and then capture) a reference (gold) image containing the big apps (office 2010 etc) that you want in your image, once done you'll have a captured WIM file. Create another task sequence (deploy windows 7) to deploy this captured wim and this task sequence can install all your dynamic changes, customisations etc. this method will save you hours of time and is very repeatable, automatable, etc. in fact, it's the method described right here cheers niall

Step 5. Distribute the Boot image to DP's Select boot images in the left navigational pane, select the X86 boot image and on the right, right click on the Distribute Content. click on the Add drop down menu, select Distribution Point as this is a boot image, select both the normal and PXE dp's Click OK and OK again. Step 6. Update the Boot image with command support Select boot images in the left navigational pane, and on the right, right click on the X86 boot image and choose properties. click on the Windows PE tab and place a checkmark in Enable command support, and optionally select a background for your Windows PE boot image by browsing to a picture Click apply and answer Yes when prompted and continue through with the wizard until you are done Note: Repeat the above process for the X64 boot image otherwise you may get your PXE clients getting a Contacting Server: 192.168.3.10.... ...... problem later on. (check the SMSPXE.log file for errors after a PXE boot attempt - and you'll probably see Warning: Matching Processor Architecture boot image (6) not found)

i'll take a look at my script tomorrow

welcome to the forums ! and thanks for the kind words as regards the t-shirts i really need to do some more designs, I wear them regularly, today I wore my favorite, Catastrophic Failure if you do get one (or more) please post a photo of you (or whoever) in it, that would be excellent ! cheers niall

when i packaged visual studio 2008 in my current job, i wrapped the installer in a vbs script which installed all the prerequisites prior to installing the main application, are you doing something similar ?

verify if Trend micro av software is installed on the server, if so disable it and try again - see here

Step 4. Add the Windows 7 Enterprise Install Image In the Wunderbar, select Software Library and expand Operating Systems, right click Operating System Installers and choose add operating system install package browse to the network share we you have previosly copied the contents of the Windows 7 Enterprise DVD fill in some details about the image and click through to the confirmation screen Once completed we need to distribute the image to our DP's, so click on Distribute content in the Action pane Click on the drop down menu Add, then select distribution point select only the vnext dp as this is an image file (and not a boot image) click ok

copy the batch file to a folder, in configmgr software distribution, select packages right click, choose new package, point to the folder, done. Distribute it to a dp. thats it

R3 requires SP2 & KB977384, can you confirm if both are installed prior to attempting to install R3 ? also is the sql db on these boxes or off ? are you only getting errors when trying to install the hotfix (prior to installing R3 ?)

you can use the supplied task sequence and download the supplied batch file (which will be used in a separate package) cheers niall

Step 3. Add the PXE Service Point Role In the Wunderbar, click on Administration and select Site Roles, right click it and choose Create Roles. When the New Site Role Wizard appears, click on Browse and select our vNext server, As we will use data migration at some point, select the State Migration Point role in addition to the PXE Service Point role, Answer yes when prompted configure the State Migration Point by clicking on the yellow starburst enable Unknown Computer Support and take note of the notice leave the PXE database settings as they are click next through the summary and review the confirmation once done

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. In Part 4 we configured the client Agents and deployed the vNext Client. In Part 5 we deployed an Application to All Users. Now we will learn how to Deploy Windows 7 Enterprise using vNext. As we will be using PXE boot, we need to get our server ready to support this, so we will add the Windows Deployment Service which is required. Step 1. Add and configure Windows Deployment Services Perform the following on the vNext server as SMSadmin Start Server Manager and click on Add Roles When the Add Roles wizard appears, click next Select Windows Deployment Services and click next click next at the overview accept the defaults for Role Services Click install at the confirmation screen and review the results click Close. Step 2. Configure Windows Deployment Services Click on Start, Administrative Tools, Windows Deployment Services to start the WDS console. Expand the + beside Servers. You will see a yellow exclamation mark meaning that the WDS service is not yet configured. right click on it and choose Configure Server click next and change the path of Remote Installation Folder Location to suit your environment eg: D:\RemoteInstall set the PXE response setting to Respond to All client computers... de-select Add images to the server now and click Finish. Windows Deployment Services is now configured

can you post your CreateTSMedia.log file please

Users of Twitter will no doubt have noticed quite a few tweets about SCCM 2012 The new name for what we know as vNext has been released, System Center Configuration Manager 2012. This was announced today during the session MGT202 at TechEd:Europe in Berlin. So that's it, it's official, Microsoft have announced it at Teched. R.I.P vNext and welcome to System Center Configuration Manager 2012 Not only has the name been revealed but TAP nominations for beta 2 are underway. via > http://blogs.technet.com/b/systemcenter/archive/2010/11/09/announcing-configuration-manager-v-next-official-name.aspx?utm_source=twitterfeed&utm_medium=twitter

the error you are getting means that it is unsupported can you post your SMSTS.log file please ? and explain what is the step you are using to flash the bios (what hardware are you testing on)

thanks for sharing the info !

whats the last thing you see on the screen ? any error ?

Step 5. Review the application being Deployed. On the vnext server itself, logout as SMSadmin and login as TestUser (we created this user in part one). After our appointed time, the application will be made available to the User and the user will be notified with a New Required Software notification click on the message to review the details and after a few moments the software will install itself silently In the next part of this series we will dig even further into Deploying Applications

Step 3. Enable BITS on the Distribution Points Before we can deploy our software we need to enable BITS on our distribution point(s). In the Wunderbar, select Administration and select Distribution Points from the navigation menu. Select Properties Under Communication settings, place a checkmark in the Allow Clients to... section Click OK. Step 4. Deploying the Application to a User Now that we have created an application, and customised it somewhat, we want to Deploy it (think of it as creating the Advertisement). Select Software Library in the Wunderbar. Right click on our application, and select Deploy The Deploy Software Wizard appears to the right of collection, click browse At the top of the Collections screen select Users (Devices is selected by Default), then select the All Users Collection, click Ok when done Click Browse to the right of Distribution Points The Select Content Server dialog box appears allowing you to configure the distribution point(s) for our application, select Change to Distribution Points. select our vNext server from the list and click ok. click Next, on the next screen we get to choose between Available and Required for Intent (this is the equivalent of Optional and Mandatory), choose Required. we can choose the Schedule for this deployment, so set a schedule and click Next for User Experience click on the drop down menu and select Show All Notifications Leave the Alerts as default click next at the summary and review the progress and finally the confirmation screen (deployment processing complete). click Close to exit.