Ah... Why can't it be done once in advance? How much storage are we talking about?
*ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…* On Wed, Aug 5, 2015 at 5:28 PM, J- P <[email protected]> wrote: > I know I CAN do it, the goal is to automate the process as I am only > there once a week. > > This needs to happen whenever a user (standard user) logs into the pc. > > > > ------------------------------ > From: [email protected] > To: [email protected] > Subject: RE: [NTSysADM] Adding files/folder to Program Files -options > Date: Wed, 5 Aug 2015 21:20:30 +0000 > > Do it from a server where you’re logged in as an account that has local > admin permissions on the target systems, and make your target UNC > \\workstation\c$\Program files\vectorworks > > > > Your elevated perms and the c$ is the magic here. > > > > You could even do it from your PC logged in as domain admin and have it > copy from \\server\cadfiles\.... To \\workstation\c$\Program > files\vectorworks. > > > > In my environments I have a dedicated “utlilty server” for just this kind > of thing, that way my local machine isn’t tied up for big file copies > (among many other reasons for having a utility machine/server). > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *J- P > *Sent:* Wednesday, August 05, 2015 2:06 PM > *To:* NT > *Subject:* RE: [NTSysADM] Adding files/folder to Program Files -options > > > > I must be dense because I'm totally missing this; > > Source files reside on \\server\cadfiles\.... > They MUST be placed on each workstation in C:\program > files\vectorworks\..... > > What method are you using to override the native security that prevents > files going into C:\Program files? > > This is to happen whenever a user logs into the CAD worksation > > > > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [NTSysADM] Adding files/folder to Program Files -options > Date: Wed, 5 Aug 2015 20:55:41 +0000 > > Funny, I do exactly this to public machines that are locked down as to not > allow browsing of the local drives. Easier to copy from an unrestricted > master machine to \\publicPC1\c$\<wherever> than logging in locally, > unlocking the settings, copying the file, then relocking the settings… > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Andrew S. Baker > *Sent:* Wednesday, August 05, 2015 1:29 PM > *To:* ntsysadm > *Subject:* Re: [NTSysADM] Adding files/folder to Program Files -options > > > > Copy it remotely, and you won't have to worry about the UAC requirements. > > > > > > > > > *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> > *Providing Virtual CIO Services (IT Operations & Information Security) for > the SMB market…* > > > > > > On Wed, Aug 5, 2015 at 4:14 PM, J- P <[email protected]> wrote: > > Hi all, > > Our CAD program (Vectorworks) uses libraries that have to placed under the > > C:\Program files\vectorworks2015 or C:\Program files (x86)\vectorworks2015\ > > directory. > > > Using a batch file fails due to the default security settings to the > Program Files directory, however, it can/will work if the batch file is > "run as administrator". (rather not do that if possible) > > Getting the vendor to change the software is not going to happen, can > someone advise or suggest a way to get this accomplished ? > > server 2008 / w7 pro workstations > > TIA > > > > Attention: Information contained in this message and or attachments is > intended only for the recipient(s) named above and may contain confidential > and or privileged material that is protected under State or Federal law. If > you are not the intended recipient, any disclosure, copying, distribution > or action taken on it is prohibited. If you believe you have received this > email in error, please contact the sender, delete this email and destroy > all copies. > Attention: Information contained in this message and or attachments is > intended only for the recipient(s) named above and may contain confidential > and or privileged material that is protected under State or Federal law. If > you are not the intended recipient, any disclosure, copying, distribution > or action taken on it is prohibited. If you believe you have received this > email in error, please contact the sender, delete this email and destroy > all copies. >
