728x90

https://joinlync.mani4u.co.kr/meet/sojuhyang/HCTHWVVL?sl=1

모임 URL 뒤에 ?sl=1 옵션을 붙여준다.

728x90
728x90

Get-Counter "\LS:USrv - Endpoint Cache\USrv - Active Registered Endpoints","\LS:USrv - Endpoint Cache\USrv - Active Registered Users" | Select-Object -ExpandProperty CounterSamples | Format-Table Path,CookedValue -Auto


Get-Counter "\LS:USrv - Endpoint Cache\USrv - Active Registered Endpoints","\LS:USrv - Endpoint Cache\USrv - Active Registered Users" -ComputerName frontend.contoso.com | Select-Object -ExpandProperty CounterSamples | Format-Table Path,CookedValue -Auto

728x90
728x90

A question that comes up from customers from time to time is how do I get a list of what users are actually using OCS/Lync?  While there’s no built in report to easily tell you what users are actually signing into the environment, there is some information stored in SQL that you can use to help figure out adoption rate in your environment.  The information we’re looking for is stored in the LastNewRegisterTime column in the HomedResourceDynamic table in the rtcdyn database.  You can run the following queries* to pull back the user’s SIP URI and their last registration time:

For Lync Server 2010/2013

USE rtcdyn
SELECT rtc.dbo.Resource.UserAtHost, rtcdyn.dbo.HomedResourceDynamic.LastNewRegisterTime
FROM rtcdyn.dbo.HomedResourceDynamic
INNER JOIN rtc.dbo.Resource on rtc.dbo.Resource.ResourceId = rtcdyn.dbo.HomedResourceDynamic.OwnerId
INNER JOIN rtcdyn.dbo.RegistrarEndpoint ON rtcdyn.dbo.RegistrarEndpoint.OwnerId = rtcdyn.dbo.HomedResourceDynamic.OwnerId
WHERE IsServerSource = 0
ORDER BY UserAtHost

Which produces the following output:

For OCS 2007 R2

USE rtcdyn
SELECT rtc.dbo.Resource.UserAtHost, rtcdyn.dbo.HomedResourceDynamic.LastNewRegisterTime
FROM rtcdyn.dbo.HomedResourceDynamic
INNER JOIN rtc.dbo.Resource ON rtc.dbo.Resource.ResourceId = rtcdyn.dbo.HomedResourceDynamic.OwnerId
ORDER BY UserAtHost

Which produces the following output:


Note: A user with a LastNewRegisterTime of NULL is a user that has never logged in, but has been added to someone’s contact list.  You would want to remove these entries from your exported results.

While the query to gather the information is very similar the SQL instance that you connect to to retrieve this information is different depending on which version you’re using.  In OCS 2007 R2 all of this information was stored in the rtcdyn database on the SQL instance that you defined when first creating the pool.  Because of the changes to the registrar functionality in Lync Server 2010 to support survivability, the information that we’re looking for has moved to the RTCLOCAL SQL instance that is stored on each registrar.

You can see this if you compare the HomedResourceDynamic table in the rtcdyn database between the Front End Pool SQL Instance and one of the Front End Server’s RTCLOCAL SQL Instance:

Front End Pool SQL Instance

RTCLOCAL SQL Instance

 

For row 2, OwnerId 12 corresponds to my Lync test user that has logged into the client.  You can see that the information that we’re looking for, LastNewRegisterTime, only gets populated in the RTCLOCAL SQL instance on the Front End Server.  So this means that in Lync Server 2010 you don’t have one place you can go for all of the users homed on that pool.  You will need to run the query and aggregate the data from every registrar in the pool, as well as any SBA/SBS deployed.  The other issue that comes up in an Enterprise Edition pool with multiple Front End Servers is that when users fail-over to another Front End Server in the pool, there is a record created in that Front End Server’s RTCLOCAL rtcdyn database.  After you run the queries and have exported all of the results you would want to clean up the duplicate entries so that you weren’t reporting inflated numbers.

Even though there’s a little work involved in gathering the information this is a fairly easy way to gauge adoption and see which of your users are actually using the OCS/Lync.

