Search the Community

I'm using SCCM 2007 R2 to deploy Windows 7 and I've noticed that the OS Disk gets labelled D: Although this isn't terrible, I'd prefer it to be C: (expecially given the lack of any other partitions!). Any ideas? I created my WinPE images and task sequences via MDT 2010 (integrated to SCCM). The issue arrises on x86 and x64 installs.

Hey! This one has been driving me crazy for weeks! So I have OSD set up on MECM to deploy to the built in unknown PCs Collection and it works a treat, I can PXE boot an image PCs to my hearts content, but once imaged I can't get them to re-image without deleting them from the MECM database (to make them unknown again). I have set up a custom collection and deployed a task sequence to that collection. When I PXE boot again it loads the boot image wim, then reaches MECM deployment screen and just reboots before the box to continue and select a task sequence appears. I can see in the smsts.log file it says "No Task Sequence Available", but according to my console there is a task sequence deployed to the collection! I don't want to have to delete machines from the MECM database every time we want to re-image and we don't want to use software centre, we just want to PXE boot a machine and it be able to image once already imaged on MECM. Can anyone advise on this? Thanks

Hi all Just found out a new classroom has been supplied with an iiyama touchscreen with a built in Win 10 Slot-PC. Totally open question - has anyone here ever built an SCCM image for these for OSD?? Any idea where to get the drivers from?

I was finally getting somewhere with my OSD using SCCM and tests were going well - I could add new computers into a collection via Operating System Deployment->Computer Association and all was well. I've now added a few more packages/programs to be installed with the OS build and deleted the test computers as I had done several times before. My problem now is that I cannot add new computers via Computer Association. I go through the wizard and it all appears OK but then nothing happens. Everything seems to be running OK and I can't seem to see anything in the logs either. HELP!

I am trying to image some new laptops with a newly built Windows 10 EDU image. The image works, I have deployed it to other machines (including other E560s) without any issues. I am struggling with a group of these laptops that will not take the image. The error i get is 80070490, it cannot find a suitable partition. From WinPE, using Diskpart, I can write to and access the drive. I can see folders being created on the C: drive during the OSD process. But it fails pretty consistently, with a few exceptions that imaged fine. I have added new drivers for this configuration and still no luck. I've also tried PXE booting with similar results. Not sure what i am missing here. Anyone see this behavior elsewhere? If so, how did you get around it? Thanks. I am running SCCM Current Branch 1511.

Hi All, I am getting a black screen with cursor after deploying Windows 10 OSD SCCM task sequence. Not certain what the cause is. If anyone has come across this issue or similar, would you mind sharing your solution ? Background OS Version - Windows 10 - 1803 SCCM 2016 - CB (latest Update) ADK - Latest Version Boot Image (x64) - latest version - imported from ADK --- I have created a OSD Task Sequence in SCCM, with the basics - 1) Partition Disk 2)Apply OS 3)Apply Windows (I have specced an unattend.xml) 4)Apply Network (basic DNS & domain extension) 5)Apply Drivers (have enabled - unattended install of unsigned drivers) 5) Setup Windows & ConfigMgr (have set SMSMP, DNSSUFFX, SMSCACHESIZE) 6)Install Applications (setup as packages rather than Applications) .Net 3.5 Chrome Impero Google File Stream VLC 7-zip The process appears to complete without errors, however the computer gets stuck on a black screen with just a cursor. If you force the computer to switch off using the power button & then power it back on again, the PC continues fine. The OOBE appears and goes through (doesnt ask for anything due to the unattend.xml) and then drops you at the Windows Login screen. Once you login, the applications have installed fine & all the correct drivers appear to have been picked up. Looking in Event Viewer - I can't see any obvious errors. The smsts.log does show a couple of yellow flags, as follows, but I haven't been able to pin down if they are relevant RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram GetTsRegValue() is unsuccessful. 0x80070002. Thanks in advance for any suggestions. Cheers Andy

