Quantcast
Channel: PowerGUI Wiki
Viewing all articles
Browse latest Browse all 16

6484.powergui release notes v3 8

$
0
0
Revision 1 posted to PowerGUI Wiki by DELL-Claudine Farah on 6/16/2014 2:51:19 PM

PowerGUI®

Version 3.8

Release Notes

October 31, 2013

Contents

Welcome to PowerGUI

New in this Release

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

 


Welcome to PowerGUI

PowerGUI is a comprehensive solution helping you get the most of Windows PowerShell. The product has two components:

  • Administrative Console
  • Script Editor and debugger

PowerGUI Administrative Console is a graphical user interface for the Microsoft PowerShell scripting environment and runtime, bundled with an advanced PowerShell script editor.

PowerGUI Administrative Console is designed to:

  • Streamline PowerShell-based administration tasks by providing ready-made tools through a unified interface
  • Make the extensive capabilities of PowerShell accessible to users who are not comfortable with the text console environment
  • Help establish administration tiers by making specific tools available to specific groups of users, such as Active Directory administrators, help desk staff, and end users

Note: The MobileShell remote server management toolset is no longer included in PowerGUI. If you need functionality similar to MobileShell, try out the Quest Mobile IT product. For information on Quest Mobile IT, go to http://www.quest.com/mobile-it/.

 

Back to Top


New in this Release

Significantly enhanced support for script as an executable compilation

  • Now compiled executable can be run directly from network shares.
  • Silent installation is now supported for scripts compiled as a service.
  • There is an ability to select icon for compiled executable file.
  • Target .NET framework can be now specified for compiled scripts.

Improved add-ons and plugins

  • Call Stack Window add-on now supports Windows 8 and Windows Server 2012.
  • Script Editor Essentials add-on now supports Windows Server 2008.
  • Improved Script Explorer plugin:
  • Newly opened files are now automatically added to the explorer tree.
  • Now plugin expanded/collapsed state is saved between Script Editor sessions.

Different and easily distinguishable icons for PSM1 and PSD1 files

 

Back to Top


Known Issues

The following is a list of issues known to exist at the time of PowerGUI 3.8 release.

Feature

Known Issue

Defect ID

General

If you install PowerGUI on a computer running 64-bit operating system with the User Account Control enabled, the license update can be performed only for the current user. To update a license correctly, run the product in the elevated mode.

ST63185

If you try to change a language for the application while executing a script, the application stops responding. Wait until the script completes its operations.

ST62108

PowerGUI does not support the $Host.UI.RawUI.ReadKey function.

ST57826

If you have the Administrative Console and the Script Editor running and change a language or auto update settings in the Script Editor, for example, these settings will be saved only if you close Script Editor after the console, i.e. all settings will be saved only for the last closed application.

ST56767

First start of application and first connection to remote computer may take more time than usual. Also changing the language settings takes an extended period of time.

ST74277

The Collect anonymous usage data and submit it while I'm online option is displayed only in PowerGUI Script Editor. However, it affects both PowerGUI Administrative Console and PowerGUI Script Editor.

ST77125

The Start Page options are displayed only in PowerGUI Script Editor. However, they affects both PowerGUI Administrative Console and PowerGUI Script Editor.

ST77278

Changes of the Start Page options are applied only after PowerGUI Administrative Console or PowerGUI Script Editor restart.

ST77286

While updating the license from the About dialog box of PowerGUI Administrative Console or PowerGUI Script Editor, you can get the following error message: "Cannot update license. Please supply a valid license or contact us". In this case run the program in elevated mode to update the license.

ST77726

PowerGUI Setup

Setup hangs when it checks free space on Virtual Machine running Microsoft Vista Business Edition SP2. Workaround: start installation with addition keys: msiexec /i PowerGUI.build_number.msi /qr"

 

Administrative Console

If you select a line in the Results tab and copy this line to the clipboard during the execution of a script node or an action, object properties that are not visible within the Results tab frame at the moment may have empty values. Wait for execution to complete and then repeat the operation.

ST64617

If you cancel an action in the dialog where action parameters can be set, you may receive an error with the following message: «An error of type "System.Management.Automation.Host.PromptingException" has occurred». This error is not critical and you can skip it.

ST63988

If you set a different default action from another PowerPack and reimport the current PowerPack, two or more default actions will appear in the PowerGUI Administrative Console. To resolve this issue, restart the console.

ST63901

If you create a new filter in the Administrative Console and specify a filter value of an incorrect type, you will receive an error about a wrong filter that does not allow you to clear filter fields using the Clear All button. To resolve this problem, remove the wrong filter value.

