sparkeh

How are you referencing the applications in the xml? Anything installed before first boot (i.e. as part of an sccm TS) should be referenced by DesktopApplicationLinkPath and everything installed after first boot should use DesktopApplicationID and the application's AppID (found by running the PS command get-startapps) I've found that the applications referenced by the AppID are the ones that will pop up if the Start Menu is applied before the app installation.

I've found that since v1703 this is no longer true. If you deploy a start menu to a PC that contains an item that isn't installed it doesn't show anything. However after installing it, and the shortcut appears in the %ALLUSERSPROFILE% start menu, the tile pops up.

Exact same issue. Couldn’t find a decent solution so ended up letting the machines pick up the missing drivers from windows update. This is in the to do list to fix

Have a word with @ICTDirect_Dave

@Millgate

I wouldn't say so no. I think there is a fairly even split. Personally I think that Edu is the way to go. As you will have seen the pro and cons have been argued over but I wouldn't like being constrained by the hardware limitations of LTSB and using a a version that is designed to static systems that are updated infrequently. I can imagine it coming back to bite you in the future but hey, many others will tell you the opposite Essentially it comes down to deciding which version fits your environment the best.

Don’t worry it bombed the first time too.

Snowed here and it’s settled, rain forecast for later though

Q: why did the chicken cross the road? A: Terrible Some QA issues on our jokes this year [emoji3]

Oh and to those that observe it, Happy Hogswatch! [emoji3]

Merry Christmas! [emoji3] [emoji1335]

Whilst this isn't company bashing, I just want to share my experience of why we left SW after many years as customer, I hope that its helps the new management to get to grips with things. Of course this is my experience and others may vary. When we first went with SW (and for the next few years) it was an amazing company to deal with. Support was awesome, engineers knew the product inside out and most issues were sorted quickly at 1st line and escalations were dealt with quickly. I recommended SW to many other schools. Whilst it was more expensive than other solution the price was well worth paying. The first thing I noticed was the quality of first line support dropping. The well trained support seemed to me, to be replaced with less well trained operatives who couldn't solve the kind of things the old ones could. Unless an issue could be solved easily it had to be passed up to second line. And then you had to wait. This became a frustrating pattern. Contact between updates became longer and longer and the support became a big issue for us. The other problem for us was the price of the renewal. At our last renewal the price was astronomical. Also the quote had impenetrable lines of licences that needed a phone call to sales for clarification for what we are actually paying for. In comparison, the solution we migrated to had a very clear table of options to choose from and a clear quote at the end. Also it was dramatically cheaper. I made the call to SW sales to discuss price and the account manager dutifully told us about all the benefits of SW but informed us that there was no movement on price. So I ordered another solution and informed SW that we wouldn't be renewing. Lo and behold I was made an improved offer to stay with SW which infuriated me and confirmed our decision to leave. In summary, the problem for us was quality of support and price.

The .local domain thing is an old problem, we have one and apple stuff works just fine https://support.apple.com/en-gb/HT201275

The Tory dream has come true!

Only for the first user that logins and installs a new printer for that machine. Subsequent logins shouldn’t have an impact at all unless you add more printers with different drivers that need installing. If that is unacceptable for you, you could even install the driver before anyone logs in; depending on your imaging method you could bake it into the image or deliver during OSD. Edit: basically what was posted above by @Duke5A but I didn’t read

Whilst you can use machine gpps to deliver printers per machine you need to use the user gpps to set a default printer. We use user GPPs with loop back processing and item level targeting so printers are delivered per machine not per user. Never had a printer disappear with this.

Mindhorn. Good silly fun. But then I laugh like a drain at anything with Julian Barrett in.

Welcome everyone. Don’t use my mug, it’s the plain white one with my face on the bottom.

Oh no how sad [emoji17]

Yeah you need to use the DesktopApplicationID attribute rather than DesktopApplicationLinkPath and use the Application ID. So if you run the Powershell command 'get-startapps' you can see all the Application IDs of all the start menu items. For URLs its actually just the URL itself. So I would expect the line you need is actually:

Yeah a few people have reported that here. Seems to be our older machines it happens on. Definitely gets worse the longer it’s open, affected users just reboot now.

Sccm + defender, does the job and peanuts via ovs-es

Well this morning was fun. -6 and my drive was an ice rink. Its on an incline as well that added to the fun. Ended up using a sledgehammer to break up as much ice as I could (it was ridiculously thick!) and covering the drive in cat litter to gain some traction.

VPN for us.

You’re a degree off being obtuse there. Or are you fishing or complements on that joke, you’re a right angler you are.