1) Download the Script. Change the file extension from txt to ps1 and save it to networkshare. The GUI is created with Sapien Powershell Studio
2) Create a package in sccm but do not create a program. Distribute the package to DP.
3) Edit your Task Sequence and add ”Run Powershell Script”. Browse for the package you just create and write the name of the script in ”Script Name” section. Change execution policy to ”bypass”.
4) Deploy you TS.

OSDpopup

DO NOT forget to update your boot image to support .Net and Powershell.

1) Save the following script as OSDComputerName.ps1 on a networkshare.

I use Hyper-v in my labb and Hyper-v virtual machin gives you over 30 digits of serialnumber and here in this script i want only the four first of them. This is because NetBios computer names can handle a maximum lenght of 15 characters.

$SerialNumber = (Get-WmiObject -Class Win32_BIOS | Select-Object SerialNumber).SerialNumber
$ShortSerialNumber = $SerialNumber.Substring(0,4)
$OSDComputerName = “LABB-” + $ShortSerialNumber
$TSEnv = New-Object -COMObject Microsoft.SMS.TSEnvironment
$TSEnv.Value(“OSDComputerName”) = “$OSDComputerName”

2) Create a package in sccm but do not create a program. Distribute the package to DP.

3) Edit your TS and create a ”Group” before ”Apply Windows/Nework Settings” and name it OSDComputerName.

4) Add a ”Run Command Line” with the name ”Set PowerShell Execution Policy” and paste the following:

powershell.exe -noprofile -command "Set-ExecutionPolicy Bypass LocalMachine" -force

5) Add a ”Run command Line” with the name ”OSDComputerName.ps1” and paste the following:

powershell.exe -noprofile -file OSDcomputername.ps1

In ”Package” section browse for the script we created and saved in a networkshare.

6) Add a ”Run command Line” with the name ”Revert Powershell Execution Policy” and paste the following:

powershell.exe -noprofile -command "Set-ExecutionPolicy RemoteSigned LocalMachine" -force

Save the TS and test in your test environament.

Windows 8.1Senior Product Marketing Manager at Microsoft Ben Hunter recently blogged about a new way that Windows 8.1 can be installed while still ensuring that there is plenty of storage left for apps and data.

The method uses the well-known Windows Image Boot format. But instead of uncompressing the image during installation, WIMBoot keeps all of the operating system files compressed on a separate partition. From the user’s perspective, however, nothing looks any different: You still see a C: volume containing Windows, your apps, and all of your data.

A standard WIM file is not usually bigger than around 3GB. This allows for installation on devices with smaller disks, e.g. devices with 16GB or 32GB SSDs or eMMC storage, while still ensuring that there is plenty of storage left for apps and data.

Note that UEFI is a requirement and that WIMBoot will only be supported on Windows 8 logo-certified devices.

Read more about Windows Image File Boot (WIMBoot) here.
http://technet.microsoft.com/en-us/library/dn594399.aspx

Read about Michael Niehaus experiences from experimenting with WIMBoot using MDT 2013 here:
http://blogs.technet.com/b/mniehaus/archive/2014/04/13/experimenting-with-wimboot-using-mdt-2013.aspx

Vi vill tipsa om en bra steg-för-steg guide över hur du kan lägga till Internet Explorer 11 i en referensavbildning för Windows 7 SP1 .

Du hittar guiden här:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/124/Adding-Internet-Explorer-11-to-your-Windows-7-SP1-reference-image.aspx

 
Ps.
    Läs även kommentarerna kring unattend.xml.

 

The RC1 is now available for download on Connect.

  • Support for Configuration Manager 2012 RC2 (while still supporting Configuration Manager 2007)
  • New User-Driven Installation components for CM 2007 and CM 2012
  • Ability to migrate MDT 2012 task sequences from CM 2007 to CM 2012
  • Customize deployment questions
  • Integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for remote control and diagnostics
  • New monitoring capabilities to see the progress of currently running deployments
  • Support for deploying Windows to computers using UEFIAbility to deploy Windows 7 so that the computer will start from a new VHD file, ”Deploy to VHD”
  • Improved deployment wizard user experience
  • And many small enhancements and bug fixes

Read more on the Microsoft Deployment Toolkit Team Blog

DOWNLOAD

The Microsoft Solution Accelerators team is pleased to announce Microsoft Deployment Toolkit 2012 Beta 2 is available for download on Connect now. We hope you’ll take the time to preview and provide feedback on MDT 2012 Beta 2.

New Connect members join the MDT 2012 Beta 2 program now (Windows Live ID required):

http://go.microsoft.com/fwlink/?LinkId=217607

Existing Connect members bookmark this link to get the latest project details:

http://go.microsoft.com/fwlink/?LinkId=233070

Beta 2 of the Microsoft Deployment Toolkit (MDT) 2012 is now available for download! New features and enhancements make large-scale desktop and server deployments smoother than ever! For System Center Configuration Manager customers, MDT 2012 Beta 2 provides an improved, extensible wizard and designer for customizing deployment questions. MDT 2012 makes full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment. MDT 2012 integrates with configuration templates from the Security Compliance Manager (SCM) tool to ensure a secure Windows installation from the beginning of the deployment. Download the latest version of MDT and improve your deployment experience. Existing MDT users will find more reliability and flexibility with the many small enhancements and bug fixes and a smooth and simple upgrade process.

Key Benefits:

  • Full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
  • Improved Lite Touch user experience and functionality.
  • A smooth and simple upgrade process for all existing MDT users.


Have gotten the Task Sequence error code 0x80072F87 lately and you have no clue of what it means or why your task sequences won’t run even though everything looks OK?

Well this little bugger kept me and the whole team where I am assigned at confused for a day or two.

The solution was simple: The computer date and time was wrong.

So fix the date and time and you’re all set to go.

Good Luck! 🙂

Hi,

Have you had an USMT job running and you want to exclude a specific file but it keeps on getting migrated? You check your xml file and see that everything is as it should but the file still keeps migrating? Well there is a reason for that. I’m going to try and give you a quick explanation.

Simply put if you have a include of any type somewhere in your xml file(s) then your targeted exclusion will still be migrated. So you can use as many Excludes or Unconditional Excludes as you like, but if you have another Rule section or Component section or etc. It will be included.

To read more on this topic in detail please visit: http://chentiangemalc.wordpress.com/2011/02/01/how-to-exclude-files-usmt-4-0/

Hope this helps you out with your next USMT job 😉