25 ott 2010

Exchange 2010: When you trying to recover a deleted Exchange 2010 public folder from Outlook you receive error: "Outlook was unable to recover some or all of the items in this folder. Make sure you have the required permissions ..."

When you trying to recover a deleted Exchange 2010 public folder from Outlook, we received the following error:

"Outlook was unable to recover some or all of the items in this folder. Make sure you have the required permissions to recover items in this folder and try again. If the problem persists contact your administrator"

We can resolve this issue following these steps:

1. Download ExFolder from the following link: http://msexchangeteam.com/files/12/attachments/entry453398.aspx

2. Unzip the file, copy the Exfolders.exe to "Program files\Microsoft\Exchange Server\V14\Bin"

3. Run the reg file to import it.

4. Start Exfolders.exe. Select Public Folder, Global Catalog, public folder Database. Click OK

5. Right click the parent folder contains the deleted folder, choose Show Deleted subfolders. (Deleted folders will be listed with red folder names)

6. Right click the folder you would like to recover, choose Recover folder. (It will displayed normally now)

7. In the right window, select Items and check whether items can be displayed or not.

Note: To recover deleted items, select Deleted contents under Items tab, right click the item and choose "Recover items"

 


17 ott 2010

Lingoes V2.7.1 has been released

New version of Lingoes integrates cursor translator, looking-up in dictionaries and intelligent translation by creative zoned word translator. With selection of word or sentence in screen by cursor, it will translate as many as 23 languages of text into your native language. It's very convenient to use, we believe the new technology will change communication method among people.

New features:

Mini windows

Innovative zoned word translator can translate as many as 23 languages of text into your native language(or other language)

Natural voice can perfectly pronounce word just like a native English speaker.

Provide plugin for Adobe Acrobat Pro

Support cursor translator more fluently in Firefox 3

http://www.lingoes.net/

16 ott 2010

SBS 2008: Companyweb and SharePoint Central Admin not accessible after installing KB2345304

For those who are running into this issue, the solution is very simple in most cases and we see a very high success rate. However, for some it is a little more complex. What we document below has helped the majority of the situations where this issue has been seen.

check the following article from the sbs official blog

http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx

15 ott 2010

New HA Design Guidance Articles

New HA Design Guidance Articles was wroted

Source: http://msexchangeteam.com/archive/2010/10/14/456597.aspx

14 ott 2010

Fix Windows 7 Desktop Shortcuts Disappearing

If you run Windows 7 you might have noticed that desktop shortcuts disappear with no apparent reason whatsoever. Turns out that System Maintenance is responsible for that. It runs as a weekly maintenance service that affects desktop shortcuts in two ways.

It will first remove desktop shortcuts that have not been used for at least three months. System Maintenance will also remove broken shortcuts on the desktop if there are more than four of them. The problem with the latter is that Windows 7 will recognize shortcuts to disconnected network locations as broken and also shortcuts that link to shell folders.

Microsoft offers two solutions to the problem. The first advice is to keep the number of broken shortcuts below four. This is not always possible due to the problems with broken shortcuts mentioned above.

The second suggestion by Microsoft is to turn off Computer Maintenance:

  • Click Start, and then click Control Panel.
  • Under System and Security, click Find and fix problems.
  • On the left navigation pane, click Change settings.
  • Set Computer Maintenance to Off.

This does however turn off all other computer maintenance related tasks like checking the system time, disk volume errors or the disk space error reports.

All the maintenance tasks are powered by scripts that are located in c:\windows\Diagnostics\Scheduled\Maintenance\. Options are to edit the scripts directly in that directory. The permissions prohibit that the files are edited by the current user.

Fixing Windows 7 Desktop Shortcuts Disappearing

Please note: This is a hack which might have consequences on other parts of the operating system. Everything worked fine afterwards on the test system but make sure to backup the files properly before editing them

First we need to take control of the files so that we can edit them. To do that you need to take ownership first and then modify the access rights of the current user so that the files can be modified.

