However, I’ve created a packaging tool which can be found here. How can I build a package for distribution for SCCM or a package manager? MarcEdit isn’t updated using a regular update cycle, however, a set of RSS feeds exist that provide notifications when new updates have been posted. All user data will be stored within the user hive of the system, within the C:\Users\\AppData\Roaming\Terry Reese\marcedit7.5 directory. Typically, that will be: c:\Program Files\Terry ReeseMarcEdit 7.5 or c:\Program Files (x86)\Terry Reese\MarcEdit 7.5 depending on the version installed. The application and all program files are stored in the program directory. This wizard will only show the first time a user runs MarcEdit 7.5. Failing to run the Wizard will result in the program potentially not being configured correctly for your organizations MARC data. This is important, because MarcEdit is MARC agnostic. It will show on first run, and provides the user (typically a cataloger) the ability to set the configuration of the application. When installing MarcEdit 7.5 for the first time, the user will be presented with a configuration wizard. You may also utilize the general exe files found on the downloads page if that works better for you. For organizations wanting to manage the software via a distribution client like SCCM, I’ve provided an MSI file for 64-bit systems. For organizations wishing to management MarcEdit - determine the version that you want to support. To simplify the process of managing MarcEdit, I’ve included a set of general best practices. These requirements usually include distributing software via a distribution client like Microsoft’s SCCM as well as tracking updates/bug fixes to the application. Large organizations often have very specific requirements when managing software for their users. Jump to the Install Files and Instructions
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |