![]() ![]() I'd try what u/mikeh361 mention and try Visio 2021, same versions, and see if you have the same results. On your Visio install, is it re-installing Office 2019? This is partially why I ended up with the pkg built that I have. Your Visio content is going to include the entire suite not just the Visio bits, so its applying those office bits with its Visio install and with them being different versions I can totally see this being an issue. I am not using VL so my input may not be relevant.Īlthough your situation is a bit different, my assumption here is your issue is with the different versions/channels here. All visio, project and server (shared licensing) are in one package using the same content and the deployment type dictates the relevant config to run. Reviewing my configs, the versions are specified in my config to help ensure that same content is to be used. I use the same content and simply run with a different config for the Visio installer. Thanks for any help - I dislike these CTR installers! Any pointers how I stop this? If I deploy this via mecm it's just going to fail or remove Office. The issue I am running into is that when we run the click-to-run installer for Visio it wants us to remove Office 2021. Download the offline installer from your account portal To download the offline installer, go to If you're not already signed in with the Microsoft account associated with your copy of Microsoft 365 or Microsoft 365 do that now. We are trying to deploy Office 2021 LTSC and Visio 2019. Perhaps a little bit out of the scope of this sub-reddit but I am wondering if you can point me in the right direction? As a general rule, if someone has flair, they almost definitely know what they're talking about. Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog. ![]() Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |