Quest One Quick Connect Management Shell
Version 1.2.0
Release Notes
April, 2013
Welcome to Quest One Quick Connect Management Shell
Resolved Issues and Enhancements
The Quick Connect Management Shell is an automation and scripting shell that provides a command-line management interface for synchronizing data between external data systems via the Quick Connect Service. The Quick Connect Management Shell is implemented as a Windows PowerShell snap-in, providing an extension to the Windows PowerShell environment. The commands provided by the Quick Connect Management Shell conform to the Windows PowerShell standards, and are fully compatible with the default command-line tools that come with Windows PowerShell.
This release of Quick Connect Sync Engine offers the following major new feature:
For detailed information about the new cmdlets included in this release and usage examples, see the Quick Connect Management Shell Help.
For instructions on how to view the Quick Connect Management Shell Help, see Getting Help.
There are no issues resolved and enhancements implemented in this Quick Connect Management Shell release.
The following is a list of issues
known to exist at the time of this Quick Connect Management Shell release.
TF00161077
The Get-QCSyncHistoryDetails cmdlet may fail to provide synchronization history
details for some categories of objects, such as processed objects or objects not
meeting scope conditions.
WORKAROUND
Contact Quest Support for more information on this issue.
TF00161203
Unexpected behavior when you are using the Get-QCObject cmdlet: The names of
object attributes you specify in the cmdlet parameters are case sensitive. As a
result, the cmdlet may fail to perform the requested operation if you do not
enter the attribute names in the proper case.
WORKAROUND
Check to make sure you use the proper case in the attribute names specified in
the cmdlet parameters.
TF00218549
Unexpected behavior when you install the 64-bit version of Quick Connect
Management Shell on a computer that has the 32-bit version of Quick Connect
Management Shell installed: The 64-bit version of Quick Connect Management Shell
replaces the 32-bit version.
The expected behavior in the described situation is that the 32-bit and 64-bit
versions of Quick Connect Management Shell should install side by side.
WORKAROUND
If you want to have both 32-bit and 64-bit versions of Quick Connect Management
Shell installed on one computer, reinstall the 32-bit version after installing
the 64-bit version.
Quick Connect Management Shell 1.2 does not support upgrade from earlier versions of Quick Connect Management Shell. Before installing Quick Connect Management Shell 1.2, make sure your computer does not have any earlier version of Quick Connect Management Shell installed.
| Operating System |
You computer must run one of the following operating systems (both x86
and x64 platforms are supported): - Microsoft Windows Server 2012 with or without any Service Pack - Microsoft Windows Server 2008 R2 with or without any Service Pack - Microsoft Windows Server 2008 with or without any Service Pack - Microsoft Windows Server 2003 with Service Pack 1 or Service Pack 2 - Microsoft Windows XP with Service Pack 2 or Service Pack 3 - Microsoft Windows 7 with or without any Service Pack |
| Microsoft .NET Framework | Microsoft .NET Framework 3.5 SP1 |
| Quest One Quick Connect Sync Engine |
Quick Connect Sync Engine
5.2 You can install the Quick Connect Management Shell on any computer joined to the Active Directory domain in which the Quick Connect Sync Engine is deployed. |
| Windows PowerShell | Your computer must have one of the following versions
installed: - Windows PowerShell 3.0 - Windows PowerShell 2.0 |
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.
In this section:
Before installing the Quick Connect Management Shell, make sure your computer meets the System Requirements.
You can open the Quick Connect Management Shell by using either of the following procedures. Each procedure loads the Quick Connect Management Shell snap-in into Windows PowerShell. If you do not load the Quick Connect Management Shell snap-in before you run a command (cmdlet) provided by that snap-in, you will receive an error.
Alternatively, complete the following steps related to your version of Windows:
| Windows Server 2003, 2003 R2, 2008, or 2008 R2 | Windows Server 2012 |
|
On the Start screen, click the Quick Connect Management Shell tile. |
Upon the shell start, the console may display a message stating that a certain file published by Quest Software is not trusted on your system. This security message indicates that the certificate the file is digitally signed with is not trusted on your computer, so the console requires you to enable trust for the certificate issuer before the file can be run. Press either R (Run once) or A (Always run). To prevent this message from appearing in the future, it is advisable to choose the second option (A).
All cmdlets are presented in verb-noun pairs. The verb-noun pair is separated by a hyphen (-) without spaces, and the cmdlet nouns are always singular. The verb refers to the action that the cmdlet performs. The noun identifies the entity on which the action is performed. For example, in the Get-QCObject cmdlet name, the verb is Get and the noun is QCObject. All the Quick Connect Management Shell cmdlets have the nouns prefixed with QC, to distinguish the Quick Connect Management Shell cmdlets from those provided by PowerShell itself or by other PowerShell snap-ins.
This section provides instructions on how to get help information for the cmdlets added by the Quick Connect Management Shell to the Windows PowerShell environment.
| To view this | Run this command |
| A list of all the Quick Connect Management Shell cmdlets available to the shell. | Get-QCCommand |
| Information about the parameters and other components of a Quick Connect Management Shell cmdlet. | Get-QCCommand <CmdletName> -OR- Get-Command <CmdletName> Note: You can use wildcard character expansion. For example,
to view information about the cmdlets with the names ending in Workflow,
run this command: |
| Basic help information for a Quick Connect Management shell cmdlet. | Get-Help <CmdletName> |
| Detailed help information for a Quick Connect Management Shell cmdlet, including the descriptions of available parameters and usage examples. | Get-Help <CmdletName> -full |
| Basic information about how to use the help system in Windows PowerShell, including Help for the Quick Connect Management Shell. | Get-Help |
The release package contains the following items:
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web | http://www.quest.com |
Refer to our Web site for regional and international office information.
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 our Support Portal at www.quest.com/support.
From our Support Portal, you can do the following:
View the Global Support Guide for a detailed explanation of support
programs, online services, contact information, policies and procedures.
The guide is available at
www.quest.com/support.
© 2013 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this document 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.
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.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 email: legal@quest.com |
Refer to our Web Site www.quest.com for regional and international office information.
Quest, Quest Software, the Quest Software logo 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.
This product contains some third party components (listed below). Copies of their licenses may be found at http://www.quest.com/legal/third-party-licenses.aspx. Source code for components marked with an asterisk (*) is available at http://rc.quest.com.