Using the Lync Server 2013 Monitoring Server

If you have the Monitoring Server role configured in your environment, and for Lync Server 2013 everyone should!, you can use information contained in the LcsCDR database to pull back the last time a user signed in.  You can run the following query* to pull back the user’s SIP URI and their last login time:

USE LcsCDR
SELECT dbo.Users.UserUri, dbo.UserStatistics.LastLogInTime
FROM dbo.UserStatistics
JOIN dbo.Users ON dbo.Users.UserId = dbo.UserStatistics.UserId
ORDER BY UserUri

Which produces the following output:

The advantage to using the Monitoring Server to obtain this data is that unlike the information contained in the rtcdyn database, the information from the LcsCDR data will persist even when the user isn’t signed into Lync.

 

*These queries are provided for you to use at your own risk.  Please make sure you test before running in a production environment.

728x90
728x90

use rtc


declare @sipQuery nvarchar(250)

set @sipQuery = 'test1@contoso.com'


select FE.Fqdn,R.UserAtHost, * from FrontEnd FE

join RoutingGroupAssignment RGA

On FE.FrontEndId = RGA.FrontEndId

join ResourceDirectory RD

on RGA.RoutingGroupId = RD.RoutingGroupId

join Resource R

on RD.ResourceId = R.ResourceId

where R.UserAtHost = @sipQuery


Aggregated Presence stateDescription

3,000-4,499

Available

4,500-5,999

Available - Idle

6,000-7,499

Busy

7,500-8,999

Busy - Idle

9,000-11,999

Do Not Disturb

12,000-14,999

Be Right Back

15,000-17,999

Away

18,000+

Offline


참고

https://msdn.microsoft.com/en-us/library/bb878933.aspx

http://mikestacy.typepad.com/mike-stacys-blog/2009/08/are-you-really-away.htmlㄴ

728x90
728x90

use rtc

declare @sipQuery nvarchar(250)
set @sipQuery = 'sipusername%'

select Publisher, MIN(Status) as Status
from
(select Publisher, Status=
CASE
when Availability BETWEEN 0 AND 2999 then 'Not defined:'+Availability
when Availability BETWEEN 3000 AND 4499 then 'Available'
when Availability BETWEEN 4500 and 5999 then 'Available - Idle'
when Availability BETWEEN 6000 and 7499 then 'Busy'
when Availability BETWEEN 7500 and 8999 then 'Busy - Idle'
when Availability BETWEEN 9000 and 11999 then 'Do not Disturb'
when Availability BETWEEN 12000 and 14999 then 'Be right back'
when Availability BETWEEN 15000 and 17999 then 'Away'
when Availability > 18000 then 'Offline'
end
from
(
select Publisher,
substring(
substring(PublicationDocument,patIndex('%<availability>%',PublicationDocument)+14,50),0,
patIndex('%<availability>%',substring(PublicationDocument,patIndex('%<availability>%',PublicationDocument)+14,50))
) Availability
from
(select UserAtHost Publisher,ContainerNum,CONVERT(varchar(4000),convert(varbinary(4000),Data)) PublicationDocument
from rtcdyn.dbo.PublishedInstance tblPublishedInstance,
rtc.dbo.Resource tblResource
where tblPublishedInstance.PublisherId = tblResource.ResourceId) as PublishedDocuments
where LEN(replace(PublicationDocument,'aggregateState','')) < LEN(PublicationDocument)
and ContainerNum = 2
) as PublisherAndAvailability
where Publisher like @sipQuery
union
select UserAtHost Publisher, 'Offline-Not Registered Here' Status
from rtc.dbo.Resource
where UserAtHost like @sipQuery) as PublisherAndStatus
group by Publisher


참고

http://mikestacy.typepad.com/mike-stacys-blog/sql/

Container 테이블 설명

https://msdn.microsoft.com/en-us/library/bb879521.aspx

https://msdn.microsoft.com/en-us/library/office/dn454664.aspx

Access Control List Containers

Office Communications Server creates these reserved containers to provide access control functionality.

