Jump to content


Sign in to follow this  
anyweb

using vNext in a LAB - Part 7. Deploying Windows 7 Enterprise

Recommended Posts

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

 

create task sequence.png

 

from the wizard that appears, choose Build and Capture a reference operating system image

 

build and capture.png

 

Fill in details about the image and select the X86 boot image we udpated previously

 

ts details.png

 

when the Install Windows Operating System window appears click on browse

 

browse os.png

 

and select our Windows 7 X64 Enterprise image

 

win7.png

 

select Always use the same administrator password and type in an admin password

 

always use the same administrator password.png

 

as this is Build and Capture, it's recommended best practise to be a member of a workgroup (don't join the domain)

 

workgroup.png

 

for the Install Configmgr Client step, click on browse

 

install configmgr client.png

 

and select our ConfigMgr Client Upgrade Package (if you don't have this package see here for details of how to create it)

 

package.png

 

we have not enabled the SUP yet, so do not install software updates

 

Dont install any software updates.png

 

leave applications blank

 

install apps.png

 

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

 

image details.png

 

enter the capture wim file name (path) and user details to save the capture with

 

capture details.png

 

Click Next, Next and review the confirmation.

 

success bac.png

 

 

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.

 

 

site properties.png

 

Click on the Component Configuration tab, software distribution, edit

 

edit.png

 

enter the network access account details (click on the network access account tab), and click ok, ok

 

network access account.png

Share this post


Link to post
Share on other sites

Step 2. Deploy (advertise) the Task Sequence to the Unknown Computers Collection

 

highlight our newly created task sequence, right-click and choose Deploy

 

deploy ts.png

 

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

 

select collection.png

 

leave the schedule as it is

 

schedule.png

 

set the distribution point settings as follows

 

access content directly.png

 

and continue through the wizard accepting defaults

 

adv created.png

Share this post


Link to post
Share on other sites

Step 3. Create New hyperV virtual Machine

 

on your HyperV host, startup Hyper-V Manager, right click and choose New, Virtual Machine

 

new vm.png

 

specify name and location

 

specify name and location.png

 

give it 1024 mb ram

 

ram.png

 

set the network type to Internal Only

 

internal only.png

 

set the storage size to 40gb

 

40.png

 

choose Install the operating system later

 

install os later.png

 

click Finish to close the wizard. When done, highlight the new vm in hyperv, right click and select settings

 

settings.png

 

click Add Hardware, choose Legacy Network Adaptor, click Add

 

add.png

 

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

 

bios.png

 

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).

 

f12.png

 

at the welcome to the task sequence screen, press next

 

no pxe password.png

 

select our Build and Capture Task sequence

 

select ts.png

 

and off it goes

 

partition.png

 

this will be slow until you edit the partition disk 0 step and change the format to Quick Format

 

bac.png

 

and out image is being captured

 

capture.png

  • Like 1

Share this post


Link to post
Share on other sites

My build and capture does not work at all.

It gets pass the PXE boot by pressing f12, then it shows the SCCM logo screen.

But it never displays the task sequence window.

It just reboots back into the PXE post screen again.

 

This time displaying an error...

 

 

What did I do wrong and how to fix please.

Share this post


Link to post
Share on other sites

if you enable command support in your boot image, press f8 and get a look at your smsts.log, what does it asay

Share this post


Link to post
Share on other sites

Hi

 

I am getting "Failed to Save environment to 80070057" error from my TS, my SMStslog says (please see the attached)

 

I don't realy understand the fix mentions at

 

http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/page__p__1088#entry1088.

 

can you please help me out?

 

Thanks.

post-6580-0-94667500-1298121657_thumb.png

Share this post


Link to post
Share on other sites

post-16545-0-12184100-1362980437_thumb.jpgHi,

 

I've followed all your steps and when I booted the computer it comes up as the image1 attached.

 

Then I press F12 and came up with the error as image 2 attached

 

 

Anyone knows in which part it could be wrong?

 

Cheers

post-16545-0-87604000-1362980475_thumb.jpg

Share this post


Link to post
Share on other sites

this post is for a beta release of Configuration Manager 2012, which version of Configuration Manager are you testing with ?

Share this post


Link to post
Share on other sites

I'm using sccm 2012 version 5.0.7711.0, I compared the screen shot that I've found my TFTP Download:boot\x64\pxeboot.n12 whereas in your screen shot it's TFTP Download: smsboot\x64\pxeboot.com

 

If this the case, how to change the TFTP Download to point to smsboot?

Share this post


Link to post
Share on other sites

this post is for a beta release of Configuration Manager 2012, which version of Configuration Manager are you testing with ?

 

I'm using sccm 2012 version 5.0.7711.0, I compared the screen shot that I've found my TFTP Download:boot\x64\pxeboot.n12 whereas in your screen shot it's TFTP Download: smsboot\x64\pxeboot.com

 

If this the case, how to change the TFTP Download to point to smsboot?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...