Anyone use "Sites and Services" to push software down instead of OUs?
Anyone use "Sites and Services" to push down software instead of OUs?
That's how we originally started which our consultant got it goin for us. So far it seems to work great as software gets pushed from the site the server is at. Now here's how we do it. We have a group for every software package. We have every software package on each server site. Each package has the approprite group of users to get the software.
Now here's where I have one of my questions. Say all Group Adobe users get the Adobe package on Site A server or Site B server depending which location they're in. Now I'm wondering if a laptop user in the Adobe group goes from Site A to Site B. If he has Adobe from Site A will he get Adobe pushed down a 2nd time from Site B? I know.. why not just test it. I will soon, but maybe an answer here will save me the time.
2nd question is. How do most of you all deploy packages from WAN environments?
Thanks for the info.
That's how we originally started which our consultant got it goin for us. So far it seems to work great as software gets pushed from the site the server is at. Now here's how we do it. We have a group for every software package. We have every software package on each server site. Each package has the approprite group of users to get the software.
Now here's where I have one of my questions. Say all Group Adobe users get the Adobe package on Site A server or Site B server depending which location they're in. Now I'm wondering if a laptop user in the Adobe group goes from Site A to Site B. If he has Adobe from Site A will he get Adobe pushed down a 2nd time from Site B? I know.. why not just test it. I will soon, but maybe an answer here will save me the time.
2nd question is. How do most of you all deploy packages from WAN environments?
Thanks for the info.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
rasmsn3
20 years ago
I have done some testing with this, not at the site level but moving from one policy to another at the OU level. Here is what will happen:
If you have Uninstall this application when it falls out of the scope of management checked in the properties of the package in group policy under the deployment tab it will uninstall the application and install the application when the new gpo at the different site is applied (Very time consuming).
If you do not have this checked it will start the install when you move to the next site but will realize it is already installed and skip the install, but you will see it try to install. After this I was able to uninstall the software with group policy which was my concern. I would still recommend some more testing but this is what I saw.
If you have Uninstall this application when it falls out of the scope of management checked in the properties of the package in group policy under the deployment tab it will uninstall the application and install the application when the new gpo at the different site is applied (Very time consuming).
If you do not have this checked it will start the install when you move to the next site but will realize it is already installed and skip the install, but you will see it try to install. After this I was able to uninstall the software with group policy which was my concern. I would still recommend some more testing but this is what I saw.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