Container IDDescription

100

Public, Federated subscribers

200

Workplace subscribers

300

Team member subscribers

400

Personal subscribers

32000

Blocked subscribers


Special Containers

Office Communications Server defines special containers for receiving published data.

Container IDDescription

0

A container with an exclusive access scope.

1

Self-presence category data, which includes userPropertiesalertsrccOptionsuserInformation, and calendarData.

2

The server aggregates user, machine, phone and calendar states published to this container. The states are published to container 100, 200, or 400.

3

The server aggregates presence states in this container and publishes the aggregated computer and user states to container 300.


728x90
728x90

[환경]

Windows Server 2008 R2

     

     

파워쉘을 이용하여 사용자 계정에 대한 최근 접속 이력을 체크하고 특정 조건을 사용하여 비활성화 하는 방법

     

     

1. Active Directory 모듈 활성

Get-ADUser, Disable-ADAccount, Move-ADObject 명령을 실행하기 위해 도메인 컨트롤러 서버에서 Active Directory Powershell 모듈을 활성화합니다.

Import-Module ActiveDirectory

     

2. 조회

다음 조건을 만족하는 사용자를 조회합니다.

*조건1. 마지막 로그온 날짜가 30일 이상 지남

Get-ADUser -Filter * -Properties "LastLogonDate" | sort-object -property lastlogondate -descending | where-object {$_.LastLogonDate -le ((get-date).AddDays(-30))} | where-object {$_.LastLogonDate -ne $null} | Format-Table -property name, lastlogondate, DistinguishedName, Enabled -AutoSize

   

3. 계정 Disable

다음 조건을 만족하는 사용자는 상태를 disable로 변경합니다.

*조건1. 마지막 로그온 날짜가 30일 이상 지남

Get-ADUser -Filter * -Properties "LastLogonDate" | where-object {$_.LastLogonDate -le ((get-date).AddDays(-30))} | where-object {$_.LastLogonDate -ne $null} | Disable-ADAccount

     

결과> 계정 상태 변경 (disable)

     

4. 계정 OU 이동

다음 조건을 만족하는 사용자를 "Prison" OU로 이동합니다.

*조건1. 마지막 로그온 날짜가 30일 이상 지남

*조건2. Disable 상태

Get-ADUser -Filter * -Properties "LastLogonDate" | where-object {$_.LastLogonDate -le ((get-date).AddDays(-30))}

| where-object {$_.LastLogonDate -ne $null} | where-object {$_.Enabled -eq $false} | Move-ADObject -TargetPath "OU=Pris

on,DC=corp,DC=hypark,DC=lab"

     

결과> Users2 에서 Prison 으로 OU 변경 됨

728x90
728x90
  • Exchange Server에서 PartnerApplication 설정

    "C:\Program Files\Microsoft\Exchange Server\V15\Scripts\Configure-EnterprisePartnerApplication.ps1 -AuthMetaDataUrl 'https://pool01.koreare.com/metadata/json/1' -ApplicationType Lync"

       

       

    • SFB 서버에서 서버간 인증구성

       

    • SFB서버에서 Exchange 서버를 파트너어플리케이션으로 생성

    New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl "https://autodiscover.koreare.com/autodiscover/metadata/json/1"

       

    • SFB Server에서 테스트 진행(success면 성공)

PS C:\Users\administrator.KOREARE> Test-CsExStorageConnectivity -sipuri "iu@kore

are.com" -Verbose

자세한 정보 표시: Successfully opened a connection to storage service at

localhost using binding: NetNamedPipe.

자세한 정보 표시: Create message.

자세한 정보 표시: Execute Exchange Storage Command.

자세한 정보 표시: Processing web storage response for ExCreateItem Success.,

result=Success, activityId=9b682e2e-536a-481c-b8b9-749ad889ac7a, reason=.

자세한 정보 표시: Activity tracing:

2016-04-19 08:10:58.966 Lookup user details, sipUri=sip:iu@koreare.com,

smtpAddress=iu@koreare.com, sid=S-1-5-21-1919050813-91945802-1330746039-1638,

