From XP to Win7

[ScottCrowe]

Currently (XP 32-bit, WF4 M100), we use a fairly typical (I believe)approach for admin of ProE. Loadpoint is in Program Files, with .sup and company .pro in text directory. User .pro/.win located in "home" directory. Certain directories (notes/tables/formats/materials, etc...) are kept on network drive and pointed to. Some items such as company .pro and .sup are copied down to local text directory upon startup of PC via .bat file (generic .bat file which calls a .bat file on the network). I prefer this because I can adjust the .bat file on the network for all users. This has worked great for us thus far. Recently we were given a short amount of time to move to Win7. Not being an IT guy, I'm stuggling a bit with how to accomplish the admin friendly environment we had set up in XP.

With Win7, Program Files is not letting any files be copied in (??). Any time a .bat file is run from the network, the user must OK to continue. There is no C:\Documents and Settings\":User"\Start Menu\Startup directory to put the .bat file in.

So, the Program Files issue is easy enough - install to a different directory. I cannot find a Startup directory - so my thought is to incorporate the xcopy actions intoa .psf file. But this disables the ability to adjust what is being copied unless new .psf files are pushed to the users.

Any suggestions would be great. TIA

Scott

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[dgschaefer]

I'm using a very similar set up with Windows7 x64, but all of our batch
files are on the server. The start menu shortcut points directly to a
server based batch file. I do not get any OK prompts when running the
batch file. I don't think we made any changes in order to make that
work, but I'm not sure.

On the Program Files directory, it's simply a permissions issue. We had
the same issue with XP, frankly. All users need write permissions on
the Pro/E folders, at the very least the text folder.

Doug Schaefer

[JamesKerkstra]

Have you tried running your batch file as administrator (it's a hidden option on Windows 7 )? (right click on the batch and select run as administrator). If this fixes the issue then simply make a shortcut ot your batch on the users machinesand set it torun as administrator ( I don't remember how off hand ).

Also, C:\documents and settings\<username> is still on Windows 7 it is simply hidden but maps to the exact same location as C:\Users\<username>

Hope that helps,

In Reply to Scott Crowe:

Currently (XP 32-bit, WF4 M100), we use a fairly typical (I believe)approach for admin of ProE. Loadpoint is in Program Files, with .sup and company .pro in text directory. User .pro/.win located in "home" directory. Certain directories (notes/tables/formats/materials, etc...) are kept on network drive and pointed to. Some items such as company .pro and .sup are copied down to local text directory upon startup of PC via .bat file (generic .bat file which calls a .bat file on the network). I prefer this because I can adjust the .bat file on the network for all users. This has worked great for us thus far. Recently we were given a short amount of time to move to Win7. Not being an IT guy, I'm stuggling a bit with how to accomplish the admin friendly environment we had set up in XP.

With Win7, Program Files is not letting any files be copied in (??). Any time a .bat file is run from the network, the user must OK to continue. There is no C:\Documents and Settings\":User"\Start Menu\Startup directory to put the .bat file in.

So, the Program Files issue is easy enough - install to a different directory. I cannot find a Startup directory - so my thought is to incorporate the xcopy actions intoa .psf file. But this disables the ability to adjust what is being copied unless new .psf files are pushed to the users.

Any suggestions would be great. TIA

Scott