Question for HAL Swapping & "ZTIHaldetect.vbs" script

Question for HAL Swapping & "ZTIHaldetect.vbs" script (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager

Message

jq -> Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/7/2008 9:42:42 AM)
Hello everyone, I had a question/scenario regarding HAL swapping using the "ZTIHaldetect.vbs" script method described here - http://www.myitforum.com/articles/15/view.asp?id=8997 So my original reference computer was a VMware Workstation 6 build, single processor with the "ACPI Uniprocessor PC - ACPIAPIC_UP" HAL. I am able to capture this and deploy to another VMware Workstation 6 machine single processor without any issues. I am able to deploy to a Lenovo X41 laptop [single processor with the "ACPI Uniprocessor PC - ACPIAPIC_UP" HAL], and it successfully deploys without any issues. I attempted to deploy to a Lenovo T41 laptop [single proccessor with the "Advanced Configuration and Power Interface (ACPI) PC - ACPIPIC_UP" HAL], and upon reboot it just goes to a black screen with no hard drive activity. The following is logged on the SCCM server [shows no errors]; The task sequence execution engine successfully completed the action (Update HAL) in the group (Install Operating System) with exit code 0 Action output: a connection to \\sccmserver.abc.com\SMSPKGD$\DC10001D\ with default computer account Connection request for "\\sccmserver.abc.com\SMSPKGD$\DC10001D" No credentials available for connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D". See whether the share has already been connected. Connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Successfully connected to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Resolved source to '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Command line for extension .exe is "%1" %* Set command line: Run command line Working dir '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Command line returned 0 Entering ReleaseSource() for \\sccmserver.abc.com\SMSPKGD$\DC10001D reference count 1 for the source \\sccmserver.abc.com\SMSPKGD$\DC10001D\ before releasing Released the resolved source \\sccmserver.abc.com\SMSPKGD$\DC10001D\. I attempted to deploy the same image/task sequence to a Dell GX280 [dual processor with the "ACPI Multiprocessor PC - ACPIAPIC_MP"], and after the restart the blank screen appeared with no hard drive activity. The following is loged on the SCCM server [errors present]; The task sequence execution engine successfully completed the action (Update HAL) in the group (Install Operating System) with exit code 0 Action output: \DC10001D". See whether the share has already been connected. Connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Successfully connected to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Resolved source to '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Command line forextension .exe is "%1" %* Set command line: Run command line Working dir '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. ????4???????????4??????????????????????????????????Command line returned 0 Entering ReleaseSource() for \\sccmserver.abc.com\SMSPKGD$\DC10001Dreference count 1 for the source \\sccmserver.abc.com\SMSPKGD$\DC10001D\ before releasing Released the resolved source \\sccmserver.abc.com\SMSPKGD$\DC10001D\\sccmserver.abc.com\SMSPKGD$\DC10001D\ZTIHaldetect.vbs(61, 5) Microsoft VBScript runtime error: Path not found ??????????????????????????????????4???????????›???????. I placed the ZTIHaldetect.vbs in the Task Sequence after "Apply Network Settings" and before "Setup Operating System" -- is this the correct spot for it? Should the "Start in" field on the Task Sequence that holds the ZTIHaldetect.vbs be blank? If not, what should be there? Does anyone have any ideas why the "ZTIHaldetect.vbs" script would be failing? Thanks for any pointers you can provide. Regards.

iburnell -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/8/2008 11:27:32 AM)
I have this set immediately after Apply Operating System TS. Sounds to me like there's an issue with the package location. Try refreshing the DP with the package to see if that fixes it because its not even running the script by the look of your log One other tip - checkout your build can resolve the FQDN path by pinging the server from the F8 prompt during the build. I've hit this before and its a DNS issue- changing the site role not to use FQDN (temporaily) fixed it

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 10:15:07 AM)
quote: ORIGINAL: iburnell I have this set immediately after Apply Operating System TS. Sounds to me like there's an issue with the package location. Try refreshing the DP with the package to see if that fixes it because its not even running the script by the look of your log One other tip - checkout your build can resolve the FQDN path by pinging the server from the F8 prompt during the build. I've hit this before and its a DNS issue- changing the site role not to use FQDN (temporaily) fixed it Ian, Thanks for the reply. I will move the UpdateHAL step to immediately after Apply Operating System, per your suggestion. I am able to see the script files on the DP (\\<sccmserver>\smspkgd$\DC10001D) via another computer on the domain. I have not verified within WinPE and F8 if I can see the files -- I will be checking shortly and post back. Thanks for the suggestions. Regards.

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 11:06:03 AM)
So a bit more info after troubleshooting. In WinPE I can; 1) ping FQDN of SCCM server 2) Map drive to \\sccmserver.abc.com\smspkgd$ 3) Browse to Advertisement ID share and view script files I was able to grab the smsts.log and here is an excerpt from the relevant section for UpdateHAL TS step; quote: LOG]!><time="14:35:05.703+240" date="06-09-2008" component="TSManager" context="" type="1" thread="1428" file="instruction.cxx:2957"> <![LOG[Expand a string: WinPEandFullOS]LOG]!><time="14:35:05.703+240" date="06-09-2008" component="TSManager" context="" type="0" thread="1428" file="executionenv.cxx:782"> <![LOG[Executing command line: smsswd.exe /run:DC10001D cscript.exe ZTIHaldetect.vbs]LOG]!><time="14:35:05.703+240" date="06-09-2008" component="TSManager" context="" type="1" thread="1428" file="commandline.cpp:799"> <![LOG[=======================[ smsswd.exe ] =======================]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="main.cpp:303"> <![LOG[PackageID = 'DC10001D']LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="main.cpp:332"> <![LOG[BaseVar = '', ContinueOnError='']LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="main.cpp:333"> <![LOG[SwdAction = '0001']LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="main.cpp:334"> <![LOG[Found the location for the package _SMSTSDC10001D. The location is on \\sccmserver.abc.com\SMSPKGD$\DC10001D\]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="resolvesource.cpp:2438"> <![LOG[nPos != CCM::Utility::String::npos, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,165)]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="0" thread="564" file="resolvesource.cpp:165"> <![LOG[Creating a connection to \\sccmserver.abc.com\SMSPKGD$\DC10001D\ with default computer account]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="resolvesource.cpp:1997"> <![LOG[Connection request for "\\sccmserver.abc.com\SMSPKGD$\DC10001D"]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="tsconnection.cpp:208"> <![LOG[No credentials available for connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D". See whether the share has already been connected.]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="tsconnection.cpp:233"> <![LOG[Connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D"]LOG]!><time="14:35:05.812+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="tsconnection.cpp:268"> <![LOG[Successfully connected to "\\sccmserver.abc.com\SMSPKGD$\DC10001D"]LOG]!><time="14:35:05.828+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="tsconnection.cpp:287"> <![LOG[Resolved source to '\\sccmserver.abc.com\SMSPKGD$\DC10001D']LOG]!><time="14:35:05.828+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:178"> <![LOG[Command line for extension .exe is "%1" %]LOG]!><time="14:35:05.843+240" date="06-09-2008" component="InstallSoftware" context="" type="0" thread="564" file="commandline.cpp:229"> <![LOG[Set command line: Run command line]LOG]!><time="14:35:05.843+240" date="06-09-2008" component="InstallSoftware" context="" type="0" thread="564" file="commandline.cpp:701"> <![LOG[Working dir '\\sccmserver.abc.com\SMSPKGD$\DC10001D']LOG]!><time="14:35:05.843+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:266"> <![LOG[Executing command line: Run command line]LOG]!><time="14:35:05.843+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="commandline.cpp:799"> <![LOG[Process completed with exit code 0]LOG]!><time="14:35:06.015+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="commandline.cpp:1071"> <![LOG[Microsoft (R) Windows Script Host Version 5.7]LOG]!><time="14:35:06.015+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:30"> <![LOG[Copyright (C) Microsoft Corporation. All rights reserved.]LOG]!><time="14:35:06.015+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:30"> <![LOG[]LOG]!><time="14:35:06.015+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:30"> <![LOG[\\sccmserver.abc.com\SMSPKGD$\DC10001D\ZTIHaldetect.vbs(61, 5) Microsoft VBScript runtime error: Path not found]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="3" thread="564" file="runcommandline.cpp:36"> <![LOG[]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="3" thread="564" file="runcommandline.cpp:36"> <![LOG[Command line returned 0]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="runcommandline.cpp:283"> <![LOG[Entering ReleaseSource() for \\sccmserver.abc.com\SMSPKGD$\DC10001D\]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="resolvesource.cpp:2687"> <![LOG[reference count 1 for the source \\sccmserver.abc.com\SMSPKGD$\DC10001D\ before releasing]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="resolvesource.cpp:2694"> <![LOG[Released the resolved source \\sccmserver.abc.com\SMSPKGD$\DC10001D\]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="InstallSoftware" context="" type="1" thread="564" file="resolvesource.cpp:2714"> <![LOG[Process completed with exit code 0]LOG]!><time="14:35:06.031+240" date="06-09-2008" component="TSManager" context="" type="1" thread="1428" file="commandline.cpp:1071"> <![LOG[!--------------------------------------------------------------------------------------------!] From the SCCM Console, the error appears as; quote:* The task sequence execution engine successfully completed the action (Update HAL) in the group (Install Operating System) with exit code 0 Action output: \DC10001D". See whether the share has already been connected. Connecting to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Successfully connected to "\\sccmserver.abc.com\SMSPKGD$\DC10001D" Resolved source to '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Command line forextension .exe is "%1" %* Set command line: Run command line Working dir '\\sccmserver.abc.com\SMSPKGD$\DC10001D' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. ????4???????????4??????????????????????????????????Command line returned 0 Entering ReleaseSource() for \\sccmserver.abc.com\SMSPKGD$\DC10001Dreference count 1 for the source \\sccmserver.abc.com\SMSPKGD$\DC10001D\ before releasing Released the resolved source \\sccmserver.abc.com\SMSPKGD$\DC10001D\\sccmserver.abc.com\SMSPKGD$\DC10001D\ZTIHaldetect.vbs(61, 5) Microsoft VBScript runtime error: Path not found ??????????????????????????????????4???????????›???????. To me, it looks like it can locate the script and execute it, but the error lies within the script. (\SMSPKGD$\DC10001D\ZTIHaldetect.vbs(61, 5) Microsoft VBScript runtime error: Path not found) -- on line 61?? Also to note, the OSD deploy took the drive letter E: before rebooting. I noticed in the ZTIHalDetect.vbs, it is looking to write to the sysprep.inf file on the C: drive; If sHalType(0) = "acpiapic" Then if oWshShell.Environment.item("NUMBER_OF_PROCESSORS") = 1 then WriteIni "c:\sysprep\sysprep.inf", "Unattended", "UpdateUPHAL", "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" else writeini "c:\sysprep\sysprep.inf", "Unattended", "UpdateHAL", "ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" end if Do I need to change this to read that sysprep.inf is located on E: ? Back to troubleshooting....

wbracken -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 11:16:00 AM)
Although I dont use this script itself it seems that the drive letter should be whatever your partition that your OS is being applied to. This is typically C: The exception is if your running the advertisement from withing Windows which would then apply Windows PE to the local drive then reboot to it. This scenerio then could change the drive letter of your "local drive" from C: to E: (if I recall correctly). My custom script checks for the existance of X:\Sysprep\Sysprep.inf in multiple drive letters (C:, E:, X:) and then modifies sysprep.inf once it finds where it is. Hope this helps!

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 11:44:01 AM)
quote: ORIGINAL: wbracken Although I dont use this script itself it seems that the drive letter should be whatever your partition that your OS is being applied to. This is typically C: The exception is if your running the advertisement from withing Windows which would then apply Windows PE to the local drive then reboot to it. This scenerio then could change the drive letter of your "local drive" from C: to E: (if I recall correctly). My custom script checks for the existance of X:\Sysprep\Sysprep.inf in multiple drive letters (C:, E:, X:) and then modifies sysprep.inf once it finds where it is. Hope this helps! William, Thank you for the reply. I think you are on to something. You are correct that I am initiating the OSD from within Windows (not PXE). I just manually changed the path in the ZTIHalDetect script for sysprep.inf to appear as; If sHalType(0) = "acpiapic" Then if oWshShell.Environment.item("NUMBER_OF_PROCESSORS") = 1 then WriteIni "e:\sysprep\sysprep.inf", "Unattended", "UpdateUPHAL", "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" else writeini "e:\sysprep\sysprep.inf", "Unattended", "UpdateHAL", "ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" end if And it did not report any errors, and updated the sysprep.inf file! I checked the sysprep.inf file and it was updated with the line "UpdateHAL=ACPIAPIC_MP,X:\windows\Inf\Hal.inf" - should this be pointing to the path of X:\, or C:\? It seems to be resolving the variable %WINDIR% as "X:" So the next task is to incorporate the query which you mention - to check for which drive the sysprep.inf file resides, and switch the paths accordingly. Could you post a sample of your script that checks for the sysprep location and updates the paths? Thanks again for the help! Regards.

wbracken -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 11:50:51 AM)

Here's the snippet from my script:

'#######################################
'  get location of Sysprep
'#######################################
strSysprep = "Sysprep\Sysprep.inf"
Set FSO = CreateObject("Scripting.FileSystemObject")
If FSO.FileExists("E:\Sysprep\Sysprep.inf") Then
 strSysDrv = "E:"
 strADTXT = "E:\adsite.txt"
ElseIf FSO.FileExists("C:\Sysprep\Sysprep.inf") Then
 strSysDrv = "C:"
 strADTXT = "C:\adsite.txt"
ElseIf FSO.FileExists("X:\Sysprep\Sysprep.inf") Then
 strSysDrv = "X:"
 strADTXT = "X:\adsite.txt"
End If

The WINDIR will unfortunately resolve to the wrong directory if running from within Windows PE because its using Windows PE's variable of the WINDIR, not the installed OS. This is why you see the strSysDrv in my snippet above so that I can set that inf location based on this value instead of the WINDIR variable. ;)

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 12:10:14 PM)
Thanks for posting the script. I am curious why you have the "strADTXT" lines? Also, how would I carry the variable over to the WriteINI lines? [sorry for the basic questions, I'm a VBscript newbie]

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 12:39:30 PM)
Another thing I noticed with my testing (now that the UpdateHAL is somewhat working)... I created the image on a ACPI Uniprocessor PC (ACPIAPIC_UP) HAL. "ACPI Uniprocessor PC - ACPIAPIC_UP" to "ACPI Uniprocessor PC - ACPIAPIC_UP" = Success "ACPI Uniprocessor PC - ACPIAPIC_UP" to "ACPI Multiprocessor PC - ACPIAPIC_MP" = Success "ACPI Uniprocessor PC - ACPIAPIC_UP" to "Advanced Configuration and Power Interface (ACPI) PC - ACPIPIC_UP" = Fail Has anyone been able to successfuly deploy to the scenario #3 listed above?

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/9/2008 2:52:18 PM)
quote: ORIGINAL: jq Another thing I noticed with my testing (now that the UpdateHAL is somewhat working)... I created the image on a ACPI Uniprocessor PC (ACPIAPIC_UP) HAL. "ACPI Uniprocessor PC - ACPIAPIC_UP" to "ACPI Uniprocessor PC - ACPIAPIC_UP" = Success "ACPI Uniprocessor PC - ACPIAPIC_UP" to "ACPI Multiprocessor PC - ACPIAPIC_MP" = Success "ACPI Uniprocessor PC - ACPIAPIC_UP" to "Advanced Configuration and Power Interface (ACPI) PC - ACPIPIC_UP" = Fail Has anyone been able to successfuly deploy to the scenario #3 listed above? Sorry to keep bumping the thread, but wanted to update with my findings. I read through the support article by Microsoft [http://support.microsoft.com/?id=309283] which explains the scenarios, and came across this; quote: You can deploy a Sysprep image created on a computer that uses an ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll) to a computer that uses the following HAL types: - ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll) - ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll) So it appears that it is not possible according to Microsoft - can anyone confirm this?

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/10/2008 11:04:55 AM)
So I'm pretty sure I have this close to being complete. I just need to confirm one last thing; For the UpdateHAL/UpdateUPHAL in the [Unattended] section of the sysprep.inf file, should the %WINDIR% path resolve to where the sysprep.inf file currently resides (in my examples this was on the E: drive) - or - should this be hardcoded with a path to the C: drive (the final drive letter after the renaming?) Thanks to anyone who can confirm. Regards.

wbracken -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/10/2008 1:38:26 PM)
That should be whatever drive letter contains your Windows installation when its boots for the first time I do believe which is typically C: of course.

jq -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/10/2008 4:35:08 PM)
William, Thank you for the reply. I hardcoded the path C:\WINDOWS to substitute the %WINDIR% variable and it is working very well now. I tested on a VM platform and I ended up getting this error; quote: The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point. Once I powered off the VM and started it again, it proceeded with the task sequence. I did not get any errors when running on two separate physical machines (one was a Uniprocessor, the other was a Multiprocessor). Thanks again for all your help. Regards.

wbracken -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/10/2008 11:26:09 PM)
Excellent! Good on ya jq I am glad I could contribute. [:)]

MhermanNBME -> RE: Question for HAL Swapping & "ZTIHaldetect.vbs" script (6/12/2008 4:45:37 PM)
As for the drive letter in a task sequense, I think the best way would be to use the task sequence values. I got this from another thread on this forum, it's in the beginning of my ztihaldetect: --------------------------------------------------------------- Set env = CreateObject("Microsoft.SMS.TSEnvironment") driveLtr = env("OSDTargetSystemDrive") sysprepfile = driveLtr & "\sysprep\sysprep.inf" ---------------------------------------------------------------- and all the writeini locations are changed to 'sysprepfile' that will use the right drive letter no matter what. I'm not sure of the details, but i'm pretty sure it's possible to go from any hal to any to any hal, but certian senarios are "not supported" by microsoft.

Page: [1]

0.296875