GrizNation23
asked on
SCCM Deployment PXE
We seem to be having issues with our image packages or something just doesnt seem right and I am hoping someone would be able to give pointers for troubleshooting, what logs to view or where to start. the errors are below with Dell Optiplex machines:
optiolex 755
optiplex 745
Also a Latitude E5440
The issues/errors below are what we get every 3 to 6 machines we try to image, but what concerns me is that we get the errors, but after few runs, they complete successfully. Suggestions what logs to view for errors or anything I should check on task sequences or anything? some other machines go right through the imaging, while other machines end with the errors and after a few more tries will complete successfully. any help would be greatly appreciated.
Error_0x00000035.jpg
Error_0x8007052E.jpg
Error_0x80070002.jpg
optiolex 755
optiplex 745
Also a Latitude E5440
The issues/errors below are what we get every 3 to 6 machines we try to image, but what concerns me is that we get the errors, but after few runs, they complete successfully. Suggestions what logs to view for errors or anything I should check on task sequences or anything? some other machines go right through the imaging, while other machines end with the errors and after a few more tries will complete successfully. any help would be greatly appreciated.
Error_0x00000035.jpg
Error_0x8007052E.jpg
Error_0x80070002.jpg
ASKER
Thnx Voglar, will try today and report on results.
ASKER
now we getting more errors :( will post later this weekend. thnx
ASKER
would SCEP affect my pxe boot environment if installed on my SCCM server?
Hi,
You have multiple apparently separate issues but I think they may be linked:
Task Sequence failed with error code 0x8007052E".
means join domain is failing. Either the OU is denied or the joindomain account
Error 00000035 - is network driver is missing (in WinPE)
Error 0x80070002 in SCCM 2012 - is also a network error during OSD, because files are not accessible by the computer
My conclusion from the screenshots is WinPE is missing network drivers and the network account does not have the right permissions.
The curious thing is how it works eventually if you keep trying. I have no answer to that, without more info.
I am currently deploying OptiPlex 7020s and 5530 laptops. They both worked fine with default WinPE drivers - i.e. no extras required. I did add 4 network drivers for other Dell hardware.
I would look at those possible issues first.
Troubleshooting steps
Enable F8 in your WinPE boot image and check you have an IP.
Look at smsts.log in x:\windows\temp\smstslog during the WinPE stage.
Later it moves to C:\_SMStasksequence\SMSTSL og
Read it with cmtrace which is already in WinPE. During the Windows phase you will need a USB stick with it on.
The other thing to try, is to simplify. Create a copy of your task-sequence and remove/disable all the apps and just leave drivers and test with that. It will be much quicker and prove the bare essentials work.
SCEP would have no effect on your deployment that I know of.
Note - I am currently on a project deploying the above Dell models daily and have built and rebuilt them many, many times without the issues you've seen so it's not the hardware!
Attach your smsts.log here if you're still stuck. Post one from a good machine and one from a failing machine would be best. There are lots of other logs but they are far less useful until later.
Mike
You have multiple apparently separate issues but I think they may be linked:
Task Sequence failed with error code 0x8007052E".
means join domain is failing. Either the OU is denied or the joindomain account
Error 00000035 - is network driver is missing (in WinPE)
Error 0x80070002 in SCCM 2012 - is also a network error during OSD, because files are not accessible by the computer
My conclusion from the screenshots is WinPE is missing network drivers and the network account does not have the right permissions.
The curious thing is how it works eventually if you keep trying. I have no answer to that, without more info.
I am currently deploying OptiPlex 7020s and 5530 laptops. They both worked fine with default WinPE drivers - i.e. no extras required. I did add 4 network drivers for other Dell hardware.
I would look at those possible issues first.
Troubleshooting steps
Enable F8 in your WinPE boot image and check you have an IP.
Look at smsts.log in x:\windows\temp\smstslog during the WinPE stage.
Later it moves to C:\_SMStasksequence\SMSTSL
Read it with cmtrace which is already in WinPE. During the Windows phase you will need a USB stick with it on.
The other thing to try, is to simplify. Create a copy of your task-sequence and remove/disable all the apps and just leave drivers and test with that. It will be much quicker and prove the bare essentials work.
SCEP would have no effect on your deployment that I know of.
Note - I am currently on a project deploying the above Dell models daily and have built and rebuilt them many, many times without the issues you've seen so it's not the hardware!
Attach your smsts.log here if you're still stuck. Post one from a good machine and one from a failing machine would be best. There are lots of other logs but they are far less useful until later.
Mike
Any update?
ASKER
I am currently waiting for a few more computers to be imaged, that way i can start the troubleshooting. Thanks a lot, ill try the suggestions Mike. will keep you posted. thnx
ASKER
Mike T, I sent a PM, suggestions. thanks,
ASKER
Ok, I am not sure how to post my log without providing too much information about my network, so here are few copies of the errors I am receiving.
...
Start to compile TS policy TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Policy complied successfully in WMI 'root\ccm\policy\defaultma chine\requ estedconfi g' namespace TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
End TS policy compilation TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Compiling AppManClientConfig policy... TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Retrieving value from TSEnv for '_SMSTSAppManClientConfigP olicy' TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
::DecompressBuffer(65536) TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Decompression (zlib) succeeded: original size 977, uncompressed size 6358. TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Instance path = 'CCM_ApplicationManagement ClientConf ig.SiteSet tingsKey=" 1"' TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Start to compile TS policy TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagement ClientConf ig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Policy complied successfully in WMI 'root\ccm\policy\defaultma chine\requ estedconfi g' namespace TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
End TS policy compilation TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Get Install Directory for SMS Client TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Updating settings in \\.\root\ccm\policy\machin e\actualco nfig TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
RequestedConfig policy instance(s) : 436 TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
Locked \\.\ROOT\ccm\Policy\Machin e\Requeste dConfig for source SMS:Client:Default:{8864FB 91-94EE-4F 16-A144-0D 82A232049D } successfully TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
Namespace: \\.\ROOT\ccm\Policy\Machin e\Requeste dConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:Client:Default:{8864F B91-94EE-4 F16-A144-0 D82A232049 D}") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
...
...
Start to compile TS policy TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Policy complied successfully in WMI 'root\ccm\policy\defaultma
End TS policy compilation TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Compiling AppManClientConfig policy... TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Retrieving value from TSEnv for '_SMSTSAppManClientConfigP
::DecompressBuffer(65536) TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Decompression (zlib) succeeded: original size 977, uncompressed size 6358. TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Instance path = 'CCM_ApplicationManagement
Start to compile TS policy TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagement
Policy complied successfully in WMI 'root\ccm\policy\defaultma
End TS policy compilation TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Get Install Directory for SMS Client TSManager 10/14/2015 2:53:09 PM 1664 (0x0680)
Updating settings in \\.\root\ccm\policy\machin
RequestedConfig policy instance(s) : 436 TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
Locked \\.\ROOT\ccm\Policy\Machin
Namespace: \\.\ROOT\ccm\Policy\Machin
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 10/14/2015 2:53:10 PM 1664 (0x0680)
...
ASKER
another portion with error:
...
CcmExec service is up and fully operational TSManager 1664 (0x0680)
Remediating TSManager 1664 (0x0680)
pNAP->GetSystemIsolationIn fo(&pNAPIn fo, &bUnknownConnections), HRESULT=8027000c (e:\nts_sccm_release\sms\c lient\task sequence\n apcontrol\ remediate. cpp,463) TSManager 1664 (0x0680)
GetSystemIsolationInfo(spN apClientIn fo, &IsoStat), HRESULT=8027000c (e:\nts_sccm_release\sms\c lient\task sequence\n apcontrol\ remediate. cpp,632) TSManager 1664 (0x0680)
Error getting system isolation info. Code 8027000C TSManager 1664 (0x0680)
ComputeComplianceAndRemedi ate(&QStat e), HRESULT=8027000c (e:\nts_sccm_release\sms\c lient\task sequence\n apcontrol\ tsnapcontr ol.cpp,48) TSManager 1664 (0x0680)
Remediation failed. Code 8027000C TSManager 1664 (0x0680)
hr = m_oNapCtrl.Remediate(QStat e), HRESULT=8027000c (e:\nts_sccm_release\sms\c lient\task sequence\t smanager\t smanager.c pp,1539) TSManager 1664 (0x0680)
Remediation failed with error code 8027000C TSManager 1664 (0x0680)
Initializing TS Engine TSManager 1664 (0x0680)
Getting TaskSequenceXML from environment TSManager 1664 (0x0680)
Parsing task sequence . . . TSManager 1664 (0x0680)
...
...
CcmExec service is up and fully operational TSManager 1664 (0x0680)
Remediating TSManager 1664 (0x0680)
pNAP->GetSystemIsolationIn
GetSystemIsolationInfo(spN
Error getting system isolation info. Code 8027000C TSManager 1664 (0x0680)
ComputeComplianceAndRemedi
Remediation failed. Code 8027000C TSManager 1664 (0x0680)
hr = m_oNapCtrl.Remediate(QStat
Remediation failed with error code 8027000C TSManager 1664 (0x0680)
Initializing TS Engine TSManager 1664 (0x0680)
Getting TaskSequenceXML from environment TSManager 1664 (0x0680)
Parsing task sequence . . . TSManager 1664 (0x0680)
...
Hi,
We really need the whole log file as an attachment. Please feel free to delete IP addresses and server names. Use find & replace in notepad will be fine.
Mike
We really need the whole log file as an attachment. Please feel free to delete IP addresses and server names. Use find & replace in notepad will be fine.
Mike
ASKER
Start executing the command line: smsswd.exe /run: powershell.exe -command n:\scripts\PCRename.ps1 TSManager 1664 (0x0680)
!------------------------- ---------- ---------- ---------- ---------- ---------- ---------- -------! TSManager 1664 (0x0680)
Expand a string: WinPEandFullOS TSManager 1664 (0x0680)
Executing command line: smsswd.exe /run: powershell.exe -command n:\scripts\PCRename.ps1 TSManager 1664 (0x0680)
[ smsswd.exe ] InstallSoftware 1736 (0x06C8)
PackageID = '' InstallSoftware 1736 (0x06C8)
BaseVar = '', ContinueOnError='' InstallSoftware 1736 (0x06C8)
ProgramName = 'powershell.exe -command n:\scripts\PCRename.ps1' InstallSoftware 1736 (0x06C8)
SwdAction = '0001' InstallSoftware 1736 (0x06C8)
::LogonUser(sUserAccountNa me, sUserDomainName, sUserPassword, LOGON32_LOGON_INTERACTIVE, LOGON32_PROVIDER_DEFAULT, &hUserToken), HRESULT=8007052e (e:\nts_sccm_release\sms\c lient\osde ployment\i nstallsoft ware\runco mmandline. cpp,324) InstallSoftware 1736 (0x06C8)
LogonUser failed with the error 0x8007052e InstallSoftware 1736 (0x06C8)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=8007052e (e:\nts_sccm_release\sms\c lient\osde ployment\i nstallsoft ware\main. cpp,372) InstallSoftware 1736 (0x06C8)
Install Software failed to run command line, hr=0x8007052e InstallSoftware 1736 (0x06C8)
Process completed with exit code 2147943726 TSManager 1664 (0x0680)
!------------------------- ---------- ---------- ---------- ---------- ---------- ---------- -------! TSManager 1664 (0x0680)
Failed to run the action: Renaming PC.
Logon failure: unknown user name or bad password. (Error: 8007052E; Source: Windows)
TSManager 1664 (0x0680)
MP server http://Server.domain.com. Ports 80,443. CRL=false. TSManager 1664 (0x0680)
Setting authenticator TSManager 1664 (0x0680)
Set authenticator in transport TSManager 1664 (0x0680)
Sending StatusMessage TSManager 1664 (0x0680)
Setting message signatures. TSManager 1664 (0x0680)
Setting the authenticator. TSManager 1664 (0x0680)
CLibSMSMessageWinHttpTrans port::Send : URL Server.domain.com:80 CCM_POST /ccm_system/request TSManager 1664 (0x0680)
Request was successful. TSManager 1664 (0x0680)
Set a global environment variable _SMSTSLastActionRetCode=-2 147023570 TSManager 1664 (0x0680)
Set a global environment variable _SMSTSLastActionSucceeded= false TSManager 1664 (0x0680)
Clear local default environment TSManager 1664 (0x0680)
Let the parent group (PC Rename) decides whether to continue execution TSManager 1664 (0x0680)
The execution of the group (PC Rename) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 1664 (0x0680)
Failed to run the last action: Renaming PC. Execution of task sequence failed.
Logon failure: unknown user name or bad password. (Error: 8007052E; Source: Windows) TSManager 1664 (0x0680)
MP server http:// Server.domain.com. Ports 80,443. CRL=false. TSManager 1664 (0x0680)
Setting authenticator TSManager 1664 (0x0680)
Set authenticator in transport TSManager 1664 (0x0680)
Sending StatusMessage TSManager 1664 (0x0680)
Setting message signatures. TSManager 1664 (0x0680)
Setting the authenticator. TSManager 1664 (0x0680)
CLibSMSMessageWinHttpTrans port::Send : URL: Server.domain.com:80 CCM_POST /ccm_system/request TSManager 1664 (0x0680)
Request was successful. TSManager 1664 (0x0680)
Launching command shell. OSDSetupHook 2160 (0x0870)
executing command: C:\WINDOWS\system32\cmd.ex e /k OSDSetupHook 2160 (0x0870)
executed command: C:\WINDOWS\system32\cmd.ex e /k OSDSetupHook 2160 (0x0870)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005
(e:\nts_sccm_release\sms\c lient\task sequence\t smanager\t smanager.c pp,923) TSManager 1664 (0x0680)
Task Sequence Engine failed! Code: enExecutionFail TSManager 1664 (0x0680)
************************** ********** ********** ********** ********** ********** TSManager 1664 (0x0680)
Task sequence execution failed with error code 80004005 TSManager 1664 (0x0680)
Cleaning Up. TSManager 1664 (0x0680)
Removing Authenticator TSManager 1664 (0x0680)
Cleaning up task sequence folder TSManager 1664 (0x0680)
Unable to delete file C:\_SMSTaskSequence\TSEnv. dat (0x80070005). Continuing. TSManager 1664 (0x0680)
hr, HRESULT=80070091 (e:\nts_sccm_release\sms\f ramework\c ore\ccmcor e\ccmfile. cpp,1218) TSManager 1664 (0x0680)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 1664 (0x0680)
(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION , pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\nts_sccm_release\sms\f ramework\t score\util s.cpp,6675 ) TSManager 1664 (0x0680)
SetNamedSecurityInfo() failed. TSManager 1664 (0x0680)
SetObjectOwner() failed. 0x80070005. TSManager 1664 (0x0680)
SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\nts_sccm_release\sms\f ramework\t score\util s.cpp,6772 ) TSManager 1664 (0x0680)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv. dat. 0x80070005. TSManager 1664 (0x0680)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 1664 (0x0680)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d -f741-45d5 -ab29-0ad8 aa4771ca ... TSManager 1664 (0x0680)
DeleteFileW(sVolumeIDFile. c_str()), HRESULT=80070002 (e:\nts_sccm_release\sms\f ramework\t score\reso lvesource. cpp,508) TSManager 1664 (0x0680)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 1664 (0x0680)
Command line for extension .exe is "%1" %* TSManager 1664 (0x0680)
Set command line: "C:\WINDOWS\CCM\TsProgress UI.exe" /Unregister TSManager 1664 (0x0680)
Executing command line: "C:\WINDOWS\CCM\TsProgress UI.exe" /Unregister TSManager 1664 (0x0680)
==========[ TsProgressUI started in process 692 ]========== TsProgressUI 2668 (0x0A6C)
!-------------------------
Expand a string: WinPEandFullOS TSManager 1664 (0x0680)
Executing command line: smsswd.exe /run: powershell.exe -command n:\scripts\PCRename.ps1 TSManager 1664 (0x0680)
[ smsswd.exe ] InstallSoftware 1736 (0x06C8)
PackageID = '' InstallSoftware 1736 (0x06C8)
BaseVar = '', ContinueOnError='' InstallSoftware 1736 (0x06C8)
ProgramName = 'powershell.exe -command n:\scripts\PCRename.ps1' InstallSoftware 1736 (0x06C8)
SwdAction = '0001' InstallSoftware 1736 (0x06C8)
::LogonUser(sUserAccountNa
LogonUser failed with the error 0x8007052e InstallSoftware 1736 (0x06C8)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=8007052e (e:\nts_sccm_release\sms\c
Install Software failed to run command line, hr=0x8007052e InstallSoftware 1736 (0x06C8)
Process completed with exit code 2147943726 TSManager 1664 (0x0680)
!-------------------------
Failed to run the action: Renaming PC.
Logon failure: unknown user name or bad password. (Error: 8007052E; Source: Windows)
TSManager 1664 (0x0680)
MP server http://Server.domain.com. Ports 80,443. CRL=false. TSManager 1664 (0x0680)
Setting authenticator TSManager 1664 (0x0680)
Set authenticator in transport TSManager 1664 (0x0680)
Sending StatusMessage TSManager 1664 (0x0680)
Setting message signatures. TSManager 1664 (0x0680)
Setting the authenticator. TSManager 1664 (0x0680)
CLibSMSMessageWinHttpTrans
Request was successful. TSManager 1664 (0x0680)
Set a global environment variable _SMSTSLastActionRetCode=-2
Set a global environment variable _SMSTSLastActionSucceeded=
Clear local default environment TSManager 1664 (0x0680)
Let the parent group (PC Rename) decides whether to continue execution TSManager 1664 (0x0680)
The execution of the group (PC Rename) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 1664 (0x0680)
Failed to run the last action: Renaming PC. Execution of task sequence failed.
Logon failure: unknown user name or bad password. (Error: 8007052E; Source: Windows) TSManager 1664 (0x0680)
MP server http:// Server.domain.com. Ports 80,443. CRL=false. TSManager 1664 (0x0680)
Setting authenticator TSManager 1664 (0x0680)
Set authenticator in transport TSManager 1664 (0x0680)
Sending StatusMessage TSManager 1664 (0x0680)
Setting message signatures. TSManager 1664 (0x0680)
Setting the authenticator. TSManager 1664 (0x0680)
CLibSMSMessageWinHttpTrans
Request was successful. TSManager 1664 (0x0680)
Launching command shell. OSDSetupHook 2160 (0x0870)
executing command: C:\WINDOWS\system32\cmd.ex
executed command: C:\WINDOWS\system32\cmd.ex
Execution::enExecutionFail
(e:\nts_sccm_release\sms\c
Task Sequence Engine failed! Code: enExecutionFail TSManager 1664 (0x0680)
**************************
Task sequence execution failed with error code 80004005 TSManager 1664 (0x0680)
Cleaning Up. TSManager 1664 (0x0680)
Removing Authenticator TSManager 1664 (0x0680)
Cleaning up task sequence folder TSManager 1664 (0x0680)
Unable to delete file C:\_SMSTaskSequence\TSEnv.
hr, HRESULT=80070091 (e:\nts_sccm_release\sms\f
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 1664 (0x0680)
(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION
SetNamedSecurityInfo() failed. TSManager 1664 (0x0680)
SetObjectOwner() failed. 0x80070005. TSManager 1664 (0x0680)
SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\nts_sccm_release\sms\f
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 1664 (0x0680)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d
DeleteFileW(sVolumeIDFile.
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 1664 (0x0680)
Command line for extension .exe is "%1" %* TSManager 1664 (0x0680)
Set command line: "C:\WINDOWS\CCM\TsProgress
Executing command line: "C:\WINDOWS\CCM\TsProgress
==========[ TsProgressUI started in process 692 ]========== TsProgressUI 2668 (0x0A6C)
Hi,
Your task sequence is failing because your PC rename script needs user credentials and fails. It needs the username and password and is either not being passed them, the account is locked out or they are wrong (typos)
"LogonUser failed with the error 0x8007052e"
That is not really the best way to name machines. It is much more versatile and supported to use the customsettings.ini file. You can get complex with this if you want but it's up to you as the naming convention you have.
I tend to use the BIOS service tag as it is unique enough.
Check out this article:
http://deploymentbunny.com/2012/04/21/back-to-basic-customsettings-ini-explained/
Mike
Your task sequence is failing because your PC rename script needs user credentials and fails. It needs the username and password and is either not being passed them, the account is locked out or they are wrong (typos)
"LogonUser failed with the error 0x8007052e"
That is not really the best way to name machines. It is much more versatile and supported to use the customsettings.ini file. You can get complex with this if you want but it's up to you as the naming convention you have.
I tend to use the BIOS service tag as it is unique enough.
Check out this article:
http://deploymentbunny.com/2012/04/21/back-to-basic-customsettings-ini-explained/
Mike
ASKER
log attached. thnx
SMSTS.log.pdf
SMSTS.log.pdf
Hi,
I can see a few things
"Connect to Network Scripts Folder. Instruction pointe Set" This is normally more trouble than it is worth because the TS runs as system context and you have to explicitly run as another account.
It is easier to create a package (not application) and put all your scripts in that instead. Arguably better still is to create a custom directory inside the MDT toolkit scripts directory and use that.
To use the latter you can use %deployroot%\scripts\yours cript.ps1
this is where your TS fails.
Executing command line: smsswd.exe /run: powershell.exe -command n:\scripts\PCRename.ps1
ProgramName = 'powershell.exe command n:\scripts\PCRename.ps1'
LogonUser(sUserAccountName , sUserDomainName, sUserPassword, LOGON32_LOGON_INTERACTIVE LogonUser failed with the error 0x8007052e
Is access denied, I guess to the N: drive, because you're trying to access the path and it can't.
If you follow the answer to (1) this will avoid the whole issue.
Mike
I can see a few things
1. Network folder
"Connect to Network Scripts Folder. Instruction pointe Set" This is normally more trouble than it is worth because the TS runs as system context and you have to explicitly run as another account.
It is easier to create a package (not application) and put all your scripts in that instead. Arguably better still is to create a custom directory inside the MDT toolkit scripts directory and use that.
To use the latter you can use %deployroot%\scripts\yours
2. PC rename script
this is where your TS fails.
Executing command line: smsswd.exe /run: powershell.exe -command n:\scripts\PCRename.ps1
ProgramName = 'powershell.exe command n:\scripts\PCRename.ps1'
LogonUser(sUserAccountName
Is access denied, I guess to the N: drive, because you're trying to access the path and it can't.
If you follow the answer to (1) this will avoid the whole issue.
Mike
ASKER
thanks Mike i am currently working on this today. will provide an update asap. thnx
ASKER
Hello,
we actually had consultants create our first TS and images. I am going to create my own TS now and deploy our basic reference capture. Any good reference material or suggestions on how to get TS to install the Config Manager client on the newly imaged pc, or is it best to just have the scheduled push to do that job? thanks,
we actually had consultants create our first TS and images. I am going to create my own TS now and deploy our basic reference capture. Any good reference material or suggestions on how to get TS to install the Config Manager client on the newly imaged pc, or is it best to just have the scheduled push to do that job? thanks,
ASKER
by the way, it seems consults did not use MDT.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Decided to integrate mdt and create my own task sequence and edit. Thanks a lot, sounds like less headache after mdt is integrated successfully. thanks,
you will get a command prompt.
The log you are looking for is smsts.log
copy the log to nework share ond open it with SMS Tracer Utility
http://prajwaldesai.com/location-of-smsts-log-during-sccm-osd/