So you want to add the $OEM$ folder to your SCCM 2007 OS Deployments? Well, if you just add the $OEM$ folder to the package (any location) it will be skipped… The reason is because the “Setup Windows and ConfigMgr” action adds (or overwrites) the OemFilesPath=C:\_SMSTaskSequence\OSD\$OEM$ value in unattend.txt before starting Winnt32.exe The workaround is simple. […]
The default “Setup Windows and ConfigMgr” SCCM action will effectively replace all variables in sysprep.inf And since that action is run under WinPE, the %WINDIR% variable will be replaced with X:\Windows. So never, ever use that variable in sysprep.inf… (unless you really deploy Windows to X: which I highly doubt 🙂 ) This is by […]
Tired of using the ConfigMgr console just because you need a new SCCM Task Sequence boot media (WinPE)? … Well, you don’t have to… In the ConfigMgr SDK there is a API (tsmediaapi) that can be used together with a vbscript…. Step-by-step Download the ConfigMgr SDK, and install to the default location (http://www.microsoft.com/downloads/thankyou.aspx?familyId=064a995f-ef13-4200-81ad-e3af6218edcc&displayLang=en) Register […]
The HAL Replacement script for MDT 2008 (LiteTouch and ZeroTouch) has been updated with support for XP SP3 and SCCM 2007. Note: 2008-12-23, added standalone version for users running third party deployment solution like Intel LANDesk or Altiris, Download link: http://www.deployvista.com/Repository/tabid/71/EntryId/53/DMXModule/396/ctl/EntryDetails/mid/396/language/sv-SE/Default.aspx
This is a step-by-step guide to boot DOS 7.10 images from Windows Deployment Services (WDS). Booting DOS 7.10 images from Windows Deployment Services (WDS) Create a DOS 7.10 image file (.ima) using winimage 8.10 (http://www.winimage.com). You can also download a DOS boot image from http://www.bootdisk.com/ and use winimage to convert it from .exe to .ima. […]
It turns out that the well-known security patch for DNS last summer breaks WDS, but only if DNS and WDS are running on the same box. This is also valid for Windows Server 2008 and Windows Server 2008 R2 which has the patch built-in. In brief, the issue with DNS and WDS on the same […]
As you probably know, WDS doesn’t provide any security for it’s native boot images (Windows PE 2.x). However, by adding pxelinux and vesamenu.c32 to WDS, you can add that feature. Here is how… Download and extract syslinux from http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.71.zip (it contains pxelinux) Copy the syslinux-3.71\com32\menu\vesamenu.c32 to your WDS Server, D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86 […]
Here is a step-by-step (how-to) guide for deploying Ubuntu 8.04.1 LTS 32-bit (Hardy Heron) from a Windows Server running WDS (Windows Deployment Services) Part 1 – Stage the Ubuntu Setup files on your Server Note: If you really wan’t to do Ubuntu deployments with style, you should of course skip downloading the alternate ISO’s and […]
Why Microsoft choosed to release MDT 2008 Update 1 with a known superbug in it I don’t understand… but I don’t work for Microsoft so I guess I shouldn’t… Anyway, the MDT 2008 update 1 will wipe your deployment point(s) settings completely… make sure to backup the deploy.xml file before applying the update, by default […]
A common error when deploying a MDT 2008 generated Task Sequence for SCCM 2007 is the following error: Task Sequence: has failed with the error code (0x80091007). The full error is “the hash value is not correct”. Workaround: One common solution is to change the advertisment to access content directly from a distribution point when […]