MAK Key Aktivierung in der Tasksequence
Tom_BE
Ich habe ein Build and Capture Image erstellt mit der Basissoftware, Updates
etc. drin. Nun habe ich eine Tasksequence erstellt mit dem erstellten Image.
Alles funktioniert sehr gut. Ein Problem stellt sich mir nun noch. Wie und wo
kann ich den MAK Key integrieren und auch aktivieren mittels Tasksequence?
Die Command Line für den MAK Key müsste wohl so aussehen:
cscript.exe c:\windows\system32\slmgr.vbs -ipk <MAK Key>
gefolgt von:
cscript.exe c:\windows\system32\slmgr.vbs -ato
für die Aktivierung.
Nur sehe ich nicht ganz wo dies in der Tasksequence rein muss, wohl am
Schluss? Funktioniert die Aktivierung überhaupt während der Tasksequence?
Oder kann ich dies auch schon im Build and Capture integrieren?
Hat da schon jemand Erfahrungen gesammelt oder weis jemand Rat?
Danke für die geschätzte Hilfe.
Gruss Tom
Unten die aktuelle Tasksequence:
******************************************************
<?xml version="1.0"?>
<SmsTaskSequencePackage
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<BootImageID>C0000001</BootImageID>
<Category />
<DependentProgram />
<Description />
<Duration>360</Duration>
<Name>VOS:1.4W</Name>
<ProgramFlags>152084496</ProgramFlags>
<SequenceData>
<sequence version="3.00">
<referenceList>
<reference package="C0000019" />
<reference package="C000006F" />
<reference package="C0000016" />
</referenceList>
<globalVarList>
<variable name="OSDEnableTCPIPFiltering"
property="EnableTCPIPFiltering">false</variable>
<variable name="OSDAdapterCount" property="NumAdapters">0</variable>
</globalVarList>
<group name="Install Operating System" description="Actions to run in
Windows PE to install and configure the image">
<step type="SMS_TaskSequence_PartitionDiskAction" name="Partition
Disk 0" description="Actions to partition and format the new machine"
runIn="WinPE" successCodeList="0">
<condition>
<expression type="SMS_TaskSequence_VariableConditionExpression">
<variable name="Operator">notExists</variable>
<variable name="Variable">_SMSTSClientCache</variable>
</expression>
</condition>
<action>osddiskpart.exe</action>
<defaultVarList>
<variable name="OSDDiskIndex" property="DiskIndex">0</variable>
<variable name="OSDDiskType" property="DiskType">Basic</variable>
<variable name="OSDDiskpartBiosCompatibilityMode"
property="DiskpartBiosCompatibilityMode">false</variable>
<variable name="OSDGPTBootDisk"
property="GPTBootDisk">false</variable>
<variable name="OSDPartitionStyle"
property="PartitionStyle">MBR</variable>
<variable name="OSDPartitions" property="Partitions"
hidden="true">1</variable>
<variable name="OSDPartitions0Bootable"
property="Partitions0Bootable">true</variable>
<variable name="OSDPartitions0FileSystem"
property="Partitions0FileSystem">NTFS</variable>
<variable name="OSDPartitions0QuickFormat"
property="Partitions0QuickFormat">true</variable>
<variable name="OSDPartitions0Size"
property="Partitions0Size">100</variable>
<variable name="OSDPartitions0SizeUnits"
property="Partitions0SizeUnits">PERCENT</variable>
<variable name="OSDPartitions0Type"
property="Partitions0Type">PRIMARY</variable>
<variable name="OSDPartitions0VolumeLetterVariable"
property="Partitions0VolumeLetterVariable">
</variable>
<variable name="OSDPartitions0VolumeName"
property="Partitions0VolumeName">XXXX</variable>
</defaultVarList>
</step>
<step type="SMS_TaskSequence_ApplyOperatingSystemAction" name="Apply
Operating System" description="Actions to apply operating system"
runIn="WinPE" successCodeList="0">
<action>OSDApplyOS.exe /image:C000006F,%OSDImageIndex%
"/config:C0000019,%OSDConfigFileName%"</action>
<defaultVarList>
<variable name="OSDConfigFileName"
property="ConfigFileName">unattend.xml</variable>
<variable name="ConfigFilePackage" property="ConfigFilePackage"
hidden="true">C0000019</variable>
<variable name="OSDImageIndex" property="ImageIndex">1</variable>
<variable name="ImagePackageID" property="ImagePackageID"
hidden="true">C000006F</variable>
</defaultVarList>
</step>
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply
Windows Settings" description="Actions to apply windows settings"
runIn="WinPE" successCodeList="0">
<action>osdwinsettings.exe /config</action>
<defaultVarList>
<variable name="OSDLocalAdminPassword" property="AdminPassword">
</variable>
<variable name="OSDComputerName"
property="ComputerName">%_SMSTSMachineName%</variable>
<variable name="OSDProductKey" property="ProductKey">
</variable>
<variable name="OSDRandomAdminPassword"
property="RandomAdminPassword">false</variable>
<variable name="OSDRegisteredOrgName"
property="RegisteredOrgName">XXXX</variable>
<variable name="OSDRegisteredUserName"
property="RegisteredUserName">XXXX</variable>
<variable name="OSDServerLicenseConnectionLimit"
property="ServerLicenseConnectionLimit">5</variable>
<variable name="OSDTimeZone" property="TimeZone">W. Europe
Standard Time</variable>
</defaultVarList>
</step>
<step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply
Network Settings" description="Actions to configure network settings"
runIn="WinPEandFullOS" successCodeList="0">
<action>osdnetsettings.exe configure</action>
<defaultVarList>
<variable name="OSDDomainName"
property="DomainName">XXXX</variable>
<variable name="OSDDomainOUName"
property="DomainOUName">LDAP://OU=XXXX,OU=XXXX,DC=XXXX,DC=XXXX,DC=XXXX,DC=XXXX</variable>
<variable name="OSDJoinPassword" property="DomainPassword">
</variable>
<variable name="OSDJoinAccount"
property="DomainUsername">XXXX</variable>
<variable name="OSDEnableTCPIPFiltering"
property="EnableTCPIPFiltering" hidden="true">false</variable>
<variable name="OSDNetworkJoinType"
property="NetworkJoinType">0</variable>
<variable name="OSDAdapterCount" property="NumAdapters"
hidden="true">0</variable>
</defaultVarList>
</step>
</group>
<group name="Setup Operating System" description="Setup Operating
System">
<step type="SMS_TaskSequence_SetupWindowsAndSMSAction" name="Setup
windows and ConfigMgr" description="Actions to setup windows and ConfigMgr
client" runIn="WinPEandFullOS" successCodeList="0">
<action>OSDSetupWindows.exe</action>
<defaultVarList>
<variable name="SMSClientInstallProperties"
property="ClientInstallProperties">SMSCACHESIZE=10000</variable>
<variable name="_SMSClientPackageID"
property="ClientPackageID">C0000016</variable>
</defaultVarList>
</step>
</group>
<group name="Install Updates" description="">
<step type="SMS_TaskSequence_InstallUpdateAction" name="Install
Updates" description="" continueOnError="true" runIn="FullOS"
successCodeList="0">
<condition>
<expression type="SMS_TaskSequence_VariableConditionExpression">
<variable name="Operator">notEquals</variable>
<variable name="Value">FullMedia</variable>
<variable name="Variable">_SMSTSMediaType</variable>
</expression>
</condition>
<action>TSInstallSWUpdate.exe
/target:%SMSInstallUpdateTarget%</action>
<defaultVarList>
<variable name="SMSInstallUpdateTarget"
property="Target">All</variable>
</defaultVarList>
</step>
</group>
<group name="Clear all Events" description="">
<step type="SMS_TaskSequence_RunCommandLineAction" name="Clear
EventViewer" description="" runIn="WinPEandFullOS" successCodeList="0 3010">
<action>smsswd.exe /run: wevtutil.exe clear-log Application &
wevtutil.exe clear-log Security & wevtutil.exe clear-log System</action>
<defaultVarList>
<variable name="CommandLine" property="CommandLine"
hidden="true">wevtutil.exe clear-log Application & wevtutil.exe clear-log
Security & wevtutil.exe clear-log System</variable>
<variable name="SMSTSDisableWow64Redirection"
property="DisableWow64Redirection">false</variable>
<variable name="_SMSTSRunCommandLineAsUser"
property="RunAsUser">false</variable>
<variable name="SuccessCodes" property="SuccessCodes"
hidden="true">0 3010</variable>
</defaultVarList>
</step>
</group>
</sequence>
</SequenceData>
<SourceDate>2008-12-29T14:32:30</SourceDate>
<SupportedOperatingSystems />
<IconSize>0</IconSize>
</SmsTaskSequencePackage>
******************************************************
Torsten [MVP]
das Thema gab's hier schon:
http://groups.google.de/group/microsoft.public.de.sms/browse_thread/thread/8c679a6b5454950/996fee1c3b3a37a8
Gruß,
Torsten
Torsten [MVP]
Der Link zeigt ja auf eine Frage von Dir; allerdings hast Du als letzte
Antwort geschrieben, dass es funktioniert hat. Wenn's einmal funktioniert
hat, dann muss es doch auch noch ein zweites Mal funktionieren. Also wie denn
jetzt? ;-)
Gruß,
Torsten
Tom_BE
Nach genaueren Test habe ich festgestellt, dass es eben doch nicht
funktioniert :-(.
Gruss Tom
Torsten [MVP]
was ist denn im setupact.log und im smsts.log bzw welche Fehlermeldung
kommt?
An welcher Stelle in der TS hast du denn das Skript eingebaut?
Gruß,
Torsten
"Tom_BE" <To...@discussions.microsoft.com> schrieb im Newsbeitrag
news:1E86031D-2A7D-4BBF...@microsoft.com...
Tom_BE
Nun der erste Teil, setzen des MAK Key, funktioniert (Auszug aus dem
smsts.log):
***********************************************************
Start executing an instruciton. Instruction name: Apply Key. Instruction
pointer: 13 TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Set a global environment variable _SMSTSCurrentActionName=Apply
Key TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Set a global environment variable
_SMSTSNextInstructionPointer=13 TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Set a local default variable
SMSTSDisableWow64Redirection TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Set a local default variable _SMSTSRunCommandLineAsUser TSManager 29.01.2009
09:41:57 2732 (0x0AAC)
Set a global environment variable
_SMSTSLogPath=C:\Windows\system32\CCM\Logs\SMSTSLog TSManager 29.01.2009
09:41:57 2732 (0x0AAC)
Expand a string: smsswd.exe /run: cscript.exe c:\windows\system32\slmgr.vbs
-ipk XXXX-XXXX-XXXX-XXXX-XXXX TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Expand a string: TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Command line for extension .exe is "%1" %* TSManager 29.01.2009
09:41:57 2732 (0x0AAC)
Set command line: smsswd.exe /run: cscript.exe c:\windows\system32\slmgr.vbs
-ipk XXXX-XXXX-XXXX-XXXX-XXXX TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Start executing the command line: smsswd.exe /run: cscript.exe
c:\windows\system32\slmgr.vbs -ipk
XXXX-XXXX-XXXX-XXXX-XXXX TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Expand a string: WinPEandFullOS TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
Executing command line: smsswd.exe /run: cscript.exe
c:\windows\system32\slmgr.vbs -ipk
XXXX-XXXX-XXXX-XXXX-XXXX TSManager 29.01.2009 09:41:57 2732 (0x0AAC)
=======================[ smsswd.exe ]
======================= InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
PackageID = '' InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
BaseVar = '', ContinueOnError='' InstallSoftware 29.01.2009 09:41:57 4056
(0x0FD8)
SwdAction = '0001' InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
Command line for extension .exe is "%1" %* InstallSoftware 29.01.2009
09:41:57 4056 (0x0FD8)
Set command line: Run command line InstallSoftware 29.01.2009 09:41:57 4056
(0x0FD8)
Working dir 'not set' InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
Executing command line: Run command line InstallSoftware 29.01.2009
09:41:57 4056 (0x0FD8)
Microsoft (R) Windows Script Host Version 5.7 InstallSoftware 29.01.2009
09:41:57 4056 (0x0FD8)
Copyright (C) Microsoft Corporation. All rights
reserved. InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
InstallSoftware 29.01.2009 09:41:57 4056 (0x0FD8)
Process completed with exit code 0 InstallSoftware 29.01.2009 09:42:07 4056
(0x0FD8)
Installed product key XXXX-XXXX-XXXX-XXXX-XXXX
successfully. InstallSoftware 29.01.2009 09:42:07 4056 (0x0FD8)
InstallSoftware 29.01.2009 09:42:07 4056 (0x0FD8)
Command line returned 0 InstallSoftware 29.01.2009 09:42:07 4056 (0x0FD8)
Process completed with exit code 0 TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Successfully complete the action (Apply Key) with the exit win32 code
0 TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Sending status message . . . TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Send a task execution status message
SMS_TSExecution_ActionCompleteInfo TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
***********************************************************
Der zweite Teil, Aktivierung von Vista funktioniert nicht (Auszug aus dem
smsts.log):
***********************************************************
Start executing an instruciton. Instruction name: Activating Vista.
Instruction pointer: 14 TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Set a global environment variable _SMSTSCurrentActionName=Activating
Vista TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Set a global environment variable
_SMSTSNextInstructionPointer=14 TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Set a local default variable
SMSTSDisableWow64Redirection TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Set a local default variable _SMSTSRunCommandLineAsUser TSManager 29.01.2009
09:42:07 2732 (0x0AAC)
Set a global environment variable
_SMSTSLogPath=C:\Windows\system32\CCM\Logs\SMSTSLog TSManager 29.01.2009
09:42:07 2732 (0x0AAC)
Expand a string: smsswd.exe /run: cscript.exe c:\windows\system32\slmgr.vbs
-ato TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Expand a string: TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Command line for extension .exe is "%1" %* TSManager 29.01.2009
09:42:07 2732 (0x0AAC)
Set command line: smsswd.exe /run: cscript.exe c:\windows\system32\slmgr.vbs
-ato TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Start executing the command line: smsswd.exe /run: cscript.exe
c:\windows\system32\slmgr.vbs -ato TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Expand a string: WinPEandFullOS TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
Executing command line: smsswd.exe /run: cscript.exe
c:\windows\system32\slmgr.vbs -ato TSManager 29.01.2009 09:42:07 2732 (0x0AAC)
=======================[ smsswd.exe ]
======================= InstallSoftware 29.01.2009 09:42:07 3368 (0x0D28)
PackageID = '' InstallSoftware 29.01.2009 09:42:07 3368 (0x0D28)
BaseVar = '', ContinueOnError='' InstallSoftware 29.01.2009 09:42:07 3368
(0x0D28)
SwdAction = '0001' InstallSoftware 29.01.2009 09:42:07 3368 (0x0D28)
Command line for extension .exe is "%1" %* InstallSoftware 29.01.2009
09:42:07 3368 (0x0D28)
Set command line: Run command line InstallSoftware 29.01.2009 09:42:07 3368
(0x0D28)
Working dir 'not set' InstallSoftware 29.01.2009 09:42:07 3368 (0x0D28)
Executing command line: Run command line InstallSoftware 29.01.2009
09:42:07 3368 (0x0D28)
Microsoft (R) Windows Script Host Version 5.7 InstallSoftware 29.01.2009
09:42:08 3368 (0x0D28)
Copyright (C) Microsoft Corporation. All rights
reserved. InstallSoftware 29.01.2009 09:42:08 3368 (0x0D28)
InstallSoftware 29.01.2009 09:42:08 3368 (0x0D28)
Process completed with exit code 1 InstallSoftware 29.01.2009 09:42:37 3368
(0x0D28)
Activating Windows(TM) Vista, Enterprise edition
(74e464f6-45db-41f6-9356-66260bdf3c65) ... InstallSoftware 29.01.2009
09:42:37 3368 (0x0D28)
Run 'slui.exe 0x2a 0x80072EFD' to display the error
text. InstallSoftware 29.01.2009 09:42:37 3368 (0x0D28)
Error: 0x80072EFD InstallSoftware 29.01.2009 09:42:37 3368 (0x0D28)
InstallSoftware 29.01.2009 09:42:37 3368 (0x0D28)
Command line returned 1 InstallSoftware 29.01.2009 09:42:37 3368 (0x0D28)
Process completed with exit code 1 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Failed to run the action: Activating Vista.
Incorrect function. (Error: 00000001; Source: Windows) TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Sending status message . . . TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Send a task execution status message
SMS_TSExecution_ActionFailError TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
MP server XXX and port 80. SSL=false. CRL=false. TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Site code: C00 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Client machine name: XXX TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Client GUID: GUID:11D4159F-214A-4402-B86E-F0CFA5C532A7 TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Advertisement ID: C002004E TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Package ID: C0000087 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Sending StatusMessage TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
CLibSMSMessageWinHttpTransport::Send: URL: XXX:80 CCM_POST
/ccm_system/request TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Set a global environment variable
_SMSTSLastActionRetCode=1 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Set a global environment variable
_SMSTSLastActionSucceeded=false TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Clear local default environment TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Let the parent group (Activating Vista) decides whether to continue
execution TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
The execution of the group (Activating Vista) has failed and the execution
has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Failed to run the last action: Activating Vista. Execution of task sequence
failed.
Incorrect function. (Error: 00000001; Source: Windows) TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Sending status message . . . TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Send a task execution status message
SMS_TSExecution_TaskSequenceFailError TSManager 29.01.2009 09:42:37 2732
(0x0AAC)
MP server XXX and port 80. SSL=false. CRL=false. TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Site code: C00 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Client machine name: XXX TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Client GUID: GUID:11D4159F-214A-4402-B86E-F0CFA5C532A7 TSManager 29.01.2009
09:42:37 2732 (0x0AAC)
Advertisement ID: C002004E TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Package ID: C0000087 TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Sending StatusMessage TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
CLibSMSMessageWinHttpTransport::Send: URL: XXX:80 CCM_POST
/ccm_system/request TSManager 29.01.2009 09:42:37 2732 (0x0AAC)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005
(e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,742) TSManager 29.01.2009 09:57:49 2732 (0x0AAC)
Task Sequence Engine failed! Code: enExecutionFail TSManager 29.01.2009
09:57:49 2732 (0x0AAC)
**************************************************************************** TSManager 29.01.2009 09:57:49 2732 (0x0AAC)
Task sequence execution failed with error code 80004005 TSManager 29.01.2009
09:57:49 2732 (0x0AAC)
Cleaning Up. Removing Authenticator TSManager 29.01.2009 09:57:49 2732
(0x0AAC)
Cleaning up task sequence folder TSManager 29.01.2009 09:57:49 2732 (0x0AAC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,420) TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Successfully unregistered Task Sequencing Environment COM
Interface. TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Command line for extension .exe is "%1" %* TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
Set command line: "C:\Windows\system32\CCM\TsProgressUI.exe"
/Unregister TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Executing command line: "C:\Windows\system32\CCM\TsProgressUI.exe"
/Unregister TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
==========[ TsProgressUI started in process 1132
]========== TsProgressUI 29.01.2009 09:57:50 3100 (0x0C1C)
Command line: "C:\Windows\system32\CCM\TsProgressUI.exe"
/Unregister TsProgressUI 29.01.2009 09:57:50 3100 (0x0C1C)
Unregistering COM classes TsProgressUI 29.01.2009 09:57:50 3100 (0x0C1C)
Unregistering class objects TsProgressUI 29.01.2009 09:57:50 3100 (0x0C1C)
Shutdown complete. TsProgressUI 29.01.2009 09:57:50 3100 (0x0C1C)
Process completed with exit code 0 TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Successfully unregistered TS Progress UI. TSManager 29.01.2009 09:57:50 2732
(0x0AAC)
Setting program history for C0000087:* TSManager 29.01.2009 09:57:50 2732
(0x0AAC)
Opening the task sequence key HKLM\Software\Microsoft\SMS\Task
Sequence TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Deleting the package ID from registry key HKLM\Software\Microsoft\SMS\Task
Sequence\Package TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
kTaskSequence.DeleteValue(L"Package"), HRESULT=80070002
(e:\nts_sms_fre\sms\framework\tscore\utils.cpp,3053) TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task
Sequence\Package. Error code 0x80070002 TSManager 29.01.2009 09:57:50 2732
(0x0AAC)
Deleted 64 instances TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Policy cleanup done TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
g_TSManager.Run(), HRESULT=80004005
(e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,646) TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Error Task Sequence Manager failed to execute task sequence. Code
0x80004005 TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Sending error status message TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Sending StatusMessage TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
CLibSMSMessageWinHttpTransport::Send: URL: XXX:80 CCM_POST
/ccm_system/request TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Resuming SMS Components TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Waiting for CcmExec service to be fully operational TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
CcmExec service is up and fully operational TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
The cookie that will be used for SWD resume = 17776 TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
Resume for CCM component SoftwareDistribution requested TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
The cookie that will be used for SWUpdate resume =
17776 TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Resume for CCM component SoftwareUpdates requested TSManager 29.01.2009
09:57:50 2732 (0x0AAC)
Access handle will be read from
_SMSTSActiveRequestHandle TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Access handle: TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
IIDFromString(bsHandle, &ActiveRequestGUID) == S_OK, HRESULT=80004005
(e:\nts_sms_fre\sms\client\tasksequence\tsmanager\swdupdatescontroller.cpp,298) TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
IIDFromString() failed. TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Task Sequence Manager could not release active TS request. code
80004005 TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Opening the task sequence key HKLM\Software\Microsoft\SMS\Task
Sequence TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Deleting a pause cookie from registry key HKLM\Software\Microsoft\SMS\Task
Sequence\SoftwareDistribution TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Opening the task sequence key HKLM\Software\Microsoft\SMS\Task
Sequence TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Deleting a pause cookie from registry key HKLM\Software\Microsoft\SMS\Task
Sequence\SoftwareUpdates TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
Opening the task sequence key HKLM\Software\Microsoft\SMS\Task
Sequence TSManager 29.01.2009 09:57:50 2732 (0x0AAC)
***********************************************************
Die beiden Command Line laufen an der letzten Stelle des TS.
Danke für Deine Hilfe,
Torsten [MVP]
jetzt ist die Frage, ob das Skript mit dem Parameter -ato zwar funktioniert
und sich (unsinnigerweise) mit Errorcode 1 beendet oder aber ob da wirklich
etwas schief gelaufen ist.
Mit slmgr.vbs -dlv kannst Du danach den Aktivierungsstatus überprüfen.
Zur Not einfach mal den Step mit -ato in der TS weglassen und danach
händisch starten und schauen, wie sich das Ding verhält (vor allem wegen dem
Errorcode). Vielleicht sieht man im Eventlog oder in einem sonstigen Log
irgendwas ;-)
Tom_BE
Ich habe den Fehler nun gefunden. Während der Tasksequence ist noch kein
Proxy-Server im IE eingetragen. Daher funktioniert die Aktivierung nicht.
Trage ich den Proxy manuell ein und starten den Skript mit dem Parameter
slmgr.vbs -ato funktioniert die Aktivierung.
Nun stellt sich gleich das nächste Problem. Wie trage ich den Proxy während
der Tasksequence ein? Habe da bisher nichts dazu gefunden. Hast Du da event.
eine Idee?
Danke für Deine geschätzte Hilfe,
Torsten [MVP]
Google spuckte ziemlich schnell das aus:
http://www.microsoft.com/technet/scriptcenter/resources/qanda/may05/hey0519.mspx
oder per GPO.
Gruß,
Torsten
"Tom_BE" <To...@discussions.microsoft.com> schrieb im Newsbeitrag
news:25A95086-4746-4593...@microsoft.com...