Jump to content


Search the Community

Showing results for tags 'osd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. Running the OSD task sequence from the Software Center shows that it is being installed... Does anyone know what's going on? TSAgent.log Show these errors reply has no message header marker Failed to request policy assignments (Code 0x80004005) Error initializing policy environment variables. Code 0x80004005 Error LoadPolicyBasedEnvVars, return code 80004005 Error initializing Task Sequence environment. Code 0x80004005 Task sequence launcher deployment failed!. Code 0x80004005 Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 CTSAgent::Execute - Failed to launch Task Sequence manager. execmgr.log smsts.log TSAgent.log
  2. I created an offline media of the Windows 20H2, where I have two Windows version options, I'll call version A and version B Version A: is a standard task sequence, which disables the bitlocker, partitions the disk, installs install.wim, installs the configuration manager, restarts, then adds 3 programs, which are: 7Zip, Adobe and Notepad++, and finishes Version B: identical to version A, but without 7zip. The most bizarre thing is that in version B, everything works without a problem. But in version A, at the end of the Task Sequence (NOTE: I use TSBackground, but that's not the problem, otherwise it would affect both versions) the success screen appears, and I click the Finish button, and then I go to a screen blue (not the BSOD) saying: "Sign-in process initialization failure, Interactive logon process initialization has failed. Please consult the event log for more details." How is this possible if the difference between them is just 7zip? This screen does not corrupt the system, it only appears once, restarts, and I can log in again without any problems, and 7Zip is still there without any problem, and consulting the smsts.log, 7Zip is terminated with Exit Code 0. This error does not interfere with nothing, but it bothers me a lot, even more that I will distribute this system to more than 2,000 machines, everyone will have doubts about this screen, and this is not pleasant to leave showing. I googled it, but it seems that it happens when it really corrupts the system, in my case it doesn't, it shows up once, but I wanted to understand why the hell it shows up because of a 7Zip (already tested it with msi version, exe, old version, version new, and etc and with no result, I tried to put another program in place, like CCleaner for example and it causes the same result) I created an offline media, where I have two Windows version options, I'll call version A and version B Version A: is a standard task sequence, which disables the bitlocker, partitions the disk, installs install.wim, installs the configuration manager, restarts, then adds 3 programs, which are: 7Zip, Adobe and Notepad++, and finishes Version B: identical to version A, but without 7zip. The most bizarre thing is that in version B, everything works without a problem. But in version A, at the end of the Task Sequence (NOTE: I use TSBackground, but that's not the problem, otherwise it would affect both versions) the success screen appears, and I click the Finish button, and then I go to a screen blue (not the BSOD) saying: "Sign-in process initialization failure, Interactive logon process initialization has failed. Please consult the event log for more details." How is this possible if the difference between them is just 7zip? This screen does not corrupt the system, it only appears once, restarts, and I can log in again without any problems, and 7Zip is still there without any problem, and consulting the smsts.log, 7Zip is terminated with Exit Code 0. This error does not interfere with nothing, but it bothers me a lot, even more that I will distribute this system to more than 2,000 machines, everyone will have doubts about this screen, and this is not pleasant to leave showing. I googled it, but it seems that it happens when it really corrupts the system, in my case it doesn't, it shows up once, but I wanted to understand why the hell it shows up because of a 7Zip (already tested it with msi version, exe, old version, version new, and etc and with no result, I tried to put another program in place, like CCleaner for example and it causes the same result) (Note, the 2004 version I've never seen this happen and it's the same Task Sequence, I just changed install.wim to the new 20H2 version)
  3. We have some MECM managed Windows 7 PC's that are on slow satellite links. Is it possible to ship the files to those locations, have them copied to the hard drives of those PC's and run OSD to use the locally copied files and install Windows 10?
  4. Selcted OU will copy the files I want my selected OU will copy files to WMS folder in the desktop. And here is the selected OU choose the filepath. How will I do that ?
  5. I am deploying Windows 10 to HP Z840 and Z8 PC's using OSD in Config Manager 2010. Some of the Z8's are brand new, but most of the systems are running Windows 7 and are managed by SCCM. Some of them have single SATA or SSD drives. Some have multiple SATA or a mix of SATA and SSD drives. In systems that have an SSD and a SATA drive, I want to ensure the OS gets deployed to the SSD. In systems with multiple SATA drives, I want to ensure the OS gets deployed to the smaller drive and the larger one will be used for data storage. How best to accomplish this?
  6. We are deploying a Windows 1909 IUP which consists of a Pre-Cache TS which tattoos the registry and then moves the client to a new collection which has an app advertised to run the actual IUP (which references another TS). I have followed Martin Bengtssons excellent guides to do this https://www.imab.dk/windows-as-a-service-sharing-my-precache-and-in-place-upgrade-task-sequences-part-1/ https://www.imab.dk/windows-as-a-service-sharing-my-precache-and-in-place-upgrade-task-sequences-part-2/ The problem we are experiencing is that on about 10% of the clients the Pre-Cache TS is stuck in "installing" state despite the fact that it has managed to carried out all the steps int the TS (downloaded OS + packages etc) and tattooed the registry. I have already read the articles below but unfortunatley none of the suggestions have helped: http://www.potentengineer.com/task-sequence-stuck-installing-in-software-center/ https://social.technet.microsoft.com/Forums/en-US/e382da34-079c-4619-8fdb-e5e44c436857/software-center-show-application-stuck-at-installing Has anyone else experienced this problem and have any suggestions? I have tried reparing the client which has not helped (I don´t think I've ever managed to repair a corrupt client tbh). From what I´ve read it seems to be a WMI issue and we need a silver bullet to fix these clients once we understand what the issue is. Any tips would be greatly appreciated Emile Risberg
  7. Hello, I recently deployed an OS task sequence to a device collection and all of the computers came up with "Inaccessible Boot Device" afterward. This is the first time I have tried pushing an OSD as a required deployment to computers that are already powered up and running Windows. The OSD works fine with booting to media, and this same OSD worked fine on these computers after I circled back around to reload them via bootable media. The computers showed up in AD with the automatically generated name, so I believe the OSD was successful, maybe just missing some drivers? Has anyone run into this before, or can you suggest a course of action? Thanks for any help you can offer! Scott
  8. Hi I have an issue whereby my Windows 10 IPU task sequence is downloading all driver packages specified in the TS (Download Package Content) allthough the correct driver packages already exist in the CCM cache on the PC running the TS. I have used the following guide to create a PreCache task sequence: https://www.imab.dk/windows-as-a-service-sharing-my-precache-and-in-place-upgrade-task-sequences-part-1/ (credit to Martin Bengtsson for the excellent guide) and it works very well. A PC which has successfully run the PreCache TS downloads the correct drivers (using a WMI query) and other packages specified that are needed and then places the computer in a collection to where the actual IPU task sequence is deployed. The problem is that the IPU task sequence which is deployed with the setting "Download all content locally before starting the task sequence" (the setting found under the "Distribution Point" tab) starts to download driver packages for other hardware models that are specified in the TS (despite using WMI queries in this TS also). Because of the current Covid-19 pandemic the majority of our users are working from home so we obviously want to keep the amount of data transfered to a minimum, it seems stupid to cache driver content that´s not needed to work around the problem. I thought that the IPU TS would evaluate the queries before downloading (i read somewhere that this was only possible for upgrade packages/language packs but in later versions of current branch also included other packages). We are running CB 1910. Hope this makes sense, if anyone has experienced this and can suggest a workaround or confirm how it´s supposed to work it would be greatly appreciated. Regards Emile
  9. I am running into an extremely odd issue. I have several task sequences that are failing to apply image during OSD. When I check the smstslog I see the following error "Failed to run the action: Apply Operating System. Error 255" I can find no mention of error 255 anywhere on the internet. When I check the status messages for the deployment ID I see the following: "The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 255 Action output: ... Downloading file /SMS_DP_SMSPKG$/P0100051/sccm?/Windows%2010%202019%20LTSC_REF2020.wim range 6442450941-7214257158 Downloaded file from http://SVD-SCCM.WCPS.K12.VA.US:80/SMS_DP_SMSPKG$/P0100051/sccm?/Windows%2010%202019%20LTSC_REF2020.wim to C:\_SMSTaskSequence\Packages\P0100051\Windows 10 2019 LTSC_REF2020.wim VerifyContentHash: Hash algorithm is 32780 Content successfully downloaded at C:\_SMSTaskSequence\Packages\P0100051. Opening image file C:\_SMSTaskSequence\Packages\P0100051\Windows 10 2019 LTSC_REF2020.wim Image file P0100051 version "" will be applied Starting to apply image 1 from Windows 10 2019 LTSC_REF2020.wim to C:Wiping C:Set "C:\_SMSTaskSequence" to not be wiped Set "%OSDStateStorePath%" to not be wiped Set "%_SMSTSClientCache%" to not be wiped Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped Skipping C:\_SMSTaskSequence for wipe Calculating expected free space. Reporting deletion progress. Successfully wiped C:Applying image to C:Applying image 1. The operating system reported error 255: The extended attributes are inconsistent. I have tried redistributing the image and I still get the same issue. I was able to successfully deploy the image to a VM bu when I try on a physical PC I get the failure. I have tested on two different pieces of hardware. Thanks for the help! smsts.log
  10. Hey all, Since upgrading to CM 2002, I have done the following: Upgrade ADK to 2004, rebuild boot images. Now, when I PXE boot, it loads the WIM, loads up the WinPE environment background - then poof, it restarts (I never get prompted with the password entry to start my OSD). I cannot press F8 to have the command prompt appear (I still have that enabled), therefore I cannot get to any log files to diagnose. I am attempting to deploy Windows 10 1903. Any suggestions?
  11. We have some Dell Optiplex 7070 computers, and I'm trying to deploy a Windows 10 1909 image to them without changing the default bios configuration, which comes set to "Raid On" in Sata Operation. The default dell image works fine, so I'm not sure why ours does not. I'm imported all of the drivers that I could find for this model and intel storage in general. The task applies the OS and works in winPE fine, but after rebooting just gets a blue screen. How do I get this working? Thanks
  12. Anyone tried to determine hardware UEFI capability with SCCM? I am trying to find out if a machine is UEFI capable, cant fine any way to do it at this point.
  13. Hello all. I've run into a bit of an odd issue with a defaultuser0 account being created, as well as an "account unknown" showing up in User Profiles. I am able to log in with a domain account, as well as a local account, but one side effect of these two "accounts" is that the "Desktop" shortcut under "Quick Access" is stuck to "C:\Users\Default\Desktop" regardless whether a domain or local account logs on the computer. Is there some step I can do to prevent this "defaultuser0" and account unknown from being created, or any way to purge these two accounts during OSD? I manually can remove Account Unknown, delete C:\Users\Default, re-pin the "Desktop" to quick access, and it functions fine. Additional info: Used build and capture process on a base install.wim, did no configuration changes, so essentially a vanilla image, but not just using install.wim.
  14. I am attempting to create and deploy a single universal OSD task sequence in SCCM (current branch) in my organization and will install and apply the appropriate language(and other regional settings) for the region. I have created the task sequence with steps outlined in the thread below. However, Windows 10 version 1903 no longer use standard lp.cab files but rather use the Features on Demand and appx packages to apply languages. There doesnt appear to be any current documentation on how to accomplish this during OSD using sccm with the change in how Windows applies languages. Any assistance would be greatly appreciated. Ive attempted to tackle this problem from a few different angles with no luck. I have also tried the steps outlined below to apply the language/regional settings with similar results. https://thesleepyadmins.com/2019/01/26/sccm-task-sequence-windows-10-language-pack/ In addition to this, I created a bat file package which executes the dism commands to load the .cabs and .appx as well as set the other regional settings to no avail. Running the DISM commands to manually load the 5 different language cab files and the appx (language experience pack) does not actually change the language, or even make it available in the language selection dropdown in Win10 Settings. The only way to get the new language to appear in the dropdown is to go to the MS store and load it on each individual PC even after manually installing the appx. I really want to automate this, and have whatever regional language set as default, and English as the secondary(if applicable). Thanks, Dave
  15. So l’m kind new to SCCM’s OSD and I’ve been assigned to do an upgrade for Windows 7 workstation to Windows 10 v1703. I read online that the maximum ADK supported by SCCM 1606 is v1607, lucky I also read some posts online saying that it worked fine with Windows 10 v1706 although Microsoft does not support it. Now, my questions is our environment has an older ADK version that I don’t wish to remove if that possible. Can I just install the new ADK + upload new images to console + use new USMT Package for user data migration? Or must I upgrade the whole winPE to the new ADK environment? And if so, is there is any easier way then using scripts to update image and adk level ? ( older SCCM versions don’t have the option of reloading boot images) *current environment has two ADKs !! win 8.1 /older version of win 10 adk . If anyone can guide me please, I’m supposed to start the upgrade as soon as possible as windows 7 is going to be out of support in 2020.
  16. Hi all, I'm new to SCCM (this is day 4), and I'm trying to get some laptops that are only connected with Wifi to run an OSD, including a domain join, all the way through. By having it cache the files locally, I've gotten pretty far. I used USMT to preserve a netsh wifi export xml file. Now, where I'm stuck is getting that xml imported as the first thing that happens after the first reboot, and I'm not sure how, because none of the steps in the TS are very descriptive in what all they are doing or when the reboot is happening. Now, I know I can make an image with the xml in there, and I can also do a join domain from setupcomplete with a powershell script. BUT... I'd like to do this in a way that is not image dependent, if possible, and using the SCCM domain join network setup function to keep my boss happy. So my question is, where do I put the netsh wlan add command in the series of steps, and also what is the best syntax for that command (I've seen 'command not found' in the ccm logs, but that may be due to being in winPE, not sure). Thanks
  17. Hello. We currently have an OSD Task Sequence for deploying Windows 10 Enterprise 1709 to our client machines. This works quite well for existing PCs which are known to AD and SCCM. We have a mixed environment, where we have multiple departments which require their own set of applications. Again, this works well for existing machines. The issue in which I'm being faced with at the moment, is when we introduce new clients to the environment. Due to the design of SCCM with AD System Discovery, new devices are not discovered as there is no DNS entry for those devices. I have done the following - Pre-staged computer accounts on Active Directory. Created computer objects within SCCM with the Name and MAC address of the new devices. Added new objects to the OSD Device Collection for OSD. The problem here is that some Device Collections which have Collection Variables attached, rely on Active Directory OU membership rules. As these machines haven't yet been discovered as such, they don't become members of these collections until the OSD process has finished the installation of the ConfigMgr Client has completed. Once that has completed, the machines then fall into the correct collections, but the Install Applications step within the Task Sequence doesn't complete as the collection variables haven't yet been evaluated. I was wondering if anybody else here has experienced this and maybe have a solution/work around? Would there be any Powershell scripts which could be used to force a re-evaluation on collection variables prior to the Install Applications step? Cheers, Richard
  18. Guys Been building Windows 10 1709 for about a year all fine... We are starting to build 1809 and all works except the TS/Naming now seems to ignore the Collection Variable 'OSDComputerName' I have both 1709 and 1809 images, both building from the same 'All Unknown Computers' collection, the 1709 works the 1809 does not. the 1809 uses a copy of the TS from 1709 with just the WIM changed. Any ideas? thanks
  19. Hi all, I was trying to deploy a Task sequence, which I Copied from standard T.S. and made little change and trying to test it before using. This T.S. is to make BIOS system to UEFI system in boot (Dell system) and then install OS. But when I try to implement this its throwing an error code "0x80004005". I am pasting my SMSTS log file. Please help me. Log: please see the attachment.
  20. Hi I have a couple of questions regarding using language packs in a reference image in MDT. We want to deploy Swedish OS to all our users and I was advised to do this using English OS media with corresponding language pack (Windows 10 1803) instead of using localized media. It appears to have installed the language pack correctly in the reference image but the display language of the OS before the capture is in English (I have a suspend action in the task sequence). My question is what is the best way to set the display language automatically to Swedish once the LP is installed by the task sequence? Some other concerns regarding patching and updating the client once it has been deployed: We will be deploying the REF-image using OSD in SCCM 1802 and use SUP/ADR rules to patch the clients, I assume the patches we download for Windows 10 will need to be in English since the base OS is English? Are there any other considerations we need to make? What are the implications of using SCCM/Servicing for Windows 10 when updating a client with a LP, say 1709 to 1803? I know that the version of the language pack must match the release version of Windows but is there anything else? I would really appreciate if someone has some experience of this and could give me some feedback. Regards Emile
  21. Hi all, I have an unusual problem in that my employer is purchasing old Supermicro blade servers. They don't support SAS and as such I'm using large SATA drives and I'm pretty sure these are BIOS only as I didn't see anything in BIOS setup that looked like I could enable a UEFI boot mode (they are over 7 years old and cheap.) Currently, I've run down to 3TB and above and my 2016 installations are failing as SCCM is forcing initialization to GPT to use the 3TB capacity. I need these to be MBR and 2TB for Windows to successfully be deployed. The trouble is, I can't locate where the diskpart.exe and diskpartscript.txt are being run during the installation. I'm guessing it's buried in a VBS script in the OSDDiskpart step but I haven't acquired the skills yet to get down to the granular level of tweaking. So far I've tried enabling: Set Diskpart BIOS compatibility in both locations where it's greyed out. Disabling all three Format and Partition Disk (UEFI) and tried flipping the Disk Type drop-down option in each UEFI format step to MBR from GPT, but for some reason that didn't work. but the disk still gets initialized to GPT. If I knew where the initialization step was taking place I could just add a WMI query that ignores Supermicro X8DTT-H or something similar. Another possible solution would be to insert my own Diskpart script that converts it back to MBR right before it's failing. Here's part of my log: And here are the details of what's happening in Stdout: Diskpart.exe STDOUT: Microsoft DiskPart version 10.0.14393.0 Copyright (C) 1999-2013 Microsoft Corporation. On computer: MININT-7SO7UHO Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C NTFS Partition 2047 GB Healthy Disk 0 is now the selected disk. DiskPart succeeded in cleaning the disk. Disk is uninitialized, initializing it to GPT. DiskPart succeeded in creating the specified partition. DiskPart successfully assigned the drive letter or mount point. The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks. Thanks for any help! I'm just finding that the MDT task schedule is a bit blackboxed and I can't seem to find where this lives.
  22. OSD Run Command Line: One Liners Please find attached a set of usefull SCCM OSD Task Sequence "Run Command Line" One-Liners Show Task Sequence Name in SCCM Status Messages: cmd.exe /C "echo %_SMSTSPackageName%" Format Disk 0 for Staging (Remove Bitlocker before downloading first Package) cmd.exe /c "(echo select disk 0&& echo.clean&& echo.list disk&& echo.list volume) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" Adjust OSDDiskIndex (Max two disks) (Useful if a device has two disk and either one can/should be the C drive. Work in combination with the step "Format and Partition Disk" and overwrites the "Disk Number" value) cmd.exe /V /C "(set /a osdID=1-%OSDDiskIndex% > null&& tsenv.exe "OSDDiskIndex=!osdID!")" Set Drive Offline/Online by variable (see: Bitlocker Pre-Provision multi Disk) cmd.exe /c "(echo select disk %OSDDiskIndex%&& echo.offline disk&& echo.list disk) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" cmd.exe /c "(echo select disk %OSDDiskIndex%&& echo.online disk&& echo.list disk) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" Fix Drive Letter of mounted devices (Best used in combination with conditions) cmd.exe /V /C "FOR /F %V IN ('mountvol.exe D: /L') DO (mountvol.exe D: /D & mountvol.exe F: %V)" (Checks if devices has one disk and device with drive letter D is an USB Drive --> Map USB from D to F Drive Letter) (Checks if devices has one disk and device with drive letter D is an CDRomDrive --> Map CDRom from D to E Drive Letter) Forcefully halt the task sequence (The file does not exist and therefor generates an error, best/only to use with conditions) Enables Task Sequence Powershell special return codes StopTaskSequenceWithError.exe The step before is a "Run PowerShell Script" step and may return "SomeRandomPs1ReturnCode". But the step does not support defining return codes. To overcome this issue change the powershell script or set "Continue on Error" and create this step afterwards. If you like this collection and have some other useful commands by your own please share them in a "reply to this Topic"
  23. OSD Run Command Line: WMI to TS Variable (Tested with WinPE 1703 and Windows 10 1703 / SCCM 2012 Version 1706 / MDT ) A short guide how to store WMI information into a Task Sequence Variable without the need of a script. (And therefore without a "Update Distribution Point") Create a new "Run Command Line" Step Set the step name for example: "Set Task Sequence Variable OSD_VariableName" Command Line: powershell -Command "& {(New-Object -COMObject Microsoft.SMS.TSEnvironment).Value('OSD_VariableName') = (Get-WmiObject Win32_ComputerSystemProduct).Version}" Done The example shows how to store the property "Version" of the WMI Class "Win32_ComputerSystemProduct" into the Variable "OSD_VariableName". This is for example usefully for Lenovo devices because the property holds the real model name (Lenovo Model Names) and not the cryptic ID which may change. Other examples would be: Device Disk Count: powershell -Command "& {(New-Object -COMObject Microsoft.SMS.TSEnvironment).Value('OSD_DiskCount') = @(Get-WmiObject -query 'Select * from Win32_DiskDrive WHERE MediaType = \"Fixed hard disk media\"').Count}" Device TPM Chip Available: powershell -Command "& {(New-Object -COMObject Microsoft.SMS.TSEnvironment).Value('OSD_TPMChipAvailable') = [boolean](Get-WmiObject -Namespace 'ROOT\cimv2\Security\MicrosoftTpm' -query 'SELECT * FROM Win32_Tpm')}" Event more complicated commands are possible but at some point a script provides more flexibility. Important Note: "Run Command Line" step in conjunction with "powershell -Command "& {Crazy-PowershellFunction}" has problems with double quotes ("). If they are required they need to be escaped with "\". See for example: Device Disk Count: Other special characters my produce similar issues. If you like this quick and simple solution and found some other useful commands please share them in a reply to this Topic
  24. Background (Using SCCM CBB 1802, MDT & Deployment share on a physical computer, and the image is Windows 10 LTSB 1607) Two part question: I am capturing my Windows 10 image using MDT. The MDT TS installs Windows, then checks and installs windows updates, next it installs office 2016 - run windows updates again - sysprep and capture. - Entire TS runs without a hitch. Then that image is imported into SCCM, then being deployed to new computers. Once completed with OSD (which shows no errors), I receive the following issue when attempting to check for updates: Windows Update failed to check for updates with error 0x8024500C. Error 5/8/2018 2:06:54 PM WindowsUpdateClient 25 Windows Update Agent What could be causing this? Is it a result of running the WIndows update steps during my MDT process? Thanks
  25. Hi guys, Hoping to find people that have managed to push HP BIOS settings via OSD (Windows 10), I've pretty much followed this guide (only the folder structures are slightly different) but I'm having issues actually deploying the settings, setting the BIOS password seems to work okay and I've read that for certain TPM settings to be pushed then a BIOS password must be set prior. My folder setup: BIOS Config settings to push: BIOSConfig 1.0 ; ; Originally created by BIOS Configuration Utility ; Version: 4.0.24.1 ; Date="2018/03/20" Time="14:53:23" UTC="0" ; ; Found 215 settings ; Virtualization Technology (VTx) Disable *Enable Reset to default TPM Reset to Factory Defaults *No Yes Reset of TPM from OS *Disable Enable OS Management of TPM Disable *Enable Activate TPM On Next Boot Disable *Enable TPM Device Hidden *Available TPM Activation Policy F1 to Boot Allow user to reject *No prompts Hide TPM Device Security Level Change *View Hide OS Management of TPM Security Level Change *View Hide Reset of TPM from OS Security Level Change *View Hide Task sequence setup: The bios password sets just fine, but in the SMSTS log I see the following for BIOS settings - HP EliteBook 840 G2 itself: Have attached the SMSTS.log. Any help would greatly be appreciated, I've been working on this for the last couple of days without success, I've tried: Adding CMD.exe /C prefix (same error) Changing the format of the file to repset (same error) Ran the command manually on the device and works just fine with the same configuration files (as .txt and .repset) Tried running the steps in WinPE rather than in the operating system (same error) Thanks in advance. smsts.log
×
×
  • Create New...