Out of curiosity, what exactly is running at machine startup (and why can't you control it)? Or are you confusing startup with logon? Startup and logon are two distinct events, despite their close timing.
On Mon, Aug 31, 2009 at 10:18 AM, tony patton < tony.pat...@quinn-insurance.com> wrote: > The reasoning for not using GPO's is the amount of things that are already > running on machine startup, no control over this. > > Machine shutdown GPO is an option. > > -sc, the reason I mentioned logging, or lack thereof, is that we're pushing > for a proper patch management/deployment system, there is supposedly a > project kicking off over the next few months for this. I can log by > scripting it, that's not a problem, but we don't want a PSEXEC deployment > solution to do everything we need. > We only need it in the interim, we don't want it as a long term solution. > > To use PSEXEC long-term would be a full-time job, and we have enough to do > at the minute. > > Regards > > Tony Patton > Desktop Operations Cavan > Ext 8078 > Direct Dial 049 435 2878 > email: tony.pat...@quinn-insurance.com > > > From: "Sam Cayze" <sam.ca...@rollouts.com> To: "NT System Admin Issues" > <ntsysadmin@lyris.sunbelt-software.com> Date: 31/08/2009 13:35 Subject: RE: > [On-Topic] Patching with PSEXEC > ------------------------------ > > > > +1 > > I just use psexec for the random one-off tasks. > > Sam > > ------------------------------ > *From:* Kennedy, Jim > [mailto:kennedy...@elyriaschools.org<kennedy...@elyriaschools.org> > ] * > Sent:* Monday, August 31, 2009 6:57 AM * > To:* NT System Admin Issues > * > Subject:* RE: [On-Topic] Patching with PSEXEC > > > Ok, I am going off in a completely different direction. I did not see the > part where you talked to others about PSEXEC so I don’t know why you are > going in that direction. > > Why not just script it to the machines via GPO. If it is a machine policy > the install/update will run with elevated privs so you will not have any > trouble. You can get a run down on almost any app at this site, as far as > what switches and what package to use to get them deployed. > > *http://www.appdeploy.com/* <http://www.appdeploy.com/> > > Your script can log the ip/machine name as it deploys….. > > > *From:* tony patton > [mailto:tony.pat...@quinn-insurance.com<tony.pat...@quinn-insurance.com>] > * > Sent:* Monday, August 31, 2009 5:59 AM* > To:* NT System Admin Issues* > Subject:* [On-Topic] Patching with PSEXEC > > Hey all, > > Following on from IE8 doesn't work thread, management here wants start > using PSEXEC to patch applications. > > I'm a bit hesitant to use it for patching 2800 desktops for Adobe reader, > flash, firefox and UltraVNC, fine for running scripts and such, just not > sure about patching. > > Logging is a whole other thing, personally, I don't want to be able to log > which machines were successful, failed or not on > as there would be no incentive to get a proper patching solution. > I can wrap a batch file around it to re-direct output to a file, so the > possibility of logging is there. > > What are the pitfalls that any of you that use this approach have come > across? > > Also thanks to Sam Cayze for the PSEXEC command for Adobe, hadn't attempted > to work out the command for Flash but this does it, saved me a bit of work > :-) > > Slightly off-topic, don't know why anyone would want to leave this list, > keeps me sane most days. > > Sorry if this is a bit all over the place, 11am and been here before 7 :-( > All information greatly appreciated. > > Regards > > Tony Patton > Desktop Operations Cavan > Ext 8078 > Direct Dial 049 435 2878 > email: tony.pat...@quinn-insurance.com > ==================================================================== > http://www.quinn-insurance.com > > This e-mail is intended only for the addressee named above. The contents > should not be copied nor disclosed to any other person. Any views or > opinions expressed are solely those of the sender and > do not necessarily represent those of QUINN-Insurance, unless otherwise > specifically stated . As internet communications are not secure, > QUINN-Insurance is not responsible for the contents of this message nor > responsible for any change made to this message after it was sent by the > original sender. Although virus scanning is used on all inbound and > outbound e-mail, we advise you to carry out your own virus check before > opening any attachment. We cannot accept liability for any damage sustained > as a result of any software viruses. > > ==================================================================== > > QUINN-Life Direct Limited is regulated by the Financial Regulator. > QUINN-Insurance Limited is regulated by the Financial Regulator and > regulated by the Financial Services Authority for the conduct of UK > business. > > ==================================================================== > > QUINN-Life Direct Limited is registered in Ireland, registration number > 292374 and is a private company limited by shares. > QUINN-Insurance Limited is registered in Ireland, registration number > 240768 and is a private company limited by shares. > Both companies have their head office at Dublin Road, Cavan, Co. Cavan. > > > > > > > > > > > ====================================================================http://www.quinn-insurance.com > > This e-mail is intended only for the addressee named above. The contents > should not be copied nor disclosed to any other person. Any views or > opinions expressed are solely those of the sender and > do not necessarily represent those of QUINN-Insurance, unless otherwise > specifically stated . As internet communications are not secure, > QUINN-Insurance is not responsible for the contents of this message nor > responsible for any change made to this message after it was sent by the > original sender. Although virus scanning is used on all inbound and > outbound e-mail, we advise you to carry out your own virus check before > opening any attachment. We cannot accept liability for any damage sustained > as a result of any software viruses. > > ==================================================================== > > QUINN-Life Direct Limited is regulated by the Financial Regulator. > QUINN-Insurance Limited is regulated by the Financial Regulator and > regulated by the Financial Services Authority for the conduct of UK > business. > > ==================================================================== > > QUINN-Life Direct Limited is registered in Ireland, registration number > 292374 and is a private company limited by shares. > QUINN-Insurance Limited is registered in Ireland, registration number > 240768 and is a private company limited by shares. > Both companies have their head office at Dublin Road, Cavan, Co. Cavan. > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