The first part can be automated. Just download the script at this forum and execute it. This should add a Take Ownership entry to the right-click menu in Windows Explorer.

Go to C:\Windows\diagnostics\scheduled\Maintenance in Windows Explorer after installing the script and right-click the file TS_BrokenShortcuts.ps1. Select the Take Ownership option which should transfer ownership to the logged in user.

The user still does not have permissions to save the file which means that we have to complete the next step as well before we can edit the broken shortcuts Powerscript file so that it will not delete broken shortcuts automatically.

Open an elevated command line prompt. You do that by clicking on the Start orb, All Programs, then Accessories. Right-click the Command Prompt link and select to Run As Administrator.

Now issue the following command to grant the active user full rights of the file. Make sure you replace USERNAME with the name of the active user.

icacls c:\windows\diagnostics\scheduled\maintenance\TS_BrokenShortcuts.ps1 /grant USERNAME:F

Now you can edit the file normally in a text editor like Notepad. Open it and locate the line (line 11)

[string]$list = ""

Delete everything below that is below that line up to (line 22)

return $list

The lines that are deleted are:

Get-ChildItem -Path $path -filter *.lnk | Foreach-Object {
$fullPath = ConvertTo-WQLPath $_.FullName
$wmiLinkFile = Get-WmiObject -query "SELECT Name,Target,AccessMask FROM Win32_ShortcutFile WHERE Name = '$fullPath'"

if(-not(Test-ValidLink $wmiLinkFile) -and (Test-Delete $wmiLinkFile))
{
$list = AttachTo-List $list $wmiLinkFile.Name
}
}

This basically returns a blank list to the script so that no shortcuts get deleted. I have tested it with five broken shortcuts and they have not been deleted after running system maintenance.

That fixed the broken shortcuts but we still have the issue that shortcuts that have not been used for some time are deleted by Windows 7 as well.

We have to (almost) perform the same operation here. Locate the file TS_UnusedDesktopIcons.ps1 in the same directory. Take ownership of it and grant the active user access rights.

Edit the file afterwards and locate the line (24)

[string]$list = ""

Delete everything up to line (35)

return $list

so that the following lines get deleted

Get-ChildItem -Path $path -filter *.lnk | Foreach-Object {
$fullPath = ConvertTo-WQLPath $_.FullName
$wmiLinkFile = Get-WmiObject -query "SELECT Name,Target,AccessMask FROM Win32_ShortcutFile WHERE Name = '$fullPath'"
$lastAccessTime = Get-LastAccessTime $_.FullName

if((Test-ValidLink $wmiLinkFile) -and (Test-Delete $wmiLinkFile) -and (Test-FileShortcut $wmiLinkFile) -and (Test-Unused $lastAccessTime $threshold))
{
$list = AttachTo-List $list $wmiLinkFile.Name
}
}

Please note that I did not test the second script but it should work just as fine.

This should resolve all issues that users have with removed shortcuts on the Windows 7 desktop.

source: http://www.ghacks.net/2010/03/30/fix-windows-7-desktop-shortcuts-disappearing/

12 ott 2010

Exchange 2010: Restore Database e Mailbox tramite i Recovery Database

