Litetouch.wsf and Win XP Upgrade

Chris T.

2008-12-17 02:27:11 UTC

This seems like the problem I am having.
Can someone confirm this as being a problem?

reference:
http://www.techtalkz.com/windows-deployment/195273-userstate-backup-lti-scenarios.html

Recently I have seen a number of users attenmpting to manipulate
DeploymentType property in the customsetting.ini. You have to be very
specific about using this. For example Upgrade and Refresh and Replace have
no meaning when a system is first booted into WinPE. A machine with no
previous state on the local disk, booted into Windows PE, can only be a
NewComputer, and can optionally restore user state if configured and data
found.

Looking at the logs it looks like you have DeploymentType=Upgrade in your
customsettings.ini default section. The system booted up in WinPE, saw no
old state, set DeploymentType to NewComputer, and then processed
customsettings.ini (resetting DeploymentType to Upgrade), then ran the LTI
wizard, the user chose Replace, and this value is not a legal value outside
of the old OS - it is only used for state capture phase in an old os and is
run as a standalone job and exits..

How did the user get to choose Replace in the Wizard? Because the Upgrade
value over-rode Newcomputer, changed the environment detection conditions
and offered up the generic full OS UI screens - It got confused. The wizard
woudl have only set Upgrade in previous screens if it was running in a full
OS, so later screens continnuye to build on the options chose in earlier
prompts. The earlier screens validate legal entries at input time, but not
every property along the entire way.

You will not want to specify DeploymentType in a default section, only in a
machine specific case (such as a certain MAC address, Serial or asset
number), where you know the starting condition of the machine. The LTI
wizard is performing the logic to select the proper combination of options
and when we start skipping the Wizards and setting certain values, you take
the burden of of that detection onto your rules and targeting methods.

A similar symptom was observed in another entirely different case for ZTI
where the ZeroTouchInstallation.vbs was not configured to run for each
program properties custom action - it needs to be called for all six phases
of the program. The result was the same - the task sequence was started in
the validation, skipped until Post Install, and things got really confused
since there was no opportunity for the correct actions to take place in each
phase. It started running USMT in WinPE since that was the next recorded
step.

Post by Chris T.
Helo,
I have BDD 2008 and Windows Deployment Server setup on a Windows 2003
server.
I want to upgrade my Windows XP computers to Vista using BDD 2008 and
Windows Deployment Server. So far I beilieve I have everything correctly
setup except for one nagging problem. When I boot into WinPE and the
litetouch.wsf file runs it doesn't UPGRADE Windows XP it does a clean
install of Vista instead. However if I am logged in on Windows XP map a
drive to the $ditribution share and run litetouch.wsf it does an inplace
UPGRADE like I want it to. So why does BDD fail to upgrade my Winodws XP
pro computers when it run from WinPE? Is this by design? Do I have
something not setup correctly?
boot.ini
[Settings]
Priority=Default
[Default]
DeployRoot=\\ALT\Distribution$
SkipBDDWelcome=YES
KeyboadLocale=en-US
UserDomain=somedomain
UserID=someusername
UserPassword=somepassword
Home_Page=http://url
EventShare=\\ALT\Events
SLShare=\\ALT\Logs
customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac /lae
SkipWizard=YES
DeploymentType=UPGRADE
TaskSequenceID=UPGRADEXPTOVISTA
ComputerName=%ComputerName%
LanguagePacks1={3af4e3ce-8122-41a2-9cf9-892145521660}
LanguagePacks2={84fc70d4-db4b-40dc-a660-d546a50bf226}
UILanguage=en-US
UserLocale=en-US
KeyboardLocale=en-US
TimeZoneName=Central Standard Time
Applications001={0b0f6912-3ffb-4b02-a20b-1a645f2e9687}
SLShare=\\ALT\Logs