- #Install project office 365 install#
- #Install project office 365 mod#
#Install project office 365 install#
Examples: 5 will install Office 365 with no access + Visio, 17 will install Office 365 Vanilla with project and visio. The profile is selected in the UDI Wizard and set an OSD Variable once the script kick's in it will generate the xml file from scratch for that installation. During OSD only the script that generates the configuration is used. I have 2 powershell scripts that decide (depending on the situation) what to install, the first one will check if the user has any pre-determined Office (MSI based installation) and the 2nd one will generate the configuration.xml to be used for installation. That said, I will look all suggestions below to improve the deployment going forward. We can then authorize that for users on request. It seems perfectly logical to create a separate packages with just visio and project only, considering I already have the project package finished, I can just change the detection method for a quick win. I should explain a little why i'm looking at Cam's answer, in my view it's the historical route of deploying separate apps in SCCM, this might not be current or right, but I'm under time pressure (aren't we all) to get a test deployment together, so I'm sticking to what I know. Many options here and saved me a lot of headache. I'll have a read through the links provided, but I do like Cam_Cam_Cam_Cam's answer to be honest, I wanted to avoid installing project for all users when we're only at around 10 users who need it, 
You wonderful helpful people, this answers my question - Thank you. 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.
#Install project office 365 mod#
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 kommentar(er)
