Jamoire

How I have done it in the past is assigning variables to a collection and then use the options tab in the Install Application step in the task sequence so to set conditions to look for the variable. So then any client that is in this collection directly or indirectly will get that App installed during the task sequence. Only real drawback is that it doesnt work with unknown clients to SCCM as they aren't in the collections yet but it works great for reimaging or if you prerevision the device into SCCM before imaging for the first time and get it in the right collections. Have also used it with the OS Installation steps so all our clients in School A get Windows 10 and all the ones in School B, C and D get Windows 11 etc based on variables in the collections.

We did it last February half term. All worked fine and was much smoother than we expected. Only issue that we experienced that wasn't documented at the time was the class materials folder link needing to be recreated, but that looks to be in your list. We also never experienced any issues with assignments, old ones continued to work OK for us so interesting that Ms are flagging it as an issue now. Iirc it took at 3 hours for about 1500 users and 500 ish teams / sharepoint sites.

My favourite is White Chocolate and Raspberry too.

We purchased it through Stone. http://www.stonegroup.co.uk

We use Group Policy Preferences to create the shortcuts in a folder on the local PC and redirect to there. If you use custom icons as you can also use GPP to copy the ico files to the PC and then point the shortcut to the local location of the icon. As shortcuts and icons are on the PC they will show up when off the network too.

"Me please!"

Worth bearing in mind that you have been able to update to the last few H2 updates via an enablement package which is a very quick update over SCCM/WSUS etc. So very quick and easy to move on to the longer support version when its available.

I got the initial confirmation but I havnt had a dispatch email yet [emoji3525]. Hopefully doesn't mean I'm not getting one, I need more VeryPC socks for my collection. [emoji16]

Comment

We had a similar error after latest sccm build, it turned out our reboot steps in the task sequence were too short and the ts was rebooting while the client was busy causing the issue. Increased the timer in the reboot steps (i think to 45 secs but would have to check) and all was good. Might he worth a try.

We've had laptops from Stone & VeryPC with the same chassis purchased a couple of months apart and they both had the same issue with the screws so I would say it is definitely a chassis or batch issue rather than a supplier one. Probably happened more on the Stones, which may be because they are slightly older, but Both have been great with fixing them.

https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/ Apologies if its been posted before but found this blog yesterday; worth a read if you are experiencing high bandwidth usage when using 10. Helped me figure out why our clients were still downloading content from Windows Update when they were set to use our SCCM Update point.

https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/ Apologies if its been posted before but found this blog yesterday; worth a read if you are experiencing high bandwidth usage when using 10. Helped me figure out why our clients were still downloading content from Windows Update when they were set to use our SCCM Update point.

Like others we have a PowerShell script to assign the licenses but we have it as a scheduled task that runs each time the AD sync finishes so users get the licenses assigned relatively quickly after being created.

We are having the same issue on random PC's where the Settings app (and in our case the Start Menu wont open), haven't found a cure other than a rebuild yet either. The different build numbers just refer to which of the Cumulative Updates are installed. 14393.351 is the October 27th Cumulative Update (KB3197954) 14393.447 is the November 8th Cumulative Update (KB3200970)

Apologies for having to cancel my place, last minute change of plan at work. Will hopefully be able to make the next one.

https://jairocadena.com/2016/01/18/how-domain-join-is-different-in-windows-10-with-azure-ad/ That's the information I used when setting it up if I remember correctly.

We have had it running on a couple of machines as a pilot, signs the user into the Store, Office 365 Sway etc automatically fine. We had it going via the Directory Sync tools rather than ADFS so it takes a little while for it to register, the only issue we found was when we rebuilt a machine and keep the old AD name it didn't seem to re-register with Azure AD so the SSO wouldn't work. Haven't had chance to try and solve it though so not sure how much of a problem it is.

You could possibly do it in Manageengine ServiceDesk by creating a task linked to the ticket, and in the tasks you can set the Task Start and finish times.

Its called 'System Center Config Mgr Client Mgmt License (current branch)'

I know the OP is a couple of months hold so you may have it sorted now, but you only want to run the Auto Apply Drivers step if you haven't manually got a specific drivers package for the model? Rather than evaluate on the driver package itself, you could put each driver package in a separate group in the task sequence and add a set Task Sequence Variable step to each group setting a variable such as DriversInstalled with a value of TRUE. Evaluate each group with the WMI query of the model as you do with the package now, and then only run the Auto Apply Drivers step if DriversInstalled doesn't equal TRUE. That way when you add a new drivers package you can just replicate an existing group rather than editing x amount of WMI Queries.

You can set the XML file location in GPO as well but I haven't tried it that way, so no idea how well it works. Computer configuration > Administrative templates > Windows Components > File Explorer > Set a default associations configuration file

We have done it by getting the defaults how you want them on a reference machine and then run the following which should create an XML file with the settings in. And the copy the XML file to the new machine and run the following at the end of the our deployments Task Sequence

We also use XIBO and have them running on the Atom Intel Compute Sticks which you can pick up for ~£70 ex VAT. Seems to work pretty well.

We've pretty much always gone for Stone / VeryPC laptops. Never had any trouble with them. As localzuk said, don't go off the web site prices you get much better pricing going through an account manager and if you want an extended warrantee you can get them for next to nothing compared to most of the big brands. Novatech, Ergo etc use pretty much the same Clevo chassis as well. We found a big advantage of them is all the models we've had over the last 6-7 years all use the same generic 19V chargers so are easy to swap between laptops and cheap to replace. Stone have always been very reasonable priced to get hold of replacement parts as well if anything does get damaged.