[AccessD] OT: Network registry?

MartyConnelly martyconnelly at shaw.ca
Thu Jul 22 20:02:34 CDT 2004


You could also use ADSI scripts to add this info into a registry key on 
each clients machine
from a network admin account.
Use the ADsSecurity.dll COM component from the ADSI SDK (Win2000) or the
built-in AdsSecurityUtility object on WinXP. It has a COM interface as 
well as
an API interface. This is not easy stuff! But it would give the BOFH 
heart failure.
No, I have not done this before but should be possible to write from vbs 
or Access.


DWUTKA at marlow.com wrote:

>Along the lines of the window service, I would recommend going with Named
>Pipes.  They're pretty easy to setup, and they're fast.  
>
>Drew
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Brett Barabash
>Sent: Thursday, July 22, 2004 10:32 AM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] OT: Network registry?
>
>
>Here's the problem.  I have an encrypted piece of information that I
>want to share with every computer in my network (~70 machines).  This
>information can change at any time so it would be difficult to store it
>locally on each workstation.
> 
>Currently I am storing this information in an INI file on a network
>share, which causes a series of problems:
>- I need to hard code the INI file location in the code accessing the
>data.  If the file location changes, I would need to update all of the
>workstations.
>- All users accessing this file need the appropriate file permissions.
>There really isn't a single network location that ALL users in this
>building access.
> 
>I was thinking of writing a Windows service that could run on one of the
>servers, that could monitor incoming requests from client workstations,
>and return the encrypted data.  That way, one would only need to know
>the local IP address of the server, which is unlikely to change.
> 
>Any other ideas?
>
>Brett Barabash
>Lead Software Developer
>Tappe Construction, Co.
>Eagan, MN
>
>Email: bbarabash at tappeconstruction.com
>Phone: (651) 256-6831
>
>"Intel Inside: The world's most widely used warning label" - Jim Hopper
>
> 
>
>----------------------------------------------------------------------------
>----------------------------------------
>The information in this email may contain confidential information that 
>is legally privileged. The information is only for the use of the intended
>recipient(s) named above. If you are not the intended recipient(s), you 
>are hereby notified that any disclosure, copying, distribution, or the
>taking 
>of any action in regard to the content of this email is strictly prohibited.
>If 
>transmission is incorrect, unclear, or incomplete, please notify the sender 
>immediately. The authorized recipient(s) of this information is/are
>prohibited 
>from disclosing this information to any other party and is/are required to
>destroy the information after its stated need has been fulfilled.
>
>Any views expressed in this message are those of the individual
>sender, except where the sender specifies and with authority,
>states them to be the views of Tappe Construction Co.
>
>This footer also confirms that this email message has been scanned
>for the presence of computer viruses.Scanning of this message and
>addition of this footer is performed by SurfControl E-mail Filter software
>in conjunction with virus detection software.
>--
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada






More information about the AccessD mailing list