如何/在哪里存储企业配置设置？
我公司有一个大客户，有很多地区/站点/办事处。 每个位置都可以拥有自己的一组服务器以及自己的数据。 系统的用户通过域进行集中管理。 该网络中的计算机被锁定，只能通过 http 访问互联网。 有一个全公司范围的 Sharepoint 门户。 所有服务器和计算机都基于Windows（主要是XP、Server 2003）。
我们为他们编写了许多实用程序。 有些是从网络加载的，但其中越来越多的直接安装到用户计算机上。 通常，我们通过 ini 或 xml 配置这些工具。 然而，如果服务器更新或需要调整设置，更新就会变得很麻烦。
虽然我不关心数据的存储方式，但我希望有一种通用的方法来查找或定位这些数据。 该方法必须知道用户所在的办公室/区域并返回适当的位置。 我必须在计算机本地缓存这些数据，以防网络故障（似乎经常发生）。
我已经想到了一些想法，但不知道这些想法有多有效或实用：
- 使用 Sharepoint。
- 使用 ActiveDirectory/LDAP。
- 使用 Bonjour/Zeroconf。
我可以在企业范围内使用哪些工具和/或技术来配置本地安装的应用程序？
My company has a large customer that has many regions/sites/offices. Each location can have its own set of servers with its own data. The users of the system are centrally administered thru a domain. The computers in this network are locked down with only http access to the internet. There is a company wide Sharepoint portal. All servers and computers are Windows based (mostly XP, Server 2003).
We have written a number of utilities for them. Some are loaded from the network, but an increasing number of these are installed directly to a users machine. Typically we have been configuring these tools thru ini's or xml's. However, this is becoming cumbersome to update if a server is updated or settings need to be tweaked.
While I'm not concerned with how the data is stored, I'd like to have a common way to find or locate this data. The method will have to contend with certain knowing what office/region the user is on and return an appropriate location. I'll have to cache this data locally on the machine in case the network fails (seems to happen every so often).
I've already thought of a couple of ideas, but have no idea how effective or practical these are:
- Use Sharepoint.
- Use ActiveDirectory/LDAP.
- Use Bonjour/Zeroconf.
What tools and/or technologies can I use enterprise wide to configure locally installed applications?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您的客户已经使用 Active Directory，那么您可以使用登录脚本下载他们可能需要的主配置文件。
仅当他们在连接到域时登录以便满足您的连接要求时才会发生这种情况，并且因为只有在那时才下载它，所以您的所有客户端应用程序都可以在本地加载数据以满足位置要求。
然后，当您部署更新的配置文件时，所有用户需要做的就是在连接到网络时再次登录。
该脚本与经常用于安装可用网络共享或配置本地打印机的脚本没有什么不同。 在每种情况下，您都可以确定用户所在的位置，从而确定他们应该下载什么配置文件。
当然，这是假设这些配置值不经常更改。 如果它们可能会频繁更改，从而导致注销/登录不方便，那么您将不得不采用另一种方法。
If your customer uses active directory already, then you can use a logon script to download the master configuration files they might need.
This would only occur when they login while connected to the domain so your connectivity requirement is met, and since it'd only be downloaded at that time all your client apps could load the data locally satisfying the locality requirement.
Then, when you deploy an updated configuration file, all users would need to do is login again while connected to the network.
This script would not be unlike the scripts often used to mount available network shares or configure local printers. In each case, you can determine where a user is located and thus what config file they should download.
That is of course presuming that these config values don't change very often. If it's likely that they will change so often as to make a logout/login inconvenient, you'll have to go with another approach.