Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender

Jumanji_21's Achievements


Newbie (1/14)



  1. We don't use PXE presently, our machines are being built via USB boot stick hence why I thought it may be a driver issue of some kind?
  2. The BIOS is set to Legacy Support Disable and Secure Boot Enable. It has been saved so is set to that at each machine boot up.
  3. Hi, My boot image OS Version is 10.0.10240.16384 The Windows ADK version we are using is 10.0.26624 as well.
  4. Hi everyone, I am attempting to do my first UEFI-based SCCM install for Windows 10x64 for my firm. Previously, we had Windows 7x86 installed on these devices, and everything worked fine. Attached is the driver list that i am currently using in my x64 boot disk. When I try to do the bootup - I get the below message... Status: 0xc0000001 Info: A required device isn't connected or can't be accessed Any ideas? Thank you in advance.
  5. If your departments have different subnets, or IP addresses - you can easily do it that way. That's what I do in my firm, we have global sites so we need to be able to easily move them to the correct OU each time the machines are built. We use the "Gather" step to capture the machines details - and then process this using the TS Variable of DefaultGateway001 = XXX.XXX.XXX.XXX Then when joining the machine to the domain you can move it wherever. You should also be able to do this using the CustomSettings.ini as well.
  6. Hi everyone, I wonder if someone could help me. In my corporate environment, we have collections setup for deployments that our Service Desk use to build machines. The idea is that machines are created or added into that Collection, and the Task Sequence is also deployed to the Collection. We have upgraded to SCCM 1702 in recent times and ntoiced that we cannot always import machines to the collection - we get an error code, like 2152205056. I just looked at: So will test that out tomorrow when I am back in the office. The other issue I am having is; when we have existing machines that are in SCCM and show at Active with a tick etc, we cannot always rebuild them. Sometimes we can just start off the boot media and then either proceed or clean the disk first and then reboot/start the Task Sequence. Other times I get the "There are no task sequences available for this computer" message. What are we doing wrong?
  7. Hi everyone, I am working on a new TS after we have begun migrating from MDT 2013 to SCCM 2012 R2 v1511. The issue I have is that we want to be able to automatically rename machines based on the Device Affinity. I can import the machine into SCCM no problem... When it comes to my Task Sequence, I have setup a step called Gather based on MDT. I have then setup another step called Set Computer Name, this references OSDComputername and points to the Variable: %_SMSTSMachineName% This doesn't work and I end up getting the standard MIN_INT etc name. How can I resolve this? At the moment I am working on a Windows 7 image but I will also need to apply this to Windows 10 as well. I know as another resort, I can amend the Unknown Computers Collection - but I'd rather have it automated, as we'll be having our supplier send us a list of MAC addresses and Asset stickers which will be used to generate the name at the point where the machine is being built. Any help would be appreciated.
  8. You can use the variable; OSDComputerName in a task sequence like I do in my current place... We set the value of a code and then...%serialnumber% so its something like: XXXX-%serialnumber% This always works for us... and it won't be renamed afterwards.
  9. Try: https://social.technet.microsoft.com/Forums/en-US/064981ba-47ea-4b05-9986-9ed0ccd06853/sccm-2012-sp1-cant-add-boot-image-only-finalized-boot-images-are-supported?forum=configmanagerosd or http://clintboessen.blogspot.co.uk/2013/10/you-can-not-import-this-boot-image-only.html
  10. Hi guys, and girls... I recently upgraded our SCCM environment from SCCM 2012 CU1 to SCCM 2012 R2 CU5 and during the first few months, everything worked fine. I had to recreate task sequences, and also Boot images due to this upgrade but again no worries there. Recently over the last week or so, I have begun seeing a major slowness when building machines. This is not just relative to Desktops but also to Laptops as well. I have tried recreating the Boot.WIM file, and added the relevant drivers but this makes little or no difference. I have also installed the: KB2905002 hotfix already. When the task sequence is run, the WIM file goes to about 4% and then slows down incredibly. The original time to complete a build used to be about 40 minutes or so, now its closer to 1.5 hours... Please can someone help me?
  11. Have to admit, that I'm really looking forward to SCCM 2016... One thing that interests me is how the WIM file will be created as from trying Windows 10 Enterprise, it needs to be pre-joined to a domain at first boot.
  12. How long is the update schedule for? Maybe try forcing it through manually and monitor the logfile through cmtrace. We used to have network scans running every 7 days but when I joined the company that I work for now, I amended that policy.
  • Create New...