upn=iu@koreare.com, tenantId=00000000-0000-0000-0000-000000000000

2016-04-19 08:10:59.014 Autodiscover, send GetUserSettings request,

SMTP=iu@koreare.com, Autodiscover

Uri=https://autodiscover.koreare.com/autodiscover/autodiscover.svc, Web

Proxy=<NULL>

2016-04-19 08:10:59.044 Autodiscover.EWSMA trace,

type=AutodiscoverRequestHttpHeaders, message=<Trace

Tag="AutodiscoverRequestHttpHeaders" Tid="82" Time="2016-04-19 08:10:59Z">

POST /autodiscover/autodiscover.svc HTTP/1.1

Content-Type: text/xml; charset=utf-8

Accept: text/xml

User-Agent: ExchangeServicesClient/15.00.1005.003

   

   

</Trace>

   

2016-04-19 08:10:59.063 Autodiscover.EWSMA trace, type=AutodiscoverRequest,

message=<Trace Tag="AutodiscoverRequest" Tid="82" Time="2016-04-19 08:10:59Z"

Version="15.00.1005.003">

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope

xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover"

xmlns:wsa="http://www.w3.org/2005/08/addressing"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Header>

<a:RequestedServerVersion>Exchange2013</a:RequestedServerVersion>

   

<wsa:Action>http://schemas.microsoft.com/exchange/2010/Autodiscover/Autodiscove

r/GetUserSettings</wsa:Action>

   

<wsa:To>https://autodiscover.koreare.com/autodiscover/autodiscover.svc</wsa:To>

   

</soap:Header>

<soap:Body>

<a:GetUserSettingsRequestMessage

xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover">

<a:Request>

<a:Users>

<a:User>

<a:Mailbox>iu@koreare.com</a:Mailbox>

</a:User>

</a:Users>

<a:RequestedSettings>

<a:Setting>InternalEwsUrl</a:Setting>

<a:Setting>ExternalEwsUrl</a:Setting>

<a:Setting>ExternalEwsVersion</a:Setting>

</a:RequestedSettings>

</a:Request>

</a:GetUserSettingsRequestMessage>

</soap:Body>

</soap:Envelope>

</Trace>

   

2016-04-19 08:10:59.569 Autodiscover.EWSMA trace,

type=AutodiscoverResponseHttpHeaders, message=<Trace

Tag="AutodiscoverResponseHttpHeaders" Tid="82" Time="2016-04-19 08:10:59Z">

HTTP/1.1 200 OK

Transfer-Encoding: chunked

request-id: b628865a-b7b6-4244-886b-2bce32c62d2c

X-CalculatedBETarget: ex16.koreare.com

X-DiagInfo: EX16

X-BEServer: EX16

X-FEServer: EX16

Cache-Control: private

Content-Type: text/xml; charset=utf-8

Date: Tue, 19 Apr 2016 08:10:59 GMT

Set-Cookie:

X-BackEndCookie=actas1(sid:S-1-5-21-1919050813-91945802-1330746039-1638|smtp:iu

@koreare.com|upn:iu@koreare.com)=u56Lnp2ejJqBmZrHnc3KzJzSmcjNztLLzZ7I0p2bx57SnJ

qdzs2dy8nGyczGgYHNz87J0s/K0s7Gq8/Hxc7PxcrGgZSQjZqejZrRnJCSgc8=; expires=Thu,

19-May-2016 08:10:59 GMT; path=/autodiscover; secure; HttpOnly

Server: Microsoft-IIS/8.5

X-AspNet-Version: 4.0.30319

X-Powered-By: ASP.NET

   

   

</Trace>

   

2016-04-19 08:10:59.570 Autodiscover.EWSMA trace, type=AutodiscoverResponse,

message=<Trace Tag="AutodiscoverResponse" Tid="82" Time="2016-04-19 08:10:59Z"

Version="15.00.1005.003">

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:a="http://www.w3.org/2005/08/addressing">

<s:Header>

<a:Action

s:mustUnderstand="1">http://schemas.microsoft.com/exchange/2010/Autodiscover/Au

