Receiving “The /target parameter specifies an invalid target location.” when attempting to Install XP SP3 via MDT 2012 TS in SCCM 2012 SP1 Beta

 SCCM2012, Windows XP  No Responses »
Jan 092013
 

Post URL: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/ca4ca7ba-b208-4c19-9a60-cd8a5f1e7169

Built DC01 and CM01 via Johan’s Hydration Kit. Win 7 deploys with no issues, but fails when attempting to install XP via a clean or .WIM installation.

Receiving a “The /target parameter specifies an invalid target location.” error.

SMS..log output:
<![LOG[Expand a string: OSDApplyOS.exe /install:PS100019,%OSDInstallEditionIndex% "/config:PS100015,%OSDConfigFileName%" /target:%OSDisk%]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”0″ thread=”1472″ file=”executionenv.cxx:782″>

<![LOG[Expand a string: ]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”0″ thread=”1472″ file=”executionenv.cxx:782″>
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”0″ thread=”1472″ file=”commandline.cpp:228″>
<![LOG[Set command line: OSDApplyOS.exe /install:PS100019,%OSDInstallEditionIndex% "/config:PS100015,%OSDConfigFileName%" /target:%OSDisk%]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”0″ thread=”1472″ file=”commandline.cpp:706″>
<![LOG[Start executing the command line: OSDApplyOS.exe /install:PS100019,%OSDInstallEditionIndex% "/config:PS100015,%OSDConfigFileName%" /target:%OSDisk%]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”1″ thread=”1472″ file=”instruction.cxx:2929″>
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”1″ thread=”1472″ file=”instruction.cxx:2958″>
<![LOG[Expand a string: WinPE]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”0″ thread=”1472″ file=”executionenv.cxx:782″>
<![LOG[Executing command line: OSDApplyOS.exe /install:PS100019,%OSDInstallEditionIndex% "/config:PS100015,%OSDConfigFileName%" /target:%OSDisk%]LOG]!><time=”21:10:57.509+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”1″ thread=”1472″ file=”commandline.cpp:802″>
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time=”21:10:57.565+300″ date=”01-08-2013″ component=”ApplyOperatingSystem” context=”" type=”0″ thread=”1892″ file=”commandline.cpp:228″>
<![LOG[Set command line: "OSDApplyOS.exe" /install:PS100019,1 "/config:PS100015,unattend.txt" /target:%OSDisk%]LOG]!><time=”21:10:57.565+300″ date=”01-08-2013″ component=”ApplyOperatingSystem” context=”" type=”0″ thread=”1892″ file=”commandline.cpp:706″>
<![LOG[((g_Target.Disk > 0) || (arg == L"0")) && (g_Target.Partition >= c_MinPartition), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,254)]LOG]!><time=”21:10:57.565+300″ date=”01-08-2013″ component=”ApplyOperatingSystem” context=”" type=”0″ thread=”1892″ file=”applyos.cpp:254″>
<![LOG[The /target parameter specifies an invalid target location.]LOG]!><time=”21:10:57.565+300″ date=”01-08-2013″ component=”ApplyOperatingSystem” context=”" type=”3″ thread=”1892″ file=”applyos.cpp:254″>
<![LOG[ParseCommandLine(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,429)]LOG]!><time=”21:10:57.565+300″ date=”01-08-2013″ component=”ApplyOperatingSystem” context=”" type=”0″ thread=”1892″ file=”applyos.cpp:429″>
<![LOG[Process completed with exit code 2147942487]LOG]!><time=”21:10:57.571+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”1″ thread=”1472″ file=”commandline.cpp:1098″>
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time=”21:10:57.571+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”1″ thread=”1472″ file=”instruction.cxx:3011″>
<![LOG[Failed to run the action: Apply Operating System Image. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time=”21:10:57.571+300″ date=”01-08-2013″ component=”TSManager” context=”" type=”3″ thread=”1472″ file=”instruction.cxx:3102″>

Log Files .ZIP: https://panaconsulting.box.com/s/k9h067346p8g2mwzt473

Share

Apply Open Office Settings via Script Or Batch

 MDT, SCCM, Scripting, Windows 7, Windows XP  No Responses »
Jan 192011
 

In most cases, my customer base have decided to install Open Office applications outside of their base images.  The silent installations are fairly simple, because the install files are provided in .MSI format.

Applying custom settings after a clean installation need to also be addressed.  I found this was also fairly simple.  All of the settings changed are made to the files stored in the following folder:
Windows 7: “C:\Users\Administrator\AppData\Roaming\OpenOffice.org”
Windows XP: “C:\Documents and Settings\Administrator\Application Data\OpenOffice.org”

So Simply apply the desired setting changes on a test machine and capture the settings folder.  Then change the permissions of the folder to the following:

Grant Everyone “Full Control”
image
image

Next in your Post Image processing overwrite the Directory with your custom settings Directory and you are all set.
xcopy "%~dp0OpenOffice.org\" "C:\Users\Administrator\AppData\Roaming\OpenOffice.org" /heyi

Share

How to Build a Script or Batch to Change “When I close the lid of my portable computer” Setting in Windows XP

 MDT, Scripting, Windows XP  2 Responses »
Jan 162011
 

I build all of my Core images in Virtual Machine environments.  There are many benefits of doing this, which I’ll leave for another article.  However, some cons exist; such as the ability to change settings only related to portable computers in the core image prior to capture.  Due to this limitation, I need to set this setting Post-Image.  Unfortunately, Windows XP’s “powercfg.exe” built-in utility does not have this setting available.  I found a great 3rd party, which works flawlessly and runs silent.

image

URL: https://panaconsulting.egnyte.com/h-s/20111107/6dc07a5da5c74062
Includes: “Disable Standby.exe” AND “Enable Standby.exe”

Due to the Advanced setting being tied to each User account,  the application must be run by the End User to apply the setting.  To force this action, I added a call to the application in the “Default User”’s StartUp Folder.  See files used below:

EnableStandbySetup.bat

copy “%~dp0Enable Standby.exe” “%TEMP%\Enable Standby.exe”
copy “%~dp0EnableStandby.bat” “C:\Documents and Settings\Default User\Start Menu\Programs\Startup\EnableStandby.bat”
start /w “Enable Standby” “%TEMP%\Enable Standby.exe”

EnableStandby.bat

start /w “Enable Standby on Lid Close” “%TEMP%\Enable Standby.exe”
del “%~dp0EnableStandby.bat” /q

Note: “Enable Standby.exe” can be replaced with “Disable Standby.exe” to perform that desired.

Share