Switches for Cmd files

  • Thread starter Thread starter Susie
  • Start date Start date
S

Susie

Hi
I am pushing an AT Scheduler job to use an administrator
account through the login script.
The script executes but the dialog box comes up that shows
where it's pointing to along with the admin user and
password.
I don't want want the information in the dialog box
displayed.
does anyone know what the switch would be to hide all the
information?
I have used /q
Thank you for your input!!
Susie
 
Susie said:
I am pushing an AT Scheduler job to use an administrator account through
the login script. The script executes but the dialog box comes up that
shows where it's pointing to along with the admin user and password. I
don't want want the information in the dialog box displayed. does anyone
know what the switch would be to hide all the information? I have used /q
Thank you for your input!!
Click to expand...

Hi Susie,

Read this first:

http://www.catb.org/~esr/faqs/smart-questions.html#goal

In other words, what precisely are you trying to accomplish? This may not
be the best way to do it.

HTH,

Bill
 
-----Original Message-----


Hi Susie,

Read this first:

http://www.catb.org/~esr/faqs/smart-questions.html#goal

In other words, what precisely are you trying to accomplish? This may not
be the best way to do it.

HTH,

Bill


.
Click to expand...
Hi Bill,
thanks for the link I will go to view that. What I am
trying to do is set the AT Scheduler to use the Admin acct
on every pc instead of the user. The purpose is for
application installs, updates etc that are written in
command files that reside on the network.
We have about 600 pc's or so over 7 different locations
and the band width would suffer badly if I just pushed out
to all users.
So there is a task that runs everyday in our login script
when users log in that looks to a file on the network.
When we need to push an update or install we change the
cmd file to look at the update we want to push.
There is also another file that has all the pc's names in
them next to the pc name we increment the time the task is
scheduled to run on the users pc. When that user time
arrives the install will take place.
I hope you can make sense of this..
Thanks Susie
 
See tip 8032 in the 'Tips & Tricks' at http://www.jsiinc.com


Hi Bill,
thanks for the link I will go to view that. What I am
trying to do is set the AT Scheduler to use the Admin acct
on every pc instead of the user. The purpose is for
application installs, updates etc that are written in
command files that reside on the network.
We have about 600 pc's or so over 7 different locations
and the band width would suffer badly if I just pushed out
to all users.
So there is a task that runs everyday in our login script
when users log in that looks to a file on the network.
When we need to push an update or install we change the
cmd file to look at the update we want to push.
There is also another file that has all the pc's names in
them next to the pc name we increment the time the task is
scheduled to run on the users pc. When that user time
arrives the install will take place.
I hope you can make sense of this..
Thanks Susie
Click to expand...


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
Susie said:
Hi
I am pushing an AT Scheduler job to use an administrator
account through the login script.
The script executes but the dialog box comes up that shows
where it's pointing to along with the admin user and
password.
I don't want want the information in the dialog box
displayed.
does anyone know what the switch would be to hide all the
information?
I have used /q
Thank you for your input!!
Susie
Click to expand...

If you use a startup script rather than a logon script,
it will run under the context of the local system account.
If you are accessing the network, you may need to put
the computer account into a group with permissions to the
share and files that need to be accessed. Or you could
loosen up permissions somehow to allow the local system
ID access.

--
Matt Hickman
Despite the crepehangers, romaniticists, and anti-intellectuals,
the world steadily grows better because the human mind, applying
itself to environment, makes it better.
Robert A. Heinlein (1907 - 1988)
_The Door Into Summer_ 1956
 
Are these machines in domain(s), or are they stand-alone machines?

If you use domains, group policy and startup-scripts are easy ways to
accomplish these management tasks.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
-----Original Message-----


Hi Susie,

Read this first:

http://www.catb.org/~esr/faqs/smart-questions.html#goal

In other words, what precisely are you trying to accomplish? This may not
be the best way to do it.

HTH,

Bill


.
Click to expand...
Hi Bill,
thanks for the link I will go to view that. What I am
trying to do is set the AT Scheduler to use the Admin acct
on every pc instead of the user. The purpose is for
application installs, updates etc that are written in
command files that reside on the network.
We have about 600 pc's or so over 7 different locations
and the band width would suffer badly if I just pushed out
to all users.
So there is a task that runs everyday in our login script
when users log in that looks to a file on the network.
When we need to push an update or install we change the
cmd file to look at the update we want to push.
There is also another file that has all the pc's names in
them next to the pc name we increment the time the task is
scheduled to run on the users pc. When that user time
arrives the install will take place.
I hope you can make sense of this..
Thanks Susie
 
Back
Top