todiscover/GetUserSettingsResponse</a:Action>

<h:ServerVersionInfo

xmlns:h="http://schemas.microsoft.com/exchange/2010/Autodiscover"

xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

<h:MajorVersion>15</h:MajorVersion>

<h:MinorVersion>1</h:MinorVersion>

<h:MajorBuildNumber>225</h:MajorBuildNumber>

<h:MinorBuildNumber>41</h:MinorBuildNumber>

<h:Version>Exchange2015</h:Version>

</h:ServerVersionInfo>

</s:Header>

<s:Body>

<GetUserSettingsResponseMessage

xmlns="http://schemas.microsoft.com/exchange/2010/Autodiscover">

<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

<ErrorCode>NoError</ErrorCode>

<ErrorMessage />

<UserResponses>

<UserResponse>

<ErrorCode>NoError</ErrorCode>

<ErrorMessage>오류가 없습니다.</ErrorMessage>

<RedirectTarget i:nil="true" />

<UserSettingErrors />

<UserSettings>

<UserSetting i:type="StringSetting">

<Name>InternalEwsUrl</Name>

<Value>https://mail.koreare.com/EWS/Exchange.asmx</Value>

</UserSetting>

<UserSetting i:type="StringSetting">

<Name>ExternalEwsUrl</Name>

<Value>https://mail.koreare.com/ews/exchange.asmx</Value>

</UserSetting>

<UserSetting i:type="StringSetting">

<Name>ExternalEwsVersion</Name>

<Value>15.01.0225.000</Value>

</UserSetting>

</UserSettings>

</UserResponse>

</UserResponses>

</Response>

</GetUserSettingsResponseMessage>

</s:Body>

</s:Envelope>

</Trace>

   

2016-04-19 08:10:59.605 Autodiscover, received GetUserSettings response,

duration Ms=589, response=NoError

2016-04-19 08:11:01.697 Lookup user details, sipUri=sip:iu@koreare.com,

smtpAddress=iu@koreare.com, sid=S-1-5-21-1919050813-91945802-1330746039-1638,

upn=iu@koreare.com, tenantId=00000000-0000-0000-0000-000000000000

자세한 정보 표시: Items choice type: CreateItemResponseMessage.

자세한 정보 표시: Response message, class: Success, code: NoError.

자세한 정보 표시: Item:

Microsoft.Rtc.Internal.Storage.Exchange.Ews.MessageType, Id:

AAMkADM3YWM1NGU3LWI2ZmQtNGE3OS1iZjkxLWEyNWI3YzMyNzlkNABGAAAAAAASKHyaongGQoN9klK

qwo7tBwDYpKMYqsX0T5qOmJzkL3KFAAAAlsY0AADYpKMYqsX0T5qOmJzkL3KFAAAK/EftAAA=,

change key: CQAAABYAAADYpKMYqsX0T5qOmJzkL3KFAAAK+5Gs, subject: , body: .

자세한 정보 표시: Is command successful: True.

Test passed.

PS C:\Users\administrator.KOREARE>

   

   

  • SFB서버에서 Exchange 트러스트 어플리케이션 풀 생성 해줍니다.(하기는 미리 구성 되어 있어서 설정값만 수정 후 조회했습니다.)

    또한 5199포트로 OutlookWebapp에 대한 트러스트어플리케이션 생성

   

  • Exchange 서버에서 OCS 사용 설정

   

  • Exchange 서버에서 IM(노란색 참조)

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Set-OwaMailboxPolicy -Identity "Default" -InstantMessagingEn

abled $True -InstantMessagingType "OCS"

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>New-SettingOverride SetIMServerNameEX16 -Server EX16 -Compon

ent OwaServer -Section IMSettings -Parameters @('IMServerName=pool01.koreare.com') -Reason "OWA IM config"

   

   

RunspaceId : 58f32e19-d237-4984-90e0-9cf1b5a618a9

ComponentName : OwaServer

SectionName : IMSettings

FlightName :

ModifiedBy : koreare.com/Users/Administrator

Reason : OWA IM config

