anyweb

this is great stuff keep sharing

I also saw the problem, as a workaround, don't enter any pxe password for now, that will work fine.

absolutely ! it's awesome, try it

Windows "Microsoft has updated the Windows Service Pack Blocker Tool Kit to include Service Pack 1 for Windows 7 and Windows Server 2008 R2. As has been the case with previous service packs, soon after SP1 hits the RTM milestone, it will first go out on Windows Update, and then eventually Microsoft will push it out via Automatic Updates." Users who don't want SP1 will be able to simply disable AU. Many businesses, however, prefer to keep AU on, but block the service pack so they can first test to make sure it works with all their software. The service pack blocker will allow them to continue having Windows 7 and Windows Server 2008 R2 update automatically without SP1. The tool is valid for 12 months following general availability of the service pack. After that, Microsoft will push out SP1 to everyone with AU on, regardless of whether it has been blocked. The tool kit consists of three components: a Microsoft-signed executable, a script, and an ADM template. All of them set or clear a specific registry key that is used to detect and block the Service Pack download from WU. Companies can choose the one that works best with their computer management infrastructure. Microsoft released the Release Candidate (RC) of SP1 for Windows 7 and Windows Server 2008 R2 SP1, two weeks ago. Microsoft says it expects to release the final version of SP1 in the first quarter of 2011. Microsoft typically updates the Service Pack Blocker Tool Kit two months before a service pack's release. If Microsoft sticks to this timeline, we can expect SP1 in January 2011. via > http://arstechnica.com/microsoft/news/2010/11/microsoft-releases-service-pack-blocker-for-windows-7-sp1.ars

if you do not set the site as a protected site system does it work ? are you getting an error during dp creation or after the event ?

is it out of disk space ? how did you create your dp's ? which guides were you following as a matter of interest ? (i'm running a series right now)

Step 3. Create New hyperV virtual Machine on your HyperV host, startup Hyper-V Manager, right click and choose New, Virtual Machine specify name and location give it 1024 mb ram set the network type to Internal Only set the storage size to 40gb choose Install the operating system later click Finish to close the wizard. When done, highlight the new vm in hyperv, right click and select settings click Add Hardware, choose Legacy Network Adaptor, click Add Change the Network to Internal Only from the Drop down menu, then select BIOS and ensure Boot from Legacy Network Card is first in the list Once done PXE boot the Virtual Machine (turn it on) and press F12 when prompted, if you see 'contacting server: 192.168.3.10....... then verify you distributed both boot images). at the welcome to the task sequence screen, press next select our Build and Capture Task sequence and off it goes this will be slow until you edit the partition disk 0 step and change the format to Quick Format and out image is being captured

Step 2. Deploy (advertise) the Task Sequence to the Unknown Computers Collection highlight our newly created task sequence, right-click and choose Deploy when the wizard appears, browse for the Unknown Computers collection, and make sure to place a checkmark in Make this task sequence available to boot media and PXE leave the schedule as it is set the distribution point settings as follows and continue through the wizard accepting defaults

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