Search the Community

So probably looking over something really small, but I can't find it. Right now, I'm in the testing stages of deploying Windows 11 via a MECM task sequence. After about a week of tweaks and VM reverts, I finally got a successful upgrade without Teams and the other junk that gets installed. Before the upgrade, printers worked just fine...even with all the print nightmare updates. Instead of GPOs, re deploy printers from our print server using WMI. The reason we don't do a direct add is because we use pCounter. $printclass = [wmiclass]"win32_printer" $printclass.AddPrinterConnection("\\server.fqdn.edu\Sample Printer") And this worked with no issue. Then after I upgrade to Windows 11, this breaks. Gives me different error codes for different printers (3221225480 & 1722). I checked to see if the printers were configured any differently, but they're aren't. Again, these are in production with Windows 10 just fine. We also pre-install the Universal HP Drivers, so that's not a problem as well. I'm not sure if Windows 11 supports type 3 drivers or not, but that would be a bit weird if it didn't. Even then, pCounter is unable to support Type 3 drivers...according to my reading. I just can't figure out the issue here.

We have an ongoing problem which has been brought up on other forums but thought i'd try here in case anyone had a solution. So we're currently having to set our OSD task sequences to ONLY run on Windows 2000 based machines. This prevents the task sequences being advertised on all our machines within windows, but allows us to pxe boot the machines and run optional/mandatory sequences. This is mainly to prevent the icon from springing up in the notification area when a task sequence becomes available. This has worked fine but is not ideal as it causes problems with duplicate records in sccm. This means that if I need software to be distributed to the computers immediately after deployment, I have to run a system discovery for the new computer objects to be dropped into the right collection. Then I have to run a machine policy update. This is all a bit of a backwards way of doing things, not to mention the amount of rejected advertisement data this is collecting. Ideally what we need is for task sequences only to be available in windows to certain users (us) and disabled for everyone else. The other option is to find a way to disable the notification icon on the task bar which pops up if there's an advertisement. Little Jimmy can't run the TS though, as they don't have privileges but it really has to be hidden...just in case. If you're wondering why I don't just install the software during the task sequence it's because our converted Prism packages don't play nice with config manager and usually fail. Any ideas?? Cheers chris

Hi, I've been trying to image a set of Opti 390s and a weird thing happens when the TS has finished. You get to the login screen after which I log in with my network creds, only you just get a white sccm 2012 background and a mouse cursor and nothing else; no start bar or desktop icons or anything. Restarting the computer and logging in again seems to solve the problem but I was wondering if anyone else had this problem? I have another restart at the end of the TS but would it be best just to whack in a shutdown -r command? Thanks BC

Hi Everyone, Long time searcher first time poster. I need some assistance please, I have been asked to give our image to vendors so that they can pre load the hardware. I don't have problem with this actually love the idea. BUT My task sequence is an MDT\SCCM Task seuquence that when you boot it starts UDI and asks for Computer Name then installs the OS. How can i have it apply the Data Image (At Vendor without Network Access) > Shutdown > When unboxed at location continue with UDI asking for Computer Name and Continuing.

Hi, hope someone can help. Just started getting a problem when migrating XP user’s to Win7. Up until now the USMT task sequence has worked fine and I’ve used it to migrate several users. However, I’ve just started getting the error “Unable to find the SMS task sequence. The deployment will not proceed.” At the point where the TS should be restoring the userstate. The user’s data is captured and the OS is applied. The TS then logs into the Administrator profile ok but then gives me that error. BDD log has an entry saying: “ ” The LiteTouch.wsf is in the programs\start folder but even manually running it gives the same results. The MDT is online on and will work for deploying an image, and I can map to it with the failed client. As far as I’m aware nothing has changed in the MDT server so I’m baffled as to why it’s started doing this now. Google search has had a few people with the same error rebuild their deployment but I don’t want to go down that road unless necessary. Thanks for reading, Rob

Just ran across this handy little task sequence template for MDT which allows you to very easily and automaticly run just a capture task on a freshly minted image without having to juggle command lines or resort to other methods. deployvista.com > Home - Capture only Task Sequence for MDT 2008 (Lite Touch)

I want to deploy BitLocker onto our laptops when I perform the Windows 7 deployment to them. Has anybody done this with SCCM? The problem I have at the moment is this... I have a task sequence which creates a system partition and a Windows partition. These are then named C: and D: leaving the optical drive as E: - something that my users will struggle to comprehend. What I want to do is deploy Windows like the setup media does (with a hidden 100MB partition). From my Internet readings, I've seen lots of people suffering from my problem with the standard task sequence operations and I've seen people changing the 'extra' drive letter to something like Q: or O: but I don't really like this option either.

Is there a way to Preserve Computer Name on a Refresh Task Sequence? I'd like to be able to Refresh a Lab of 30 PC's over the summer, or as needed, and maintain the existing PC Name. Everything I've read leads me to believe that I won't be able to do this easily, if at all. If preserving a Computer Name on a Refresh cannot be done, I guess I can change the naming convention 'on the fly' for that classroom, and then rename them back to the standard computer names after the fact Or, I could just delete the 30 PC's from AD, and manually type in the PC names individually in the task Sequence as I PXE boot these to refresh them with Litetouch. Either method is not ideal, but I don't see a better option. Feedback on how you deal with a Lite Touch refresh of multiple PC's where you want to maintain the PC name of the computer would be appreciated. Thanks, Stephen

Hi,I have deployed a new Task Sequence as a required deployment to a collection containing 30 devices. I have set the scheduling as I normally do when this has worked in the past. I have also put the "Rerun" behaviour as "never rerun deployed program" as this is a new Task Sequence. The Task sequence however doesn't start. In the config manager log, I am receiving the error "The deployment has not yet started because the content for the package "****" has not been acquired". This package it is referencing is the Config Mgr Client.The Client is successfully distributed to this DP. Has anyone got any ideas why this is happening please? Some things I have tried so far : - Validating the package again to this DP (successful) - Testing a reimage manually which works fine, if the package was an issue it would be highlighted? - I have had mixed results when testing a different Task sequence that uses the Config Mgr Client, sometimes it works and gets passed this stage, sometimes it doesn't - so its been hard to pinpoint the issue. - Tried changing the "Rerun" behaviour to "always redeploy"- I have been able to image remotely at a different site that uses a different DP but the same Config Mgr Client. - I need to read up more on Boundry Groups, however the config I see looks OK and worked fine on our last automated deployment. - I have logged into one of the devices, and watched this in Software Centre and it stays stuck on Downloading. - I have tried running a Config Mgr Client repair

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.

Basically i have setup my Deployment Share with 2 seperate task sequences one for Windows 7 Enterprise 32bit and one for 64bit both also have their own driver folder x86 and x64 respectively which they point to Bascially this is the only manual process (apart from name and OU which i want to keep manual) which i want to automate What i am trying to do is basically get MDT to query the amount of RAM that the machine currently has from the BIOS etc and point it to either 32bit if 3.5GB RAM or lower / 64bit task sequence if 4GB +?? Thanks Jack