MinVersion :

MaxVersion :

FixVersion :

Server : {EX16}

Parameters : {IMServerName=pool01.koreare.com}

XmlRaw : <S CN="OwaServer" SN="IMSettings" MB="koreare.com/Users/Administrator" R="OWA IM config"><Ss><S>EX1

6</S></Ss><Ps><P>IMServerName=pool01.koreare.com</P></Ps></S>

AdminDisplayName :

ExchangeVersion : 0.1 (8.0.535.0)

Name : SetIMServerNameEX16

DistinguishedName : CN=SetIMServerNameEX16,CN=Setting Overrides,CN=Global Settings,CN=koreare,CN=Microsoft Exchange,CN=

Services,CN=Configuration,DC=koreare,DC=com

Identity : SetIMServerNameEX16

Guid : dbccc5dc-b624-413b-8062-2eba1d7bebd1

ObjectCategory : koreare.com/Configuration/Schema/ms-Exch-Config-Settings

ObjectClass : {top, msExchConfigSettings}

WhenChanged : 2016-04-19 오후 5:53:43

WhenCreated : 2016-04-19 오후 5:53:43

WhenChangedUTC : 2016-04-19 오전 8:53:43

WhenCreatedUTC : 2016-04-19 오전 8:53:43

OrganizationId :

Id : SetIMServerNameEX16

OriginatingServer : DC01.koreare.com

IsValid : True

ObjectState : Unchanged

   

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>New-SettingOverride SetIMCertificateThumbprintEX16 -Server E

