mattfarnell

I tested a local source this evening on a test pc at work and still got the same result of 30 min. I did the setup.exe /configure configuration. <Configuration ID="f35def0d-bd75-4e4c-bc0d-268ea24671eb"> <Info Description="" /> <Add OfficeClientEdition="64" Channel="Current" SourcePath="\\server\repository$\Microsoft office 365 2026 local source" AllowCdnFallback="TRUE"> <Product ID="O365ProPlusRetail">. So does this test confirm that it isn't the web access?

This is my config but like i say i got 5 min from home so don't think its tha. <Configuration ID="57ca5aaa-3f77-449b-bfc9-1eb890c464a5"> <Info Description="" /> <Add OfficeClientEdition="64" Channel="Current"> <Product ID="O365ProPlusRetail"> <Language ID="en-gb" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="Outlook" /> </Product> </Add> <Property Name="SharedComputerLicensing" Value="1" /> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Property Name="DeviceBasedLicensing" Value="0" /> <Property Name="SCLCacheOverride" Value="0" /> <Updates Enabled="TRUE" /> <AppSettings> <Setup Name="Company" Value="##########" /> <User Key="software\microsoft\office\16.0\excel\options" Name="defaultformat" Value="51" Type="REG_DWORD" App="excel16" Id="L_SaveExcelfilesas" /> <User Key="software\microsoft\office\16.0\powerpoint\options" Name="defaultformat" Value="27" Type="REG_DWORD" App="ppt16" Id="L_SavePowerPointfilesas" /> <User Key="software\microsoft\office\16.0\word\options" Name="defaultformat" Value="" Type="REG_SZ" App="word16" Id="L_SaveWordfilesas" /> </AppSettings> <Display Level="None" AcceptEULA="TRUE" /> </Configuration>

I haven't configured any optimization or any local sources. I'll try a local source today and see how that goes. That will prove if its a web issue or a physical install issue.

We are deploying office 365 but having some speed issues. The installation is taking around 30-35 min. From current channel on the CDN Below is a list of what we've tried but so far not had any luck with fixing the issue. -We have rebuilt the config and checked there's no iffy lines of code in it. (used ODT). -We have tried multiple methods of deployment, mdt, pdq and just plain install via cmd. -I have spoken with another school in our cluster and they are getting installs sub 15 min, we checked our configs and firewall ports and they all match. -I took the installation off site and ran independently and i got an install in 5 min which points to an internal issue. -After this i tested with permissions, thinking it might be a user thing. Both local admins and Domain admins with full web access gave the 30 min result. Has anyone had experience like this before with office

i can only describe the state as loss of all policies and not actually useable. It does break windows when t does it. It broke the logon screen last time i did it. The laptop started up and gave me the standard wallpaper but nothing on it, so it removed all the settings but didn't restore defaults. Just had a look at the above, we block powershell and cmd so i'll have to have a play about with the computer policy to allow it through. It's a nice idea though. Basically like a GP result

i've just assigned it a license. it did have one however it wasn't a full one. Lots of components were unticked. I'll report back if it cures it. Thanks

Just checked and there's nothing pointing to that user directly. As a bit of a test, i built a clean environment no policies or scripts assigned to the device. I gave it a wallpaper and it worked as a normal user. I logged on as accountx and it removed it. almost like it's a user setting somewhere that says "Will not use policies". It's very odd.

im hoping, not. it has done a few updates and fingers crossed it didn't put them back 😬

Going through a lot of forums and noticed there's quite a few methods but nothing quite permanent without running scripts. I've managed to put together a guide on how i've managed to achieve a method that is permanent and doesn't run scripts for every user. Hope this helps someone else. · Obtain latest ISO · Mount the ISO · Open the mounted ISO · Copy the install.wim file from the sources folder (I copied it to E Drive) · Create a folder somewhere (I create E:\Mounted) · Open elevated Powershell · Run this command (Replace with the locations you have used) Mount-WindowsImage -ImagePath "E:\install.wim" -index 1 -Path "E:\Mounted" · Now the E:\Mounted folder will show a regular PC’s disk drive contents. From this you can run what ever commands you like and it will change the image. · Some of the ones I have removed: remove-appxprovisionedpackage -path e:\Mount -packagename Clipchamp.Clipchamp_3.0.10220.0_neutral_~_yxz26nhyzhsrt remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.BingNews_4.1.24002.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.BingSearch_2022.0.79.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.BingWeather_4.53.52892.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.GamingApp_2024.311.2341.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.GetHelp_10.2302.10601.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.MicrosoftOfficeHub_18.2308.1034.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.MicrosoftSolitaireCollection_4.19.3190.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.MicrosoftStickyNotes_4.6.2.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.OutlookForWindows_1.0.0.0_neutral__8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.PowerAutomateDesktop_11.2401.28.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.SecHealthUI_1000.26100.1.0_x64__8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.StorePurchaseApp_22312.1400.6.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.Todos_2.104.62421.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.Windows.DevHome_0.100.128.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.WindowsAlarms_2022.2312.2.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.WindowsFeedbackHub_2024.125.1522.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.Xbox.TCUI_1.23.28005.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.XboxGamingOverlay_2.624.1111.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.XboxIdentityProvider_12.110.15002.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.XboxSpeechToTextOverlay_1.97.17002.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.YourPhone_1.24012.105.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename Microsoft.ZuneMusic_11.2312.8.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename MicrosoftCorporationII.QuickAssist_2024.309.159.0_neutral_~_8wekyb3d8bbwe remove-appxprovisionedpackage -path e:\Mount -packagename MSTeams_1.0.0.0_x64__8wekyb3d8bbwe · If you want to view what’s in the image run: get-appxprovisionedpackage -path E:\Mounted | select PackageName · At the end, to “stitch” the image back up you need to reboot the machine that it is mounted on. This is because you need to make sure it’s not being used by anything. (If it is you end up back at square one) · Then run this command: Dismount-WindowsImage -Path "E:\Mounted" -Save Now the install.wim file will remove or add whatever you selected. Just import this into your MDT sequence.

We have been using intune for a while now but only for MDM stuff, not really main stream computers. As we are looking to expand i've been testing new policies and restrictions and the such. When i started looking at Intune, i was told under no circumstances do i log on with this account. (call it accountx for reference). The account is well known for stripping Intune policies of the device and leaves it in a state where it can only be fixed by autopilot reset. By accident last week, i logged on to a device as accountx and sure enough i've had to autopilot it just to make it work again. Is this something that someone may have set up or broken somewhere in Intune? It's the only account known on our network to do this. A sensible person would disable or not use that account however it's one of our "special" accounts so can't really do that. Any help would be much appreciated

Jumping back to this thread, i now think there is a bigger issue at play. ATM we are using windows 10 and 11 images. So office is installed by a prebuilt application (as all the guides show) and deploys in windows 10. Today i've added that application to the same place in the windows 11 TS and imaged a pc and it doesn't work. the CMD flashes up for a second or 2 then disappears. It then continues the TS.

hi, thanks for this. after a bit of tweaking and fiddling, it's started to install in the TS now

It doesn't show a run as in application install tasks, but i notice you are using a run command task. Do they run better from that than the app install task?

this is my TS

i'm testing it on a vm so i can log in directly but it appears like it's in a remote session. (Asks me if i want to disconnect the user). Just whilst i've been posting this, i moved the papercut application to another server and tried installing it with remote files rather than on MDT and it installed. So it's interesting it won't install from the mdt server but will another, and office does work from the usual deployment share