Seems a sensible idea. Make the dbas use the binaries they are pushing for and ensure they can manage the install scripts but not their workstations and you're good to go. On 19 Oct 2010 19:42, "Kellyn Pedersen" <kjped1313@xxxxxxxxx> wrote: We have multiple workstation configuration/OS, so everything from XP, Vista, Windows 7 and even a few Linux and Mac... We are also using a mapped network drive with a everything configured to point to this one. No issues with any of the workstation configs, the client is installed on a NAS drive that everything but a few web servers and of course the database servers, use. I do not want to be responsible for a ton of misconfigured workstation installs, (just because somehow it would become a DBA problem.... LOL) Kellyn Pedersen Sr. Database Administrator http://www.linkedin.com/in/kellynpedersen www.dbakevlar.blogspot.com "Go away before I replace you with a very small and efficient shell script..." ------------------------------ *From:* Harel Safra <harel.safra@xxxxxxxxx> *To:* Mark.Brady@xxxxxxxxxxxxxxxxx *Cc:* "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx> *Sent:* Tue, October 19, 2010 12:36:52 PM *Subject:* Re: Network Installation of Client Binaries We're running about 600 PCs like that. The oracle client is installed on a mapped network drive and...