Hey all, So just like the title suggests, I would like to get rid of Teams as we are a G Suite school. Therefore, no need to have it automatically added. If a user needs to use it, they can either install the user-level app, or just use the browser (which is what we do on Windows 10). I'm ripping it out via a PowerShell script during OSD via MECM. But then I noticed that once OSD is completed, Teams gets installed upon the first login. So then I created a logon task to remove Teams using the SYSTEM account. And this works as intended. Then about 4 or 5 days later, Teams is reinstalled. And it's installed as a provisioned app. This tells me Microsoft is adding it back somehow. Just like I stated above, I don't want to completely Teams because there are a few legitimate cases, but for the most part it is not needed, and I'm trying to avoid confusing my users. Here is my code to remove it during logon. I know it's redundant, but it's a catch all, just in case. [color=#D4D4D4][font=Consolas][color=#9cdcfe]$TeamsProPkg[/color] = [color=#dcdcaa]Get-AppxProvisionedPackage[/color] -Online | [color=#dcdcaa]Where-Object[/color] { [color=#9cdcfe]$_[/color][color=#dcdcaa].DisplayName[/color] -like [color=#ce9178]'*Teams*'[/color] } | [color=#dcdcaa]Select-Object[/color] -ExpandProperty PackageName -First [color=#b5cea8]1[/color] [color=#dcdcaa]Remove-AppxProvisionedPackage[/color] -PackageName [color=#9cdcfe]$TeamsProPkg[/color] -Online -AllUsers -ErrorAction SilentlyContinue [color=#9cdcfe]$TeamsPkg[/color] = [color=#dcdcaa]Get-AppxPackage[/color] -AllUsers | [color=#dcdcaa]Where-Object[/color] PackageFullName -Match [color=#ce9178]'Teams'[/color] | [color=#dcdcaa]Select-Object[/color] -ExpandProperty PackageFullName -First [color=#b5cea8]1[/color] [color=#dcdcaa]Remove-AppxPackage[/color] -Package [color=#9cdcfe]$TeamsPkg[/color] -ErrorAction SilentlyContinue -AllUsers | [color=#dcdcaa]Out-Null[/color] [/font][/color] Is there a registry key or something that tells Windows to install it? Checked the GPOs, but don't see anything but the chat icon. I haven't tried using dism.exe, but I'm sure the above cmdlets are the same as using dism.exe. Any help will be greatly appreciated.

Hi all Firstly I have searched and found (and read) this thread: Toshiba C50 :Laptops will not boot PXE - Page 3 (edugeek.net) My issue is similar but annoyingly different. I can get the laptops to PXE and start the WINPE bit. Everything runs fine until the first reboot. Once that happens I get the Dynabook logo and the spinning circles then nothing. I left the laptop like this overnight and no change the next morning. If I go into the safe mode options and choose any version of safe mode the same thing happens except that the spinning circle doesn't appear. I tried debugging and bootlogging but no logs appear and no change in the boot. If I choose to disable signed driver enforcement the circle stops spinning and then nothing happens. The laptop is set for UEFI boot and the drive is formatted OK (going via Diskpart whilst the first bit of the TS is running). All of our other laptops (different makes) use UEFI and work fine with the same image I could change our DHCP to do a non-UEFI boot and format the drive as legacy but that would mean chopping and changing the DNS settings whenever this laptop model needs rebuilding - annoying as everything else in the school uses UEFI. I have read that there is a way to set DHCP up so that you can boot to both at the same time but the changes it suggests never worked for me. Toshiba no longer provide dedicated SCCM driver packs to download so I've had to cobble drivers together. I first got the drivers from a working (OEM) Windows installation using this method: "Go to C:\Windows\System32\DriverStore\FileRepositorySort by date.All of the most recent folders (there should be a group) contain the drivers that Windows itself doesnt include.Copy these folders and import them to SCCM." I then manually downloaded the latest drivers from the Toshiba support site and imported those... Still no joy. So with a laptop that will not boot into Windows in normal or safe mode, will not log debugging or boot logging how do I go about troubleshooting the problem. The only thing I can see is that the SMSTS.log file suggests this is all failing before the driver packs are installed so that makes this even more odd.... Any help would be nice!!

Morning all Since installing SP1 I have been having an issue with OSD when using an answer file. I have set it up so that there are commands that run during first logon, this is an auto administrator logon, and once they are done the system is told to restart. After the install of SP1 I have noticed that after the machine has finished installing etc. that I find a logged on administrator user, my initial thought was that the answer file was causing an error somewhere during the last sequence but as far as I could see all the commands were being implemented and the smsts.log didn't show anything useful. It turns out that they have reorganised the deployment sequence between RTM and SP1, previously SCCM would do all of it's stuff like install the client and deploy updates, and then finish off with the answer file command lines. Now it will go through those command lines while installing the client, so the first auto logon that I used to need is unnecessary and leaves a potentially vulnerable machine if installed unobserved. I should note that I don't have any documentation besides my own monitoring of the install process to back this up. Hope that helps someone in the future.

Good Morning, Hoping someone can advise please. New to SCCM and we're just working on the OS Deployment task sequence. Everything seems to be working okay, I have had to make a number of tweaks for Win10 1903 such as the unattend file to fix the "just a moment..." screen, but it looks okay at first glance. My question is, how do you tell that the task sequence has been completed 100% like 15/15 steps successful? I know there are numerous log files dotted around, but is there somewhere obvious that shows 15/15 successful? I've had the task sequence fail at various points when I have added some steps in, but when it fails, the machine reboots and sits at the login screen.. Just the same as it would if it got all the way through the task sequence successfully. Thanks in advance.

Hey Guys, Just after some input how you guys do your SCCM. Currently, a site I look after has a Task Sequence for each organisation unit in AD. Example, TS Name is "Deploy W10 - Student Laptops". The same task sequence exists for around 10 other OU's. Granted, this is only a small school, however I was wondering of getting this down to 1 main TS? I would like it if I could get SCCM to prompt for the OU location upon running the TS. I have managed to get a prompt for a Computer Name using the OSDComputerName value, would be nice to get a list populated of AD OU's. Or, do you guys do it manually? As in, join to the domain, and manually move the computer into the correct OU? Looking forward to the replies. James

I've got a single PC that I'm trying to build but it only seems to want to boot the x64 boot image. The PC is correctly identified as being x86 prior to loading the image and then, of course, it bombs out. I have the PC in a collection that only has an x86 task sequence applied to it and I've even updated the BIOS in a hope to fix the problem. Any ideas guys?