|
|
The Resume-Scenario command enables you to resume the replication process on a suspended Replica host. Once the replication is resumed, the accumulated changes are transferred and applied to the Replica without any need to perform a full re-synchronization of the data.
Resume-Scenario [-Name] <String> [-Host] <String>
The scenario name.
The name of the suspended Replica host you want to resume.
Example: Resume the replication process on a suspended Replica
resume-scenario "File Server 1" 192.168.1.153
Outcome:
Scenario File Server 1 resumed on 192.168.1.153
The Run-Scenario command enables you to start one or several scenarios.
Run-Scenario [-Name] <String> [-Mode] <String> [-Ignore] <Boolean>
The scenario name. You can enter several scenario names by using the Get-Scenario command.
The synchronization mode. Enter one of the following:
B=Binary
F=File
Ignore files of the same name and size during the data comparison. Enter one of the following:
1=Yes
0= No
Notes:
Get-Scenario |Run-Scenario
Example: Start a scenario
run-scenario "File Server 1" F 1
Outcome:
Scenario File Server 1 Starting...
The Run-Assessment command enables you to assess the accurate bandwidth usage and compression ratio benchmarking that is needed for replication, without actually replicating data. When you run this command, no replication occurs but statistics are gathered. A report is provided once the assessment process is stopped.
Important! Do not forget to stop the scenario that runs in Assessment Mode after the period you wanted to assess has passed, by using the Stop-Scenario command.
Note: To view the Assessment Report after its generation, open the Report Center from the Overview Page, and select the required report.
Run-Assessment [-Name] <String>
The scenario name.
Example: Run a scenario in Assessment Mode
run-assessment "File Server 1"
Outcome:
Scenario File Server 1 executed successfully
A bookmark is a checkpoint that is manually set to mark a state that you may want to rewind back to. The Set-Bookmark enables you to set a bookmark for a given scenario. Bookmarks are set in real-time, and not for past events. We recommend setting a bookmark just before any activity that may cause data to become unstable.
Notes:
Set-Bookmark [-Name] <String> [[-Message] <String>]
The name of the scenario.
The name of the bookmark. The default name includes the date and time of the bookmark setting.
Note: We recommend giving a meaningful name to the bookmark that will later help you recognize it.
Example: Set a rewind bookmark
set-bookmark "File Server 1" Backup1
Outcome:
Scenario File Server 1: Rewind bookmark set successfully
The Stop-Scenario command enables you to stop one or several scenarios.
Note: To check if the operation was completed successfully, use the Get-Scenario and Get-Events commands.
Stop-Scenario [-Name] <String>
The name of the scenario you want to stop. You can enter several scenario names by using the Get-Scenario command.
Example: Stop a scenario
stop-scenario "File Server 1"
Outcome:
Scenario File Server 1 stopped
The Suspend-IsAliveCheck command lets you manually suspend IsAlive checking for a given running HA scenario.
Suspend-IsAliveCheck [-ScenarioName] <String>
The scenario name.
Example: Suspend IsAlive checking of SQLscenario
Suspend-IsAliveCheck SQLscenario
Outcome:
Suspends periodic is-alive checking of SQLscenario.
The Suspend-Scenario command enables you to temporarily cease delivering changes to a suspended Replica. During the suspension, changes are accumulated in a spool until replication is resumed so that re-synchronization is not required.
Important! It is imperative that during suspension, you do nothing on the Replica that causes the data to change in any way, including starting an application such as Exchange Server, SQL Server, or Oracle. If you need to start programs that will change data on the Replica, you may use the Assured Recovery option.
Notes:
Suspend-Scenario [-Name] <String> [-Host] <String>
The scenario name.
The Replica host you want to suspend.
Example: Suspend updates on a Replica
suspend-scenario "File Server 1" 192.168.1.153
Outcome:
Scenario File Server 1 Suspended on 192.168.1.153
The Switchover-Scenario command enables you to start the switchover process for a given HA scenario. To switch back the roles between the Master and the Replica, use the Switchover-Scenario command again.
Switchover-Scenario [-Name] <String>
The scenario name.
Example: Perform a switchover
Switchover-Scenario "SQL Server 1"
Scenario SQL Server 1 switching over to 192.168.1.153
Done!
The Sync-Scenario command enables you to synchronize the Master and the Replica of a given scenario. The synchronization process can be manually activated at any time, whether replication is running or not.
Sync-Scenario [-Name] <String> [-Mode] <String> [-Ignore] <Boolean>
The scenario name. You can enter several scenario names by using the Get-Scenario command.
The synchronization mode. Enter one of the following:
B=Binary
F=File
Ignore files of the same name and size during the data comparison. Enter one of the following:
1=Yes
0= No
Example: Initiate a synchronization
sync-scenario "File Server 1" F 1
Outcome:
Synchronization is running for scenario FS 1...
Done!
The Test-Integrity command enables you to activate an automatic integrity test on a Replica host for assured recovery.
Notes:
Test-Integrity [-Name] <String> [-Host] <String>
The name of the scenario.
The IP address or hostname of the Replica host you want to test.
Example: Perform Integrity Test for Assured Recovery
Test-Integrity "Exchange Server 1" 192.168.1.153
Integrity testing for assured recovery started on 192.168.1.153
Done!
Integrity testing for assured recovery completed on 192.168.1.153
The Unmount-Snapshot command enables you to release an exposed snapshot without losing the snapshot itself. The snapshot is still exposed but it does not use a mount point.
Unmount-Snapshot [-Name] <String> [[-Index] [<Int32>]] [[-Port] [<String>]]
The name of the host whose snapshot you want to expose.
The index no. of the snapshot, as returned by the Get-Snapshot command.
The port that is used for connecting to the given host. The default port is 25000.
Example: Unmount a snapshot
Unmount-Snapshot {97127d0b-f1c9-4db5-943d-96c39b712fe6} 1
Snapshot {97127d0b-f1c9-4db5-943d-96c39b712fe6} unmounted
This section describes CA ARCserve RHA PowerShell commands that enable you to edit scenarios and scenario groups.
The Add-dir command enables you to add root directories to the Master and Replica hosts. You can define the same root dirrectory path for both the Master and Replica, or you can enter two different paths. If you do not enter a different path for the Replica, by default it will be the same as the Master path.
Add-Dir [-Name] <String> [-MasterPath] <String> [[-ReplicaPath] [<String>]]
The scenario name.
The full path of the root directories on the Master.
The full path of the root directories on the Replica(s). If no value is entered, the same path will be used for the Master and Replica.
Example: Add the same root directory to the Master and the Replica
add-dir "File Server 1" C:/Tools
Root Directory: C:/Tools added successfully
The Add-Group command enables you to create a new scenario group.
Note: When no scenario is assigned, empty scenario groups do not appear on the Overview Page.
Add-Group [-Name] <String>
The name of the new scenario group.
Note: Enter a unique name, since you cannot use the same name for more than one scenario group. If you use an existing name for the new group, the system will change it automatically.
Example: Create a new scenario group
add-group "File Server Scenarios"
Group File Server Scenarios added successfully
The Add-Master command enables you to add a Master host to a given scenario. When defining a Master host, you need to enter its hostname. In addition, you can also enter the Master IP address, but this parameter is not mandatory.
Notes:
Add-Master [-Name] <String> [-Host] <String> [[-IP] [<String>]]
The name of the scenario.
The hostname of the new Master.
The IP address of the new Master. If no IP address is defined, by default the system seeks it by using the specified hostname, and uses the first IP address it finds. For this reason, if the host has multiple IP addresses, we recommend to enter here the IP address you want to use.
Example: Add a Master host to a scenario
add-master "File Server 1" 130.119.185.152
Master 130.119.185.152 added successfully
The Add-Replica command enables you to add a Replica host to a given scenario. When defining a Replica host, you need to enter its hostname, and optionally, its IP address as well. Then, you need to enter its parent host, which can be either the Master or another Replica.
Note: You can enter the IP address as the hostname.
When using ACL security delegations, you need to enter the values of three additional parameters: UserName, Password, and DomainName.
Add-Replica [-Name] <String> [-Host] <String> [[-IP] [<String>]] [-Parent] <String> [[-UserName] <String>] [[-Password] <String>] [[-DomainName] <String>]
The name of the scenario.
The hostname of the new Replica.
The IP address of the new Replica. If no IP address is defined, by default the system seeks it by using the specified hostname, and uses the first IP address it finds. For this reason, if the host has multiple IP addresses, we recommend to enter here the IP address you want to use.
The parent host of the new Replica host. The parent can be either the Master or an upstream Replica, and you can use either its hostname or IP address.
The User Name, password and domain of a user, who has the right to add a new Replica host.
Example: Add a Replica host to a scenario
add-replica "File Server 1" 130.119.185.153 -parent 130.119.185.152
Replica 130.119.185.153 added successfully
The Add-Replicas command enables you to add multiple Replica hosts at once to a given scenario. To add multiple Replica hosts, you need to create a text file that contains the hostnames and IP addresses of the hosts. When you use the command, first define the scenario name and the parent host of all the Replica hosts you want to add. Then, specify the name and path of the file that contains the details of the new hosts.
Add-Replicas [-ScenarioName] <String> [-ParentHost] <String> [-FileName] <String>
The name of the scenario.
The parent host of the new Replica host. The parent can be either the Master or an upstream Replica, and you can use either its hostname or IP address.
A text file that contains the host names and their IP addresses. The text should be formatted as follows:
#host name IP address
QA95-W2K3-SQL1 *130.119.185.155
QA95-W2K3-EX2 *130.119.185.153
The User Name, password and domain of a user, who has the right to add new Replica hosts.
Example: Add multiple Replica hosts to a scenario
add-replicas "Exchange Server" QA95-W2K3-EX1 D:\New_Replica_Hosts.txt
130.119.185.151 QA95-W2K3-EX1
130.119.185.152 QA95-W2K3-EX2
2 replicas were added.
The Add-Scenario command enables you to create a new scenario. When creating a new scenario, you need to define the following:
The new scenario is created without hosts and root directories. You define these parameters at a later stage, using the Add-Master, Add-Replica and Add-Dir commands.
Add-Scenario [-Name] <String> [[-Group] [<String>]] [[-Application] [<String>]] [[-Type] [<String>]] [[-AR] [<Boolean>]
The name of the new scenario.
Note: Enter a unique name, since you cannot use the same name for more than one scenario. If you will use an existing name for the new scenario, the system will change it automatically.
The scenario group name that contains the new scenario.
Notes:
The type of server whose data will be replicated:
The type of solution:
Whether to perform an Assured Recovery test of the recoverability of the data on the Replica server:
Example: Create a new scenario
add-scenario "File Server 1" "File Server Scenarios" FS DR 0
Scenario File Server 1 added successfully
The Remove-Dir command enables you to remove root directories from the Master and Replica hosts.
Note: You cannot remove a root directory only from the Replica using this command. Once you remove the Master root directories, the corresponding Replica root directories will be removed as well.
Remove-Dir [-Name] <String> [-MasterPath] <String>
The name of the scenario.
The root directory path on the Master.
Example: Remove a root directory from the Master and Replica
remove-dir "File Server 1" C:/Tools
Outcome:
Root Directory: C:/Tools removed
The Remove-Group command enables you to delete a given scenario group.
Note: You can only remove an empty scenario group. If you want to remove a group that contains scenarios, first you need to remove the scenarios.
Remove-Group [-Name] <String>
The name of the scenario group you want to delete.
Example: Delete a scenario group
remove-group "new group 1"
Group new group 1 removed
The Remove-Replica command enables you to remove a Replica host from a given scenario.
Remove-Replica [-Name] <String> [-Host] <String> [-Parent] <String>
The name of the scenario.
The name of the Replica host you want to remove.
The parent of the Replica host you want to remove in the replication tree. It can be either the Master or an upstream Replica.
Example: Remove a Replica host from a scenario
remove-replica "FS 1" 130.119.185.153 -parent 130.119.185.152
Replica 130.119.185.153 removed
The Remove-Scenario command enables you to delete a given scenario.
Note: You cannot delete a running scenario.
Remove-Scenario [-Name] <String>
The name of the scenario you want to delete.
Example: Remove a scenario
remove-scenario "File Server 2"
Scenario File Server 2 removed
The Rename-Group command enables you to change the name of a given scenario group.
Rename-Group [-Name] <String> [-NewName] <String>
The current name of the scenario group.
The new name for the scenario group.
Note: Enter a unique name, since you cannot use the same name for more than one scenario group. If you use an existing name for the scenario group, the system changes it automatically.
Example: Rename a scenario group
rename-group Server "Exchange Server Scenarios"
Group Server renamed!
The Rename-Scenario command enables you to change the name of a given scenario.
Note: You cannot rename a running scenario. To change its name, you need to stop it first.
Rename-Scenario [-Name] <String> [-NewName] <String>
The current name of the scenario.
The new name for the scenario.
Example:
rename-scenario "File Server 1" "File Server"
Scenario File Server 1 renamed!
You may now change certain scenario properties while a scenario is running. This section lists the syntax and examples for the commands that apply to editing a scenario while it is running.
The Apply-AllPendingRuntimeChangeableScenarioProperties command lets you apply all changes to all changed scenarios at run time.
Apply-AllPendingRuntimeChangeableScenarioProperties
None
Example
Suppose you changed properties on several scenarios. Those changes are all pending. To apply them immediately use this command.
The Apply-PendingRuntimeChangeableScenarioProperties command lets you apply all changes to the specified running scenario.
Apply-PendingRuntimeChangeableScenarioProperties [Name]
Name - The name of the running scenario you wish to change.
Example
The following command applies changes to the scenario called FileServer:
Apply-PendingRuntimeChangeableScenarioProperties FileServer
The result is a list of properties and their values:
error_source : engine_verification_error
error_level: Error
host_index: 2
root_dir_index: 0
property_xpath: Scenario.ReplicationTree.ReplNode.ReplNode.SpecificReplicaProps. ReplicaScheduledTask.Suspend.SuspendScript.Path
The Discard-AllPendingRuntimeChangeableScenarioProperties command cancels all the changes you configured for all scenarios.
Discard-AllPendingRuntimeChangeableScenarioProperties
None
The Discard-RuntimeChangeableScenarioProperties command lets you cancel any changes made on the specified running scenario.
Discard-RuntimeChangeableScenarioProperties [Name]
Name - This is the name of the running scenario for which you wish to discard changes.
Example
If you have made numerous changes to a running scenario called FileServer and discover problems, use the following command to set the scenario back to all original values:
Discard-RuntimeChangeableScenarioProperties FileServer
All changes made to the scenario called FileServer are reset back to their original values.
If you wish to set only a specific property back to its original value, use the Set-RuntimeChangeableScenarioProperties command to change only the specified property for the running scenario. Note that when you have discarded changes, all records in the Get-AllPendingRuntimeChangeableScenarioProperties list are deleted. Running Apply-PendingRuntimeChangeableScenarioProperties results in a warning message that the specified scenario was not changed at run time.
The Get-AllPendingRuntimeChangeableScenarioProperties command lists all the scenarios that were changed while running.
Get-AllPendingRuntimeChangeableScenarioProperties
None
Example
The following command lists all the scenarios changed while running.
Get-AllPendingRuntimeChangeableScenarioProperties
The result is a list of scenario names.
The Get-AllRuntimeChangeableScenarioProperties command enables you to list all the properties that can be changed while any scenario is running.
get-AllRuntimeChangeableScenarioProperties
None
Example:
The following code issues the command to list all editable properties and redirect the output to a text file.
Get-AllRuntimeChangeableScenarioProperties > d:\1.txt
The result is a set of the editable properties in Scenario/Master/Replica/PropertyName format.
The Get-RuntimeChangeableScenarioProperties command enables you to find all the properties you can edit while the specified scenario is running. The command returns a list of the properties you may change for that scenario. Combine with I/O redirection commands to format output to a text file.
Get-RuntimeChangeableScenarioProperties [Name]
Name - the name of the running scenario
Example:
The following command lists all the editable properties for the scenario called File Server Scenario 1:
Get-RuntimeChangeableScenarioProperties FileServerScenario1
Property: False
Host: 10.0.0.0
Value: False
Index: 111
Category: Replica
Name: SpecificReplicaProps.Suspend.SuspendScript
The Get-PendingRuntimeChangeableScenarioProperties command lets you list all the changes made to the specified running scenario.
Get-PendingRuntimeChangeableScenarioProperties [Name]
Name - The name of the running scenario
Example:
The following example shows the list of all properties changed for the scenario called FileServer:
Get-PendingRuntimeChangeableScenarioProperties FileServer
The result is a list of Properties, their Original Values and their New Values.
The Set-RuntimeChangeableScenarioProperty command enables you to update the value of the specified property in the named scenario while it is running.
Set-RuntimeChangeableScenarioProperty [Name] [Index] [Value] [Host]
Name - The name of the running scenario whose properties you wish to change.
Index - The index or name of the property you want to change. To determine correct names, use the Get-AllRuntimeChangeableScenarioProperties or the Get-RuntimeChangeableScenarioProperties commands. The index value is generated internally; for two scenarios even of the same type, the same property can have a different index. Ensure you obtain the correct indexes or names.
Value - The new setting for the specified property.
Host - (Optional) The host needs to be specified only for Master or Replica property changes. For generic or HA properties, this value is optional.
Example:
The following command updates the argument of the suspend script property based on its name:
Set-RuntimeChangeableScenarioProperty FileServer SpecificReplicaProps.Suspend.SuspendScript 456 -Host 10.0.0.1
The result is a table showing the Property, its Original Value and the New Value.
The Test-RuntimeChangeableScenarioProperty command lets you confirm whether the specified property can still be edited while the scenario is running.
Test-RuntimeChangeableScenarioProperty [Name] [Index] [Host]
Name - The name of the running scenario
Index - The index or name of the property you wish to test
Host - Optional
Example
The following command tests the property whose index is 113 for a running scenario called FileServer.
Test-RuntimeChangeableScenarioProperty FileServer 113 -host 10.0.0.3
The result is a true or false value for the index or property name specified.
This section describes CA ARCserve RHA PowerShell commands that enable you to monitor the DR and HA processes.
The Get-Dirs command enables you to list all root directories of a given scenario.
Get-Dirs [-Name] <String>
The scenario name.
Example: List the root directories of a given scenario
get-dirs "File Server 1"
ID : 2721474912
Scenario : File Server 1
Master : 192.168.1.152
Path : C:/Tools
DB : False
The Get-Events command displays a list of replication events of a given scenario. The event list can include informational, warning and error events. The displayed information consists of the event ID, the event date and time, the scenario name, the event severity and the event message.
Get-Events [-Name] <String>
The name of the scenario whose events you want to view.
Example: List events of a given scenario in an auto-sized format table
get-events "File Server 1" | FT -auto
ID Time Scenario Severity Message
-- ---- -------- -------- -------
SM00165 10/28/2008 6:02:52 PM File Server 1 Significant Connected to...
SR00014 10/30/2008 7:17:31 PM File Server 1 Significant Starting...
SR00139 10/30/2008 7:17:35 PM File Server 1 Significant Starting File...
IR00119 10/30/2008 7:18:16 PM File Server 1 Info Root directory...
SR00120 10/30/2008 7:18:16 PM File Server 1 Significant Synchronization...
IM00405 10/30/2008 7:15:06 PM File Server 1 Info Posting...
SR00202 10/30/2008 7:18:21 PM File Server 1 Significant All modifications...
SR00096 11/3/2008 6:47:40 PM File Server 1 Significant Stopping scenario...
The Get-Group command enables you to list all scenario groups that carry a given name. To display this list, you need to enter the name you are searching for.
In addition, this command enables you to list all existing scenario groups. To list all scenario groups, just enter the command without a scenario name.
Get-group [[-GroupName] [<String>]]
The name of the scenario group.
Note: You can use the '*" or "?" wildcards as part of the scenario group name.
Example: List all scenario groups that carry a given name
get-group *Server*
File Server Scenarios 2
File Server Scenarios 1
Exchange Server Scenarios
File Server Scenarios
The Get-Hosts command enables you to list all hosts of a given scenario.
Get-Hosts [-Name] <String>
The scenario name.
Example: List the hosts of a given scenario in an auto-sized format table
Get-Hosts "File Server 1" |FT -auto
Scenario Name Role Parent State IP Port
-------- ---- ---- ------ ----- -- ----
File Server 1 192.168.1.152 Master -- Running 192.168.1.152 25000
File Server 1 192.168.1.153 Replica 1192.168.1.152 Running 192.168.1.153 25000
The Get-Scenario command enables you to list all scenarios that carry a given name. To display this list, you need to enter the name you are searching for.
In addition, this command enables you to list all existing scenarios. To list all scenarios, just enter the command without a scenario name.
Get-Scenario [[-Name] [<String>]]
The scenario name.
Note: You can use the '*" or "?" wildcards as part of the scenario name.
Example: List all scenarios that carry a given name in an auto-sized format table
get-scenario File* |FT -auto
ID Group Name Type Master State Sync AR
-- ----- ---- ---- ------ ----- ---- --
1123633852 Scenarios FileServer FileServer Unknown File False
1123633468 Scenarios File Server 1 FileServer 192.168.1.153 Stopped File False
The Get-Snapshot command enables you to display all VSS snapshots of a given Replica Host.
Get-Snapshot [-Name] <String> [[-Port] <String>]
The name of the host as it appears in the scenario.
The connection port to the given host. The default port number is 25000.
Example: Display all VSS snapshots of a given Replica host in an auto-sized format table
Get-Snapshot 130.119.173.7 |FT -auto
Index Snapshot Created Exposed Mounted Drive Scenario
----- -------- ------- ------- ------- ----- --------
0 {4f2bb053-5f2d} 11/18/2008 4:03:09 PM False Not Mounted C:/ FileServer
1 {bcbdda2b-6165} 11/18/2008 4:06:00 PM False Not Mounted C:/ FileServer
2 {c1f206be-2ad0} 11/18/2008 4:07:17 PM False Not Mounted C:/ FileServer
The Get-State command enables you to list all the scenarios that are defined for a given host, along with their details and states.
Get-State [-Name] <String>
The name of the host.
Example:
get-state 130.119.185.152
ID : 2505374864 Group : FS Scenarios Name : FS 1 Type : FileServer Master : 130.119.185.152 State : Running Sync : File AR : False
ID : 2721467841 Group : File Server Scenarios Name : File Server 1 Type : FileServer Master : 130.119.185.152 State : Stopped Sync : File AR : False
The Get-Stats command enables you to display scenario statistic per host during a run.
Get-Stats [-Name] <String>
The name of the scenario.
Example: Display replication statistics of a given scenario during a run
get-stats "File Server 1"
Scenario : File Server 1
Name : 192.168.1.152
Role : Master
Spool_Size : 0
Sync_Files : 345
Sync_MBytes : 86
Rep_MBytes : 0
Scenario : File Server 1
Name : 192.168.1.153
Role : Replica
Spool_Size : 0
Sync_Files : 345
Sync_MBytes : 86
Rep_MBytes : 0
This section describes CA ARCserve RHA PowerShell commands that enable you to monitor and manage User Groups and Users for ACL-based Control Service.
Note: A special license is needed for using the ACL commands.
The Get-SuperUserGroup command enables you to display the name of the Super User Group of the connected Control Service.
Get-SuperUserGroup
Note: This command does not have parameters.
Example: Display the name of the Super User Group
Get-SuperUserGroup
QA95-W2K3-SQL\\CA XOsoft Users
The Set-SuperUserGroup command enables you to change the Super User Group.
Set-SuperUserGroup [-GroupName] <String>
The name of the new Super User group.
Example: Change the Super User Group
Set-SuperUserGroup Administrators
Set super user group successfully
The Get-Users command enables you to list all users that belong to the Super User Group.
get-users
Note: This command does not have parameters.
Example: List all users that belong to the Super User Group
get-users
QA95-W2K3\Administrator
QA95-W2K3-SQL\User2
QA95-W2K3-SQL\User1
The Get-ScenarioUsers command enables you to list all users that have rights on a certain scenario.
get-ScenarioUsers [-ScenarioName] <String>
The name of the scenario.
Example: List all users that have rights on a given scenario
Get-ScenarioUsers "File Server"
name
----
QA95-W2K3-SQL\User2
QA95-W2K3-SQL\User1
The Set-ScenarioUser command enables you to assign to a user certain rights on a specific scenario.
Set-ScenarioUser [-Name] <String> [-User] <String> [-Right] <String>
The name of the scenario.
The full name of the user.
The type of rights the user will have on the scenario. Enter one of the following:
A = Admin
C = Control
V = View Only
Example: Assign to a user Control rights on a given scenario
Set-ScenarioUser "File Server" QA95-W2K3-SQL\User2 C
Set user right successfully
The Remove-ScenarioUser command enables you to cancel the rights of a user on a certain scenario.
Remove-ScenarioUser [-Name] <String> [-User] <String>
The name of the scenario.
The name of the user.
Example: Cancel the rights of a user on a given scenario
Remove-ScenarioUser "File Server" QA95-W2K3-SQL\User2
User removed successfully.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |