Skip to content

Commit c5d96ad

Browse files
kenwithkenwith
authored
Merge pull request MicrosoftDocs#170 from nsshommo/nasim
Cleanup and Consolidate
2 parents 38d5dd1 + 0466965 commit c5d96ad

File tree

6 files changed

+157
-5754
lines changed

6 files changed

+157
-5754
lines changed

‎exchange/exchange-ps/exchange/Export-UMCallDataRecord.md

Lines changed: 3 additions & 83 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,6 @@ schema: 2.0.0
66
# Export-UMCallDataRecord
77

88
## SYNOPSIS
9-
!!! Exchange Server 2010
10-
11-
Use the Export-UMCallDataRecord cmdlet to export Unified Messaging (UM) call data records for UM dial plans and UM IP gateways for a date that you've specified.
12-
13-
!!! Exchange Server 2013
14-
159
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
1610

1711
Use the Export-UMCallDataRecord cmdlet to export Unified Messaging (UM) call data records for UM dial plans and UM IP gateways for a date that you've specified.
@@ -22,23 +16,10 @@ For information about the parameter sets in the Syntax section below, see Exchan
2216

2317
```
2418
Export-UMCallDataRecord -ClientStream <Stream> -Date <ExDateTime> [-Confirm] [-DomainController <Fqdn>]
25-
[-Organization <OrganizationIdParameter>] [-UMDialPlan <UMDialPlanIdParameter>]
26-
[-UMIPGateway <UMIPGatewayIdParameter>] [-WhatIf] [<CommonParameters>]
19+
[-UMDialPlan <UMDialPlanIdParameter>] [-UMIPGateway <UMIPGatewayIdParameter>] [-WhatIf] [<CommonParameters>]
2720
```
2821

2922
## DESCRIPTION
30-
!!! Exchange Server 2010
31-
32-
The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records for a specified date to a comma separated value (.csv) file. You can filter call data records for specific UM dial plans and/or UM IP gateways; however, if you don't specify a UM IP gateway, all call data records will be returned.
33-
34-
The Export-UMCallDataRecord cmdlet is available when you're using the Exchange Control Panel. You can't use the cmdlet from the Exchange Management Shell.
35-
36-
After this task is completed, a report is generated that contains Unified Messaging call data records.
37-
38-
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "UM call data and summary reports" entry in the Unified Messaging Permissions topic.
39-
40-
!!! Exchange Server 2013
41-
4223
The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records for a specified date to a comma-separated value (CSV) file. You can filter call data records for specific UM dial plans or UM IP gateways. However, if you don't specify a UM IP gateway, all call data records are returned.
4324

4425
The Export-UMCallDataRecord cmdlet is available when you're using the Exchange Administration Center. You can't use the cmdlet from the Exchange Management Shell.
@@ -49,28 +30,14 @@ You need to be assigned permissions before you can run this cmdlet. Although all
4930

5031
## EXAMPLES
5132

52-
### Example 1 -------------------------- (Exchange Server 2010)
53-
```
54-
Export-UMCallDataRecord -Date 02/01/10
55-
```
56-
57-
This example returns all Unified Messaging call data records and exports them to a CSV file.
58-
59-
### Example 1 -------------------------- (Exchange Server 2013)
33+
### Example 1
6034
```
6135
Export-UMCallDataRecord -Date 02/01/12
6236
```
6337

6438
This example returns all Unified Messaging call data records on February 1, 2012, and exports them to a CSV file.
6539

