Jump to content


  • 0
anyweb

Deploy Windows 7

Question

Please note that this guide is designed to get you Deploying Windows 7 with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums.

 

 

 

In a production environment please consult Technet for best practise, see below links:

 

Operating System Deployment:

 

Operating System Deployment in Configuration Manager

Overview of Operating System Deployment

 

Configuration:

 

System Center Configuration Manager 2007

 

Best Practices:

 

Configuring Configuration Manager Sites for Best Performance

Checklist for Security Best Practices

Best Practices for Central and Primary Site Hardware and Software Configuration

Best Practices for Operating System Deployment

 

 

 

This guide assumes that you've installed and configured SCCM 2007 already and that you have set it up to deploy operating system's such as Windows Vista SP1. In addition you must have installed SP2 for ConfigMgr. It is available for download here.

 

The most up to date version of this Guide will always be found in the Deploy 7 section of the windows-noob.com forums.

 

For best practise information about deployments using SCCM you should always consult with Microsoft Technet.

 

 

 

Step 1. get the ISO

 

I chose the 64bit Enterprise version which was en_windows_7_enterprise_x64_dvd_x15-70749.iso.

 

Now that you have the ISO, mount it or burn it to DVD and copy the contents of it (all files and folders) to a network share on your SCCM server.

 

copying files.jpg

 

Step 2. Add Operating System Install Package

In System Center Configuration Manager 2007 expand the Operating System Deployment node and right click on Operating System Install Packages, choose add operating system install package.

 

 

 

When the Add Operating System Install Package wizard appears, point it to the path where the Windows 7 operating system files can be found eg:

 

\\SCCM\sources\os\7\rtm\x64\ent\

 

add operating system install package data source.jpg

 

fill in the name, version and a comment about the image

 

details about the image.jpg

 

review the summary

 

review the summary.jpg

 

and verify the confirmation

 

confirmation.jpg

 

 

Step 3. Create Distribution Point for the Image

 

Now that we have added the operating system files to our available operating system install packages, we need to create a new distribution point for it so let's do that.

 

Expand the newly added Windows 7 image you just added in Operating System Install Image Packages and right click on Distribution Points, select New Distribution Points. Click next on the Welcome screen.

 

new distribution points.jpg

 

As this is not a boot image (it's an Entire Operating System), select only the first distribution point (do not select the PXE one)

 

select first dp.jpg

 

click next and close.

 

Step 4. Update Distribution Point

 

now that we have created a distribution point, let's update it, so right click on distribution points and choose update distribution points, answer yes when prompted.

 

update dp.jpg

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

Ok I just upgraded to SP2, everything was working great on SP1 R2. Now I'm trying to deploy Win7 enterprise x64 like everybody (I think) but the thing isn't working.

 

I can boot with pxe, I fill in the pxe password, it starts to partition the disk, the it says 'Setup windows and Configmgr' (like always) with the win7 background and then it fails.

It's not a driver problem I think, otherwise it had been rebooting. I think there is some authority or update of package or something missing. I already updated the sccm client package.

 

This is the log

 

Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\AAN0018C	OSDSetupWindows	13/09/2010 16:43:03	1252 (0x04E4)
reference count 1 for the source C:\_SMSTaskSequence\Packages\AAN0018C before releasing	OSDSetupWindows	13/09/2010 16:43:03	1252 (0x04E4)
Delete source directory C:\_SMSTaskSequence\Packages\AAN0018C	OSDSetupWindows	13/09/2010 16:43:03	1252 (0x04E4)
Released the resolved source C:\_SMSTaskSequence\Packages\AAN0018C	OSDSetupWindows	13/09/2010 16:43:04	1252 (0x04E4)
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)	OSDSetupWindows	13/09/2010 16:43:04	1252 (0x04E4)
Windows setup failed, code 31	OSDSetupWindows	13/09/2010 16:43:04	1252 (0x04E4)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)	OSDSetupWindows	13/09/2010 16:43:04	1252 (0x04E4)
Exiting with code 0x80004005	OSDSetupWindows	13/09/2010 16:43:04	1252 (0x04E4)
Process completed with exit code 2147500037	TSManager	13/09/2010 16:43:04	1124 (0x0464)
!--------------------------------------------------------------------------------------------!	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Failed to run the action: Setup windows and ConfigMgr. 
Unspecified error (Error: 80004005; Source: Windows)	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Sending status message . . .	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Send a task execution status message SMS_TSExecution_ActionFailError	TSManager	13/09/2010 16:43:04	1124 (0x0464)
MP server prim_server.AANTER.fr and port 80. SSL=false. CRL=false.	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Site code: AAN	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Client machine name: metosmachine 	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Client Identity: GUID:01C5EE96-AECB-4DBA-84D9-EB64BC6BA526	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Advertisement ID: AAN2059F	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Package ID: AAN00188	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Sending StatusMessage	TSManager	13/09/2010 16:43:04	1124 (0x0464)
Formatted header:	TSManager	13/09/2010 16:43:04	1124 (0x0464)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>8b28e089-91b4-41ab-b0ee-40f04d43dca9</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-09-13T14:43:04Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4266"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager	13/09/2010 16:43:04	1124 (0x0464)

