WinPE: Restarting DHCP client service

Written by Ingmar Verheij on July 7th, 2011. Posted in Deployment

A bare-metal deployment is build using Altiris Deployment Solutions (HP Rapid Deployment Pack, to be precise). When a client boots Windows PE 2.1 to execute a job (installation of operating system) it doesn’t seem to get an IP address from the DHCP server (Restarting DHCP client service: retry x).

WinPE : Restarting DHCP client service: retry










This is strange since the WinPE 2.1 image is downloaded via a PXE boot which acquired a IP address from the DHCP server without problems, the DHCP mechanism is working.

This caused me some serious headache a few months ago (at another customer). I investigated the problem and found the cause of the problem.

Change driveletter of CD-rom

Written by Ingmar Verheij on September 16th, 2010. Posted in Deployment

In a deployment using Altiris (or any other deployment utility) it is common to change driveletters. Especially when servers are reinstalled once in a while, you probably encounter problems doing so using diskpart.
Diskpart is the utility supplied with Windows by Microsoft which enables you to manage you disks, partitions and volumes. One limitation is, however, that you’re unable to select a specific drive using filters. For instance a CD-rom drive.
In an initial deployment you know how many disks there are and how many volumes. Because these are static you can create the diskpart script easily by specifying the disk ID or volume ID, which is numbered in the order of presence.
However, when you redeploy that same server this might be changed. If you’ve added a disk (or formatted it) the order of presence might be changed and the script will fail to execute the way you expected it.

RE: Installing Windows Features with Windows PowerShell

Written by Ingmar Verheij on February 17th, 2010. Posted in Deployment, PowerShell

Recently my colleague Robin Plomp wrote an article about installing features in Window Server 2008 R2 (or Windows 7) with Windows PowerShell scripts:

“I ‘m a big fan of the new version of the Windows server platform. I’ve recently deployed 6 Windows 2008 (64) R2 servers. On one of the servers I am going to install Microsoft Office Communicator 2007 R2. One of the prerequisites is .NET Framework 3.5 SP1. This can be installed in the ServerManager under Features. This means you have to scroll down a long list of Windows Features. There has to be an easier way.
Enter the world of Windows PowerShell!”

Read more

Although PowerShell is a great tool for installing features, or performing other tasks, it isn’t necessary for automated installation of features.
Enter the world op “Deployment Image Servicing and Management(DISM)” or dism.exe (located in the system folder)!!!

Windows Installer proxy information not correctly registered

Written by Ingmar Verheij on February 11th, 2010. Posted in Deployment

I’m creating a new deployment for a 2008 R2 Remote Desktop Server using Altiris. Most of the jobs that are executed are installation jobs using the Windows Installer.
Altough the first installation (after a reboot) goes well, the next installation always fails because the installer is unable to connect to the Windows Install object.
In the event log are several events which occur within 2 seconds of each other:
Source : User Profile Service
Event ID : 1530
Level : Warning
General : Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

(Computer)naam van Thin Clients

Written by Ingmar Verheij on September 22nd, 2008. Posted in Deployment

Het probleem
Bij de meeste klanten waar ik kom worden de werkstations, servers en Thin Clients met behulp van een image in Altiris ingespoeld. Na het inlezen van de image wordt de naam aangepast naar de (vooraf) opgegeven naam.
De gebruikers van de helpdesk hebben de volgende instructie meegekregen om een nieuwe TC in te spoelen;

  • Computer object toevoegen in Altiris
    • Selecteer de map `Thin Clients`
    • `New Computer`
    • Klik op Add
    • Vul de nieuwe naam, bijvoorbeeld PBNLTC0267, in bij Name & Computername
    • Vul het MAC address, deze staat op de TC, in bij MAC Address
  • Job klaarzetten voor Computer
    • Sleep de job `Jobs. Operating SystemThin Clients01. Deploy ThinClient` naar het computer object PBNLTC0267
    • Klik op OK

Nadat de job `001. Deploy ThinClient` is succesvol is uitgevoerd wordt de job `002. Configure ThinClient` uitgevoerd welke de computernaam aanpast (niet alleen in Windows, maar ook in Citrix!).
Tijdens het inspoelen van nieuwe Thin Clients (TC) door de servicedesk ging dit echter niet goed. Alle TC’s die werden ingespoeld kregen de naam PBNLTC0001 ipv de vooraf opgegeven naam (PBNLTC0267).