Release Notes
Using OS Deployment tasks from multiple OEMs within the same task sequence
Tocrea teatasksequenceinConfigurationMana gerthatperfor ms systemhardwareconfigurationandoperatingsystemdeployment,and
worksonmultiplehardwareplatforms,enablingyoutoaddOriginalEquipmentMa nufa cturer(OEM)hardwareconfigurationsteps
from morethanonevendor intothesametasksequence.
Open Issues and Resolutions
Fixed Issu es/def
TheOEM add‐onsfor systemhar dwa re confi gur a t i o nutilizepre ‐configuredtemplatestoarrangestepsinthetaskseque n ce inaprope r
order. Whenyo uaddanewOEMstepintoatasksequence,it firstcheckstoseeifthetasksequencealreadyhasanyOEMstepsinit.If
therearenosteps,itpromptsyoufo rautomaticconfigurationofthesteps.Incertaincases,suchastheadditionofa"Re boottoPXEor
USB"step,ifyoudonotallowtheautomaticreconfiguration,itwillfail.
Inthefirst releasedve r s i o n oftheintegrationcomponentsonwhi ch
theOEMhardwareconfigurationadd‐insarebuilt,theFormchecks
forpre‐existingOEM tasksteps,butdoes notcheckforot he rexistingOEMsteps.This causesanissuewheread di ng oneOEMsteptoan
existingtasksequencecreatedbyanotherOEM'sautomaticconfigurationcausesthene w ly‐addedstep
tobetakenasthefirstOEMstep
inthetasksequence.
Incaseofthehardwareconfigurationstep,cancelthereconfigurationbeca u s e itwouldstilladdavalidtas ksteptothesequence.How e ve r ,
ifyouareaddinga"R eboottoPX EorUSB"step,cancelingtheautomaticreconfigurationwillle avethetaskstepun ‐configuredandi nvalid.
Acceptingthe
Re config urationwillre‐applytheoriginalgroupingandreorganizationtothetasksequence,whic hwillalsorenderitinvalid.
Resolution
Theini tial OEMreleaseworkscorrectlyonitsownands ubs e q ue nt versionsoftheunde rly in gintegrationcompo n e n t s willcheckfor
existingstepsfromanyOEM.Therefore,ensurethatyouusethefollowingprocedureforusing Stepsfr o mmultipleOEMsinatask
sequence:
1.
Createane w tasksequencewithOEMconfigurationsteps (preferably,usetheright‐cl ickactiononthe"TaskSequences"node ).
2.
YoucannowaddstepsfromanyOEMintoata sksequenceandit willbehandledcorrectly .
Task Sequence Issues/Limitations:
InthetasksequencesavingtheBIOSsettingswiththeoption"[Configura tionsavedasaVaria bl e]" failstoapplyBIOSsettings.Savethe
settingsinan.INIfiletosuccessfullyapplyBIOSsetti ngs.[353292]
Whileusin gtheUnknownComputerfe a tu re oftheDellServerD e plo yme nt Pack,whe nthesystemboots
up,itpresentswithascreento
captur ethecredentialsandthehostname. Clickingthe"AddMachineNow" buttonco ul d taketimetorespond,asthesystemneedsto
contacttheCo nf ig ur at ionManagerSiteServerforaddi ng ittothespecifiedknownCollection.[368090]
Array Builder Issues/Limitations:
CERCSAT A1.5/6‐Channel(C H),andCERCSATA1.5/2Scontrollersareno t supportedinDellServerDe ployment Pack .
RAIDconfigurationonPERC S100/S300contr ol lers arenotsupportedwithX64bootimages.UseX86bootimageormanuallycon figure the
RAIDbef ore Operatingsystemdeployment.[367624]
General Issues/Limitations:
YellowbangdisplaysfortheBroadcom5708Cdrive r afteryoudeploy WindowsServer2003Operat ingSystemonaPow e r E dg e 1950
system.Updatethedrivermanually.
Afterthedeploymentof Window sServer2008OperatingSystemifyoufindany devi cesnotstartedinthe"Devi ceManager"rebootthe
systemtostart
thedr i ve r .AtypicalexamplecanbeaiSCSIenabledNICdriver.[270891]
OnafreshinstallofConfigurationManager2007SP1andDSDP,amessagemay display:"Createtasksequencetemplate:Unabletoadd
thetasksequencetoThe tasksequencepacka ge" .Whenyo uclick"OK",anothermessagedisplays:"Createtask
sequencetemplat e:
Could notcreateta s ksequencepackage".Rebootyoursystem tofix thisissue.
Iconsmay notappearontheArrayBuilderGUI onasystemrunningMicroso ftWindowsXPSP2.