X16 -Component OwaServer -Section IMSettings -Parameters @('IMCertificateThumbprint=D2A9B625C0DD80B594AA0EE7039EB5D078D

2B586') -Reason "OWA IM Config"

   

   

RunspaceId : 58f32e19-d237-4984-90e0-9cf1b5a618a9

ComponentName : OwaServer

SectionName : IMSettings

FlightName :

ModifiedBy : koreare.com/Users/Administrator

Reason : OWA IM Config

MinVersion :

MaxVersion :

FixVersion :

Server : {EX16}

Parameters : {IMCertificateThumbprint=D2A9B625C0DD80B594AA0EE7039EB5D078D2B586}

XmlRaw : <S CN="OwaServer" SN="IMSettings" MB="koreare.com/Users/Administrator" R="OWA IM Config"><Ss><S>EX1

6</S></Ss><Ps><P>IMCertificateThumbprint=D2A9B625C0DD80B594AA0EE7039EB5D078D2B586</P></Ps></S>

AdminDisplayName :

ExchangeVersion : 0.1 (8.0.535.0)

Name : SetIMCertificateThumbprintEX16

DistinguishedName : CN=SetIMCertificateThumbprintEX16,CN=Setting Overrides,CN=Global Settings,CN=koreare,CN=Microsoft E

xchange,CN=Services,CN=Configuration,DC=koreare,DC=com

Identity : SetIMCertificateThumbprintEX16

Guid : f14fe273-9d77-49f5-9c8e-ec8cf8ade2b0

ObjectCategory : koreare.com/Configuration/Schema/ms-Exch-Config-Settings

ObjectClass : {top, msExchConfigSettings}

WhenChanged : 2016-04-19 오후 5:55:10

WhenCreated : 2016-04-19 오후 5:55:10

WhenChangedUTC : 2016-04-19 오전 8:55:10

WhenCreatedUTC : 2016-04-19 오전 8:55:10

OrganizationId :

Id : SetIMCertificateThumbprintEX16

OriginatingServer : DC01.koreare.com

IsValid : True

ObjectState : Unchanged

   

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Get-ExchangeDiagnosticInfo -Server $ENV:COMPUTERNAME -Proces

s Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

   

RunspaceId : 58f32e19-d237-4984-90e0-9cf1b5a618a9

Result : <Diagnostics>

<ProcessInfo>

<id>2168</id>

<serverName>EX16</serverName>

<startTime>2016-04-15T00:28:38.8612397Z</startTime>

<currentTime>2016-04-19T08:55:56.1901401Z</currentTime>

<lifetime>4.08:27:17.3289004</lifetime>

<threadCount>24</threadCount>

<handleCount>1198</handleCount>

<workingSet>83.57 MB (87,633,920 bytes)</workingSet>

</ProcessInfo>

<Components>

<VariantConfiguration>

<Overrides Updated="2016-04-19 오전 8:55:58">

<SettingOverride>

<Name>SetIMCertificateThumbprintEX16</Name>

<Reason>OWA IM Config</Reason>

<ModifiedBy>koreare.com/Users/Administrator</ModifiedBy>

<ComponentName>OwaServer</ComponentName>

<SectionName>IMSettings</SectionName>

<Status>Accepted</Status>

<Message>This override synced to the server but whether it applies to the services running on t

his server depends on the override parameters, current configuration and the context.</Message>

<Parameters>

<Parameter>IMCertificateThumbprint=D2A9B625C0DD80B594AA0EE7039EB5D078D2B586</Parameter>

</Parameters>

</SettingOverride>

<SettingOverride>

<Name>SetIMServerNameEX16</Name>

<Reason>OWA IM config</Reason>

<ModifiedBy>koreare.com/Users/Administrator</ModifiedBy>

<ComponentName>OwaServer</ComponentName>

<SectionName>IMSettings</SectionName>

<Status>Accepted</Status>

<Message>This override synced to the server but whether it applies to the services running on t

his server depends on the override parameters, current configuration and the context.</Message>

<Parameters>

<Parameter>IMServerName=pool01.koreare.com</Parameter>

</Parameters>

</SettingOverride>

</Overrides>

</VariantConfiguration>

</Components>

</Diagnostics>

Identity :

IsValid : True

ObjectState : New

   

   

   

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>

   

  • 클라이언트에서 OWA에 접속하여 Presence 상태가 나오는지 확인
  • OWA에서 IM 테스트


728x90
728x90

누가 언제 계정을 삭제 했는지 확인 해 달라는 경우가 있습니다.

GPO를 이용한 계정 감사를 해보았습니다.

   

계정 관리 감사 활성화 방법입니다.

  • 그룹 정책 관리 -> Default Domain Policy -> 편집 -> 컴퓨터 구성 -> Windows 설정 -> 보안 설정 -> 로컬 정책 -> 감사 정책

  • 계정 관리 감사 정책 활성화

  • 실행 -> cmd -> gpupdate /force 실행

       

    상위와 같이 계정 관리 감사 정책을 활성화 하면 계정 생성 및 삭제 된 정보가 이벤트 로그에 남게 됩니다.

       

  • 계정 생성 테스트

    계정을 생성하게 되면 하기와 같이 4738 이벤트가 발생

  • 계정 삭제 테스트

    계정을 삭제하면 하기와 같이 4726 이벤트가 발생

                

       


728x90
728x90

Enable-ADOptionalFeature –Identity "CN=RecycleBin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=koreare,DC=com" –Scope ForestOrConfigurationSet –Target "koreare.com"

   

Get-ADObject -SearchBase "CN=Deleted Objects,DC=koreare,DC=com" -ldapFilter "(objectClass=*)" -includeDeletedObjects | Format-List Name,ObjectClass,ObjectGuid

   

Restore-ADObject –identity c6cbe4b3-ed3d-45d6-ab46-fd6223ca7075

   

생성 된 계정 확인

   

끝.

728x90
728x90

-          Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -Name PrivateTimeout -Value <amount of time> -Type DWORD

-          Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -Name PublicTimeout -Value <amount of time> -Type DWORD

 

위의 명령어 두줄을 실행하시되, <amount of time> 에는 분단위로 세션을 지속시킬 시간을 설정 합니다. ( 단위로 1 ~ 43,200 까지 설정 가능 합니다.)

 

-          , 쿠키의 세션 타임 아웃을 8시간으로 설정하는 경우 아래와 같이 Value 값을 480으로 설정

o    Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -Name PrivateTimeout -Value 480 -Type DWORD

o    Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -Name PublicTimeout -Value 480 -Type DWORD

728x90

+ Recent posts