Re: How to remotely install software to clients?

then execute the install package on each client

Thanks for your tip but how do you "execute the install package on each
client"?





"Hapticz" <hapticz@xxxxxxxxxxxxx> wrote in message
news:%2332HPg$jGHA.4044@xxxxxxxxxxxxxxxxxxxxxxx
if you have administrator "permissions" and control of the network, the
other client units act like just another computer. they
only have a "name" that preceeeds their file directory name ( or simillar)

get a netwide summary of what clients are online, (vb can usually do this
as long as your network is properly setup)

then copy the install package to each.

then execute the install package on each client

systems may have extensive spy/virus/security ware running, so beware, as
you may be logged and traced in an instant.

you must check for enough disk space, then decide who can run what one
each client. ( there's tons to learn about
right/permissions/and other security baloney)

hava a look at some of the network help sites.

it isnt very difficult, thats why those other folks dont want people to
find out ;-))

most of what is job security, is how serpentine the individual IT folks do
to make everything seem "complicated" to protect their
"domains"

once you get root access or the admin passwords, you can wreak havoc or
create utopia. its your choice.........


"boaz" <nospam@xxxxxxxxx> wrote in message
news:us2ziXxjGHA.4584@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Those IT guys in the Server newsgroup are not helping. I know they pay
alot
of $$$$ to take the MSCE classes... but it is not like I am going to take
their job or anything like that...

So... my good CS fellows... Please help me out with this:


I have a bunch of workstations running Windows 98, 2000, and XP.
My server is running Windows NT.

Would you teach me how to install a software package to the workstations
remotely please?

Thanks!


--
There is no answer.
There has not been an answer.
There will not be an answer.
That IS the answer!
And I am screwed.
Deadline was due yesterday.

There is no point to life.
THAT IS THE POINT.
And we are screwed.
We will run out of oil soon.

http://spaces.msn.com/bzDaCat





.

Relevant Pages

  • Re: How to remotely install software to clients?
    ... the client user is aware that new stuff is going to show ... Thanks for your tip but how do you "execute the install package on each ... I have a bunch of workstations running Windows 98, 2000, and XP. ...
    (microsoft.public.vb.enterprise)
  • Re: How to remotely install software to clients?
    ... if you have administrator "permissions" and control of the network, the other client units act like just another computer. ... then copy the install package to each. ... I have a bunch of workstations running Windows 98, 2000, and XP. ...
    (microsoft.public.vb.enterprise)
  • Re: Stored procedure/trigger and scripts
    ... must have been the trigger that locked up the table. ... SQL Server has permissions to execute xp_cmdshell. ... >> client to change their password they have to call the "Client Relations" ...
    (microsoft.public.sqlserver.programming)
  • Re: Stored procedure/trigger and scripts
    ... I just ran some additional tests and it looks like my trigger is fine. ... SQL Server has permissions to execute xp_cmdshell. ... >> client to change their password they have to call the "Client Relations" ...
    (microsoft.public.sqlserver.programming)
  • Re: Stored procedure/trigger and scripts
    ... SQL Server has permissions to execute xp_cmdshell. ... Please read up on xp_cmdshell within Books Online (within the SQL Server program group). ... >> client to change their password they have to call the "Client Relations" ...
    (microsoft.public.sqlserver.programming)
Loading