Gli storage group sono stati rimossi da Exchange Server 2010 e di conseguenza anche i recovery storage group non hanno più motivo di esistere. Nel caso in cui si renderà necessario effettuare un restore, un ripristino di una singola mailbox e montare un database di Exchange in un percorso o server differente, dovremo utilizzare i recovery database. I recovery database non sono legati al server o al database sorgenti ed in ogni server Exchange 2010 si potrà montare soltanto un recovery database per volta, ne consegue che sarà possibile mantenere svariate copie di recovery database anche potremo montarne uno alla volta.
Un altra cosa importante che dobbiamo sapere prima di andare avanti è che in Exchange 2010 i backup online non sono supportati (streaming backups). Gli unici ad esserlo sono i backup basati su VSS
Il software di backup nativo in Windows Server 2008 e Windows 2008 R2 integra un plug-in in grado di supportare la tecnologia VSS. Ci sono però alcune limitazioni di cui dobbiamo tenere conto.
  • Il backup dovrà essere eseguito localmente sul rispettivo server di Exchange 2010.
  • I Backup vengono eseguiti a livello di volume (Tutti i dati in un determinato volume logico verranno salvati). Ad esempio se in un volume ci sono 3 db non potremo specificare quale salvare ma saremo obbligati a fare il backup di tutti I DB.
  • Saremo in grado di effetture backup basati su VSS ma non backup Streaming.
  • Sarà possibile utilizzare i mount point soltanto se Exchange 2010 è in esecuzione su Windows Server 2008 R2.
  • I backup potranno essere effettuati su un drive locale o removibile (usb) o in altenativa su una condivisione di rete. Nessun supporto per i tape o tape library tranne i modelli che supportano la tecnologia disk to disk.
  • Solo un backup VSS completo sarà in grado di eseguire correttamente il log truncation.
  • Non sarà possibile un restore direttamente su di un recovery database. Dunque dovremo effettuare il nostro restore prima in un percorso alternativo e solo successivamente potremo creare il recovery database, e montare il DB ripristinato nel recovery database.
  • Exchange Replication VSS Writer non è supportato e non sarà possibile effettuare il backup delle copie passive dei DB nei server Mailbox di Exchange 2010 che sono membri di un DAG, ma rimane supportato il backup sulle copie attive.
  • In caso di un restore, potremo selezionare direttamente il percorso originale o un percorso alternativo. Nel caso di un restore nel percorso originale, il processo sarà automatico e non avremo la necessità di selezionare “This database can be overwritten by a restore” o di smontare il database prima di effettuare il restore.
  • I restore sono supportati solo a livello di Volume e non di singolo Database.

Exchange 2010: Android Exchange Activesync "failed to create account" error

When you attempt to connect an Android Phone to Exchange 2010 you continually got the message "Failed to create the account. Please try again later".


The problem seems to be with security rights.



The only way to fix this issue is by having access to Active Directory ADUC.


Go Active Directory Users & Computers (Enable Advanced Features if needed)

Open the properties of the user that is having the issue

Click on the Security Tab

Click the Advanced button

In the Default Permissions tab check the box at the bottom for "Include inheritable permissions from this object's parent"

Wait for AD to propagate (a few minutes)

Important:
If you running Exchange 2010 SP1 you  have to remove the Default Activesync Policy from EMS


Remove-ActiveSyncMailboxPolicy -id Default





08 ott 2010

Released: Update Rollup 1 for Exchange Server 2010 SP1

Microsoft has released Update Rollup 1 for Microsoft Exchange Server 2010 Service Pack 1 (SP1).  #KB2407028

This update includes new fixes for the following server roles:

  • Client Access
  • Mailbox
  • Edge Server
  • Hub Transport

In particular we would like to call out the following fixes which have been included in this release:

  • 2028967 Event ID 3022 is logged and you still cannot replicate a public folder from one Exchange Server 2010 server to another
  • 2251610 The email address of a user is updated unexpectedly after you run the Update-Recipient cmdlet on an Exchange Server 2010 server
  • 978292 An IMAP4 client cannot send an email message that has a large attachment in a mixed Exchange Server 2010 and Exchange Server 2003 environment

Rollup 2 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in early December.

Download the Exchange2010-KB2407028-EN-x64 package now.

Source: Exchange Team

02 ott 2010

Exchange 2010 SP1: DAG Not displaying own Database Copies in EMC

Exchange 2010 SP1: DAG environment not displaying own Database Copies in EMC

This is a known issue and It is under research now.

Please check:

05/10/2010 :

http://blogs.technet.com/b/timmcmic/archive/2010/10/04/database-copies-fail-to-display-after-upgrading-to-exchange-2010-service-pack-1.aspx

========================================

http://workinghardinit.wordpress.com/2010/09/13/emc-does-not-show-all-database-copies-after-upgrade-to-exchange-2010-sp1-still-investigating/

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/1b6fb748-9a81-4589-aa75-2cd8b9895065