ST62600

If the UseGlobalCatalog property value is true in the configuration of the Active Directory PowerPack, computers will be shown under the Users node together with user accounts.

ST60057

When you upgrade a PowerPack, objects that were included in the old version and are not added to the new version will appear in the Administrative Console after the upgrade.

ST59486

If you create a new PowerPack from objects (nodes, actions, and so on) that are included in another existing PowerPack, check that you copy a Shared Script to the new PowerPack if it is included in the existing one. If the Shared Script is lost, objects from the newly created PowerPack may not work.

ST59225

Console does not report errors which were occurred during profile loading if the AllSigned policy is set and the profile is not signed. As the result, the profile is not loaded.

ST58584

Console hangs on when you try to create a new PowerPack while a tree node creates its child nodes and the tree has not loaded yet. To resolve this problem, right-click the PowerGUI button on the Windows taskbar.

ST57945

When you perform export operations from Actions: Common, all properties of the selected object will be saved, not only columns from the Results tab.

ST56053

The param (…) statement that is used by script nodes and actions does not support parameter names that contain curly braces or begin with a digit.

ST55707,
ST52859

When you create a node, you can use only cmdlets that start with "Get-". To use other cmdlets, create a script node.

ST52769

When you click on a node that has child nodes, and then apply a filter to this node, the filter will affect data in the Results grid and does not affect child nodes.

ST52283

Cannot load the Administrative Console from more than one terminal session simultaneously under the same user account.

ST51116

When you create a new PowerPack, you have the option of specifying PowerShell snap-ins and modules that it depends on. However, specifying these dependencies does not make PowerGUI load them automatically. You should load them manually by clicking File | PowerShell Libraries and using the dialog box that opens.

ST64819

