ReallyRotten
MIS
I'm curious to know if anyone has deployed IP communicator en masse? If so how did you deploy it to users who *likely* did not have admin rights on their machines? How were the user settings configured? (user or administrator?)
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Deploy IP communicator in a software package
- Thread starter ReallyRotten
- Start date
- Status
We have experience of pushing Jabber out en-masse and I don't expect IP Communicator being too different as I expect it is just an MSI file.
adding /quiet and /norestart switches makes the setup easier.
If you have SCCM it can be pushed out that way. I believe ours uses an account which has admin privileges on all machines.
We have also used a product called PDQ to push the software out. Again it uses a domain account which has local admin privileges on all machines.
PDQ is easier to use than SCCM and I don't think the licencing is too expensive. It is licenced by the number of concurrent sessions in the Admin tool.
adding /quiet and /norestart switches makes the setup easier.
If you have SCCM it can be pushed out that way. I believe ours uses an account which has admin privileges on all machines.
We have also used a product called PDQ to push the software out. Again it uses a domain account which has local admin privileges on all machines.
PDQ is easier to use than SCCM and I don't think the licencing is too expensive. It is licenced by the number of concurrent sessions in the Admin tool.
- Status
Similar threads
- Question
- Locked
- Question
- Locked
- Question