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

New Panasonic Toughbook Imaging Bundles Available For Download NOW (Updated)

 MDT, SCCM, Scripting, Windows 7, Windows XP  2 Responses »
Dec 312012
 
Toughbook Logo

— Fixed Bundles URL (May 1, 2013)

In some Panasonic Toughbook models upwards of 15 utilities are required to be installed to function properly. Add in some optional components, such as Wireless WAN Connectivity, GPS, and a Barcode Reader, and we could be in the neighborhood of 20-30 required installs. These “bundles” were produced to greatly simplify all of these mandatory installs.

Bundles Pros:

  1. ONE install step per Model/Mark (19A – Mk5)
  2. Logs all activity to single file (C:\Windows\Temp\Pana….log)
  3. Works with all Imaging Suites (SCCM, MDT2010/2012, LANDesk, KACE, Altiris, etc.)
  4. Supported and Produced by Panasonic.
  5. Installs and Drivers are NOT Re-Packaged or Re-Engineered.

Cons:

  1. Does not include Storage or LAN drivers, these must be downloaded from Intel (http://downloadcenter.intel.com/)
  2. Added into Imaging Suites, yet managed on File level (.ZIP file names in SRC\ folders dictate what and when they are installed)

See the following .PDF for assistance in downloading and utilizing the bundles.

Updated URL – 5/1/2013
https://panaconsulting.egnyte.com/publicController.do?folderName=20130501&fileName=02ce201186d84d71

Feedback is encouraged! (Comment here or email my team at imaging@us.panasonic.com)

Temp3

2013Jan08-RunningBundleInSCCM2012

 

 

-BG

Share

VBScript written to stage new drivers in Windows XP

 Scripting, Windows XP  No Responses »
Jul 142012
 

Script was written to stage docking station drivers into a Windows XP machine.

GitHub URL: StageDockingLANDriver.vbs

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

 
'==========================================================================
'
' NAME: StageDockingLANDriver.vbs
'
' AUTHOR: Brian Gonzalez, Panasonic 
' DATE  : 7/13/2012
'
' COMMENT:
'	Performs:
'	-Add Docking Station drivers to subDirectory of C:\Windows\inf
'	-Updates the DevicePath registry entry with newly copied driver folder.
'
'	Returns:
'	0 = No Errors
'	1 = Driver folder "lan9500-x86-n51f" not found.
'	2 = Copy of driver folder did not complete.
'	3 = Failed to read the current DevicePath value from registry.
'	4 = Failed to update registry.
'
'==========================================================================

On Error Resume Next
dim objFSO, objFile, objShell
 
set objFSO = CreateObject("Scripting.FileSystemObject")
set objShell = CreateObject("WScript.Shell")
strScriptFolder = objFSO.GetParentFolderName(WScript.ScriptFullName) 'No trailing backslash

strDockingDriverFolderPath = strScriptFolder & "\lan9500-x86-n51f"
strTargetDir = "C:\Windows\inf\dockingdrivers"
If objFSO.FolderExists(strDockingDriverFolderPath) Then
	objFSO.CopyFolder strDockingDriverFolderPath, strTargetDir, True
	If Err.Number <> 0 Then
		WScript.Quit(2)
	End If
Else
	WScript.Quit(1)
End If
 
strRegValPath = "HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath"
strCurrDevicePath = objShell.RegRead(strRegValPath)
If strCurrDevicePath = "" Then
	WScript.Quit(3)
End If
 
objShell.RegWrite strRegValPath, strCurrDevicePath & ";" & strTargetDir, "REG_EXPAND_SZ"
If Err.Number <> 0 Then
	WScript.Quit(4)
Else
	WScript.Quit(0)
End If
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
 Older Entries