Which prerequisites are needed for the RayPackage Configurator?
To use the RayPackage Configurator successfully, you need at least PowerShell version 3.0.
Where are the log files for installation and uninstallation?
The installation and uninstallation log files can be found at the following log path: C:\Windows\Logs\Software\
Why should I choose the Raynet Package Store?
Raynet provides the largest selection of high quality packages possible. The completeness of our packages are made possible by leveraging the skills of our own experienced team of packagers as well as other IT Professionals from around the world.
We are not only providing multiple levels of packages to suit your specific needs, but we are also providing easy to use configuration options you will not find anywhere else. Finally, the contents of our store are constantly being re-evaluated and enhanced as new information becomes available and to address emerging capabilities as they are introduced.
Why are so many packages unavailable?
Realizing our vision for a store that provides for every application, there will be an ongoing journey. We are working through the most popular applications now, but will prioritize efforts based on requests. If you purchase a package that is not ready, we have teams standing by to generate the required/purchased package within the posted delivery times.
What packages formats will be made available on the Package Store?
We intend to provide all types of format, but will prioritize the introduction of alternative formats based on demand. If you would like to obtain package formats like App-V, ThinApp or others, please let us know so we can prioritize these efforts to fulfill your expectations with regard to the desired package format. Even if not available in the store today, we may be able to offer the format you desire so please let us know!
How will the community contribute to the store?
The community will contribute deployment options which we will leverage to generate packages on the site, and participants will be rewarded for their efforts. Details on how one can contribute, what one can contribute, what is expected of contributions and how rewards will be valued and executed are in progress of being adapted. Please complete our questionnaire to become a participant to become part of the discussion.
What is behind the rules?
Disable Automatic Updates
This option turns off auto-update feature of the application. Depending on the application, this might be accomplished by setting a property value, registry entry or modifying a configuration file.
Remove Desktop Shortcuts
For applications that would place shortcuts on the desktop by default, this option should remove such shortcuts. Depending on the application, this might be accomplished by setting a property value, removing the files in a transform file or running a post-installation script or custom action.
Silent Install Support
For applications that support silent installation, this option should make the installation run with no visible dialogs or prompts. This is typically implemented as a command line argument (/qn, /SILENT,etc.) and offered as part of the installation script provided with the generated package.
Silent Uninstall Support
For applications that support silent removal, this option should make the installation removal run with no visible dialogs or prompts. This is typically implemented as a command line argument (/qn, /SILENT, etc.) and offered as part of the uninstall script provided with the generated package.
Per Machine Installation
For applications that support installation per machine (as opposed to per user), this option should target the installation for all users. This is typically implemented via the ALLUSERS property in Windows Installer setups and may require per-user elements to be specially handled such as by ActiveSetup.
Disable Splash Screen
For applications that support initial dialogs (for example Welcome messages, Release Notes, initial configuration prompts etc.) this option should disable this feature of the application. Depending on type of the application, it may be achieved by using custom registry entries or configuration entries that prevent them from running on first run.
Suppress Auto Start
For applications that automatically start by default, this option should prevent automatic launch of the application. Depending on the application, this might be accomplished by setting a property value, registry entry or modifying a configuration file.
For applications that may reboot as a part of (or following) installation, this option should prevent such a reboot (the customer will be responsible for initiating a reboot outside of the installation process). This is typically implemented as a command line parameter and/or MSI property(/NOREBOOT, REBOOT=ReallySuppress, etc.).
Disabled ARP Interaction
For applications that list themselves in Add Remove Programs, this option prevents interactive configuration or removal from the Windows Add or Remove Programs interface. This is typically implemented by modifying or removing values normally inserted into the registry in support of the Add or Remove Programs interface provided to end users by Windows.
What to do in case a package is not functional/if there is a problem with a package?
Raynet provides full support for all packages in the store. If you have a problem with a package please contact our support.
How can you ensure packages are of high quality?
While you may see that we intend to leverage the community, we will be doing so in such a way that it is Raynet that builds the final package in order to ensure complete awareness of package actions and contents.
Before a package is made available in the store, it must pass our quality control process. This process is a complete, rigorous solution designed by Raynet to exceed the expectations of our customers over the years. We also use our products to perform OS readiness tests and have many years of experience creating thousands of packages for various customers.
You have any other questions? Please contact us.