Is it already Monday? The weekend felt like it went by faster than usual. Snap! NHS 111 outage, Win10 22H2, bartending robots, Who, Me, & more Spiceworks Originals.I will be honest, I have considered the idea of company making faulty gea. I wanted to bring this up as a discussion because its something I haven't really thought about for a while until I saw a recent tweet/article. Is planned obsolescence a growing issue? Best Practices & General IT.Hi all,I have a user whose mailbox is used for sending customer invoices, so their sent items folder fills up every few months because of attached PDF's.I can't seem to find any way to create the rule where this user is the sender and the rule is to kick. Sent items rules, how to? Collaboration.I have a feeling that MS will push for it, but will have no choice other than to keep the 'legacy' option (what we do now) available for a long, long time. MS does want to go that way, which is what he was saying. The assumprtion that everybody has access to fast, cheap and reliable internet connectivity. It's been something that's bugged me for quite some time from MS and others. They rely on cloud for email, but no way for things like provisioning. I can move them to a blistering 20/20 on a fiber connection, but that's $1K/month and a $25K build fee. One of my yards has a 5/1 DSL connection that is down 5-10% of the time. By the nature of our business, we have to be outside metropolitan areas. Cloud is cool and all, but simply not feasible for a lot, if not the majority of customers. Since I'm the OP, I guess I can veer the thread somewhere else :).Ĭhris, you are wrong. I think the future is with the cloud and Azure to provision users and their devices versus reimaging of them. I know that 7 Pro (no matter the license type) is listed the same way in WSUS and there is only one update KB for any 7 Pro. Just look in your WSUS console before you sync it and you'll see the old update names and not the new ones. There is difference in the code between Pro and Pro VL though.Ĭan you show some proof of this? VL / OEM / Retail have, in the past, always been the same thing using the same updates.
Why should MS suddenly start labeling the updates differently based on the license type? They are all the same programs and all get the same updates. There is no difference in the code between 10 Pro retail / OEM / VL. And they are labeling Windows 10 Pro as Consumer and also as Business. The problem is that MS is now calling Windows 10 Pro a Consumer product. Just was hard to tell them apart because they had the same name. There already were two different updates. What is the actual problem being complained about?
0 kommentar(er)
