In my current job I work with SCCM, but it seems that GPP may be a faster and more versatile not to mention more reliable tool. Any one tried to use it as sole deployment alternative? and how big an organisation can it support? Is there any strategies?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Have you ever heard any of your users complain about the time it takes for them to get to their Desktop after logging in? If you go the GP deployment route, you will be adding even more time to that.

I've worked at 2 sites where GP was used for deployment. Both have now switched to SCCM but maintain the flexibility of GP by creating collections using AD groups (forcing a new AD discovery, to bypass the once-per-day default)
Answered 11/26/2010 by: VBScab
Red Belt

Please log in to comment
0
Well yes I can understand that. But there is also the possibility of advertising MSI instead of directly installing them (If I understand correctly), and with GPP you are not stuck with only MSI´s. and you can easily build complex collections. It will be intersting to see if some kind of deployment strategy is developed baed on that.
Answered 11/26/2010 by: admaai
Orange Senior Belt

Please log in to comment
0
I thought it was the other way around, with SCCM you can deploy any form of setups...?
Answered 11/26/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
Kind of...

Doing things the "proper" GP way, you have to use MSIs/MSTs. To work around that, many sites used lashed-up log-on and/or start-up scripts.

As you say, SCCM has no such restrictions.

@OP, trust me: if you switch to GP, make sure your IT Dept is prepared for posses of disgruntled users bearing down on the Service Desk personnel with flaming torches and pitchforks...
Answered 11/26/2010 by: VBScab
Red Belt

Please log in to comment
0
We are not going to switch, It´s just that the new feature seems very interesting. A bit confusion here may be, I am referring to Group Policy Prefrences, with that you can build collections of almost anything to target.
Answered 11/26/2010 by: admaai
Orange Senior Belt

Please log in to comment
0
Are you saying users complain because of the software installing taking place?


Or are users complaining because the log in is slow overall? The reason I ask is that is my only option and if it is slow period for Windows 7 I am backing off. Though I found the installs to be very fast at log for my test box.

Thanks.

ORIGINAL: VBScab

Kind of...

Doing things the "proper" GP way, you have to use MSIs/MSTs. To work around that, many sites used lashed-up log-on and/or start-up scripts.

As you say, SCCM has no such restrictions.

@OP, trust me: if you switch to GP, make sure your IT Dept is prepared for posses of disgruntled users bearing down on the Service Desk personnel with flaming torches and pitchforks...
Answered 03/07/2011 by: aahmad
Senior Yellow Belt

Please log in to comment
0
My findings are if you do not want it to be slow then do not utilize user based policies (unless you publish). My initial software package deployment through policies take 9 minutes after that log in is a breeze for users.
Answered 03/18/2011 by: aahmad
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity