Re: RE: RE: Patch management, revisited

2011-02-07 Thread Tom Miller
es. The only way we finally got a > whole lot >> of this to finally work was thru our TAM and whatever that support > team is >> called. They spent days at our site trying to get it to work. >> >> >> >> I would hope most sites aren't as fundamental

Re: RE: RE: Patch management, revisited

2011-02-07 Thread Jonathan
tations to > communicate with the server. > > Then I’d start trying to deploy the secondary sites. > > From: Jonathan [mailto:ncm...@gmail.com] > Sent: Saturday, February 05, 2011 7:54 AM > To: NT System Admin Issues > Subject: Re: RE: Patch management, revisited > > Ray - you

RE: RE: Patch management, revisited

2011-02-07 Thread Tom Miller
e secondary sites. From: Jonathan [mailto:ncm...@gmail.com] Sent: Saturday, February 05, 2011 7:54 AM To: NT System Admin Issues Subject: Re: RE: Patch management, revisited Ray - you make a good point. We're covering 13 locations across the US, with varying WAN connectivity. A

RE: RE: Patch management, revisited

2011-02-05 Thread Ray
e seems to be endless variations on how, and how often, you want the workstations to communicate with the server. Then I'd start trying to deploy the secondary sites. From: Jonathan [mailto:ncm...@gmail.com] Sent: Saturday, February 05, 2011 7:54 AM To: NT System Admin Issues Subj

Re: RE: Patch management, revisited

2011-02-05 Thread Jonathan
ing amount of power. > > > > > > From: Michael B. Smith [mailto:mich...@smithcons.com] > Sent: Friday, February 04, 2011 11:50 AM > To: NT System Admin Issues > Subject: RE: Patch management, revisited > > > > If you don't do third party patches, SCCM is _alm

RE: Patch management, revisited

2011-02-05 Thread Ray
M To: NT System Admin Issues Subject: RE: Patch management, revisited If you don't do third party patches, SCCM is _almost_ exactly like WSUS. It is based on the WSUS engine as a matter of fact, and you have to install WSUS on the Software Update Point. J Doing the SCCM installation can

RE: RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
uary 04, 2011 4:50 PM To: NT System Admin Issues Subject: RE: RE: Patch management, revisited Do you ever run into any problems with SCCM clients where folks have done supernetting of AD Sites? Our SSCM guys are scared of it because they were told it could be problematic but we're tired

RE: RE: Patch management, revisited

2011-02-04 Thread Free, Bob
ichael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, February 04, 2011 11:46 AM To: NT System Admin Issues Subject: RE: RE: Patch management, revisited So, I wouldn't do anything without a few hours of discovery. But if you are just going to use it for patch management, say three days (worst

RE: Patch management, revisited

2011-02-04 Thread Rod Trent
.aspx WakeUp eliminates close to 99% of client health issues. From: Malcolm Reitz [mailto:malcolm.re...@live.com] Sent: Friday, February 04, 2011 4:32 PM To: NT System Admin Issues Subject: RE: Patch management, revisited You are being too kind J That said, once up, the

RE: Patch management, revisited

2011-02-04 Thread Malcolm Reitz
Subject: RE: Patch management, revisited You teach SCCM classes? Good to know, because I can't even get it to install - it dies at "Setup failed to install SMS provider:" error which IIRC means I need to do some setspn thing. Dave From: Michael B. Smith [mailto:mich...@smith

RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
And there ya go. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Rod Trent [mailto:rodtr...@myitforum.com] Sent: Friday, February 04, 2011 3:53 PM To: NT System Admin Issues Subject: RE: Patch management, revisited http://social.technet.microsoft.com

RE: Patch management, revisited

2011-02-04 Thread David Lum
M and upgrade our old SMS environment. Dave From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, February 04, 2011 12:40 PM To: NT System Admin Issues Subject: RE: Patch management, revisited Like I said - it can be a little finicky to install. :) Regards, Michael B. Smith Consultan

RE: Patch management, revisited

2011-02-04 Thread Rod Trent
http://social.technet.microsoft.com/forums/en-US/configmgrsetup/thread/d06a6 b81-68d0-466a-8382-ceb7fb0bb8c3/ From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, February 04, 2011 3:40 PM To: NT System Admin Issues Subject: RE: Patch management, revisited Like I said - it

RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
Like I said - it can be a little finicky to install. :) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: David Lum [mailto:david@nwea.org] Sent: Friday, February 04, 2011 3:32 PM To: NT System Admin Issues Subject: RE: Patch management, revisited

RE: Patch management, revisited

2011-02-04 Thread David Lum
ithcons.com]> Sent: Friday, February 04, 2011 10:50 AM To: NT System Admin Issues Subject: RE: Patch management, revisited If you don't do third party patches, SCCM is _almost_ exactly like WSUS. It is based on the WSUS engine as a matter of fact, and you have to install WSUS on the Softwa

RE: RE: Patch management, revisited

2011-02-04 Thread Kennedy, Jim
Sent: Friday, February 04, 2011 2:43 PM To: NT System Admin Issues Subject: RE: RE: Patch management, revisited Sure. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan [mailto:ncm...@gmail.com] Sent: Friday, February 04, 2011 2:40 PM To: NT S

RE: RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
ael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan [mailto:ncm...@gmail.com] Sent: Friday, February 04, 2011 2:36 PM To: NT System Admin Issues Subject: Re: RE: Patch management, revisited "SCCM works very well if you have the time and staff to dedicat

RE: RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
Sure. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan [mailto:ncm...@gmail.com] Sent: Friday, February 04, 2011 2:40 PM To: NT System Admin Issues Subject: Re: RE: Patch management, revisited Also, if we wanted to start with WSUS and then

Re: RE: Patch management, revisited

2011-02-04 Thread Jonathan
Also, if we wanted to start with WSUS and then migrate to SCCM down the road, is that realistically feasible? Jonathan - Thumb typed from my HTC Droid Incredible (and yes, it really is) on the Verizon network. On Feb 4, 2011 2:36 PM, "Jonathan" wrote: > "SCCM works very well if you have the time

Re: RE: Patch management, revisited

2011-02-04 Thread Jonathan
"SCCM works very well if you have the time and staff to dedicate to it. I have about 1,000 PCs/ laptops here and tried SCCM, but never had the time to dedicate to it. And it was a real a pain to manage when you have limited time. But, it can be a great product and has flexibility. I wasn't willing

RE: Patch management, revisited

2011-02-04 Thread Rod Trent
, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tom Miller [mailto:tmil...@hnncsb.org] Sent: Friday, February 04, 2011 1:58 PM To: NT System Admin Issues Subject: Re: Patch management, revisited SCCM works very well if you have the time and staff to d

RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
Not correcting - just clarifying. :) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tom Miller [mailto:tmil...@hnncsb.org] Sent: Friday, February 04, 2011 2:11 PM To: NT System Admin Issues Subject: RE: Patch management, revisited I stand corrected

RE: RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
riday, February 04, 2011 2:08 PM To: NT System Admin Issues Subject: Re: RE: Patch management, revisited how does sccm handle clients that are not joined to active directory? Jonathan - Thumb typed from my HTC Droid Incredible (and yes, it really is) on the Verizon network. On Feb 4, 2011 2:02 PM, &qu

RE: Patch management, revisited

2011-02-04 Thread Tom Miller
Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tom Miller [mailto:tmil...@hnncsb.org] Sent: Friday, February 04, 2011 1:58 PM To: NT System Admin Issues Subject: Re: Patch management, revisited SCCM works very well if you have the time and staff to dedicate to it. I

Re: RE: Patch management, revisited

2011-02-04 Thread Jonathan
y can also be any PC (workstation) or server with an agent. > Regards, > > Michael B. Smith > Consultant and Exchange MVP > http://TheEssentialExchange.com > > From: Tom Miller [mailto:tmil...@hnncsb.org] > Sent: Friday, February 04, 2011 1:58 PM > To: NT System Admi

RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
System Admin Issues Subject: Re: Patch management, revisited SCCM works very well if you have the time and staff to dedicate to it. I have about 1,000 PCs/laptops here and tried SCCM, but never had the time to dedicate to it. And it was a real a pain to manage when you have limited time. But

Re: Patch management, revisited

2011-02-04 Thread Tom Miller
SCCM works very well if you have the time and staff to dedicate to it. I have about 1,000 PCs/laptops here and tried SCCM, but never had the time to dedicate to it. And it was a real a pain to manage when you have limited time. But, it can be a great product and has flexibility. I wasn't wil

RE: Patch management, revisited

2011-02-04 Thread Rod Trent
Just my opinion, but based on your requirements, SCCM is still the leading candidate - and I have experience with all of them. KACE may come close, IF the number of end-points is closer to 700 than 2000. One of the HUGE factors that you need to also consider is the amount of support you will g

RE: Patch management, revisited

2011-02-04 Thread Michael B. Smith
If you don't do third party patches, SCCM is _almost_ exactly like WSUS. It is based on the WSUS engine as a matter of fact, and you have to install WSUS on the Software Update Point. :) Doing the SCCM installation can be a little finicky; but once you set it up - it just RUNS. The challenge w