Another virus for Android
Rageagainstthecage is a file that can also be used to legitimately root a phone in order for the users to gain administrative rights, but in this case it's used to allow the Trojan to do things like taking screenshots, harvesting IMEI and IMSI numbers and send them to remote sites, and drop a DownloadProvidersManager Android Package that will further execute downloads in the background.
For the full list of the potentially affected apps, go here. In you think you may have installed one of them on your device, check the installed apps against it or check the “running services“ settings on your phone for the DownloadManageService started by an application.
see the full article at http://www.net-security.org/malware_news.php?id=1648
-Dario
Wednesday, March 2, 2011
NEWS!!!!! -- Intel Completes Acquisition of McAfee
Se confirmó y finalizó!!
SANTA CLARA, Calif., February 28, 2011 - Intel Corporation today announced the acquisition of McAfee, Inc. is complete.
McAfee will continue developing and selling security products and services under its own brand. Intel and McAfee plan to bring the first fruits of their strategic partnership to market later this year, with the intent of tackling security and the pervasive nature of computing threats in an entirely new way.
Intel and McAfee believe today's approach to security does not adequately address the billions of new Internet-ready devices, including PCs, mobile and wireless devices, TVs, cars, medical devices and ATM machines. With the surge in cyber threats, providing protection to a diverse online world requires a fundamentally new approach involving software, hardware and services. Together the two companies will work to help people more securely take full advantage of the potential of computing and connectivity.
As a wholly-owned subsidiary of Intel, McAfee reports into Intel's Software and Services Group. The group is managed by Renée James, Intel senior vice president, and general manager. McAfee's president, Dave DeWalt, will report to James.
"In the past, energy-efficient performance and Internet connectivity have defined computing requirements," said James. "Intel has added security as a third pillar of what people demand from their experiences with personal computers and other connected devices. Security challenges put the future potential of computing at risk. The acquisition of McAfee adds not only world-leading security products and technologies to Intel's computing portfolio, but also brings incredibly
See the full article at http://investor.mcafee.com/releasedetail.cfm?ReleaseID=553305
-Dario
SANTA CLARA, Calif., February 28, 2011 - Intel Corporation today announced the acquisition of McAfee, Inc. is complete.
McAfee will continue developing and selling security products and services under its own brand. Intel and McAfee plan to bring the first fruits of their strategic partnership to market later this year, with the intent of tackling security and the pervasive nature of computing threats in an entirely new way.
Intel and McAfee believe today's approach to security does not adequately address the billions of new Internet-ready devices, including PCs, mobile and wireless devices, TVs, cars, medical devices and ATM machines. With the surge in cyber threats, providing protection to a diverse online world requires a fundamentally new approach involving software, hardware and services. Together the two companies will work to help people more securely take full advantage of the potential of computing and connectivity.
As a wholly-owned subsidiary of Intel, McAfee reports into Intel's Software and Services Group. The group is managed by Renée James, Intel senior vice president, and general manager. McAfee's president, Dave DeWalt, will report to James.
"In the past, energy-efficient performance and Internet connectivity have defined computing requirements," said James. "Intel has added security as a third pillar of what people demand from their experiences with personal computers and other connected devices. Security challenges put the future potential of computing at risk. The acquisition of McAfee adds not only world-leading security products and technologies to Intel's computing portfolio, but also brings incredibly
See the full article at http://investor.mcafee.com/releasedetail.cfm?ReleaseID=553305
-Dario
Tuesday, March 1, 2011
NEWS!!!!! ---Two Android viruses circulating in the wild
28 February 2011
Two Google Android viruses have been spotted circulating and infecting users’ smartphones in the wild. The viruses are potentially nasty because one – SW.SecurePhone – uploads data to remote servers from the users' handset, while the other – SW.Qieting – auto-forwards messages to a remote number.
see the full article at http://mcaf.ee/cb698
-Dario
NEWS!! 500,000 Gmail accounts go offline, some users lose all their data
Folks....Always..always backup your info!!!!!!
Article's digest:
Google is the master of cloud-based services with a track record most would envy for uptime, user numbers, and speed of access. But yesterday a chink in the armor appeared as 500,000 or so Gmail accounts went offline.
Not having access to your account for a few hours may seem like a minor inconvenience, but the extent of the problem seems to be much worse. When access was returned to some accounts they were empty. All traces of e-mails, attachments, chat logs, and contacts were gone. Some users even got the “Welcome to Gmail” message as if they were new to the service.
Google is working on the issue, but as of yet there has been no solution. The last status update on the Apps Status Dashboard for Gmail read:
If an example were needed as to why you should backup your data regularly for cloud-based services, this is surely it.
See the full article
http://www.geek.com/articles/geek-pick/500000-gmail-accounts-go-offline-some-users-lose-all-their-data-20110228/
Article's digest:
Google is the master of cloud-based services with a track record most would envy for uptime, user numbers, and speed of access. But yesterday a chink in the armor appeared as 500,000 or so Gmail accounts went offline.
Not having access to your account for a few hours may seem like a minor inconvenience, but the extent of the problem seems to be much worse. When access was returned to some accounts they were empty. All traces of e-mails, attachments, chat logs, and contacts were gone. Some users even got the “Welcome to Gmail” message as if they were new to the service.
Google is working on the issue, but as of yet there has been no solution. The last status update on the Apps Status Dashboard for Gmail read:
Our team is continuing to investigate this issue. We will provide an update by February 28, 2011 11:00:00 AM UTC with more information about this problem. Thank you for your patience.This is the second issue to happen with one of the Google Apps recently. Last Wednesday Google Calendar suddenly lost all its events for some users. At the time Google quoted 0.125% of users were affected, although it seemed like a lot more from the mounting complaints that day. This time round 0.29% of Gmail users are having issues. It’s also interesting to note that when Calendar events disappeared Gmail was also having issues and blocking some users’ access. Could this be related to that problem?
If an example were needed as to why you should backup your data regularly for cloud-based services, this is surely it.
See the full article
http://www.geek.com/articles/geek-pick/500000-gmail-accounts-go-offline-some-users-lose-all-their-data-20110228/
Friday, February 25, 2011
Hey dude! Where is my Isinteg in Exchange 2010 Sp1????
UPDATED!
doesn't longer exists ...
ISInteg has offered Exchange administrators a way to check mailbox and public folder database integrity. ISInteg checks and fixes Exchange database errors that may prevent the database from mounting, prevent the user from logging on or from receiving, opening or deleting email. Curious to know what changes are coming to ISInteg in Exchange 2010 SP1? Let's take a look.
Also ISInteg is no longer a standalone program.
The functionality provided by the ISInteg tool has been rolled into two new Exchange Management Shell cmdlets:
New-MailboxRepairRequest
New-PublicFolderDatabaseRepairRequest
These new ISInteg cmdlets come with some cool new functionality!
The cmdlets work with the database mounted. It's no longer required to unmount the database to perform an integrity check or fix database errors.
You can repair logical corruption at the mailbox level.
You can fix corrupt search folders.
You can fix the Provisional Fid.
You can fix Aggregate Counts.
ISInteg can now work at the database or mailbox level
How does it do that? Well, the new schema in Exchange 2010 effectively partitions the database by mailbox. So the top problems fixed by ISInteg are now mostly limited to the affected mailboxes only. Previous versions of ISInteg required the database to be offline while validation and fixing are in progress. In Exchange 2010 SP1, the ability to do these checks at the mailbox level removes the need to dismount the database. It is actually required to have ISInteg operate against an online database!
New-MailboxRepairRequest
The New-MailboxRepairRequest cmdlet detects and fixes the following types of mailbox corruptions:
Search folder corruptions (SearchFolder): Repair tasks now look for all folders named in ptagSearchBacklinks, ptagSearchFIDs, and ptagRecursiveSearchFIDs and verifies that each folder exists. If the folder no longer exists, then it will remove that folder from the list.
Aggregate counts on folders that aren't reflecting correct values (AggregateCounts): Repair tasks tally all messages in a folder and keep a running total of various counts and sizes. Once the iteration is complete, it will verify the computed counts against the persisted counts on the Folders table record for the folder. If there is a discrepancy, it will update the persisted counts to reflect the computed counts.
Views on folders that aren't returning correct contents (FolderView): Repair tasks will iterate over all views for a folder and for each one, bring the view fully up to date and then reconstruct a temp copy. If there is a discrepancy between the existing view and the contents of the temp table, it will delete the view so it can be rebuilt from scratch the next time it is requested.
Provisioned folders that are incorrectly pointing into unprovisioned parent folders (ProvisionedFolder): Repair tasks can fix Provisioned folders incorrectly pointing into unprovisioned parents or vice versa.
Syntax
New-MailboxRepairRequest -Mailbox <MailboxIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Archive <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]New-MailboxRepairRequest -Database <DatabaseIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]
Parameters
Database, Mailbox and Archive:
You can repair an entire mailbox database or a specified mailbox by specifying either the Database or the Mailbox parameter. You can't use both. To repair the archive mailbox for the specified user, use the Archive switch.
CorruptionType:
(at least 1 required) you are already familiar with, we discussed them above:
SearchFolder
AggregateCounts
ProvisionedFolder
FolderView
You can run a repair task with multiple parameters if you separate them with a comma (as shown in the Examples section below).
DetectOnly: (Optional) The DetectOnly switch secifies that you want this command to report errors, but not fix them. You don't have to specify a value with this switch.
Other Optional Parameters: This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, type "get-help about_commonparameters".
Examples
New-MailboxRepairRequest -Mailbox administrator@contoso.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView
New-MailboxRepairRequest -Mailbox administrator -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView -WhatIf
Event Reporting
After submitting the Mailbox or Public Folder repair request, you can monitor its progress with the Event Viewer. That's right, no more text logs to weed through. The events are logged under the MSExchangeIS Mailbox Store source.
The following event IDs will be logged for repair requests:
10047 A mailbox-level repair request started
10064 A Public Folder repair request started
10048 The repair request successfully completed.
10050 The mailbox repair request task skipped a mailbox .
10059 A database-level repair request started.
10062 Corruption was detected
NOTE: in order to run this cmdlets you new belongs to below managed grop role
Just in case
Organization Management
Server Management
Recipient Management
see http://msexchangeteam.com/archive/2010/08/23/455899.aspx
Enjoy!
-Dario
doesn't longer exists ...
ISInteg has offered Exchange administrators a way to check mailbox and public folder database integrity. ISInteg checks and fixes Exchange database errors that may prevent the database from mounting, prevent the user from logging on or from receiving, opening or deleting email. Curious to know what changes are coming to ISInteg in Exchange 2010 SP1? Let's take a look.
Also ISInteg is no longer a standalone program.
The functionality provided by the ISInteg tool has been rolled into two new Exchange Management Shell cmdlets:
New-MailboxRepairRequest
New-PublicFolderDatabaseRepairRequest
These new ISInteg cmdlets come with some cool new functionality!
The cmdlets work with the database mounted. It's no longer required to unmount the database to perform an integrity check or fix database errors.
You can repair logical corruption at the mailbox level.
You can fix corrupt search folders.
You can fix the Provisional Fid.
You can fix Aggregate Counts.
ISInteg can now work at the database or mailbox level
How does it do that? Well, the new schema in Exchange 2010 effectively partitions the database by mailbox. So the top problems fixed by ISInteg are now mostly limited to the affected mailboxes only. Previous versions of ISInteg required the database to be offline while validation and fixing are in progress. In Exchange 2010 SP1, the ability to do these checks at the mailbox level removes the need to dismount the database. It is actually required to have ISInteg operate against an online database!
New-MailboxRepairRequest
The New-MailboxRepairRequest cmdlet detects and fixes the following types of mailbox corruptions:
Search folder corruptions (SearchFolder): Repair tasks now look for all folders named in ptagSearchBacklinks, ptagSearchFIDs, and ptagRecursiveSearchFIDs and verifies that each folder exists. If the folder no longer exists, then it will remove that folder from the list.
Aggregate counts on folders that aren't reflecting correct values (AggregateCounts): Repair tasks tally all messages in a folder and keep a running total of various counts and sizes. Once the iteration is complete, it will verify the computed counts against the persisted counts on the Folders table record for the folder. If there is a discrepancy, it will update the persisted counts to reflect the computed counts.
Views on folders that aren't returning correct contents (FolderView): Repair tasks will iterate over all views for a folder and for each one, bring the view fully up to date and then reconstruct a temp copy. If there is a discrepancy between the existing view and the contents of the temp table, it will delete the view so it can be rebuilt from scratch the next time it is requested.
Provisioned folders that are incorrectly pointing into unprovisioned parent folders (ProvisionedFolder): Repair tasks can fix Provisioned folders incorrectly pointing into unprovisioned parents or vice versa.
Syntax
New-MailboxRepairRequest -Mailbox <MailboxIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Archive <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]New-MailboxRepairRequest -Database <DatabaseIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]
Parameters
Database, Mailbox and Archive:
You can repair an entire mailbox database or a specified mailbox by specifying either the Database or the Mailbox parameter. You can't use both. To repair the archive mailbox for the specified user, use the Archive switch.
CorruptionType:
(at least 1 required) you are already familiar with, we discussed them above:
SearchFolder
AggregateCounts
ProvisionedFolder
FolderView
You can run a repair task with multiple parameters if you separate them with a comma (as shown in the Examples section below).
DetectOnly: (Optional) The DetectOnly switch secifies that you want this command to report errors, but not fix them. You don't have to specify a value with this switch.
Other Optional Parameters: This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, type "get-help about_commonparameters".
Examples
New-MailboxRepairRequest -Mailbox administrator@contoso.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView
New-MailboxRepairRequest -Mailbox administrator -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView -WhatIf
Event Reporting
After submitting the Mailbox or Public Folder repair request, you can monitor its progress with the Event Viewer. That's right, no more text logs to weed through. The events are logged under the MSExchangeIS Mailbox Store source.
The following event IDs will be logged for repair requests:
10047 A mailbox-level repair request started
10064 A Public Folder repair request started
10048 The repair request successfully completed.
10050 The mailbox repair request task skipped a mailbox .
10059 A database-level repair request started.
10062 Corruption was detected
NOTE: in order to run this cmdlets you new belongs to below managed grop role
Organization Management
Server Management
Recipient Management
see http://msexchangeteam.com/archive/2010/08/23/455899.aspx
Enjoy!
-Dario
After apply RU1 for Exchange 2007 SP3 we cannot create a Receive Connector
When we try to create a new receive connector in Exchange 2007, we received the error:
The accepted solution is
From Exchange 2007 SP3 source and with Schema admin permissions
C:\Source\Ex2007-SP3>setup /ps
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
Organization Checks ......................... COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema
Progress ......................... COMPLETED
The Microsoft Exchange Server setup operation completed successfully.
After that, simply try to create the Receive connector again
new-ReceiveConnector -Name 'TESTHCEX1-Inbound Mail' -Usage 'Custom' -Bindings '10.1.2.30:25' -RemoteIPRanges '192.168.0.2' -Server 'TESTHCEX1' -PermissionGroups AnonymousUsers
Identity Bindings Enabled
TESTHCEX1\TESTHCEX1-Inbound Mail {135.9.6.94:25} True
And
Get-ReceiveConnector "TESTHCEX1-Inbound Mail" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
Identity User Deny Inherited Rights
TESTHCEX1\TESTCHEX1... NT AUTHORITY\ANON... False False ms-Exch-SMTP-Accept-Any-Recipient
-Dario
New-ReceiveConnector : Active Directory operation failed on testgdc1.company.com. This error is not retriab
le. Additional information: The parameter is incorrect.
Active directory response: 00000057: LdapErr: DSID-0C090B38, comment: Error in attribute conversion operation, dat
a 0, vece
At line:1 char:21
+ new-ReceiveConnector <<<< -Name 'TEST' -Usage 'Custom' -Bindings '10.1.2.30' -RemoteIpRanges '192.168.0.2' -Server 'TESTHCEX1'
The accepted solution is
From Exchange 2007 SP3 source and with Schema admin permissions
C:\Source\Ex2007-SP3>setup /ps
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
Organization Checks ......................... COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema
Progress ......................... COMPLETED
The Microsoft Exchange Server setup operation completed successfully.
After that, simply try to create the Receive connector again
new-ReceiveConnector -Name 'TESTHCEX1-Inbound Mail' -Usage 'Custom' -Bindings '10.1.2.30:25' -RemoteIPRanges '192.168.0.2' -Server 'TESTHCEX1' -PermissionGroups AnonymousUsers
Identity Bindings Enabled
TESTHCEX1\TESTHCEX1-Inbound Mail {135.9.6.94:25} True
And
Get-ReceiveConnector "TESTHCEX1-Inbound Mail" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
Identity User Deny Inherited Rights
TESTHCEX1\TESTCHEX1... NT AUTHORITY\ANON... False False ms-Exch-SMTP-Accept-Any-Recipient
-Dario
Tuesday, February 22, 2011
How to install a certificate in Exchange 2010 using an Internal CA
Hi all,
we can install an Active Directory Certificate Services in windows server 2008, in order to configure an Internal PKI infrastructure.After that you will be able to submit server certificates for your Exchange 2010 environment, bear in mind that you will need deploy an installation of your Root CA certificates in your machines in order to trust and avoid the certificate pop up message,
Once you have your PKI infrastructure created (one Enterprise CA is enough), go to your CAS server
[PS] C:\>Set-Content -path "C:\Cert\cert.req" -Value $Data[PS] C:\>$data=New-ExchangeCertificate -GenerateRequest -SubjectName "c=CA,o=Company,cn=webmail.company.ca" -DomainName we
bmail.company.net, webmail.company.ca,autodiscover.company.ca, autodiscover.company.net, CAS1,CAS1.test.ca -FriendlyName webmail.company.net -privatekeyexportable:$true
Creating a new session for implicit remoting of "New-ExchangeCertificate" command...
[PS] C:\>Set-Content -path "C:\Cert\cert.req" -Value $DataWith this request you should go to your CA
Go to Request certificate and Advance and then to the option
Note: if you need subject alternative names, add in attributes box as
SAN:dns="webmail.test.net"&dns="autodiscover.test.net"&dns="webmail.test.ca"&dns="CAS1""&dns="CAS1.test.ca"
Submit the request and save as .cer file
In your CAS server
[PS] C:\>Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path c:\cert\certnew.cer -Encoding byte -ReadCount 0))
Thumbprint Services Subject
---------- -------- -------
633CB9DE67BD2015F649323593FC95B19B1DA95D IP.... CN=webmail.test.ca, O=Company,=CA
[PS] C:\>Enable-ExchangeCertificate -services "IIS,IMAP,SMTP"cmdlet Enable-ExchangeCertificate at command pipeline position 1
Supply values for the following parameters:
Thumbprint: 633CB9DE67BD2015F649323593FC95B19B1DA95D
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: 'C51882DC5CE37F08B57C63BB5F1D7BDB944410A7' (expires 4/27/2015 12:32:57 PM)
Replace it with certificate: '633CB9DE67BD2015F649323593FC95B19B1DA95D' (expires 5/3/2012 6:00:34 AM)
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): L
[PS] C:\>Get-ExchangeCertificate
Thumbprint Services Subject
---------- -------- -------
633CB9DE67BD2015F649323593FC95B19B1DA95D IP.WS. CN=webmail.test.ca, O=Company, C=CA
5113A9E9CC355BB8C96C6F986269AFD1584F07C3 ...... C=CA, O=Company, CN=webmail.test.net
C853F48A8A9E8500C3665777A8CF79A2AF30911D ...... C=CA, O=Company, CN=webmail.test.net
C51882DC5CE37F08B57C63BB5F1D7BDB944410A7 .P..S. CN=CAS1
Set autodiscover service
[PS] C:\>Set-ClientAccessServer -Identity CAS1 -AutoDiscoverServiceInternalUri https://webmail.test.net/autodiscover/autodiscover.xml
Set OAB service:
[PS] C:\>$a=get-OABVirtualDirectory -Server CAS1[PS] C:\>Set-OABVirtualDirectory $a -InternalURL https://webmail.test.net/OAB
[[PS] C:\>Set-OABVirtualDirectory -Identity "OAB (Default Web Site)" -RequireSSL:$true
Set Web services URL
[PS] C:\>$a=get-WebServicesvirtualdirectory -Server CAS1Creating a new session for implicit remoting of "Get-WebServicesVirtualDirectory" command...
[PS] C:\>Set-WebServicesvirtualdirectory $a -InternalURL https://webmail.test.net/EWS/Exchange.asmx
Set Exchange ActiveSync URL
[PS] C:\>$a=get-ActiveSyncvirtualdirectory -Server CAS1[PS] C:\>Set-ActiveSyncvirtualdirectory $a -InternalURL https://webmail.est.net/Microsoft-Server-ActiveSync
You must configure that in all CAS servers in your environment , of course this depends of your environment.
Further information dario.may@gmail.com, I'll glad to help you
-Dario
we can install an Active Directory Certificate Services in windows server 2008, in order to configure an Internal PKI infrastructure.After that you will be able to submit server certificates for your Exchange 2010 environment, bear in mind that you will need deploy an installation of your Root CA certificates in your machines in order to trust and avoid the certificate pop up message,
Once you have your PKI infrastructure created (one Enterprise CA is enough), go to your CAS server
[PS] C:\>Set-Content -path "C:\Cert\cert.req" -Value $Data[PS] C:\>$data=New-ExchangeCertificate -GenerateRequest -SubjectName "c=CA,o=Company,cn=webmail.company.ca" -DomainName we
bmail.company.net, webmail.company.ca,autodiscover.company.ca, autodiscover.company.net, CAS1,CAS1.test.ca -FriendlyName webmail.company.net -privatekeyexportable:$true
Creating a new session for implicit remoting of "New-ExchangeCertificate" command...
[PS] C:\>Set-Content -path "C:\Cert\cert.req" -Value $DataWith this request you should go to your CA
Go to Request certificate and Advance and then to the option
Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
Note: if you need subject alternative names, add in attributes box as
SAN:dns="webmail.test.net"&dns="autodiscover.test.net"&dns="webmail.test.ca"&dns="CAS1""&dns="CAS1.test.ca"
Submit the request and save as .cer file
In your CAS server
[PS] C:\>Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path c:\cert\certnew.cer -Encoding byte -ReadCount 0))
Thumbprint Services Subject
---------- -------- -------
633CB9DE67BD2015F649323593FC95B19B1DA95D IP.... CN=webmail.test.ca, O=Company,=CA
[PS] C:\>Enable-ExchangeCertificate -services "IIS,IMAP,SMTP"cmdlet Enable-ExchangeCertificate at command pipeline position 1
Supply values for the following parameters:
Thumbprint: 633CB9DE67BD2015F649323593FC95B19B1DA95D
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: 'C51882DC5CE37F08B57C63BB5F1D7BDB944410A7' (expires 4/27/2015 12:32:57 PM)
Replace it with certificate: '633CB9DE67BD2015F649323593FC95B19B1DA95D' (expires 5/3/2012 6:00:34 AM)
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): L
[PS] C:\>Get-ExchangeCertificate
Thumbprint Services Subject
---------- -------- -------
633CB9DE67BD2015F649323593FC95B19B1DA95D IP.WS. CN=webmail.test.ca, O=Company, C=CA
5113A9E9CC355BB8C96C6F986269AFD1584F07C3 ...... C=CA, O=Company, CN=webmail.test.net
C853F48A8A9E8500C3665777A8CF79A2AF30911D ...... C=CA, O=Company, CN=webmail.test.net
C51882DC5CE37F08B57C63BB5F1D7BDB944410A7 .P..S. CN=CAS1
Set autodiscover service
[PS] C:\>Set-ClientAccessServer -Identity CAS1 -AutoDiscoverServiceInternalUri https://webmail.test.net/autodiscover/autodiscover.xml
Set OAB service:
[PS] C:\>$a=get-OABVirtualDirectory -Server CAS1[PS] C:\>Set-OABVirtualDirectory $a -InternalURL https://webmail.test.net/OAB
[[PS] C:\>Set-OABVirtualDirectory -Identity "OAB (Default Web Site)" -RequireSSL:$true
Set Web services URL
[PS] C:\>$a=get-WebServicesvirtualdirectory -Server CAS1Creating a new session for implicit remoting of "Get-WebServicesVirtualDirectory" command...
[PS] C:\>Set-WebServicesvirtualdirectory $a -InternalURL https://webmail.test.net/EWS/Exchange.asmx
Set Exchange ActiveSync URL
[PS] C:\>$a=get-ActiveSyncvirtualdirectory -Server CAS1[PS] C:\>Set-ActiveSyncvirtualdirectory $a -InternalURL https://webmail.est.net/Microsoft-Server-ActiveSync
You must configure that in all CAS servers in your environment , of course this depends of your environment.
Further information dario.may@gmail.com, I'll glad to help you
-Dario
Chile ...no te olvides !!!! DST Patch for Windows Operative Systems...
Just a reminder.. for Chile,, we are close to 2nd Saturday of March
The December DST CU contains 2011 adjusted DST start and end-dates for the following timezones:
· Israel Standard Time
· Morocco Standard Time
· PacificSA Standard Time
· Samoa Standard Time
· Syria Standard Time
Important This update supersedes and replaces update 2158563, which was released in September 2010. This update also includes additional time zone changes made after update 2158563 was created.
If you have already deployed update 2158563, read the descriptions of the specific time zone changes that are addressed in this article to determine whether you must deploy this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity.
We recommend that you deploy the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.
Important
Gracias amigos chilenos!!
-Dario
· Israel Standard Time
· Morocco Standard Time
· PacificSA Standard Time
· Samoa Standard Time
· Syria Standard Time
Important This update supersedes and replaces update 2158563, which was released in September 2010. This update also includes additional time zone changes made after update 2158563 was created.
If you have already deployed update 2158563, read the descriptions of the specific time zone changes that are addressed in this article to determine whether you must deploy this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity.
We recommend that you deploy the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.
Important
- Before you apply the update that is described in this article, be aware of potential issues that may affect Microsoft Outlook.
For more information about these issues, click the following article number to view the article in the Microsoft Knowledge Base:931667 (http://support.microsoft.com/kb/931667/ ) How to address time zone changes by using the Time Zone Data Update Tool for Microsoft Office Outlook - If you are running Microsoft Exchange Server in an Information Technology (IT) environment, you must take additional measures to guarantee the correct operation of Exchange Server.
For more information about the Exchange daylight saving time (DST) update, click the following article number to view the article in the Microsoft Knowledge Base:941018 (http://support.microsoft.com/kb/941018/ ) How to address daylight saving time by using the Exchange Calendar Update Tool - Cumulative time zone updates contain only data that has changed for a specific region or that was added to maintain parity with other operating system versions. Therefore, if a time zone key is deleted, some original values may not be restored after you apply the cumulative zone update.
We do not recommend that you delete any registry keys that are related to time zones. On a computer that has incomplete time zone keys, first restore the time zone keys from a known good backup. Then, apply the update.
Gracias amigos chilenos!!
-Dario
Error: “Couldn’t find the Enterprise Organization Container” when Creating a New Mailbox Export Request
Hi all,
this is a new cmdlet from Exchange 2010 Sp1, that allow you to create a PST from an active mailbox. First of all you must create a share folder with the below permissions at NTFS and Share level for the Exchange Trusted Subsystem group
run the command
Further information see http://technet.microsoft.com/en-us/library/ff459227.aspx
Enjoy
-Dario
this is a new cmdlet from Exchange 2010 Sp1, that allow you to create a PST from an active mailbox. First of all you must create a share folder with the below permissions at NTFS and Share level for the Exchange Trusted Subsystem group
After that be sure if your account has the necessary permissions or create a New role for that
Add your user to this role
Further information see http://technet.microsoft.com/en-us/library/ff459227.aspx
Enjoy
-Dario
Thursday, February 17, 2011
How to export a PST file in Exchange 2010 and Tivoli Data Protection Client..this will make you forget the Exmerge tool :)
Do not tell me you miss the exmerge all miss him.... So I'm glad to show and share this solution:
Pre-requisites: (all must be installed in your Mailbox server)
Check the Tivoli for Mail documentation : http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.mail.exc.doc/b_dp_mail_exc_guide_win.pdf
Configure in your TDP client the DBTemp and LOGTemp directory and the CAS server (only available in the 6.1.3 version)
When you run the below command a new Recovery Database will be created in the local mailbox server, you must provides the user name's alias to recover and the date. If you want to recover a mailbox user from another server that local you must add the /EXCSERVER switch in the command. Then the application will search the user in the catalog and the backup more closely to the date you 've indicated before. After that the application will creates the Recovery Database in your server dismounted and start the restore.
Very important take in care the permissions, be sure that the account is member of Organization Management Role and add the send as and full access permission
From "your_installation_path\Tivoli\TSM\TDPExchange\" open the Exchange Client - Command Line and type:
TDPEXCC RESTOREMAILBOX user1 /TSMPASSWORD=Password /MAILBOXORIGLOCATION=MBX1T1,MST1DB1 /MAILBOXRESTOREDAte=02/16/2011 /MAILBOXRESTOREDESTination=PST,e:\pst\user1.pst
and this is the output
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 6, Release 1, Level 3.01
(C) Copyright IBM Corporation 1998, 2010. All rights reserved.
Starting Microsoft Exchange restore...
Querying Exchange component information...
Querying mailbox information...
Connecting to TSM Server as node 'MBX1T1_EXC'...
Connecting to Local DSM Agent 'MBX1T1'...
Preparing Exchange Recovery Database...
Performing mailbox restore using closest available backup.
Connecting to TSM Server as node 'MBX1T1_EXC'...
Connecting to Local DSM Agent 'MBX1T1'...
Starting Microsoft Exchange restore...
Beginning VSS restore of 'Logs', 'MST1DB1'...
Preparing for restore of 'MST1DB1' from TSM backup.
Files Examined/Completed/Failed: [ 3504 / 3504 / 0 ] Total Bytes: 3966952400
VSS Restore operation completed with rc = 0
Files Examined : 3504
Files Completed : 3504
Files Failed : 0
Total Bytes : 3966952400
Querying Exchange Recovery Database...
Checking Active Directory entries...
Recovering deleted items for mailbox 'User1(user1)'. This process may take several minutes...
Restoring mailbox 'User1(user1)' to 'e:\pst\user1.pst'...
Mailbox restore completed successfully with 59 items restored.
Removing Exchange Recovery Database...
Total mailboxes requested for restore: 1
Total mailboxes restored: 1
And that's it...but we have several troubles and a lot of drops of transpiration poured...
1. This is because the CAS server wasn't set in the configuration.
02/17/2011 08:00:48 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:00:48 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:00:50 The operation couldn't be performed because object 'MBX1T1' couldn't be found on 'DCT1.test.ca'.
02/17/2011 08:00:50 =========================================================================
02/17/2011 08:00:50 Request : Restore Mailbox Results
02/17/2011 08:00:50 -------------------------------------------------------------------------
02/17/2011 08:00:50 Total mailboxes requested for restore : 1
02/17/2011 08:00:50 Total mailboxes restored : 0
02/17/2011 08:00:50 -------------------------------------------------------------------------
02/17/2011 08:00:50 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:29:50 =========================================================================
2. This is because the TDP client version should be 6.1.3
2/17/2011 05:41:16 ============================================================
02/17/2011 05:41:16 Request : VSS RESTORE
02/17/2011 05:41:16 Component List : 'Logs'(full, TSM), 'MST1DB1'(full, TSM)
02/17/2011 05:41:16 Local DSMAGENT Node : MBX1T1
02/17/2011 05:41:16 Mount Wait : Yes
02/17/2011 05:41:16 ------------------------------------------------------------
02/17/2011 05:41:51 Backup(s) to be restored:
02/17/2011 05:41:51 <Logs : VSS : full : 02/16/2011 11:34:46>
02/17/2011 05:41:51 <File : VSS : full : 02/16/2011 11:34:46>
02/17/2011 05:42:02 Preparing for restore of 'MST1DB1' from TSM backup.
02/17/2011 05:59:29 VSS Restore operation completed with rc = 0
02/17/2011 05:59:29 Files Examined : 3504
02/17/2011 05:59:29 Files Completed : 3504
02/17/2011 05:59:29 Files Failed : 0
02/17/2011 05:59:29 Total Bytes : 3966952400
02/17/2011 06:00:08 ACN5909E The MAPI subsystem logon has failed. Please check that you have
02/17/2011 06:00:08 an active mailbox and sufficient privileges for this operation.
02/17/2011 06:00:11 =========================================================================
02/17/2011 06:00:11 Request : Restore Mailbox Results
02/17/2011 06:00:11 -------------------------------------------------------------------------
02/17/2011 06:00:11 Total mailboxes requested for restore : 1
02/17/2011 06:00:11 Total mailboxes restored : 0
02/17/2011 06:00:11 -------------------------------------------------------------------------
Be happy delegating this task to the Backup Team :)
Thank you JuanMa!!
-Dario
Pre-requisites: (all must be installed in your Mailbox server)
- TDP for Microsoft Exchange client version 6.1.3
- TSM BA Client version 6.2.2
- Update Rollup 2 for Exchange Server 2010 Service Pack 1
http://support.microsoft.com/kb/2425179 - Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=94274318-27c4-4d8d-9bc5-3e6484286b1f&DisplayLang=en
Check the Tivoli for Mail documentation : http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.mail.exc.doc/b_dp_mail_exc_guide_win.pdf
Configure in your TDP client the DBTemp and LOGTemp directory and the CAS server (only available in the 6.1.3 version)
When you run the below command a new Recovery Database will be created in the local mailbox server, you must provides the user name's alias to recover and the date. If you want to recover a mailbox user from another server that local you must add the /EXCSERVER switch in the command. Then the application will search the user in the catalog and the backup more closely to the date you 've indicated before. After that the application will creates the Recovery Database in your server dismounted and start the restore.
Very important take in care the permissions, be sure that the account is member of Organization Management Role and add the send as and full access permission
Add-MailboxPermission -Identity 'CN=User1,CN=Users,DC=test,DC=ca' -User 'TEST\restoreadmin' -AccessRights 'FullAccess'
Add-ADPermission -Identity 'CN=User1,CN=Users,DC=test,DC=ca' -User 'TEST\restoreadmin' -ExtendedRights 'Send-as'
From "your_installation_path\Tivoli\TSM\TDPExchange\" open the Exchange Client - Command Line and type:
TDPEXCC RESTOREMAILBOX user1 /TSMPASSWORD=Password /MAILBOXORIGLOCATION=MBX1T1,MST1DB1 /MAILBOXRESTOREDAte=02/16/2011 /MAILBOXRESTOREDESTination=PST,e:\pst\user1.pst
and this is the output
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 6, Release 1, Level 3.01
(C) Copyright IBM Corporation 1998, 2010. All rights reserved.
Starting Microsoft Exchange restore...
Querying Exchange component information...
Querying mailbox information...
Connecting to TSM Server as node 'MBX1T1_EXC'...
Connecting to Local DSM Agent 'MBX1T1'...
Preparing Exchange Recovery Database...
Performing mailbox restore using closest available backup.
Connecting to TSM Server as node 'MBX1T1_EXC'...
Connecting to Local DSM Agent 'MBX1T1'...
Starting Microsoft Exchange restore...
Beginning VSS restore of 'Logs', 'MST1DB1'...
Preparing for restore of 'MST1DB1' from TSM backup.
Files Examined/Completed/Failed: [ 3504 / 3504 / 0 ] Total Bytes: 3966952400
VSS Restore operation completed with rc = 0
Files Examined : 3504
Files Completed : 3504
Files Failed : 0
Total Bytes : 3966952400
Querying Exchange Recovery Database...
Checking Active Directory entries...
Recovering deleted items for mailbox 'User1(user1)'. This process may take several minutes...
Restoring mailbox 'User1(user1)' to 'e:\pst\user1.pst'...
Mailbox restore completed successfully with 59 items restored.
Removing Exchange Recovery Database...
Total mailboxes requested for restore: 1
Total mailboxes restored: 1
And that's it...but we have several troubles and a lot of drops of transpiration poured...
1. This is because the CAS server wasn't set in the configuration.
02/17/2011 08:00:48 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:00:48 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:00:50 The operation couldn't be performed because object 'MBX1T1' couldn't be found on 'DCT1.test.ca'.
02/17/2011 08:00:50 =========================================================================
02/17/2011 08:00:50 Request : Restore Mailbox Results
02/17/2011 08:00:50 -------------------------------------------------------------------------
02/17/2011 08:00:50 Total mailboxes requested for restore : 1
02/17/2011 08:00:50 Total mailboxes restored : 0
02/17/2011 08:00:50 -------------------------------------------------------------------------
02/17/2011 08:00:50 ANS0322E (RC5853) no text available for this return code.
02/17/2011 08:29:50 =========================================================================
2. This is because the TDP client version should be 6.1.3
2/17/2011 05:41:16 ============================================================
02/17/2011 05:41:16 Request : VSS RESTORE
02/17/2011 05:41:16 Component List : 'Logs'(full, TSM), 'MST1DB1'(full, TSM)
02/17/2011 05:41:16 Local DSMAGENT Node : MBX1T1
02/17/2011 05:41:16 Mount Wait : Yes
02/17/2011 05:41:16 ------------------------------------------------------------
02/17/2011 05:41:51 Backup(s) to be restored:
02/17/2011 05:41:51 <Logs : VSS : full : 02/16/2011 11:34:46>
02/17/2011 05:41:51 <File : VSS : full : 02/16/2011 11:34:46>
02/17/2011 05:42:02 Preparing for restore of 'MST1DB1' from TSM backup.
02/17/2011 05:59:29 VSS Restore operation completed with rc = 0
02/17/2011 05:59:29 Files Examined : 3504
02/17/2011 05:59:29 Files Completed : 3504
02/17/2011 05:59:29 Files Failed : 0
02/17/2011 05:59:29 Total Bytes : 3966952400
02/17/2011 06:00:08 ACN5909E The MAPI subsystem logon has failed. Please check that you have
02/17/2011 06:00:08 an active mailbox and sufficient privileges for this operation.
02/17/2011 06:00:11 =========================================================================
02/17/2011 06:00:11 Request : Restore Mailbox Results
02/17/2011 06:00:11 -------------------------------------------------------------------------
02/17/2011 06:00:11 Total mailboxes requested for restore : 1
02/17/2011 06:00:11 Total mailboxes restored : 0
02/17/2011 06:00:11 -------------------------------------------------------------------------
Be happy delegating this task to the Backup Team :)
Thank you JuanMa!!
-Dario
Subscribe to:
Posts (Atom)