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
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • 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
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • 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


Website URL


Location


Interests

  1. I have a OSD Task Sequence for Windows 11 22H2 being deployed to new Dell Optiplex 7000's. The Dell's are going to sleep during the "Setup Windows and Configuration Manager" step of the Task sequence. I have checked the "Run as high performance power plan" box in the more options tab, but the PC still goes to sleep. I have also tried using a run command to set the power plan to high performance "PowerCfg.exe /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c". The run command works fine in Windows PE, but doesn't persist when the task sequence boots into Windows to start the setup phase. I tried adding the run command right before the setup phase and right after the setup phase. No matter where I put the run command it doesn't seem to matter. If I don't touch the mouse or keyboard before the PC goes to sleep the TS halts. Once I shake the mouse it will continue where it left off. If I put the run command just above the "Setup Windows and Configuration Manager" It runs fine and if I hit F8 and run "powercfg /getactivescheme" it shows that the system is in high performance mode, but then when the system reboots into the installed OS the powerscheme has reset to balanced. If I put the run command after the "Setup Windows and Configuration Manager" step, then the pc goes to sleep because it runs after the fact. I guess I am asking how to set the powerscheme to high performance once the PC has booted into the installed OS but before the "Setup Windows and Configuration Manager" portion starts to run. I saw some posts from years ago on Reddit talking about connected standby and using a registry setting to change it to disabled, however I still don't know where to put the reg tweak in my TS and it seems like the adition of the "Run as high performance power plan" option was supposed to fix this. Thanks
  2. Dear brothers and sisters from the IT World, I trust this finds you very well. We have received a new DELL Model: DELL Latitude 5530. The model has the following Network Interface: Intel Ethernet I219 Network The required drivers have been properly imported and added to the task sequence (driver package). We have two vlan/subnet where we can stage the laptops: Vlan A - Same Subnet as the SCCM Server Vlan B - A diferent Subnet (Sccm Server), we use ip helpers to root the trafic. Staging Vlan A Test1 - Port RJ45 - Network Interface: Intel Ethernet I219 NetworK I tried with a diferent dell model and everything worked properly, really fast and stable. I tried with the model DELL Latitude 5530 (2 diferent laptops) and the Task Sequence return an error right at the begining, the DISK is not even formated and we get the following: An error occurred while resolving dependencies for the selected task sequence (0x80072EE2). For more information, contact your system administrator or helpdesk operator. As we can see on the SMSTS.LOG located in (X:\windows\temp), an IP is properly assigned: And as you can see in this screenshot, i have an ip address: Please find more details about the error below: Test2 - USB-C - Docking Station I tried with the model DELL Latitude 5530 (2 diferent laptops). The WINPE Img takes a lot of time to download but after that, the TS works properly (even if it is slow) and i dont get the error. Staging Vlan B Test1 - Port RJ45 - Network Interface: Intel Ethernet I219 NetworK I tried with a diferent dell model and everything worked properly, however, the network is slower but it is stable. I tried with the model DELL Latitude 5530 (2 diferent laptops) and everything worked properly, the network is slow but it is stable. Test2 - I didnt do it because the objectif if to reimage on the SCCM Subjet. This is driving me nuts.... Can you please guys have the kindness of helping me? As always, your help and support is very much appreciated. Thank you all and best regards, your help and support is very much appreciated. Peace
  3. Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all. Task Sequence Steps (in order): Capture Windows Settings Capture Network Settings Install Operating System Restart in Windows PE Format and Partition Disk Apply Operating System Apply Windows Settings The rest doesn't really matter since the task sequence is failing at "Apply Operating System" (On the HP Probook 430 G3) This issue only occurs on the Probook (laptop) and NOT the Prodesk (desktop). The way we are managing OSD here at my company is to have a "Golden" Task Sequence, then just copy that same task sequence for as many different model of systems we have and insert the corresponding driver package as well as rename the task sequence for whatever new model we discover we have or receive. So we received our new shipment of Probooks (laptops) and I did what I always do when we get a new model. I grabbed the Windows 7 drivers for it (Note: These systems come with Windows 10 installed. Our image is Windows 7 Enterprise x64 SP1.) and created/copied a task sequence for the new model by simply switching out whatever driver package was in the task sequence that I just copied with the correct package for that model (a lot of this is irrelevant since again, the task sequence is failing at "Apply Operating System" before it even tries to install drivers.) Things I Have Done: Made sure all content called for in the task sequence is on the DP Deployed the TS as Available (PXE,Media,Blah blah) to All Unknown Computers Read through the provided smsts.log and could not make sense of it. Seems error 0x80004005 is a "beat around the bush" error Created a task sequence from scratch then tested. Still same issue at the same place Thought maybe its an issue with my .wim but I dont think so as this has worked on some of our other models tested Came here for help I am at a total loss as of where to start to troubleshoot this error. Most of the info you will need to help asses the issue is probably contained in the log(CMTrace it). Please let me know of anything I left out that could help. Thank you! smtsprobook
  4. Hi all, I have an error that has plagued me since, I think, upgrading to SCCM 2012 R2. I have a handful of OSD's which I have setup and generally, they all exhibit the same issue at seemingly random times. I could have multiple machines on my bench all using the same OSD and a couple of them will hang during the installation of applications. So, it installs the Windows image, sets up the CCM client, reboots and finishes the client install and then starts installing applications. When it hits about the third or fourth application it just sits there and does nothing for as long as the machine stays on (no error). It seems to be something that happens after a fixed amount of time (not sure how long), probably ~10 minutes after the last reboot. It makes no difference how I order the apps to install. I've sorted the log list by date and time to try and find an error somewhere but I can't see anything. The really frustrating thing is, if I have a machine that is failing it will usually keep failing repetitively but then suddenly it might start working and completed the TS all the way through. Can anyone give me any advice as to what logs I should keep a closer eye on (client/server) or if anyone has heard of anything similar. It's really frustrating when you have hundreds of machines to do! Sorry if I'm a bit light on info, I'm not sure what to provide as I'm still learning! Cheers!
  5. 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
  6. 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)
  7. 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?
  8. 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
  9. 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 ?
  10. 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?
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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?
  16. Hi Everybody, this thread is for those who want the old SCCM 2007 driver management back. Normally you have to import every driver to the database first, put them into a driver package, and then deploy them during OSD. In SCCM 2007 you could easily create a Driver Package from your Driver Source Folder and apply this Driver Package during OSD. This way of Driver Management was much easier and more reliable than the new way in SCCM 2012. But luckily there is still a method to prevent importing drivers into database and directly distribute driver packages to your clients. Step 1 Download drivers for your brands and models. Put them into seperate folders - one folder for one model - like you did in SCCM 2007 Step 2 Create a Package for each model and operating system. Then distribute this packages to your DP. Step 3 Create a Step "Set Task Sequence Variable" under your Auto Apply Drivers Group (after the Apply Operating System Step) in your Task Sequence. Task Sequence Variable: winrootdir Task Sequence Value: D:\ Condition: If Folder "D:\Windows" exists I created a second step after this with Drive Letter E:\. Because on some Notebooks the Systemroot is E:\ during OSD. Step 4 Create TS Steps for each model to apply the driver package. Type: Run Command Line Command line: DISM.exe /Image:%winrootdir% /Add-Driver /Driver:.\ /Recurse Package: Choose the corresponding package you created in step 2 Success codes: Add 2 and 50 Condition: WMI Query (here an example for Dell Latitude E7240) select * from win32_computersystem where Model like "Latitude E7240%" Repeat the steps above for each computer model you want to image. With this way of applying drivers we have 0 problems in our environment. Very easy and reliable. BR Achim If you have questions - feel free to contact me http://ithilger.de/kontakt
  17. 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
  18. 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.
  19. 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
  20. What's so great about the MDT / SCCM integration, specifically about task sequences and OS deployment? I understand that using MDT to build an image is preferable for a lot of reasons, and I'm okay with that part. It's the MDT-enabled task sequences that are bothering me. It seems like whenever I need to create an MDT task sequence, I have to bend over backwards, analyze everything in the task sequence created, tweak the defaults, pat my head, and rub my tummy before it will (somewhat) work correctly. Here's my latest example: I needed a fairly simple refresh task sequence to be run on about fifteen computers of a single hardware model. I'm not concerned with preserving any data on them; I just need to format and install Windows, along with a set list of applications. I'd like to use copyprofile as well, so I turned to MDT instead of building my own unattend.xml from scratch. My MDT task sequence is now three times as long as my original "vanilla" task sequence was, contains unneeded variables for BitLocker, UEFI, and the UDI wizard, and it still fails! I get seemingly random 80040005 errors throughout the task sequence with no apparent rhyme or reason (they actually happen in different places in the same task sequence on the same machine) with no output in smsts.log. The SMSTS.log files are now stored in about four different places. In fact, when I create a new MDT task sequence without selecting the UDI wizard and try to run it from within Windows (using the Software Center), it doesn't even restart into Windows PE - I get an error when it tries to partition Windows from within Windows. I'm fairly new to MDT, so it's very possible I'm doing this wrong...but from my perspective, integrating MDT with SCCM has been nothing but a headache. Could anyone explain some of the advantages of using these enhanced task sequences?
  21. 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
  22. Hi Everyone,

    I'm a new Level 2 Technician as i was previously Level 1 technician and my main role was helping users troubleshoot issues on their Computer and recently had a few colleagues from Level 3 started helping me get into SCCM environment were i flourishing from their Wisdom, so found your site and started to visit this site to learn a few things and decided to register.

    Thank you for visiting my page

  23. 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.
  24. 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
  25. Hi everyone. I'm hoping someone out there can assist. Sorry for the length post but my aim is to provide as much information as possible to eliminate any of the common gotchas. ConfigMgr is 1702 with latest Hotfix I've spent the better part of two weeks trying to figure out why OSD has all of a suddenly stopped working. It seems to have happened around the same we upgraded our last DC from server 2012 to 2016 (swing migration) and raised the domain fictional level from 2012 to 2016. From the many hours spent doing google kung fu, ConfigMrg should not have any issues working in 2016 etc. DNS, DHCP AD are all reporting healthy with the usual couple of things that we can ignore from the BPA (Best Practices Analyzer). How we do OSD: We exclusively image Unknown Computers and have done so for many years (Since 2012 R2). We do not image our machines using deployments to any other collection. We delete the computer from the SCCM DB when we need to re-image. This works well for us in our environment. :-) All Task Sequences are deployed to the Unknown Computer collection. We are using ADK 1703 (the most recent one with all bug fixes) and boot boot x86 and x64 boot images are distributed and enabled but we only use the x64 boot image. The issue: Machines can successfully PXE Boot into WinPE, all machines no matter make, model, physical or virtual) all get an IP address and we can ping the ConfigMrg server without any issues. Once a computer gets into WinPE the screen goes blank and the computer reboots straight away. Actions taken so far: Common gotchas I have checked: Checked the date and time are correct on the client Made sure to delete any unknown computers or any references to the machines I have been using for testing or imaging in general Thinking that it might possibly be a Boot Image/PXE related issue I followed a couple of very detailed guides online and removed the PXE role from the Distributions Points by: Unticking it from each DP, deleting the files in the Windows Temp folder, deleting the RemoteInstall folder, removing the Boot images from DP's, the usual reboots, checking logs, re-enabling the PXE roll on DP's rebuilding the Boot images, deploying the boot images, enabling the both x86 and x64 boot images, making sure that my Task Sequences were referencing the newly created boot images. I then booted a machine up (in this case a test VM) and pressed F8, I ran cmtrace and opened up X:Windows\Temp\SMSTSLog\smsts.log. Then I found this error message: There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows) TSPxe 12/07/2017 12:28:40 PM 1284 (0x0504) So I thought perhaps my Task Sequence deployments themselves might have some issue on the DP's. I tried redeploying the task sequences and creating a brad new Task Sequence to test and I still got the same error. I checked the boundary groups and Active Directory Sites and Services and everything looks fine. I tried initiating a discovery of everything possible. Here is an example screen capture video of the issue we are experiencing: Looking forward to any comments below!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.