[SPAM] RE: Windows 7 Professional

[clay at andycomputer.com]

When I setup filepro on our new server with 2k8 I setup a raid array as a data drive filepro is installed in the standard directorys (f:\filepro and f:\fp) and there is a LanPub(f:\lanpub) directory that is shared and mapped as a drive letter for clients to share files. I made a batch file that is called by the telnet server and that file keeps users in filepro when they telnet to the server if they exit filepro the telnet connection is broken. The printers are called by unc names the only drawback is you can only have a limited amount of printers for all users but this keeps the filepro files from being accessed by the users directly. The client had suspisions that previous employees had copied the filepro data and program files to cd and sharing the data with rivals so this keeps users from accessing files unless they have access to the server console and there is only 3 users including me that have console access.  Doesn't keep users from printing the data to take out of the office but its a lot easier to catch someone walking out of the office with 500 printed pages then a flash drive or CD.  The client states filepro runs much faster since the server upgrade and its a lot easier to just make sure there is a telnet icon on their desktop with the logon script then having the logon script copy the filepro program to each users pc and the batch file and make sure the data folder was mapped to a drive each login. So it has made the logon process faster as well. 

Clay
Sent from my BlackBerry Smartphone provided by Alltel

-----Original Message-----
From: "Richard Kreiss" <rkreiss at gccconsulting.net>
Sender: filepro-list-bounces+clay=andycomputer.com at lists.celestial.com
Date: Tue, 28 Sep 2010 13:28:27 
To: 'George Simon'<GSimon at americanriverintl.com>; 'Kenneth Brody'<kenbrody at spamcop.net>
Reply-To: rkreiss at gccconsulting.net
Cc: 'filePro Mailing List'<filepro-list at lists.celestial.com>
Subject: [SPAM] RE: Windows 7 Professional

Are you logged in as an administrator?

As is often said, because one can do something, doesn't make it right.

Although my laptop is just for my use, and I do the no no of logging in with
admin privileges, filePro is installed as c:\appl.  When installing filePro
on a server, even on a drive other than c:\. I always place everything in
its on folder(directory) and then map the workstations to the drive\folder
with a drive letter.  

On my own system, the filepro executables are on drive mapped as t:\fp56 and
filepro is on a separate drive \programs mapped as W:\

I use a similar setup for each of my clients.  I have found that using drive
letters rather the unc runs the application much faster.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net
  





> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of George Simon
> Sent: Tuesday, September 28, 2010 1:10 PM
> To: Kenneth Brody
> Cc: filePro Mailing List
> Subject: RE: Windows 7 Professional
> 
> I just created an fp.bat file in the root directory.
> I can run the fp batch file and start filePro.
> I don't need the FPPATH file because I can set PFDSK, PFDATA,
> PFPROG,PFDIR, PFMENU, etc., in the batch file.
> You can't do this?
> 
> George Simon
> American River International
> 
> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Tuesday, September 28, 2010 12:52 PM
> To: George Simon
> Cc: filePro Mailing List
> Subject: Re: Windows 7 Professional
> 
> While "regular" users can create directories within the root directory,
only a
> process with "elevated privileges" (ie: "run as administrator") can
> create/edit/delete files within the root directory.  Even when logged in
as an
> administrator account, you can't touch files in the root directory without
> doing "run as administrator".
> 
> So, although you can create "\fp" and "\filepro" directories, you can't
create
> "\fppath", nor any startup "\something.bat" file.  Placing everything in
> something like "\appl" just simplifies things.
> 
> At least, that's the way it's been on all Vista and Windows 7 systems I've
> looked at.
> 
> --
> Kenneth Brody
>_______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list