To my readers:
I Wish You and families a Merry Christmas.
Auguro un Buon Natale a Voi e alle rispettive famiglie.
"Non c'è niente di più triste nel mondo che svegliarsi il giorno di Natale e non essere un bambino."
(E. Bombeck)
To my readers:
I Wish You and families a Merry Christmas.
Auguro un Buon Natale a Voi e alle rispettive famiglie.
"Non c'è niente di più triste nel mondo che svegliarsi il giorno di Natale e non essere un bambino."
(E. Bombeck)
The Deployment Assistant has been enhanced to include rich coexistence information for those interested in maintaining some users on-premises and some users hosted by Microsoft Office 365 for enterprises in the cloud. This approach is different than the Simple Exchange Migration (SEM) and Staged Migration options currently offered by Office 365. As of now, the available scenario is targeted solely at those organizations with a current Exchange 2003 on-premises implementation, but additional scenarios for supporting Exchange 2007 and Exchange 2010 will be coming.
Reference:
http://technet.microsoft.com/it-it/exdeploy2010/default.aspx#Index
AHCI (Advanced Host Controller Interface) enables native command queuing and hot-plugging through SATA host controllers (Serial-ATA) for your hard drives. In many scenarios it enables more efficient multi-tasking. Vista was the first Windows OS to support AHCI out of the box, where as Windows 7 does the same. But an issue with AHCI is that if you install the OS without enabling AHCI in the BIOS, enabling it after installation will render your OS unusable. This is because Windows disable the AHCI driver since it is not needed during the installation.
There is one way to fix this, although you need to have knowledge of registry editing. The detailed steps from Microsoft are as follows: To resolve this issue, enable the AHCI driver in the registry before you change the SATA mode of the boot drive.
To do this, follow these steps:
1. Exit all Windows-based programs.
2. Click Start, type regedit in the Start Search box, and then press ENTER.
3. If you receive the User Account Control dialog box, click Continue.
4. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SystemCurrentControlSet\Services\Msahci HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
5. In the right pane, right-click Start in the Name column, and then click Modify.
6. In the Value data box, type 0, and then click OK.
7. On the File menu, click Exit to close Registry Editor.
After this you’ll have to restart your computer, go to BIOS and enable AHCI. When you log in to Windows again, you’ll notice the installation of drivers for AHCI. Another restart will be required to finish the driver installation.
PingPlotter Freeware is a high performance, low-overhead traceroute application. It allows you to quickly "trace" the route between you and a target of your choice (a web site, Voice over IP provider, online game server,or similar target), and then continue to collect performance metrics about that route.
Microsoft release Windows Small Business Server 2011 Standard edition and Windows Small Business Server 2011 Premium Add-on.
Designed and priced for small businesses with up to 75 users, Windows Small Business Server 2011 Standard delivers enterprise-class server technology in an affordable, all-in-one solution. Windows Small Business Server 2011 Standard not only helps to protect, access, and manage your information from virtually anywhere, but also allows your business to be more productive by providing:
More at SBS Official Blog: http://blogs.technet.com/b/sbs/archive/2010/12/13/windows-small-business-server-2011-standard-releases-to-manufacturing.aspx
Earlier today the Exchange CXP team released a number of Update Rollups for versions of Exchange Server to the Download Center and via Microsoft Update.
Update Rollup 2 for Exchange Server 2010 SP1
This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:
In Exchange 2010 the Management tools are dependent on IIS. There are situations where the management tool connection to the target Exchange server can fail, and the error that is returned can be difficult to troubleshoot.
Thus was born Exchange Management Troubleshooter (EMTshooter).
The EMTshooter runs on the local (target) Exchange server and attempts to identify potential problems with management tools connection to it.
Terminale:
Il terminale (un LG Optimus 7usato di pochi giorni) è stato acquistato di recente su ebay per 299 €. ( più avanti capiremo il perché )
Perché?
Il mio HTC Hero attuale ha servito egregiamente ed Android a conti fatti è un ottimo sistema operativo come del resto quasi tutti i prodotti made in Google, anche se bisogna ammettere che Android sembra una brutta copia del mio precedente iPhone. E allora perché acquistare un terminale a cui mancano almeno il 50% delle feature di Android? Spirito d'avventura? Semplice curiosità?
Primo impatto.
L'LG E900 non è leggero e nemmeno troppo piccolo ma allo stesso tempo risulta particolarmente maneggevole soprattutto durante l'uso della tastiera virtuale. Nonostante avessi qualche dubbio su LG mi sento di dichiarare che il terminale è ben fatto sia come progettazione sia come materiali e non ha nulla da invidiare ai miei precedenti HTC. Il Power On del terminale ed il caricamento del sistema operativo sono molto veloci e in una quindicina di secondi posso già inserire il PIN sfruttando una tastiera virtuale numerica di generose dimensioni e molto comoda. La sensibilità del Touch Screen mi ha fatto una buona impressione e la considero alla pari di iPhone e sicuramente superiore ad Hero.
Immediatamente dopo l'inserimento del PIN ci troviamo davanti l'interfaccia METRO... I primi 5 minuti e durante tutta la configurazione dell'apparato mi sono chiesto come sia stato possibile che ci siano voluti 3 anni per sviluppare un sistema operativo così essenziale e sostanzialmente basato su quadrati e scritte.
Configurazione.
La configurazione è veloce anche perché attualmente le cose da poter configurare non sono molte. Passo direttamente alla mia posta elettronica aziendale basata su Exchange 2010, inserisco i parametri richiesti e scopro che non posso sincronizzare perché utilizzo un certificato SSL auto generato e che purtroppo non posso nemmeno forzare l'uso dello stesso come facevo su iOS e Android. Prendo atto della cosa anche se in parte non la condivido ed invio i certificati digitali della mia CA interna e del server al mio account Live che configuro con un paio di tocchi sul display. Installo i certificati SSL che mi sono appena inviato semplicemente eseguendoli ed ora posso utilizzare la mia posta aziendale senza problemi. La rubrica di Exchange e tutti i Contatti di Live ora sono nella medesima posizione, in un primo momento la cosa può sembrare scomoda ma poi ci rende conto che la si può sfruttare a nostro vantaggio.
Dato che l'uso di questo smartphone sarà per la maggior parte del tempo di tipo business decido di associarlo al vivavoce della macchina tramite Bluetooth (un Parrot di circa 3 anni fa). Nessun Problema. Ricevo e faccio qualche telefonata durante il giorno. Di nuovo nessun problema e qualcuno mi fa sapere che mi sente meglio.
Una inaspettata e piacevole sorpresa.
Il giorno seguente decido di reinserire tutte le impronte vocali nel vivavoce come feci per iPhone e Hero ma scopro con sorpresa che NON serve. Il telefono ha un supporto vocale e decido di provarlo. Premo il pulsante sul mio Parrot e sento un bip, pronuncio il nome di un mio contatto e con mia grande sorpresa il telefono mi risponde e mi istruisce suggerendomi di utilizzare il formato "Chiama NomeContatto" eseguo pedissequamente e il telefono azzecca al primo colpo ripetendo e chiedendomi "Cellulare o Abitazione" io rispondo e il telefono mi istruisce di nuovo avvisandomi che la prossima volta potò dire "Chiama NomeContatto Cellulare". Durante l’utilizzo mi è capitato di invertire nome e cognome e di avere 3 contatti con lo stesso cognome il telefono non si lascia prendere in contropiede e mi chiede quale dei 3 contatti desidero, rispondo e lui chiama per me. Il supporto vocale ha lavorato in maniera eccelsa anche nei giorni in cui ero influenzato e con la voce bassa. Lo sto usando anche senza passare dal vivavoce e si comporta bene anche in caso di rumore di fondo rendendo non necessario l’accesso alla rubrica per cercare i contatti. Davvero ottimo.
Weekend e Marketplace.
E' arrivato il weekend e decido di installare qualche app sul nuovo terminale WP7 e approfondire la parte intrattenimento. Non devo installare Zune perché lo utilizzo già come player, il telefono viene riconosciuto senza problemi così inizio a sincronizzare la mia musica ... ci sono 16Gb a disposizione, bastano e avanzano.
Nel frattempo comincio a dare un occhiata alle applicazioni, attualmente sono circa 3000 ma il market cresce rapidamente e nuove apps vengono caricate giornalmente. Nonostante non ci sia la vasta scelta dei competitor riesco a trovare quello che mi serve più di frequente. Ecco le apps che ho scaricato : Adobe Reader, BBC News, Convertitore, Currency Converter, Ebay, Facebook, foursquare, Google search, Lista della spesa, Livella, Lyrics, Marketplace Search, Messenger, Meteo, Orari nel mondo, Pagine gialle, Rai.TV, Secrets, Shazam, Simpi RSS, Stopwatch, Televideo RAI, Traduttore, Twitter, Voice Recorder, YouTube, Light Notes. L'LG ha un market suo che contiene una serie di apps davvero indispensabili.
Non c'è ancora un navigatore off-line ma sembra che qualcosa già bolla in pentola. Decido anche di caricare qualche foto.
Settimana piena.
Questa settimana sono praticamente rimasto sempre fuori ufficio. In media ricevo (nessuna di queste è spam) circa 30 email al giorno di cui almeno la metà richiedono una risposta oppure un inoltro. Le telefonate che ricevo non sono moltissime ma abbastanza lunghe. Man mano il telefono diventa il mio telefono e i "Live tiles" si adattano al miei contenuti. Anche se sui quadratoni (Live tiles) si potrebbe pensare almeno un effetto riflesso per renderli più gradevoli, l'utilizzo dell'interfaccia Metro è davvero immediato. Rispondendo molto alle email e chiamando abbastanza devo ammettere che alla fine faccio le stesse operazioni utilizzando meno tempo lo smartphone e mi sento di confermare il comportamento indicato nei vari spot pubblicitari. La lettura delle email è molto efficace e davvero chiara, senza fronzoli. Di sicuro la preferisco a quella di Android e per certi versi anche a quella di iOS anche se è più accattivante graficamente. Nell'utilizzo continuativo posso confermare che Metro è più immediato rispetto alla classica griglia di icone. Il calendario è molto essenziale, troppo, manca la visualizzazione settimanale anche se non ne ho sentito la mancanza in quanto la visualizzazione "Giorno" scorre verticalmente.
Il giorno seguente sono a Milano presso un mio cliente, noto che c'è più traffico del solito, parcheggio parecchio distante e non so dove sono esattamente, mi annoto la via. Vado piedi ed apprendo che è iniziata la costruzione della Metro 5 e che a mio malgrado non troverò più parcheggio per i prossimi 5 anni così decido di usare Bing Maps per farmi guidare verso il mio cliente consapevole che l'esperienza non potrà essere all'altezza di Google Maps. Alla fine riesco ad arrivare a destinazione e Bing Maps non è stato poi così male anche se è chiaro che c'è ancora molto spazio per migliorare. Purtroppo non esiste la navigazione "Turn by Turn" ma mi aspetto e spero nella sua introduzione a breve vista la presenza del solido supporto vocale. Poco dopo le 4 devo caricare il telefono, non è un problema in quanto il terminale monta un connettore standard microusb, si trova sul fianco destro, molto comodo, di sicuro meglio di Hero in cui era situato nella parte inferiore e di iPhone che per essere tranquillo devi acquistare 3 cavi che come sappiamo non sono standard (uno per la macchina, uno da portare in giro col netbook e uno per l’ufficio). La durata delle batterie è in linea con HTC Hero considerando che è un 3,2" e che in entrambi i casi il Wireless è spento . Con i ritmi di cui sopra l'iPhone 3G reggeva poco più di mezza giornata (si era reso necessario il jail per poter disattivare un pò di cose).
E' venerdì e c'è un problema da un cliente, non funziona più la connettività!. Faccio 2 verifiche e devo scaricare il firmware del firewall. da internet. Non posso perché WP7 non supporta il tethering, un bel problema, per fortuna ho con me una chiavetta TIM, smonto la mia SIM mi collego ad internet e salvo la situazione.
Conclusioni.
Un altro WE è arrivato e decido di provare la parte ludica del dispositivo. Scarico qualche giochino free e qualche demo di XBOX Live. Non sono un giocatore ma capisco che giochi non semplici come Need For Speed Undercover girano davvero in maniera sorprendentemente fluida per essere su un dispositivo Mobile. Niente da invidiare alla PSP di mia nipote.
Normalmente riesco ad arrivare a fine giornata usandolo tra le altre cose anche in palestra come walkman (per un oretta scarsa). Parlando di musica la parte Zune (Software e Telefono) è davvero piacevole, una spanna avanti alla parte media di Android e più pratica di iOS che però risulta più gradevole graficamente.
In Exchange 2010, before moving a mailbox cross-forest, it is necessary to ensure the corresponing AD account has been moved to the target forest. Otherwise, the mailbox move process failes. So, the following steps focus on how to move AD accounts from the legacy Exchange forest to the Exchange 2010 forest and then how to move mailboxes afterwards.
Step 1: Move AD account
Note: Please perform the following steps in the target forest where Exchange 2010 server is installed.
1. Open Exchange Management Shell, and navigate to the folder where the Prepare-MoveRequest.ps1 script stores.
2. Type the following command and press Enter:
$cred = Get-Credential
Note: You will receive a pop-up window for entering the credential. Please enter the credential of the Administrator account in the source forest.
.\Prepare-MoveRequest.ps1 -Identity <e-mail address> -RemoteForestDomainController <FQDN of DC in source forest> -TargetMailUserOU <OU name> -RemoteForestCredential $cred
Note: Please replace <e-mail address> with the e-mail address of an AD account in the source forest.
Microsoft Outlook supports the logging of the communications that occur between Outlook and various types of e-mail servers. These logs can be helpful when you troubleshoot problems with the transfer of messages between Outlook and the e-mail server.
Outlook can log the communications with Microsoft Exchange, Post Office Protocol version 3 (POP3), Simple Mail Transport Protocol (SMTP), Internet Messaging Access Protocol (IMAP), and Hotmail servers.
To enable logging, follow these steps:
For Microsoft Outlook 2010:
To achieve redundancy and load balance for send connectors, is usefull create one sender connector. Create one Send Connector and add two anti-spam servers into smart hosts list.
Create one Send Connector and add two smart hosts list. It can achieve redundancy and load balance. The both smart hosts work together, each one take half of tasks. Anyone of them breaks down, another one will take all task.
Reference:
========
Send Connectors
http://technet.microsoft.com/en-us/library/aa998662(EXCHG.80).aspx
Exchange Server 2007 routing load balancing and fault tolerance
http://msexchangeteam.com/archive/2007/01/04/432069.aspx
Since we announced the availability of the beta version of Windows Small Business Server Code name “Aurora” and Windows Small Business Server “7”, both products have been downloaded more than 9000 times through both our partner and customer community. Today as we move forward with these new releases, Microsoft is announcing the final names, licensing and estimated availability for the next generation of the Small Business Server family currently in public preview.
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"
New HA Design Guidance Articles was wroted
Source: http://msexchangeteam.com/archive/2010/10/14/456597.aspx
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:
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/
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:
In particular we would like to call out the following fixes which have been included in this release:
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
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://workinghardinit.wordpress.com/2010/09/13/emc-does-not-show-all-database-copies-after-upgrade-to-exchange-2010-sp1-still-investigating/
The Exchange 2010 SP1 installation failed at installing mailbox role with the error "Couldn't resolve the user or group "domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust."
This issue could be caused by the Discovery Search Mailbox, Delete "DiscoverySearchMailbox" mailbox.and try to install again. You can recreate the Discovery Search Mailbox after installing Exchange 2010 SP1.
Delete "DiscoverySearchMailbox" mailbox.and try to install again
After moving mailboxes across Exchange organizations or administrative groups you have to manually update the Outlook 2003 profile when the user mailboxes are moved to a new Exchange 2007/2010 server.
If we have too many mailboxes to manage, we may use either of the following methods to automatically change Outlook 2003 users Outlook profiles.
1. Update the affected users' Outlook profile through the tool Exchange Profile Update tool (ExProfRe).
We can run the ExProfRe tool by using logon scripts or by using Group Policy. Or, you can run the ExProfRe tool at a command prompt to make the needed changes to an Outlook profile.
For detailed steps, refer to the following two articles
The Exchange Profile Update tool
http://support.microsoft.com/kb/873214
ExProfRe Operation Guide
http://www.msexchange.me.uk/tools/exalltools/exprofre/exprofre.doc
Note: The tool ExProfRe also works for Exchange 2007 users' Outlook profile
2. Another option is to update their profiles with a PRF file.
For Outlook 2003 affected clients, you can create a custom PRF file using the Custom Installation Wizard. This PRF file allows you to create a new profile or manage existing profiles. For more information on how to do this for Outlook 2003.
Customizing Outlook Profiles by Using PRF Files
http://office.microsoft.com/en-us/ork2003/HA011402581033.aspx
If the migration caused a large buildup of transaction logs, this was expected and the server has plenty of space to accomodate them. What we were not expecting was the amount of time a backup would take. DPM 2010 has been running a replica creation for about 6 hours now, We are assuming this is because we have around 100,000 1MB log files which should be purged after the backup is complete.
We can solve this problem by turning off ESEUTIL on DPM2010 and running a backup.
This allowed the backup to complete as it was ESEUTIL causing timeouts (due to the massive number of transaction logs)
Once this initial backup was complete DPM purged the transaction logs, We then turned ESEUTIL back on and ran a normal backup.
We are unable to convert distribution groups to security groups via EMC or EMS.
The groupType attribute is the one which is controlling the security and distribution "Group type" for any group-object.
The values are:
a) For Distribution "Group type", the value is: 8
b) For Universal security group: -2147483640
For global security group: -2147483646
So, If we can change the value of "Group type" via script, to convert distribution groups to security groups in bulk may be achieved.
In addition, I would like to know why you need to convert distribution groups to security groups. Because of some Exchange attribute of the distribution groups may not change to the attribute which security groups have.
For example:
The msExchRecipientDisplayType attribute of Universal Distribution Group is 1, the msExchRecipientDisplayType attribute of Universal Security Group is 1073741833.
Even if you changed the Distribution Group to Security Group via ADUC, but the msExchRecipientDisplayType attribute is still 1.
Therefore, in some scenario, Exchange server still recognize it as Security Group.
As this point, to recreate the groups as Security Group is recommended.
Actually, Microsoft not recommend to import the certificate (which is exported from Exchange 2003 server) into Exchange 2010 server
The recommended steps should be the following:
1. Generate a certificate request from Exchange 2010.
2. Submit the request to third-party CA to generate a new certificate.
3. Import the new certificate into Exchange 2010 server.
4. Enable it for Exchange services such as IIS
In this Scenario, the certificate is from Exchange 2003 server, so the domain name in the certificate only has one - the external FQND name. So, we need to follow the KB940726 to change all internal URL to the external url. So, please check if the Exchange 2010 external FQDN name is the same as the name in the Exchange 2003 certificate, if yes, you can try the KB940726. If not, you have to generate a new exchange certificate request. If you changed all internal url to external url, to recreate new DNS record (with external FQDN) in internal DNS server and point to the Exchange 2010 CAS server is best.
More info:
Create a New Exchange Certificate
http://technet.microsoft.com/en-us/library/dd351057.aspx
This section lists the Exchange Server 2010 RTM features that are discontinued in Exchange Server 2010 SP1.
Export-Mailbox and Import-Mailbox cmdlets
Use export requests or import requests. For more information, see Understanding Mailbox Import and Export Requests.
Enable-AntispamUpdates
Use Forefront Security for Exchange Server to obtain automatic anti-spam updates. For more information, see Microsoft Forefront Security for Exchange Server.
Federated Delivery
Use Tenant Mail Flow control. For more information, see Understanding Transport in a Cross-Premises Deployment.
ISInteg
Use New-MailboxRepairRequest or New-PublicFolderDatabaseRepairRequest
Managed folders in the Exchange Management Console (EMC)
In Exchange 2010 SP1, use the Shell to administer managed folder features such as managed default folders, managed custom folders, and managed folder mailbox policies. You can use the EMC and the Shell to manage retention policies and retention tags, the new messaging records management (MRM) feature introduced in Exchange 2010. For more information, see Deploying Messaging Records Management.
source: http://technet.microsoft.com/en-us/library/aa998911.aspx
Exchange 2007 SP3 is now available for download.
Exchange Server 2007 SP3 provides further flexibility with the addition of Windows Server 2008 R2 support for server roles and Windows 7 support for the Exchange management tools. These additions, along with enhancements for the advanced protection options against e-mail security threats, such as spam and viruses and the tools which help manage internal compliance and high availability needs provide Exchange administrators with the tools they need to manage their Exchange 2007 environments efficiently.
Clean installations of Exchange 2007 SP3 on a new server are possible by using this download in the same manner as you would install Exchange 2007 RTM, Exchange 2007 SP1 or Exchange 2007 SP2.
Exchange 2007 SP3 supports the installation of the Exchange 2007 management tools on a computer that is running Windows 7. Additionally, Exchange 2007 SP3 provides support for the installation of the Exchange 2007 Management Tools together with the Exchange Server 2010 Management Tools on the same Windows 7-based computer
For an overview of the new features that are available in Exchange Server 2007 SP3, see "What's New in Exchange Server 2007 SP3".