|
Caf posted:You can remove these junk links by simply disabling the "Microsoft Consumer Experience" either in Group Policy or setting the appropriate registry value. Collateral Damage posted:You can disable it without having to force a standard layout. Whoops guess I need to adjust some GPOs. Thanks. Guess I'll ask this too - Is anyone running an Azure Hybrid desktop environment? I got the process started and successfully joined a test laptops but found some of the things I was interested in (Azure encryption key enforcement/escrow, log on screen integrated self-service password reset) was not available in Hybrid joined devices. The annoying part is its not stated in the documentation. I found out by people complaining in the comments.
|
#
?
Mar 6, 2018 14:50
|
|
|
|
| # ? Apr 19, 2024 06:33 |
|
|
Half of the poo poo to use for disabling doesn’t work in Pro which pisses me right the gently caress off. I know that Consumer Experience you can set but I always have to manually do it in the GUI after the fact.
|
|
#
?
Mar 6, 2018 15:07
|
|
|
LTSB. I've bitched out on entertaining this horseshit on linked clone vdi. I'm rolling out a stateless vdi environment for a client that ought to make this easier, but seriously gently caress the cadence of these massive updates and their constant changing of which gpo fields actually do what from generation to generation.
|
|
#
?
Mar 6, 2018 17:51
|
|
|
Potato Salad posted:LTSB. LTSC means no Office Pro Plus support as of 1803 or something like that. So many people are licensing Office through O365 and MS doesn't want anyone on LTSC so they added this as a big fat LTSC Tax. LTSC isn't the answer, grilling the hell out of your TAM about the issues preventing the use of native servicing and dealing with the stupid in an upgrade TS until they get things sorted out seems to be the best strategy so far.
|
|
#
?
Mar 6, 2018 21:33
|
|
|
Zaepho posted:LTSC means no Office Pro Plus support as of 1803 or something like that. So many people are licensing Office through O365 and MS doesn't want anyone on LTSC so they added this as a big fat LTSC Tax. Just to confirm, you mean LTSB right? Unless LTSC is something I haven't heard of...
|
|
#
?
Mar 7, 2018 14:09
|
|
|
Beefstorm posted:Just to confirm, you mean LTSB right? Unless LTSC is something I haven't heard of... LTSC is the new LTSB. They are calling everything "channels" instead of "branches" now. And yes, our TAM mentioned the same thing about dropping Office ProPlus support on LTSC in a call we had last week specifically to poo poo on their servicing model. He said to keep it on the DL but it seems to be backed up by this very public blog post from last month so 
|
|
#
?
Mar 7, 2018 14:51
|
|
|
They are acting like a W10 update is as smooth as an Android update when that comparison couldn't be stupider. Microsoft's stance on updates is "well, we don't really know, poo poo might break so have backups ready"
|
|
#
?
Mar 7, 2018 15:55
|
|
|
By pro plus I assume you mean o365 installer. Why not just use the msi installer? I asked our softchoice rep how MS would feel or if we would get dinged for using the msi installer if we have o365 licenses and he' said MS just wants their customers to be happy (lol) it shouldn't be an issue. Obviously the bonus for pro plus is you won't have to upgrade to the next version of office but realistically if your using ltsc for 10 years, you should be okay with not upgrading the office version? I guess that's MS' take on it.
|
|
#
?
Mar 7, 2018 18:12
|
|
|
lol internet. posted:By pro plus I assume you mean o365 installer. Why not just use the msi installer? I asked our softchoice rep how MS would feel or if we would get dinged for using the msi installer if we have o365 licenses and he' said MS just wants their customers to be happy (lol) it shouldn't be an issue. There will be no MSI installer for Office 2019. It's all going click-to-run.
|
|
#
?
Mar 7, 2018 18:45
|
|
|
Caf posted:There will be no MSI installer for Office 2019. It's all going click-to-run. I am the Enterprise MS customer MS doesn't believe exists.
|
|
#
?
Mar 7, 2018 18:49
|
|
|
Yup. https://support.microsoft.com/en-us/help/4086137/office-2019-on-premises-release-details-february-1-2018
|
|
#
?
Mar 7, 2018 18:52
|
|
|
Caf posted:There will be no MSI installer for Office 2019. It's all going click-to-run. As long as these click to run packages just loving work. The entire point to the offline installer was so that a freshly imaged machine was ready for a person to sign in and launch the loving apps they wanted. If the user has to sign in and download a bunch of poo poo that needs instructions there entire premise is idiotic.
|
|
#
?
Mar 7, 2018 19:00
|
|
|
In my experience with click-to-run over the last few years it does handle imaging and updating after pretty well and you just get stuck in eval or read-only mode until you log in to it with a licensed ID. Seems ok.
|
|
#
?
Mar 7, 2018 19:08
|
|
|
Log into it how? With a Microsoft acct? Azure AD, which we don't have? We have machines on the shop floor that a half dozen different people log into.
|
|
#
?
Mar 7, 2018 19:26
|
|
|
In my case I log in with my internal AD creds and that is linked to our O365 instance which validates my license entitlement and allows the office suite to function. Our creds synchronize in the backend with AD sync. There's a number of ways to set it up and that was our route, talk to MS and figure out what makes the most sense for you.
|
|
#
?
Mar 7, 2018 19:31
|
|
|
That's with per-user licensing though through a subscription. If KMS per-device licenses are also moving to Click-to-Run then they need to not unlicense themselves after an upgrade.
|
|
#
?
Mar 7, 2018 19:40
|
|
|
We don't have O365. We have an Exchange 2016 DAG. We're not migrating for at least 3 years. Just signed our EA 2 months ago.
|
|
#
?
Mar 7, 2018 19:40
|
|
|
I've been creating .msi files for click-to-run Office 2016 installs for a while now https://www.microsoft.com/en-us/download/details.aspx?id=49117
|
|
#
?
Mar 7, 2018 21:12
|
|
|
Well then, fingers cross that's not depreciated for 2019.
|
|
#
?
Mar 7, 2018 21:17
|
|
|
GreenNight posted:Well then, fingers cross that's not depreciated for 2019.
|
|
#
?
Mar 7, 2018 21:23
|
|
|
I really don't know which thread to drop this in, but firefox is finally getting GPO support this year. I'm banking on more windows admins wanting a heads up than regular firefox users. https://bugzilla.mozilla.org/show_bug.cgi?id=1433136 **gods plan begins to play** incoherent fucked around with this message at 02:22 on Mar 8, 2018 |
|
#
?
Mar 8, 2018 01:34
|
|
|
About god drat time.
|
|
#
?
Mar 8, 2018 01:57
|
|
|
I don't loving believe it. I don't believe it.
|
|
#
?
Mar 8, 2018 06:39
|
|
|
incoherent posted:I really don't know which thread to drop this in, but firefox is finally getting GPO support this year. I'm banking on more windows admins wanting a heads up than regular firefox users. I can’t wait to see what way his is horribly broken
|
|
#
?
Mar 8, 2018 06:41
|
|
|
On the topic of horribly broken brower configurations. Does anyone know how to remove the god drat desktop icon for Google Chrome? I want to do this in a SCCM package. The "master_preferences" file actually doesn't work and it looks like it's not an option in the GPO. I read up about copying a FIRST_RUN file to a specific directory but it didn't seem to work (didn't double check to see if it was something wrong on my end.)
|
|
#
?
Mar 8, 2018 07:00
|
|
|
lol internet. posted:On the topic of horribly broken brower configurations. I just run a step after install to delete it.
|
|
#
?
Mar 8, 2018 10:33
|
|
|
Yeah, just delete it from Public/Desktop. There's a registry key you can delete to remove it from being pinned on the Taskbar ad well (IIRC).
|
|
#
?
Mar 8, 2018 15:59
|
|
|
Anybody doing Windows 10 / EM+S (Intune, Azure AD) and AutoPilot deployments yet?
|
|
#
?
Mar 8, 2018 21:55
|
|
|
Nope but I've got a customer interested in that so let us know how it goes 
|
|
#
?
Mar 8, 2018 22:12
|
|
|
I'm pretty much deploying it now as a pilot with about 20 users involved. The settings to get things working are scattered across loads of different places but Microsoft at least seem to be trying to bring it all together. The support is really good as well. My issues are with AutoPilot - the device just isn't picking up the fact that it's a corporate device that's been registered. It doesn't help that these are machines I'm having to click through the OOBE wizard, get the AutoPilot info with a PowerShell script, upload the CSV to the Windows Business portal and then do a reset on the device. However I swear I've had this working previously in a different tenant. I'm going to bring another test VM online in the next few days on the tenant that I think I had working to see if it still works - I might be trying to fix something that's a bug on Microsoft's end.
|
|
#
?
Mar 9, 2018 01:07
|
|
|
Edit: nevremind
|
|
#
?
Mar 14, 2018 04:23
|
|
|
Seeing rumors of this month loving up VMXNET3 drivers. Time to do some thorough testing before I release to nonprod today! https://www.reddit.com/r/sysadmin/comments/84cw3n/kb4088875kb4088878_and_vmxnet3/
|
|
#
?
Mar 14, 2018 15:35
|
|
|
gently caress.
|
|
#
?
Mar 14, 2018 15:44
|
|
|
We accidentally patched our test servers (all on VMware) E: scratch that, we did have problems on some 2008 servers FISHMANPET fucked around with this message at 19:21 on Mar 14, 2018 |
|
#
?
Mar 14, 2018 15:46
|
|
|
Thanks Ants posted:I'm pretty much deploying it now as a pilot with about 20 users involved. The settings to get things working are scattered across loads of different places but Microsoft at least seem to be trying to bring it all together. The support is really good as well. For anybody remotely interested in this, the problem wasn't a problem. Without any custom branding in place in your Azure AD tenant there is no way to tell that AutoPilot is working - the policies apply (skip EULA, run user as limited account etc.) but the sign-in page looks like it usually does so I was ditching out and getting frustrated for no reason. Even if you don't bother actually applying any customisations, simply having branding enabled is enough to give you a "Welcome to SH/SC Industries" page and confirm that it's functioning as expected. https://blogs.technet.microsoft.com/mniehaus/2017/12/22/windows-autopilot-azure-ad-branding/
|
|
#
?
Mar 14, 2018 19:14
|
|
|
I was just able to reproduce the patch issue for 2008r2 servers in our environment, so that poo poo got declined with prejudice.
|
|
#
?
Mar 14, 2018 19:25
|
|
|
e: nvm I guess that one was old
anthonypants fucked around with this message at 19:36 on Mar 14, 2018 |
|
#
?
Mar 14, 2018 19:34
|
|
|
The 4th post provided the fix https://support.microsoft.com/en-us/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-windows-server-2008-r2 Not world ending if you deployed the enterprise rollup and did the prep script or after and rebooted. Declining it won't help, your problem will come back next month.
|
|
#
?
Mar 15, 2018 00:48
|
|
|
incoherent posted:The 4th post provided the fix quote:Last Updated: Dec 6, 2017
|
|
#
?
Mar 15, 2018 02:01
|
|
|
|
| # ? Apr 19, 2024 06:33 |
|
|
It appears to be the same problem now as in that last patch, though it's not acknowledged in the current patch notes.
|
|
#
?
Mar 15, 2018 03:52
|
|