Jump to content


All Activity

This stream auto-updates     

  1. Today
  2. @Richard F you can only download files when logged in as a member of windows-noob.com (which you now are), so please try again.
  3. Yesterday
  4. it's probably sitting like that because it's a shared network dongle, you can try the advice here https://systemcenterdudes.com/sccm-duplicate-hardware-identifiers/
  5. Has anyone managed to get a Microsoft Surface Go2 (LTE Model) to PXE boot successfully?, I have just got a model in to test and I'm unable to get it to PXE boot correctly, it just sits at waiting for approval. I've tried booting using a surface dock 2, i have also tried with the official USB C adaptor and it wont boot. I've updated the firmware to the latest version, I have also added the MAC in the hierarchy settings in SCCM to allow duplicate hardware identifiers. I'm currently running on v 2010 and ADK 2004.
  6. @wudevr please update us with how you get on and any challenges faced, I've updated my reply above with some more info...
  7. Last week
  8. ok and you are sure that the computer(s) are in the collection where this policy is targeted ? did you upgrade configmgr recently ?
  9. as per my guide above " double-check that you've configured and enabled the BitLocker Management Settings in the Client Management setting of the configured BitLocker Management policy "
  10. Hi, I see the bitlocker management policy in Config Manager. When I click Evaulate it goes through. However, the MBAM client is not installing by itself. It used to be seamless once the policy is pushed. I don't see the FVE\MDOPBitlockerManagement in registry, don't see MDOP/MBAM in programs and features, there is also no BitlockerManagement_GroupPolicyHandler.log. So it seems like the policy was pushed down but then there is a disconnect somewhere.
  11. I did read that but I dont understand why its failing on thie task as this worked fine on other machine and i use same script on a machine and it works fine
  12. according to your log, this is why it failed, I'm curious though, did you read the log ? The execution of the group (PreChecks) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 20/01/2021 15:39:16 9960 (0x26E8) Failed to run the last action: Foundation Application Check. Execution of task sequence failed. The line in question that you need to investigate is: Failed to run the last action: Foundation Application Check. Execution of task sequence failed.
  13. Hi, When I apply TS on some machine it crash the software centre and I can see following error in the logs 0x80004005 My TS has a powershell script which set a registry key and then copy some files based on that key Error executing Task Sequence Manager service. Code 0x80004005 I try following things on an machine 1. Check BIOS Time 2. Apply All updates 3. Remove and reinstall SCCM client SMSTS log Expand a string: WinPEandFullOS TSManager 20/01/2021 15:39:16 9960 (0x26E8) Executing command line: OSDRunPowerShellScript.exe TSManager 20/01/2021 15:39:16 9960 (0x26E8) [ OSDRunPSScript.exe ] RunPowerShellScript 20/01/2021 15:39:16 4932 (0x1344) !sScriptName.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\runpsscript\main.cpp,317) RunPowerShellScript 20/01/2021 15:39:16 4932 (0x1344) Powershell script name must be specified RunPowerShellScript 20/01/2021 15:39:16 4932 (0x1344) Process completed with exit code 2147500037 TSManager 20/01/2021 15:39:16 9960 (0x26E8) !--------------------------------------------------------------------------------------------! TSManager 20/01/2021 15:39:16 9960 (0x26E8) Failed to run the action: Foundation Application Check. Unspecified error (Error: 80004005; Source: Windows) TSManager 20/01/2021 15:39:16 9960 (0x26E8) Set authenticator in transport TSManager 20/01/2021 15:39:16 9960 (0x26E8) Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 20/01/2021 15:39:16 9960 (0x26E8) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 20/01/2021 15:39:16 9960 (0x26E8) Clear local default environment TSManager 20/01/2021 15:39:16 9960 (0x26E8) Let the parent group (PreChecks) decides whether to continue execution TSManager 20/01/2021 15:39:16 9960 (0x26E8) The execution of the group (PreChecks) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 20/01/2021 15:39:16 9960 (0x26E8) Failed to run the last action: Foundation Application Check. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows) TSManager 20/01/2021 15:39:16 9960 (0x26E8) Set authenticator in transport TSManager 20/01/2021 15:39:16 9960 (0x26E8) Task Sequence Engine failed! Code: enExecutionFail TSManager 20/01/2021 15:39:16 9960 (0x26E8) TSManager 20/01/2021 15:39:16 9960 (0x26E8) Task sequence execution failed with error code 80004005 TSManager 20/01/2021 15:39:16 9960 (0x26E8) Cleaning Up. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Removing Authenticator TSManager 20/01/2021 15:39:16 9960 (0x26E8) Cleaning up task sequence folder TSManager 20/01/2021 15:39:16 9960 (0x26E8) Unable to delete file C:_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Failed to delete directory 'C:_SMSTaskSequence' TSManager 20/01/2021 15:39:16 9960 (0x26E8) SetNamedSecurityInfo() failed. TSManager 20/01/2021 15:39:16 9960 (0x26E8) SetObjectOwner() failed. 0x80070005. TSManager 20/01/2021 15:39:16 9960 (0x26E8) RemoveFile() failed for C:_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 20/01/2021 15:39:16 9960 (0x26E8) RemoveDirectoryW failed (0x80070091) for C:_SMSTaskSequence TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting volume ID file C:_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 20/01/2021 15:39:16 9960 (0x26E8) Successfully unregistered Task Sequencing Environment COM Interface. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 20/01/2021 15:39:16 9960 (0x26E8) ==========[ TsProgressUI started in process 14144 ]========== TsProgressUI 20/01/2021 15:39:16 5784 (0x1698) Command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TsProgressUI 20/01/2021 15:39:16 5784 (0x1698) Unregistering COM classes TsProgressUI 20/01/2021 15:39:16 5784 (0x1698) Unregistering class objects TsProgressUI 20/01/2021 15:39:16 5784 (0x1698) Shutdown complete. TsProgressUI 20/01/2021 15:39:16 5784 (0x1698) Process completed with exit code 0 TSManager 20/01/2021 15:39:16 9960 (0x26E8) Successfully unregistered TS Progress UI. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Trying to restore client to the state it can be managed TSManager 20/01/2021 15:39:16 9960 (0x26E8) CCMExec service startup type is set to enabled TSManager 20/01/2021 15:39:16 9960 (0x26E8) Modifying CCMExec Service to auto start. TSManager 20/01/2021 15:39:16 9960 (0x26E8) CCMExec Service started TSManager 20/01/2021 15:39:16 9960 (0x26E8) Waiting for CcmExec service to be fully operational TSManager 20/01/2021 15:39:16 9960 (0x26E8) CcmExec service is up and fully operational TSManager 20/01/2021 15:39:16 9960 (0x26E8) Current Assigned Management Point is DP.com with Version 9012 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 20/01/2021 15:39:16 9960 (0x26E8) Successfully connected to MP DP.com:2244 TSManager 20/01/2021 15:39:16 9960 (0x26E8) Cleaning up any active TS requests in WMI. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting CCM_TSExecutionRequest instance: CCM_TSExecutionRequest.RequestID="4bae2f33-7ef9-4fe1-85d7-be634d77b491". TSManager 20/01/2021 15:39:16 9960 (0x26E8) Removed 1 instance of CCM_TSExecutionRequest for tasksequence. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Cleaning up any maintenance task requests in WMI. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{9777FA30-3D39-4A04-82C7-FA688160C574}". TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{8B259B30-7D06-40D2-95FD-201AB40544F0}". TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{4BAE2F33-7EF9-4FE1-85D7-BE634D77B491}". TSManager 20/01/2021 15:39:16 9960 (0x26E8) Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{00186E9D-286A-4461-BDE7-54BA8CAD8B7B}". TSManager 20/01/2021 15:39:16 9960 (0x26E8) Removed 4 instances of SMS_MaintenanceTaskRequests for tasksequence. TSManager 20/01/2021 15:39:16 9960 (0x26E8) Start to cleanup TS policy TSManager 20/01/2021 15:39:19 9960 (0x26E8) End Task Sequence policy cleanup TSManager 20/01/2021 15:39:19 9960 (0x26E8) RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 20/01/2021 15:39:19 9960 (0x26E8) GetTsRegValue() is unsuccessful. 0x80070002. TSManager 20/01/2021 15:39:19 9960 (0x26E8) End program: TSManager 20/01/2021 15:39:19 9960 (0x26E8) Error executing Task Sequence Manager service. Code 0x80004005 TSManager 20/01/2021 15:39:19 9960 (0x26E8) Sending error status message TSManager 20/01/2021 15:39:19 9960 (0x26E8) Set authenticator in transport TSManager 20/01/2021 15:39:19 9960 (0x26E8) Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs TSManager 20/01/2021 15:39:19 9960 (0x26E8)
  14. it's been a long time since i blogged about it (see here) but i think you'll have to go n+3, so probably offline upgrade from 1606 to 1706 or so and so on, 1606 has been unsupported for years now what took you so long you will definitely have your work cut out for you here...as you'll also need to upgrade SQL server more than likely, and maybe even the os of the server below is what an old lab of mine looks like (version 1610) after I triggered a sync, so in this case you can see that it can upgrade to 1710 (n+3) so that was... 1610 (n) 1702 1706 1710 based on this I'll guess that you can do the following... 1606 (n) 1610 1702 1706 (n+3) 1710 which would mean that you could theoretically upgrade from 1606 to CM2006 like so 1606>1706>1806>1906>2006
  15. I have some disconnected (no internet) CM 1606 sites. Can I upgrade these to 2002 using the Baseline Media? If not, what is the best way to upgrade them?
  16. @Ketan Kamble Don't target tphkload.exe because that may be inconsistent in future releases. See if this blog post helps.
  17. What is the best detection method we can keep for Lenovo Hotkey Features Integration 9.2.0.1 x64 application . I tried below detection , but somehow it is not working.
  18. I'm glad you sorted it out, thanks for posting your findings
  19. Ok, without doing anything the connection came on and was green. I then executed following sql: USE CM_PS1 EXEC spDiagChangeTracking @CleanupChangeTracking = 1 And redo the prerequisite check and all was good. The upgrade to 2010 went super 🙂 Case closed
  20. Ok I found the issue. It was a combination 🙂 I changed some rights in SQL for the installation user and system account to be able to write to the DB. And finally removed an extra nic adapter used for internet access. It's going further now but I have another error: This can be solved by opening an admin session on SQL but I have an errormessage:
  21. I just created a lab with 1 AD server and 1 CM server hosting the SQL server service and wsus. After the install I want to upgrade to 2010 directly but I have some network/auth complications with the prerequisite check For some reason there's a 'GetFileSize' error on a file which seems to be related to the pt-BR language as everything is en-US based on the servers: I attached the logfiles. I enabled 'named pipes' I disabled all firewall But the prequisite check is still running How can I stop/restart this? CMUpdate.log distmgr.log
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...