Jump to content

[Video] Windows 7 AIK/OPK deployment 101 (Updated)


ricktendo

Recommended Posts

In your video you mentioned to set copy profile to true in autounattend but you have not showed where to copy that Autounattend. I believe it has to be in sysrep folder. Can you post the autoattend examplae and do you knnow how to set default custom theme in unattended

Link to comment
Share on other sites

  • 2 weeks later...

Una cuestion. Estoy haciendo un AIO de una version previa ya manipulada con AIK para integrarle versiones 64 al x86. Pero el x86 ya tiene nombre en sus versiones al estilo de Windows 7 ULTIMATE. Cuando integré las x64 en el mismo caso puse Windows 7 Ultimate x64. Cuando corro la herramienta Windows System Image Manager para crear los archivos clg, aparece las referencias tal cual. O sea ULTIMATE y Ultimate x64. La pregunta es: ¿Cual es el comando o como hago para modificar estos titulos ya creados para que todos se vean de igual manera en el menu de instalacion?

Gracias

Edited by tele
Link to comment
Share on other sites

Yo no soy experto en AIO, lo que hago yo es eliminar las versiones que no uso dejando solo uno...acabo de seguir este tutorial y este fue mi resultado

aio.png

Que comandos usaste tu y que es lo que dice cuando haces dism /get-wiminfo /wimfile:install.wim y/o imagex /info install.wim



Index : 1
Name : Windows 7 STARTER
Description : Windows 7 STARTER
Size : 8,074,968,070 bytes

Index : 2
Name : Windows 7 HOMEBASIC
Description : Windows 7 HOMEBASIC
Size : 8,127,590,116 bytes

Index : 3
Name : Windows 7 HOMEPREMIUM
Description : Windows 7 HOMEPREMIUM
Size : 8,569,006,173 bytes

Index : 4
Name : Windows 7 PROFESSIONAL
Description : Windows 7 PROFESSIONAL
Size : 8,450,188,760 bytes

Index : 5
Name : Windows 7 ULTIMATE
Description : Windows 7 ULTIMATE
Size : 8,610,128,720 bytes

Index : 6
Name : Windows 7 HOMEBASIC (x64)
Description : Windows 7 HOMEBASIC
Size : 11,710,161,360 bytes

Index : 7
Name : Windows 7 HOMEPREMIUM (x64)
Description : Windows 7 HOMEPREMIUM
Size : 12,222,587,449 bytes

Index : 8
Name : Windows 7 PROFESSIONAL (x64)
Description : Windows 7 PROFESSIONAL
Size : 12,122,886,417 bytes

Index : 9
Name : Windows 7 ULTIMATE (x64)
Description : Windows 7 ULTIMATE
Size : 12,285,492,779 bytes
Details for image : \dvd\sources\install.wim

P.D. pruebe GImageX, talvez con el puedas renombrar imágenes

Link to comment
Share on other sites

Es básicamente es el mismo manual que uso. El procedimiento siempre es el mismo. El resultado tambien es el mismo igual al tuyo. Lo que ocurre es que quiero cambiarle el nombre (modificarlo para que en el menu de instalacion salga como debe ser) . ejemplo Windows 7 Ultimate x64 a Windows 7 ULTIMATE (X64) tal y como tu lo tienes

1. Existe alguna línea de comandos que me permita hacer esto?

2. Para incluir versiones 64 en un x86 necesariamente tengo que eliminar todos los archivos .CLG anteriores (los que ya existian en el x86) y recontruirlos nuevamente tanto los x86 como x64?

3. Con este metodo puedo integrar todos los winserver? (Windows 2000, 2003 y 2008)

4. Para que sirve el GImageX (http://www.autoitscr...-tools/gimagex/)

gracias rick

PD: que opinas de esto http://www.msfn.org/board/topic/139077-7customizer-a-windows-7-customization-and-deployment-tool/

Edited by tele
Link to comment
Share on other sites

GImageX es un GUI para ImageX, todo lo que se puede hacer con ImageX lo tiene GImageX

Ponlo en el mismo directorio que ImageX y lo corres

gimagex.png

P.D. pruebe esto (creo que es lo mismo de arriba)

imagex /info archivoDeImagen[númeroDeImagen | nombreDeImagen] [nombreNuevo] [descripciónNueva] {/boot | /check}

http://technet.micro...28WS.10%29.aspx

Link to comment
Share on other sites

Ya verifique. No hay problemas. Sin importar el nombre que le pongas (mayuscula o minuscula o x64 o (x64)) en el menu siempre sale igual. Una pregunta mas:

Con este metodo puedo integrar todos los winserver? (Windows 2000, 2003 y 2008)? y que opinas sobre 7Customizer

PD: Como es que hacer para "quitar" los windows que no usas??

gracias

Edited by tele
Link to comment
Share on other sites

  • 1 month later...

This may seem like a dumb question. But given the size of the WAIK downloads, other needed software, as well as the amount of time invested to make and configure a image, how how is this method any better than using Image for Windows, or any similar disk imaging utility and deploying that for a clean install?

Edited by BYTE-ME
Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

Hey ricktendo64,

Major concern...googled to no avail, so, thought I would try to pick your brain.

I keep getting fatal error when finnalizing sys prep; it worked fine on this image now, without rhyme or reason, it won't finnalize. I attached the sysprep logs from both the Panther and IE folders...any help or ideas would be greatly appreciated. ThanksSysprepFailure.7z

I may have found a solution:

http://support.microsoft.com/kb/929828

I'm going to include the entry from this KB in the unattend file for copy profile in the sysprep folder and try it-I'll report back.

Edited by RickSteele
Link to comment
Share on other sites

@RickSteele try integrating your updates before you sysprep I cant recall off the top of my head but there are a couple that fix sysprep issues

KB929828 fixed it, add the following to the unattend you use during sysprep immediately below your copy profile entry, but, as the KB states, don't forget to remove this entry afterwards: (it seems this relates to M$ licensing/activation issues-present even when just preparing, but, not installing an image...go figure.)


<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...nfig/2002/State" xmlns:xsi="http://www.w3.org/20...Schema-instance">
<SkipRearm>1</SkipRearm>
</component>
</settings>

This was the fourth or fifth time I loaded this image into sysprep to tweak a few things here and there, and to correct some errors I had made in group policy editor; nothing major, but, it seems three is the magic number afterwhich you either apply this workaround or rebuild the image from scratch. The following is the spartan unattend I use to sysprep:


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...nfig/2002/State" xmlns:xsi="http://www.w3.org/20...Schema-instance">
<CopyProfile>true</CopyProfile>
</component>
</settings>
</unattend>

and looks like this to prevent the fatal error:


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CopyProfile>true</CopyProfile>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>1</SkipRearm>
</component>
</settings>
</unattend>

I delete this xml from the image when I prepare for install with all updates, drivers integrated and use a much more elaborate answer file in the root of the setup folder.

Edited by RickSteele
Link to comment
Share on other sites

  • 1 month later...
  • 1 year later...

You cant integrate service pack the same way you integrate updates, but you can do a "reverse integration" where you install windows 7 to a test machine, boot into sysprep, install service pack 1, and prepare that install to be captured and make your WIM

Look at the last video "Preinstalling Applications and Capturing Image" where I talk about this process

 

BTW if you can find it, its better to download a pre-integrated sp1 iso from microsoft

Link to comment
Share on other sites

  • 1 month later...

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.

×
×
  • Create New...