Re: Deleting Scheduled Tasks across the Enterprise using SMS 2003

RicNagy wrote:
Garth, Kim

Created a bat called NightlyRebootTaskDel.bat

In it I have:

Start C:\WINNT\System32\cmd.exe
AT /delete /yes
Exit

When I double click it...it runs and gets rid of the scheduled tasks, however command prompt remains open.


"Garth" wrote:

There is no need for an MSI, you can create a package/program with the commandline only, but if you like you can put it into a batch file.

"RicNagy" <RicNagy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:80BB5CBC-094A-42B7-A5AA-3801D0588938@xxxxxxxxxxxxxxxx
Kim I have another question. Instead of building this into a package.
Could I build either a logon script or a .bat file that SMS could call that
would run the

AT /delete /yes from a cmd prompt.

With a .bat my hope would be to run it against a collection and still not
have to install anything on a workstation whereas with a MSI you still are
technically going to install something that has to be removed from ARP.


"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

RicNagy wrote:
Hello,

I have a question. A while back before I was here, there was an MSI
created. This MSI was distributed via Active Directory and GPO. The purpose
of the MSI was to force nightly reboots of workstations. The only thing that
was built into the MSI was a custom action:

AT.exe 23:59 /interactive /every:M,T,W,TH,F,S,SU cmd.exe /c
c:\winnt\tools\shutdown.exe /R /t:3600

This created a scheduled task on every workstation to reboot them at night.
We no longer need this because we are migrating to SMS 2003.

I tested the uninstall of the MSI using add/remove programs. The program did
uninstall however it did not delete the scheduled task. In fact upon
conclusion of the unininstall it created a second task.

What we would like to do is create collections in SMS 2003. Disable the GPO
for this MSI hence removing the so called program. Then using the created
collections in conjunction with the AT command remove the scheduled tasks.

Now I know the at command would normally would be

AT \\computername /delete /yes and that would delete all scheduled tasks

However my question is how to run this against the collections we create ins
SMS.

you just create a package, add a program with the command line, at
/delete /yes
You don't need \\computername since it runs locally anyway.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

as Garth said there is no need to run this in a batch file.
Just use the at command as the commandline of your package.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
.

Relevant Pages

  • Re: Deleting Scheduled Tasks across the Enterprise using SMS 2003
    ... however command prompt remains open. ... > have to install anything on a workstation whereas with a MSI you still> are ... >>> We no longer need this because we are migrating to SMS 2003. ... >>> uninstall however it did not delete the scheduled task. ...
    (microsoft.public.sms.admin)
  • RE: msi deploys but wont install
    ... It is only from the sms side they issue deploying it ... When running the command from the dos prompt it works with all the switches ... is the MSI that is the problem, ... per-user MSI install is something to be avoided like the plague. ...
    (microsoft.public.sms.swdist)
  • RE: msi deploys but wont install
    ... Note that running the install from the command line is not the same as ... At this moment you can check if it would work via Sms. ... When running the command from the dos prompt it works with all the switches ... is the MSI that is the problem, ...
    (microsoft.public.sms.swdist)
  • Re: Deleting Scheduled Tasks across the Enterprise using SMS 2003
    ... There is no need for an MSI, you can create a package/program with the commandline only, but if you like you can put it into a batch file. ... > We no longer need this because we are migrating to SMS 2003. ... > collections in conjunction with the AT command remove the scheduled> tasks. ...
    (microsoft.public.sms.admin)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I ... first time start up issues if the computer reboots after install) ... attempt at the command line from SCCM didn't. ... What if you manually uninstall Office 2003 then try running SMS ...
    (microsoft.public.sms.admin)