Pau Lo
asked on
group policy software deployment basics
I am trying to get a broad understanding of software deployment via group policy. Specifically deployment of Microsoft Office to end user devices in an AD environment (Windows 7/10 desktop & laptop computers).
I have tried to structure my query into a number of sub-questions.
1. I believe a limitation of using group policy for software deployment is the installers must have an msi extension, is this true or a myth? Is the installer for MS-Office in a corporate environment typically an MSI extension, or can it be anything?
2. Is it common to deploy apps like MS-Office using group policy, or are there other more common tools for the job? If so, what (SCCM)?
3. Is it common for standard software like MS-Office to be included in the standard build/image for user devices, e.g. if you get a new laptop, it already comes with MS-Office on it – cutting out the need for using group policy to deploy the software?
4. If its standard for MS-Office to be installed as part of the build process, for what reasons or scenarios would you need to deploy the MS-Office software via group policy?
5. How would the process work regarding the software installer itself and licence keys, e.g. where in the process would the process pick those files up and deploy to the remote PC?
6. Where are the installers typically 'stored' when using group policy for software deployment, and what would you refer to the installer repository as?
7. How does office licencing typically work in a corporate environment if say you have 500 devices you intend to apply Office to and you are attempting to do so via group policy? Presumably you don't have 500 unique installers with licence info pre-entered? Is it a case of a single licence key is valid for all 500 devices, and therefore you can somehow embed the licence key in the master installer? Or is the process a bit more involved than that?
8. If somebody found a master MSI file, for MS-Office, would that typically include a licence key that could be extracted? Or is it nothing more than an installer you could find online?
9. Is SCCM a more efficient way of deploying software than group policy, or are the two interconnected in some way, or are they two differing approaches to software deployment?
10. Is the MSI installer physically transferred onto the end user device, and if so is there a likely location to store it, or does the process simply require the machine runs the installer from this central location?
I have tried to structure my query into a number of sub-questions.
1. I believe a limitation of using group policy for software deployment is the installers must have an msi extension, is this true or a myth? Is the installer for MS-Office in a corporate environment typically an MSI extension, or can it be anything?
2. Is it common to deploy apps like MS-Office using group policy, or are there other more common tools for the job? If so, what (SCCM)?
3. Is it common for standard software like MS-Office to be included in the standard build/image for user devices, e.g. if you get a new laptop, it already comes with MS-Office on it – cutting out the need for using group policy to deploy the software?
4. If its standard for MS-Office to be installed as part of the build process, for what reasons or scenarios would you need to deploy the MS-Office software via group policy?
5. How would the process work regarding the software installer itself and licence keys, e.g. where in the process would the process pick those files up and deploy to the remote PC?
6. Where are the installers typically 'stored' when using group policy for software deployment, and what would you refer to the installer repository as?
7. How does office licencing typically work in a corporate environment if say you have 500 devices you intend to apply Office to and you are attempting to do so via group policy? Presumably you don't have 500 unique installers with licence info pre-entered? Is it a case of a single licence key is valid for all 500 devices, and therefore you can somehow embed the licence key in the master installer? Or is the process a bit more involved than that?
8. If somebody found a master MSI file, for MS-Office, would that typically include a licence key that could be extracted? Or is it nothing more than an installer you could find online?
9. Is SCCM a more efficient way of deploying software than group policy, or are the two interconnected in some way, or are they two differing approaches to software deployment?
10. Is the MSI installer physically transferred onto the end user device, and if so is there a likely location to store it, or does the process simply require the machine runs the installer from this central location?
Office setup can be started with the parameter /admin. That will bring up a configurator which creates a settings file that will allow unattended installation. It will work with your MAK key (multiple activation key of your volume licensing contract, which will let you activate all devices with the same key). It will let you uninstall previous versions as well. So all you need to do is deploy an immediate tasks to computer that is running as system account and it will upgrade all machines with a simple batch file. Office is not intended to be deployed using the classic MSI way anymore.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
About MSI deployment shares: sysvol used to be impossible on server 2003, see https://support.microsoft.com/en-us/help/889710/you-receive-a-this-installation-package-could-not-be-opened-error-mess (it could very well be that this stopped to apply on later OS').
https://docs.microsoft.com/en-us/sccm/apps/understand/introduction-to-application-management