You might encounter errors when using PowerPacks with the backtick (`) character in their names. Please do not use this character in PowerPack names.

ST64580

Chart preset settings can display not all object properties, available as columns for example in the data grid on the results tab. To add such properties to the list you should add them to the respective node/action PowerShell script (using Add-member cmdlet).

ST67354

If you enable Chart tab and create a chart for a dynamic node, PowerGUI may not open Chart tab next time you select this node. To work around this issue, choose Chart from the View menu for this node again.

ST68610

PowerGUI does not support the Enter-PSSession cmdlet.

ST56552

After upgrade of a PowerPack from PowerGUI Administrative Console, the node and action order may differ from the original one. To get the original order, delete the PowerPack and then import it again.

ST59488

Script Editor

Online help may not display after pressing the F1 key while a script is executed (not in debug mode), or while a command is executed in PowerShell Console window. Wait until the script/command completes and try again.

ST74533

You may not be able to add files from network shares (\\computer\share) to SVN Source Control using the free TortoiseSVNSCC provider. Consider mapping network shares to disks, or use another provider.

ST74688

The current version of the Script Editor does not highlight most PowerShell aliases, variables and functions, and does not display IntelliSense prompts for them, when connected to the remote computer using the Enter-PSSession cmdlet.

ST72887

The PowerGUI Script Editor cannot recognize and work with 64-bit MSSCCI providers. To work with version control, use 32-bit versions of MSSCCI providers.

ST64668

If you open a file that is under Team Foundation Server (TFS) version control, and then get the previous version of this file using the native version control client, you will receive no message about file changes.

ST63584

If you change the AutoRecovery time period in the PowerGUI Script Editor's Options dialog box on the Text Editor screen, changes will not be applied immediately. To apply changes, wait for AutoRecovery time period that was set before you change the value or restart the Script Editor.

ST63644

PowerGUI caches data about cmdlets and function that are included in a PowerShell snap-in. If the snap-in is updated but the snap-in version is not changed, cmdlets and functions that are added to the new version will be cached by the PowerGUI but not be shown in the Script Editor and IntelliSense.

ST63103

The Script Editor does not support the following commands in the "prompt" function that changes the command prompt in the PowerShell Console window: Write-Host, $host.UI.xxxxx, etc.

ST62376,
ST62375,
ST62372

In some operating systems, if you log off from your computer while the Script Editor is running and decline to close the editor before the log off, window arrangement in the Script Editor will be set to default when you launch the program again.

ST61777

If you use the Import-PSSession cmdlet in the Script Editor, the Script Editor debugger may work incorrectly. To resolve this issue, restart the Script Editor.

ST61009

The Script Editor cannot recognize fully-qualified cmdlet names, for example: "VMware.VimAutomation.Core\Disconnect-VIServer". The IntelliSense does not work for such names.

ST57668

The Script Editor does not support the More command, for example: Get-Process | More. Results are shown as a single page.

ST52522

If you load a PowerShell snap-in or module using the embedded console (with Add-PSSnapin or Import-Module) instead of using the PowerShell Libraries dialog box, then IntelliSense prompts and syntax highlighting may take some time to start working for the newly loaded cmdlets. This happens due to cmdlet caching.

ST65202

The Script Editor displays disabled breakpoints as enabled, but does not actually stop at them.

ST70994

If you set more than one breakpoint in a line using the Script Editor user interface, the breakpoints returned by the Get-PSBreakpoint cmdlet will have incorrect zero values in the Column property.

ST71264

If breakpoints are disabled using the Disable-PSBreakpoint cmdlet while the Reset PowerShell runspace each time debugging is started option is enabled in the editor preferences, then such breakpoints will be enabled the next time the script runs.

ST71419

The Get-PSBreakpoint cmdlet may return an internal PowerGUI Pro breakpoint set to the command *. This is due to the PowerGUI Pro implementation specifics, and is not an issue.

ST72069,
ST71935

The following situation is possible:

  1. You set a breakpoint on a string using Set-PSBreakpoint cmdlet.
  2. You break the string to span multiple lines, and thus breakpoint highlighting becomes multiline.
  3. After that, you cannot set breakpoints on these lines using the Set-PSBreakpoint cmdlet.

To work around this issue remove the multiline breakpoint before setting new breakpoints.

ST72041

If script execution is started while the Reset PowerShell runspace each time debugging is started option is enabled in the editor preferences, then the breakpoints set on variables and commands will be removed. However the breakpoints that were set on lines will stay unaffected.

ST72137

The following situation is possible:

  1. Script execution is paused within a function because it has reached a breakpoint or the Break button has been clicked.
  2. You use Step Out debugging command and while the debugger is stepping out of the function, you set a breakpoint anywhere in the script.
  3. Instead of stopping the script right after the function, the debugger keeps running until the next breakpoint or the end of the script.

ST72151

In a number of cases, although the current version of Script Editor displays IntelliSense prompts for file paths and .NET objects, when connected to a computer using the Enter-PSSession cmdlet, the information is displayed for the local computer instead of the remote computer.

ST72708

The current version of Script Editor does not display the properties of variables in the Variables window, only their string representations, when connected to a computer using the Enter-PSSession cmdlet.

ST72855

Remote session may be broken if WinRM service run out of 150 MB RAM (default value).

ST74643

If remote session was broken, then IntelliSense prompts for cmdlets may not be shown until you execute any script.

ST74645

If remote session was broken when accessing help, then IntelliSense prompts may be shown from remote session instead of local session until you execute any script.

ST74650

Script files may not open on Windows Vista in the following cases:

  • You try to open script file by dragging script file onto Script Editor while it is running in elevated mode.
  • You try to open script file by double-clicking script file while Script Editor is running in elevated mode.

To work around this issue, open script files from Script Editor using File | Open dialog.

ST56224

If script file from version control is being edited from more than one instance of PowerGUI Script Editor installed on the same computer then some issues may occur.

ST77171,
ST77172

Installing add-ons from the Start Page while working in a remote session fails. To avoid this, close the remote session before add-on installation.

ST77341

 

Back to Top


Upgrade and Compatibility

To upgrade PowerGUI simply install new version of PowerGUI as described in the PowerGUI User Guide - Installing PowerGUI.

 

Back to Top


System Requirements

Before installing PowerGUI, ensure your system meets the following minimum hardware and software requirements.

Administrative Console and Script Editor

CPU

1GHz 32-bit or 64-bit

Memory

Minimum 1GB

Hard Disk Space

About 70MB for the setup and extra disk space for user profiles and PowerPacks that are not included in the setup

Operating System

One of the following:

  • Windows Vista Service Pack 1
  • Windows 7
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows XP Professional Service Pack 3
  • Windows Server 2003 Service Pack 2
  • Windows Server 2003 R2 Service Pack 2
  • Windows 8
  • Windows Server 2012

For successful installation, the Windows Management Instrumentation service must be running on the target system.

Additional Software

All of the following:

  • Microsoft .NET Framework 3.5 Service Pack 1 or Microsoft .NET Framework 4.0 (Full)
  • Microsoft PowerShell 2.0 or Microsoft PowerShell 3.0
  • Any software for which you are installing additional PowerPacks. For example, Exchange 2007 Management Shell must be installed if you select the Exchange 2007 PowerPack, and so on.
  • If you are going to use VMware vSphere Client integration, VMware vSphere Client 4.0 version or later and VMware vSphere PowerCLI 4.1 version or later are required.
  • If you are going to use source control in the PowerGUI Script Editor, a source control client that supports the MSSCCI provider is required. The following version control systems have been verified to work with the PowerGUI Script Editor:
  • Microsoft Visual SourceSafe
  • Microsoft Team Foundation Server

Other version control systems should work if their providers fully support MSSCCI (for example, Subversion with the TortoiseSVNSCC provider), but they have not been tested with the PowerGUI Script Editor.

 

Back to Top


Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. The release supports Complex Script (Central Asia – India, Thailand).

 

Back to Top


Getting Started

Installation Instructions

Refer to the PowerGUI User Guide for installation instructions.

 

Back to Top


For More Information

Get the latest product information, find helpful resources, test the product betas, and join a discussion with the PowerGUI Quest team and other community members. Join the PowerGUI community at http://PowerGUI.org.

Contacting Quest Software:

Email

info@quest.com

Mail

Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA

Web site

http://www.quest.com

Please refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://quest.com/support.

From SupportLink, you can do the following:

  • Retrieve thousands of solutions from our online Knowledgebase
  • Download the latest releases and service packs
  • Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://quest.com/support..

 


 

© 2013 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Mail

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

Web

www.quest.com

Email

legal@quest.com

Refer to our Web site for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo and PowerGUI are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

 

Third Party Contributions

PowerGUI contains some third party components (listed below).

Copies of their licenses may be found at http://www.quest.com/legal/third-party-licenses.aspx and/or in product documentation.

Component

License or Acknowledgement

Extend OpenFileDialog and SaveFileDialog 1.0

The Code Project Open License (CPOL) 1.02

Extend OpenFileDialog and SaveFileDialog 1.0: License Text

Preamble
This License governs Your use of the Work. This License is intended to allow developers to use the Source Code and Executable Files provided as part of the Work in any application in any form.

The main points subject to the terms of the License are:

Source Code and Executable Files can be used in commercial applications;
Source Code and Executable Files can be redistributed; and
Source Code can be modified to create derivative works.
No claim of suitability, guarantee, or any warranty whatsoever is provided. The software is provided "as-is".
The Article accompanying the Work may not be distributed or republished without the Author's consent
This License is entered between You, the individual or other entity reading or otherwise making use of the Work licensed pursuant to this License and the individual or other entity which offers the Work under the terms of this License ("Author").

License
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CODE PROJECT OPEN LICENSE ("LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.

BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HEREIN, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE AUTHOR GRANTS YOU THE RIGHTS CONTAINED HEREIN IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO ACCEPT AND BE BOUND BY THE TERMS OF THIS LICENSE, YOU CANNOT MAKE ANY USE OF THE WORK.

Definitions.
"Articles" means, collectively, all articles written by Author which describes how the Source Code and Executable Files for the Work may be used by a user.
"Author" means the individual or entity that offers the Work under the terms of this License.
"Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works.
"Executable Files" refer to the executables, binary files, configuration and any required data files included in the Work.
"Publisher" means the provider of the website, magazine, CD-ROM, DVD or other medium from or by which the Work is obtained by You.
"Source Code" refers to the collection of source code and configuration files used to create the Executable Files.
"Standard Version" refers to such a Work if it has not been modified, or has been modified in accordance with the consent of the Author, such consent being in the full discretion of the Author.
"Work" refers to the collection of files distributed by the Publisher, including the Source Code, Executable Files, binaries, data files, documentation, whitepapers and the Articles.
"You" is you, an individual or entity wishing to use the Work and exercise your rights under this License.
Fair Use/Fair Use Rights. Nothing in this License is intended to reduce, limit, or restrict any rights arising from fair use, fair dealing, first sale or other limitations on the exclusive rights of the copyright owner under copyright law or other applicable laws.
License Grant. Subject to the terms and conditions of this License, the Author hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:
You may use the standard version of the Source Code or Executable Files in Your own applications.
You may apply bug fixes, portability fixes and other modifications obtained from the Public Domain or from the Author. A Work modified in such a way shall still be considered the standard version and will be subject to this License.
You may otherwise modify Your copy of this Work (excluding the Articles) in any way to create a Derivative Work, provided that You insert a prominent notice in each changed file stating how, when and where You changed that file.
You may distribute the standard version of the Executable Files and Source Code or Derivative Work in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution.
The Articles discussing the Work published in any form by the author may not be distributed or republished without the Author's consent. The author retains copyright to any such Articles. You may use the Executable Files and Source Code pursuant to this License but you may not repost or republish or otherwise distribute or make available the Articles, without the prior written consent of the Author.
Any subroutines or modules supplied by You and linked into the Source Code or Executable Files this Work shall not be considered part of this Work and will not be subject to the terms of this License.
Patent License. Subject to the terms and conditions of this License, each Author hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, import, and otherwise transfer the Work.
Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
You agree not to remove any of the original copyright, patent, trademark, and attribution notices and associated disclaimers that may appear in the Source Code or Executable Files.
You agree not to advertise or in any way imply that this Work is a product of Your own.
The name of the Author may not be used to endorse or promote products derived from the Work without the prior written consent of the Author.
You agree not to sell, lease, or rent any part of the Work. This does not restrict you from including the Work or any part of the Work inside a larger software distribution that itself is being sold. The Work by itself, though, cannot be sold, leased or rented.
You may distribute the Executable Files and Source Code only under the terms of this License, and You must include a copy of, or the Uniform Resource Identifier for, this License with every copy of the Executable Files or Source Code You distribute and ensure that anyone receiving such Executable Files and Source Code agrees that the terms of this License apply to such Executable Files and/or Source Code. You may not offer or impose any terms on the Work that alter or restrict the terms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may not distribute the Executable Files or Source Code with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License.
You agree not to use the Work for illegal, immoral or improper purposes, or on pages containing illegal, immoral or improper material. The Work is subject to applicable export laws. You agree to comply with all such laws and regulations that may apply to the Work after Your receipt of the Work.
Representations, Warranties and Disclaimer. THIS WORK IS PROVIDED "AS IS", "WHERE IS" AND "AS AVAILABLE", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OR GUARANTEES. YOU, THE USER, ASSUME ALL RISK IN ITS USE, INCLUDING COPYRIGHT INFRINGEMENT, PATENT INFRINGEMENT, SUITABILITY, ETC. AUTHOR EXPRESSLY DISCLAIMS ALL EXPRESS, IMPLIED OR STATUTORY WARRANTIES OR CONDITIONS, INCLUDING WITHOUT LIMITATION, WARRANTIES OR CONDITIONS OF MERCHANTABILITY, MERCHANTABLE QUALITY OR FITNESS FOR A PARTICULAR PURPOSE, OR ANY WARRANTY OF TITLE OR NON-INFRINGEMENT, OR THAT THE WORK (OR ANY PORTION THEREOF) IS CORRECT, USEFUL, BUG-FREE OR FREE OF VIRUSES. YOU MUST PASS THIS DISCLAIMER ON WHENEVER YOU DISTRIBUTE THE WORK OR DERIVATIVE WORKS.
Indemnity. You agree to defend, indemnify and hold harmless the Author and the Publisher from and against any claims, suits, losses, damages, liabilities, costs, and expenses (including reasonable legal or attorneys’ fees) resulting from or relating to any use of the Work by You.
Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL THE AUTHOR OR THE PUBLISHER BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK OR OTHERWISE, EVEN IF THE AUTHOR OR THE PUBLISHER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Termination.
This License and the rights granted hereunder will terminate automatically upon any breach by You of any term of this License. Individuals or entities who have received Derivative Works from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 6, 7, 8, 9, 10 and 11 will survive any termination of this License.
If You bring a copyright, trademark, patent or any other infringement claim against any contributor over infringements You claim are made by the Work, your License from such contributor to the Work ends automatically.
Subject to the above terms and conditions, this License is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, the Author reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.
Publisher. The parties hereby confirm that the Publisher shall not, under any circumstances, be responsible for and shall not have any liability in respect of the subject matter of this License. The Publisher makes no warranty whatsoever in connection with the Work and shall not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. The Publisher reserves the right to cease making the Work available to You at any time without notice
Miscellaneous
This License shall be governed by the laws of the location of the head office of the Author or if the Author is an individual, the laws of location of the principal place of residence of the Author.
If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this License, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
This License constitutes the entire agreement between the parties with respect to the Work licensed herein. There are no understandings, agreements or representations with respect to the Work not specified herein. The Author shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Author and You.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

 

Back to Top

 

 

Tags: new release, upgrade and compatibility, system requirements, know issues, release notes, global operations

Viewing all articles
Browse latest Browse all 16

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>