Skip to main content

SMS SCCM WDS MDT Windows 7

By

Tips- How to package software


Switches


-r
Causes Setup.exe automatically to generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.

 

Packages


cmd files must have drive letter
more info at http://www.appdeploy.com/
tick "suppress program notifications" to stop systray bubble/add and remove programs

Useful silent (un)install code:

  • msiexec /I "xxxx.msi" transforms="xxxx.mst" /qn /norestart (/qn shows no interface, /qb shows basic progress bar)

  • msiexec /x "xxxx.msi" /qn /norestart

  • C:\WINDOWS\IsUninst.exe -fC:\xxx\xxx.isu -a (-a is for silent)


IMAGEx


Enter “imagex /info img_file“, where “img_file” represents the location of the WIM file. You should see now the description of the WIM file as an XML file. The name of the tag for the image number is IMAGE INDEX.

Create a new folder where the image shall be mounted. This is the image path. Now, you can mount the image:

imagex /mount img_file img_number img_path

imagex /mountrw img_file img_number img_path

Once you’ve modified the image you can unmount it with this command:

imagex /unmount /commit img_path

DISM


dism /Mount-Wim /wimfile:d:\boot.wim /index:1 /MountDir:d:\mount
or
dism /Mount-Wim /wimfile:d:\boot.wim /index:2 /MountDir:d:\mount
or
dism /Mount-Wim /wimfile:d:\install.wim /index:3 /MountDir:d:\mount

http://technet.microsoft.com/en-us/library/dd744360%28v=ws.10%29.aspx


dism /Mount-Wim /wimfile:"E:\DeploymentShare\Operating Systems\Windows7x64-Aug12\Windows7x64.wim" /index:1 /MountDir:e:\mount
dism /Unmount-Wim /MountDir:e:\mount /commit
Dism /image:e:\mount /Set-UserLocale:EN-gb
Dism /image:e:\mount /Set-UILang:EN-us
Dism /image:e:\mount /Set-SysLocale:EN-gb
Dism /image:e:\mount /Set-InputLocale:EN-gb
Dism /image:e:\mount /Set-AllIntl:EN-gb
Dism /image:e:\mount /Set-SKUIntlDefaults:EN-gb

 

Add Drivers to Vista Boot Image


1. Update the WDS boot image to include the new third-party network driver. To do this, follow these steps.

Note The following procedure assumes that the Windows Automated Installation Kit (AIK) is installed on the WDS server. If the Windows AIK is not installed on the WDS server, you can perform the same procedure on another computer that does have the Windows AIK installed. Then, map a network drive to the WDS server.
a. On the WDS server, click Start, click Run, type wdsmgmt.msc, and then press OK.
b. Under your WDS server, double-click Boot images.
c. Right-click the boot image that you want, and then click Disable.
d. Right-click the same boot image, click Properties, and then click General.
e. Note the name and location of the boot image that is displayed in the File name box.
f. At a command prompt, type the following:
C:\program files\windows aik\tools\petools\copype.cmd x86 c:\windowspe-x86
Note Keep this command prompt window open for the next step.
Imagex /info o:\remoteinstall\boot\x86\images\kinstall.wim
Notes

  • Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed.

  • Boot.wim is the name of the boot image.
    g. Note the boot index number of the bootable image that is displayed. To identify the boot index number, locate the line that contains "boot index: X."


Note X is the boot index number. The number indicates that image number X is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify. However, always verify which image is marked as bootable.
h. At a command prompt, type the following:
Imagex /mountrw Drive:\remoteinstall\boot\x86\images\boot.wim 2 mount
peimg /inf=driver.inf mount\Windows
imagex /unmount /commit mount
Notes

  • Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed.

  • Driver.inf is the name of the third-party driver.

  • The Imagex /mountrw command mounts the specified image, with read/write permissions, to the specified directory.
    2. Enable the boot image on the WDS server. To do this, follow these steps:
    . On the WDS server, click Start, click Run, type wdsmgmt.msc, and then click OK.
    a. Under WDS server, double-click Boot images.
    b. Right-click the boot image that you want, and then click Enable.


----











copype.cmd x86 c:\windowspe-x86



imagex /info O:\RemoteInstall\Boot\x86\Images\Kcapture.WIM

imagex /mountrw O:\RemoteInstall\Boot\x86\Images\Kcapture.WIM 3 mount


------------------------

[ option1- one driver]


peimg /inf="[path to .inf]" /image=C:\windowspe-x86\mount

-------------------------------------

[ option2- multidriver]


for /R O:\RemoteInstall\driver_to_inject\network\760-960\780 %i in (*.inf) do peimg /inf=%i c:\windowspe-x86\mount\windows\

---------------------------------------------


imagex /unmount /commit C:\windowspe-x86\mount



imagex /unmount /commit mount


----------





 



Labels: 



Microsoft deployment Toolkit (MDT)


Instructions:
These instructions are brief and hopefully a useful first step.

How to deploy and Windows server 2003 image to bare metal (set to capture the file at the end of the task sequence)

1 On the computer you wish to deploy an OS instance power on and press F12 when prompted.  Select network boot (PXE boot).  Be ready to press F12 again when prompted otherwise it will time out and proceed to the next item in the boot order. Proceeding will Format the computer and delete all data!
2 Select 'Lite Touch Windows PE (x64)-Engineering' to pull down the WinPE file.
3 This produces a MDT Wizard, enter your domain credentials.
4 Select 'Microsoft Server 2003 Standard x64' from the task sequence.
5 Complete the wizard and 'begin'.
5.1 If you choose to capture the image after deployment specify the capture location as \\contoso\DeploymentShareEng$\captures
6 Upon completion you will have Server 2003 installed (and if selected a captured image).

How to sysprep and capture a current image.

1 On the computer you wish to capture click Start > Run and type \\contoso\DeploymentShareEng$\scripts\LiteTouch.vbs
2 This produces a MDT Wizard, enter your domain credentials.
3 Select 'sysprep and capture' from the task sequence.
4 Save the capure to \\contoso\DeploymentShareEng$\captures
5 Complete the wizard and 'begin'.
6 Upon completion you will have a WIM file located in \\contoso\DeploymentShareEng$\captures which can be used in other task sequences.
Labels:

Comments

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

By
Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...
161 comments
Read more

Windows 7 Offline files will not go Online when connected to network

By
Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...
151 comments
Read more

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

By
SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...
4 comments
Read more