66-
### Example 2 -------------------------- (Exchange Server 2010)
67-
```
68-
Export-UMCallDataRecord -Date 02/01/10 -UMDialPlan MyUMDialPlan
69-
```
70-
71-
This example exports all Unified Messaging call data records for February 1, 2010 for the UM dial plan MyUMDialPlan.
72-
73-
### Example 2 -------------------------- (Exchange Server 2013)
40+
### Example 2
7441
```
7542
Export-UMCallDataRecord -Date 02/01/12 -UMDialPlan MyUMDialPlan
7643
```
@@ -96,18 +63,8 @@ Accept wildcard characters: False
9663
```
9764
9865
### -Date
99-
!!! Exchange Server 2010
100-
101-
The Date parameter specifies the date of Unified Messaging call data records to retrieve, in the last 90 days. If there are no call records for the date specified, the report will be empty.
102-
103-
104-
105-
!!! Exchange Server 2013
106-
10766
The Date parameter specifies the date of Unified Messaging call data records to retrieve. If there are no call records for the date specified, the report will be empty.
10867
109-
110-
11168
```yaml
11269
Type: ExDateTime
11370
Parameter Sets: (All)
@@ -142,20 +99,10 @@ Accept wildcard characters: False
14299
```
143100
144101
### -DomainController
145-
!!! Exchange Server 2010
146-
147-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
148-
149-
150-
151-
!!! Exchange Server 2013
152-
153102
This parameter is available only in on-premises Exchange.
154103
155104
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
156105
157-
158-
159106
```yaml
160107
Type: Fqdn
161108
Parameter Sets: (All)
@@ -169,35 +116,9 @@ Accept pipeline input: False
169116
Accept wildcard characters: False
170117
```
171118
172-
### -Organization
173-
The Organization parameter is reserved for internal Microsoft use.
174-
175-
```yaml
176-
Type: OrganizationIdParameter
177-
Parameter Sets: (All)
178-
Aliases:
179-
Applicable: Exchange Server 2010
180-
181-
Required: False
182-
Position: Named
183-
Default value: None
184-
Accept pipeline input: False
185-
Accept wildcard characters: False
186-
```
187-
188119
### -UMDialPlan
189-
!!! Exchange Server 2010
190-
191-
The UMDialPlan parameter specifies the UM dial plan to export statistics for. If you don't specify a UM dial plan, statistics include all UM dial plans in the organization
192-
193-
194-
195-
!!! Exchange Server 2013
196-
197120
The UMDialPlan parameter specifies the UM dial plan to export statistics for. If you don't specify a UM dial plan, statistics include all UM dial plans in the organization.
198121
199-
200-
201122
```yaml
202123
Type: UMDialPlanIdParameter
203124
Parameter Sets: (All)
@@ -261,4 +182,3 @@ To see the return types, which are also known as output types, that this cmdlet
261182
## RELATED LINKS
262183
263184
[Online Version](https://technet.microsoft.com/library/974bfc60-6c9c-4452-877b-3a302f39dd95.aspx)
264-

‎exchange/exchange-ps/exchange/Get-LogonStatistics.md

Lines changed: 2 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,7 @@ schema: 2.0.0
66
# Get-LogonStatistics
77

88
## SYNOPSIS
9-
!!! Exchange Server 2010
10-
11-
Use the Get-LogonStatistics cmdlet to retrieve logon statistics, such as user name, logon time, last access time, client version, and adapter speed.
12-
13-
!!! Exchange Server 2013
9+
This cmdlet is available only in on-premises Exchange and is only functional in Exchange Server 2010.
1410

1511
The Get-LogonStatistics cmdlet has been deprecated and is no longer used.
1612

@@ -41,39 +37,24 @@ Get-LogonStatistics -Server <ServerIdParameter> [-DomainController <Fqdn>] [<Com
4137
```
4238

4339
## DESCRIPTION
44-
!!! Exchange Server 2010
45-
4640
The Get-LogonStatistics cmdlet retrieves logon information about currently active sessions. On Mailbox servers only, you can use the Get-LogonStatistics cmdlet without parameters. In this case, the cmdlet returns the logon statistics for all mailboxes on all databases on the local server.
4741

4842
Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you may see few or no logon statistics for Outlook Web App, even if users are logged on with this client.
4943

5044
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic.
5145

52-
!!! Exchange Server 2013
53-
54-
This cmdlet has been deprecated and is no longer used.
55-
5646
## EXAMPLES
5747

58-
### Example 1 -------------------------- (Exchange Server 2010)
48+
### Example 1
5949
```
6050
Get-LogonStatistics -Server Server01
6151
```
6252

6353
This example returns logon statistics for all users connected to the server Server01.
6454

65-
### Example 1 -------------------------- (Exchange Server 2013)
66-
```
67-
Get-LogonStatistics
68-
```
69-
70-
This cmdlet has been deprecated and is no longer used.
71-
7255
## PARAMETERS
7356

7457
### -Database
75-
!!! Exchange Server 2010
76-
7758
The Database parameter specifies the name of the mailbox database. When you specify a value for the Database parameter, the Exchange Management Shell returns logon statistics for all the mailboxes in the database specified.
7859

7960
You can use the following value:
@@ -82,14 +63,6 @@ You can use the following value:
8263

8364
This parameter accepts pipeline input from the Get-MailboxDatabase command.
8465

85-
86-
87-
!!! Exchange Server 2013
88-
89-
This parameter is reserved for internal Microsoft use.
90-
91-
92-
9366
```yaml
9467
Type: DatabaseIdParameter
9568
Parameter Sets: Set2, Set3
@@ -104,8 +77,6 @@ Accept wildcard characters: False
10477
```
10578
10679
### -Identity
107-
!!! Exchange Server 2010
108-
10980
The Identity parameter specifies a mailbox for which you want to obtain logon statistics. You can use one of the following values:
11081
11182
- GUID
@@ -124,14 +95,6 @@ The Identity parameter specifies a mailbox for which you want to obtain logon st
12495
12596
This parameter accepts pipeline input from the Get-Mailbox command.
12697
127-
128-
129-
!!! Exchange Server 2013
130-
131-
This parameter is reserved for internal Microsoft use.
132-
133-
134-
13598
```yaml
13699
Type: LogonableObjectIdParameter
137100
Parameter Sets: Set2
@@ -159,8 +122,6 @@ Accept wildcard characters: False
159122
```
160123
161124
### -Server
162-
!!! Exchange Server 2010
163-
164125
The Server parameter specifies the server from which you want to obtain logon statistics. You can use one of the following values:
165126
166127
- Fully qualified domain name (FQDN)
@@ -171,14 +132,6 @@ When you specify a value for the Server parameter, the command returns logon sta
171132
172133
This parameter accepts pipeline input from the Get-ExchangeServer and Get-MailboxServer commands.
173134
174-
175-
176-
!!! Exchange Server 2013
177-
178-
This parameter is reserved for internal Microsoft use.
179-
180-
181-
182135
```yaml
183136
Type: ServerIdParameter
184137
Parameter Sets: Set3, Set4
@@ -193,18 +146,8 @@ Accept wildcard characters: False
193146
```
194147
195148
### -DomainController
196-
!!! Exchange Server 2010
197-
198149
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
199150
200-
201-
202-
!!! Exchange Server 2013
203-
204-
This parameter is reserved for internal Microsoft use.
205-
206-
207-
208151
```yaml
209152
Type: Fqdn
210153
Parameter Sets: (All)
@@ -236,4 +179,3 @@ To see the return types, which are also known as output types, that this cmdlet
236179
## RELATED LINKS
237180
238181
[Online Version](https://technet.microsoft.com/library/c06f202e-2302-4122-a514-9d11b6ad2c47.aspx)
239-

0 commit comments

Comments
 (0)