The Microsoft Dynamics CRM Team Blog
News and views from the Microsoft Dynamics CRM Team
And with that, CRM has picked up its surfboard and will be “riding the wave” with Windows Vista, Office 2007, and the biggest chain of releases in Microsoft history.
This project, codenamed V3C, is a compatibility update of the CRM v3 Outlook Client for Vista and Office 2007. V3C is a culmination of new features, updates, and enhancements, driven by our customer commitment in ensuring that users worldwide are able to use their CRM solution against the latest and greatest of Microsoft technologies. These improvements are not simply a rollup of fixes…we have implemented features and updates originally reserved for the Titan release and taken large steps forward with V3C.
Nearly every aspect of the CRM Outlook Client has been touched and updated…
- Integration with the Office 2007 “Ribbon”
- Custom MAPI Store (no more PST file!)
- SQL Express Edition 2005 SP1
- Inclusion of all existing client hotfixes
- Windows Vista Support
o User Access Control
o GPO deployments
o Internet Explorer 7
In addition, we now also support…
- Clean installation of V3C
- Upgrade from CRM V3 Outlook Client to V3C
- Support for hotfixes and patching using MSP technology
The following versions of Windows and Office are now officially supported.
- Windows 2000 SP4
- Windows XP SP2
- Windows Vista
- Office XP SP3 (with Windows 2000 and XP only)
- Office 2003 SP2
- Office 2007
Users can download V3C from this page below (please be patient, as bits are still propagating).
Today’s release is only for English, but all other languages are already undergoing localization testing and will be released in waves beginning in January.
Physical media will be updated within the next three to four months.
An updated set of scripts for Terminal Server deployment will be released in early-January.
An update to the Exchange E-mail Connector (including the Rule Deployment Wizard) for Exchange 2007 compatibility will also be released in early-January.
A date has not been set for compatibility updates to the CRM v3i and v3 SPLA Clients, but these are in the plan and forthcoming.
Thanks and see you all next year.
The newly released Microsoft Dynamics CRM V3C has an official build number of 3.0.5300.1361. This download
It's official. Microsoft released the latest version of the CRM 3.0 client that now includes support...
And it Works! Great job done! I love Vista! Of course we do have some minor wishes...
CRM v3 Outlook Client for Vista and Office 2007 has been released. It is a culmination of new features,
This is a great early Christmas present: the MS Dynamics people have released a new version of the Outlook
The Microsoft CRM Team has announced the release of the new Vista/Office 2007 client today. Direct link:
vista and outlook 2007 work good. Outside office too in online.
With much antiicpation I installed teh new V3C today. I did so on a complete new build of Vista and Office 2007. Sadly the installation package is insisting that I install .NET and SP1 but even if I wante dto I can't because Vista has it installed a part of the operating system and so won't allow manual installations of eitehr component. So, the installation won't get beyond teh point where it inssts on installing .NET, even though it is already there. Is this an oversight or me being particualrly dim?
You can download it from here. There has been a lot more added to the "V3C" update than just Vista compatibility, such as: - Integration with the Office 2007 “Ribbon” - Custom MAPI Store (no more PST file!) - SQL Express Edition 2005 SP1 - Inclusio
You can now efficiently access contacts, tasks and more in Microsoft CRM natively with Outlook 2007.
Vous pouvez télécharger cette nouvelle version du client Microsoft Dynamics CRM 3.0 pour Outlook ici
Regarding your .NET troubles, Vista ships with .NET 2.0, but Microsoft CRM 3.0 is built using .NET 1.1 SP1, which is not included in the box with Vista.
Under most conditions, our setup will allow you to install it by simply clicking a button, but if there's a language mis-match of some sort or another, it will ask you to install it manually to be sure.
If you go through the client CD image, you should find a directory where the installation packages for .NET 1.1 and it's Service Pack 1 are located. Install them manually and give things another shot--you shouldn't have any more problems.
Happy New Year!
Got the same problem as Alan - V3C Installation stops becaus .net Framework 1.1 SP1 is needed. Vista has 3.0 installed by default and I cannot install 1.1 or 2.0 manually. How can I solve this?
Does this release fix the problem with the original date of e-mails not beeing tracked in CRM?
When you track a mail message in your Outlook inbox, the actual sent date from the mail header is not stored in CRM. The date that is stored is the date when the e-mail was actually tracked in CRM, which may be different from the sent date.
I have read the newsgroup and many people are having problems with this issue. For Example:
If a customer ever has a question about when something happened, the date of the CRM entry is the best tool for determining a sequence of events. Dates are often used to confirm when conversations occurred, emails were sent and
received, etc. This information could also be used as evidence in a court of law should a dispute arise. Without having the original dates of conversations, emails, etc., you would be unable to track or prove due diligence.
historical emails being uploaded to CRM with the current system date means that an accurate chronological order of emails will not be accurate in CRM.
This is surely a legal requirement of any organisation anywhere in the world.
Can anyone inform me whether this issue has been fixed with this release and (if not) whether there are any plans of changing this "track" behaviour??
PLeased that this has been released, however I am having an installation issue near the end of the process. I have a failure as follow:
"Action Microsoft Crm.Setup.Client.InstallPstAction failed: WritePrivateProfileSection failed!
Has anyone else had this occurence and is it a known problem?