Share this post


Link to post
Share on other sites

  • 0

Hi,

 

Followed this excellent guide and it looks like the package was being installed but at the SCCM splash screen the laptop rebooted itself, went back into PXE:

 

"downloaded WDSNPB

 

Architecture: x64

 

The details below show the info relating to the pxe boot request for this computer

 

pending request ID request: 6

 

contacting server: 192.168.1.137

TFTP Download: smsboot\x64\abortpxe.com

PXE boot aborted. Booting to next device....."

 

Appreciate any advice\assistance

 

thanks!

Share this post


Link to post
Share on other sites

  • 0

does this help ?

 

and I quote:-

 

installed MDT 2010 update 1 and connected it to SCCM. this allow me to use the "install language pack offline" task sequence step that does not exist in SCCM. I've implemented the "user driven installation" fonctionnality of MDT which allows you to run an installation wizard and let you chose the user language interface.

 

for information about connecting MDT to SCCM and implementing UDI (user driven installation), download and read the MDT help file : http://www.microsoft.com/downloads/en/details.aspx?familyid=3bd8561f-77ac-4400-a0c1-fe871c461a89&displaylang=en&tm

 

But :

 

this default procedure does not install language pack during the deployment. For SCCM the language pack has to be already present in your master (it's a little bit complicated because installed language pack make your master huge :-) ).

 

so i've customized the UDI task sequence for injected the selected language pack just after applied the operating system.

 

after the "apply operating system" step i've added one "BDD_InstallLanguagePacksOffline" step for each language pack i need to use. (in our case we have about 25 language packs ... so 25 steps).

 

in the UDI Wizard launched during the computer deployment, you can select the user language interface. The information is stored in a variable : UILanguage

 

So in order to install the right language pack, for each step added, you need to apply a condition based on the UILanguage value.

 

Example :

 

I started a computer deployment and selected the following user language : "FRENCH". the value of the task sequence variable is now "fr-FR"

 

in your task sequence, for the french "BDD_InstallLanguagePacksOffline" steo, you have applied tha following condition :

 

* Task Sequence Variable UILanguage equals "fr-FR"

 

At the end, your computer is deployed with the correct language : MISSION COMPLETE !

Share this post


Link to post
Share on other sites

  • 0

A friend has advised me to do this:

 

 

Using mdt, you can install the language pack to the existing win 7 image. This way you don’t have to create a new image file of win 7.

 

Create a software package for the language pack and then put it into the TS with MDT integration.

 

http://technet.microsoft.com/en-us/library/cc766010(WS.10).aspx

 

Since I am new to SCCM and MDT, is there a guide here that I can refer to in order to accomplish this?

 

I also saw this http://www.windows-noob.com/forums/index.php?/topic/1660-customising-windows-7-deployments-part-1/ but I am not sure how I can do the same in SCCM (MDT integrated).

 

If someone can just guide me on how can I add the LPKSETUP command in the MDT TS, I shall be thankful. Or if there is any other way.

 

Regards!

Share this post


Link to post
Share on other sites

  • 0

Not sure if I am on the right track. There is already an English image of Windows 7 on the SCCM. The client wants another image in French for some of their new computers. This SCCM was setup by a outsourced preerson who is no longer working with them. Any elaboration on this will be great.

 

Regards!

Share this post


Link to post
Share on other sites

  • 0

Ok I think I am starting to understand after trying it in a lab. Now instead of using a command line for my package, can I just create a package in ConfigMgr containing the French language pack? Then I can add "Install Language Packs Offline" step to the TS.

 

Am I right? If not can you please advise how can I use this command line in the TS?

 

Also will this give the user an option to select their default language or Can I advertise the English version to one collection and French to another?

 

 

Thanks for your patience!

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
Answer this question...

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


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.