Outils sp2013

Voici quelques-uns des outils 2013 de SharePoint 2013

1 UGSF – Pierre Erol GIRAUDY

OUTILS SP2013

Cette liste n’est pas exhaustive Merci de me communiquer des mises à jour

[email protected]

Contenu SP2013 AutoSPInstaller .............................................................................................................. 3

SP2013 Manager 2013 ............................................................................................................... 4

SharePoint 2013 Solution Deployer 4.0 ..................................................................................... 5

SP2013 WarmMeUp ................................................................................................................... 6

Replication Engine SP2013 ........................................................................................................ 7

SharePoint PowerShell Wizard ................................................................................................... 8

Free Tools IDERA ..................................................................................................................... 9

AVEPOINT .............................................................................................................................. 10

IP-Label .................................................................................................................................... 11

Schémas fonctionnel ................................................................................................................ 12

SharePoint 2013 Designer ........................................................................................................ 13

SharePoint Designer 2013′s Missing Design View – It’s Official ....................................... 14

SharePoint 2013 Design View Changes and Change Management 101 .............................. 15

Communication .................................................................................................................... 16

Lack of an alternative ........................................................................................................... 16

Lack of engagement ............................................................................................................. 16

Conclusion ............................................................................................................................ 16

RSD .......................................................................................................................................... 17

Apply information governance to SharePoint without impeding its benefits ...................... 17

HarePoint Analytics For SharePoint 2013 ............................................................................... 18

dSHIFT migration et management ........................................................................................... 19

Microsoft Outlook Baseline Diagnostic ................................................................................... 19

mailto:[email protected]



[SDP 3][2c425a45-1620-42a4-ae4d-63b453394935] Microsoft Outlook Baseline

Diagnostic ............................................................................................................................. 20

2659007 Outlook Configuration Analyzer Tool information .............................................. 29

Common Support Conditions Tested by the Diagnostic ...................................................... 34

Run Office diagnostics ......................................................................................................... 39

Discussions under Diagnostics ............................................................................................. 39

Quest ......................................................................................................................................... 42

Quest Migration Suite for SharePoint 2013 Preview ............................................................... 43

Quest Migration Suite for SharePoint 2013 Preview ........................................................... 43

Licensing Quest .................................................................................................................... 43

Capacity Planning Guide spreadsheet for Windows Azure Caching ....................................... 45



SP2013 AutoSPInstaller jeudi 4 octobre 2012 07:10

Capture d'écran effectuée : 04/10/2012 07:11

http://autospinstaller.codeplex.com/





SP2013 Manager 2013 jeudi 4 octobre 2012 07:11


http://spm.codeplex.com/

http://spm.codeplex.com/



SharePoint 2013 Solution Deployer 4.0 lundi 8 octobre 2012 11:12

SPSD SharePoint Solution Deployer - Download: SharePoint Solution Deployer 4.0 http://spsd.codeplex.com/releases/view/92451 Capture d'écran effectuée : 08/10/2012 11:13

http://spsd.codeplex.com/releases/view/92451



SP2013 WarmMeUp lundi 8 octobre 2012 11:13

WarmMeUp http://warmmeup.codeplex.com/ Capture d'écran effectuée : 08/10/2012 11:14

http://warmmeup.codeplex.com/

http://warmmeup.codeplex.com/



Replication Engine SP2013 mardi 9 octobre 2012 10:45

Informations sur les fichiers téléchargés | Microsoft Connect http://connect.microsoft.com/office/Downloads/DownloadDetails.aspx?DownloadID=46217 Capture d'écran effectuée : 09/10/2012 10:45

http://connect.microsoft.com/office/Downloads/DownloadDetails.aspx?DownloadID=46217



SharePoint PowerShell Wizard mardi 9 octobre 2012 17:39

SharePoint PowerShell Wizard http://sppowershellwizard.codeplex.com/ Capture d'écran effectuée : 09/10/2012 17:40

http://sppowershellwizard.codeplex.com/

http://sppowershellwizard.codeplex.com/



Free Tools IDERA mardi 9 octobre 2012 10:25

Free Tools for SQL Server, SharePoint and PowerShell from Idera https://www.idera.com/Free-Tools/?s=WC_SPEB_121008-WC-SPToolset&utm_source=SPEB&utm_medium=email&utm_campaign=121008-WC-SPToolset&utm_content=WC Capture d'écran effectuée : 09/10/2012 10:25

https://www.idera.com/Free-Tools/?s=WC_SPEB_121008-WC-SPToolset&utm_source=SPEB&utm_medium=email&utm_campaign=121008-WC-SPToolset&utm_content=WC

https://www.idera.com/Free-Tools/?s=WC_SPEB_121008-WC-SPToolset&utm_source=SPEB&utm_medium=email&utm_campaign=121008-WC-SPToolset&utm_content=WC



AVEPOINT mercredi 10 octobre 2012 08:00

SharePoint Download Registration https://www.avepoint.com/resources/free-trial-downloads-form/?select=docave6 Capture d'écran effectuée : 10/10/2012 08:00

https://www.avepoint.com/resources/free-trial-downloads-form/?select=docave6



IP-Label mercredi 10 octobre 2012 12:21

William Rang

Directeur Général Délégué

Tél : +33 (0)1 41 05 49 76 Mob : +33 (0)6 73 86 16 39 Fax : +33 (0)1 49 64 03 80

www.ip-label.fr

Siège : 90 boulevard National | 92250 La-Garenne-Colombes | France

http://www.ip-label.net/



Schémas fonctionnel mercredi 10 octobre 2012 07:05

http://intranetfactory.com/IntranetModeler.aspx

IntranetFactory. Intranet Modeler - free SharePoint wireframing and prototyping http://intranetfactory.com/IntranetModeler.aspx Capture d'écran effectuée : 10/10/2012 07:06





SharePoint 2013 Designer lundi 15 octobre 2012 11:58

SPD2013 vendredi 12 octobre 2012 07:58

Changes to the Design View in SharePoint Designer 2013 by

[email protected] on 10/10/2012 9:30 AM Category: SharePoint Designer SharePoint 2013 designers Developers Hi, I’m Keenan Newton, a senior product marketing manager on the SharePoint team. We’re making some changes to the Design View in SharePoint Designer 2013, and I wanted to talk about the reasoning behind the changes. With SharePoint Server 2013 embracing new web standards for client side rendering of pages such as JavaScript, JSON, and OData, there is no longer a need to support a visual web page editor within SharePoint Designer. With that in mind, we removed the ability to visually edit pages in SharePoint Designer 2013 because its page editor is designed to only understand the unique features of a SharePoint web page. With our support of new web standards, any web page designer can now be used for editing web pages in SharePoint Server 2013. This includes form customization, conditional formatting of page content, layout, theming and branding. To simplify the process of integrating customized SharePoint pages, SharePoint Server 2013 includes a new feature called the SharePoint Design Manager. This feature enables a web designer to export a web page from SharePoint, customize it, and then import it back into SharePoint, all right from the SharePoint site. SharePoint Designer 2013 will continue to support site, workflow, list, library, and external data customization and configuration. However, we will look for opportunities to leverage SharePoint itself as the primary tool for customization and configuration tasks.

Collé à partir de <http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1034>

Hi, I’m Keenan Newton, a senior product marketing manager on the SharePoint team.

We’re making some changes to the Design View in SharePoint Designer 2013, and I

wanted to talk about the reasoning behind the changes.

With SharePoint Server 2013 embracing new web standards for client side rendering of

pages such as JavaScript, JSON, and OData, there is no longer a need to support a visual

web page editor within SharePoint Designer. With that in mind, we removed the ability to

visually edit pages in SharePoint Designer 2013 because its page editor is designed to

only understand the unique features of a SharePoint web page. With our support of new

web standards, any web page designer can now be used for editing web pages in

SharePoint Server 2013. This includes form customization, conditional formatting of page

content, layout, theming and branding. To simplify the process of integrating customized

SharePoint pages, SharePoint Server 2013 includes a new feature called the SharePoint

Design Manager. This feature enables a web designer to export a web page from

SharePoint, customize it, and then import it back into SharePoint, all right from the

SharePoint site.

SharePoint Designer 2013 will continue to support site, workflow, list, library, and

external data customization and configuration. However, we will look for opportunities to

leverage SharePoint itself as the primary tool for customization and configuration tasks.

Category: SharePoint Designer; SharePoint 2013; designers; Developers

Published: 10/10/2012 9:30 AM

http://o/

http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1034

http://sharepoint.microsoft.com/blog/Pages/CategoriesCategory.aspx?CategoryId=218&Name=SharePoint%20Designer

http://sharepoint.microsoft.com/blog/Pages/CategoriesCategory.aspx?CategoryId=340&Name=SharePoint%202013

http://sharepoint.microsoft.com/blog/Pages/CategoriesCategory.aspx?CategoryId=341&Name=designers

http://sharepoint.microsoft.com/blog/Pages/CategoriesCategory.aspx?CategoryId=160&Name=Developers


http://sharepoint.microsoft.com/blog/_layouts/listform.aspx?PageType=4&ListId=%7b9296808B-00CB-4E7E-B944-A7BDABB0753A%7d&ID=218&RootFolder=*






SharePoint Designer 2013′s Missing Design View – It’s Official lundi 15 octobre 2012 11:57

Categories: SharePoint by Marc October 11, 2012 Well, Keenan Newton did a post on the Microsoft SharePoint Team Blog entitle Changes to the Design View in SharePoint Designer 2013 yesterday that makes it official: the Design View in SharePoint Designer 2013 is not just missing, it’s not coming back. I’m reproducing Keenan’s post below, but you should also read it in situ, as the comments are already piling up, and they aren’t positive.

Hi, I’m Keenan Newton, a senior product marketing manager on the SharePoint team. We’re making some changes to the Design View in SharePoint Designer 2013, and I wanted to talk about the reasoning behind the changes. With SharePoint Server 2013 embracing new web standards for client side rendering of pages such as JavaScript, JSON, and OData, there is no longer a need to support a visual web page editor within SharePoint Designer. With that in mind, we removed the ability to visually edit pages in SharePoint Designer 2013 because its page editor is designed to only understand the unique features of a SharePoint web page. With our support of new web standards, any web page designer can now be used for editing web pages in SharePoint Server 2013. This includes form customization, conditional formatting of page content, layout, theming and branding. To simplify the process of integrating customized SharePoint pages, SharePoint Server 2013 includes a new feature called the SharePoint Design Manager. This feature enables a web designer to export a web page from SharePoint, customize it, and then import it back into SharePoint, all right from the SharePoint site. SharePoint Designer 2013 will continue to support site, workflow, list, library, and external data customization and configuration. However, we will look for opportunities to leverage SharePoint itself as the primary tool for customization and configuration tasks.

I’m not going to be politic about it: this is going to hurt Microsoft and it’s a horrible decision. The things you may be able to use Design Manager to do and workflows are not what the majority of people use SharePoint Designer for. Code View will do those same people virtually zero good, and there’s no replacement strategy. Here are some of my specific beefs with the “official” stance that Keenan puts forth.

…we removed the ability to visually edit pages in SharePoint Designer 2013 because its page editor is designed to only understand the unique features of a SharePoint web page.

Exactly! The reason we choose to use SharePoint Designer is *because* it understands ”the unique features of a SharePoint web page”. Nothing else does. For better or worse, SharePoint 2013′s forms, for example, as the same as they have been in 2007 and 2010, based on the List Form Web Part. No other editor knows what that is. SharePoint Designer does.

…any web page designer can now be used for editing web pages in SharePoint Server 2013. This has always been the case, but who has decided to use Notepad or anything else in the past? We’ve always had the option to copy aspx page content out into some other editor to work on it, and that seems to be what Microsoft is recommending now. SharePoint Designer was and is the only IDE

http://sympmarc.com/category/sharepoint/

http://sympmarc.com/author/mdenton22/

http://sharepoint.microsoft.com/blog

http://sympmarc.com/blog/Pages/BlogPost.aspx?pID=1034

http://sympmarc.com/blog/Pages/BlogPost.aspx?pID=1034



that understands SharePoint’s page structures, controls, and Data Sources. With any other tool, we have to know ourselves how to set up a Data Source in a DVWP or which controls to add to take advantage of SharePoint-specific functionality. In the newly neutered SharePoint Designer, many of the ribbon buttons actually serve no purpose anymore. Things like Conditional Formatting, DVWP formatting options, etc. don’t function unless we write our own code first. On top of that, there is no longer a surface where SharePoint Designer can show us errors in that code. Errors, cryptic or not, have always been shown in the Design (or Split) View. Now we will be flying blind.

To simplify the process of integrating customized SharePoint pages, SharePoint Server 2013 includes a new feature called the SharePoint Design Manager…

Maybe Microsoft believes that the Designer word in SharePoint Designer means that people only use it for design. As you and I know, design is only one small piece of how we use SharePoint Designer. Design Manager also is only useful if you want to apply a design via a master page or page layout to an entire Site Collection that has publishing features enabled. It doesn’t do us any good on individual pages where we want to make small customizations in the design or structure for single-location functionality. All in all, I’m very disappointed in Microsoft’s decision on this one. As I’ve been telling people, I’ll be fine. As a consultant, I can keep working with SharePoint 2007 and 2010 for a long time and make a decent living at it. I can even learn to work in the Code View exclusively in SharePoint Designer 2013. I’m worried about all of the unsung heroes out there in SharePointland who have been using SharePoint Designer to build solutions that their organizations actually use, rather than what IT typically jams down their throats. Those of us who believe in user empowerment and citizen development have lost a battle this day. Important! For another great slant on all of this, check out Michal Pisarek’s (@michalpisarek) great post from yesterday SharePoint 2013 Design View Changes and Change Management 101. In it, he makes some excellent points about how the change management around all of this has been abysmal. Collé à partir de <http://sympmarc.com/2012/10/11/sharepoint-designer-2013%E2%80%B2s-missing-design-view-its-official/>

SharePoint 2013 Design View Changes and Change Management 101 lundi 15 octobre 2012 11:57 [ 1 ] October 10, 2012 | Michal Pisarek I am sure that by now you have heard that the design view in SharePoint Designer 2013 has been officially removed as detailed in this post by the Microsoft team. There have been a wide range of opinions around this from some pretty well respected people including Bjorn Furuknap and Marc Anderson in addition to some lively banter on TechCenter where people are voicing their concerns. I’m not going to get into whether this is a good thing or a bad thing. It’s a complicated argument and one that is a classic wicked problem. However what intrigues me about this whole situation is more about how this is being communicated and handled, rather than why the decision was made.

Microsoft has traditionally been very good about keeping legacy functionality in products for supportability, probably to the detriment of themselves. We upgrade software, our old stuff still works and all is good. However in this case a decision was made to remove a piece of functionality that is heavily used, regardless of its crapiness or not. In SharePoint projects change management is paramount, the same as it should be when releasing new product features to users. For those of you that feel slighted or annoyed by the decision to remove this piece of functionality, this is exactly the same feeling that most users have when we implement SharePoint without considering the potential change management issues. I want to point out how important change management is any scenario but I hope that this one resonates with those of us that are SharePoint consultants because the

http://twitter.com/michalpisarek

http://www.sharepointanalysthq.com/2012/10/sharepoint-2013-design-view-changes-and-change-management-101/

http://sympmarc.com/2012/10/11/sharepoint-designer-2013%E2%80%B2s-missing-design-view-its-official/

http://sympmarc.com/2012/10/11/sharepoint-designer-2013%E2%80%B2s-missing-design-view-its-official/



http://www.sharepointanalysthq.com/2012/10/sharepoint-2013-design-view-changes-and-change-management-101/#comments

http://www.sharepointanalysthq.com/author/admin/


http://blog.furuknap.net/i-was-wrong-kill-the-sharepoint-designer-design-view

http://sympmarc.com/2012/09/19/sharepoint-designer-2013%E2%80%B2s-missing-design-view-more-thoughts/

http://social.technet.microsoft.com/Forums/en-US/sharepointitpropreview/thread/8f8e2cb3-a90f-4653-9d22-050f9f0d8612

http://www.slideshare.net/paulculmsee/how-to-avoid-sharepoint-becoming-a-wicked-problem



same pain we feel at this decision is the same type of pain our end users feel when they get SharePoint thrust upon them.

Communication In the same way that an end user comes in one day and finds out that their homepage is set to SharePoint for some unknown reason and they have to fundamentally change the way that they work, some in the SharePoint community feel the same way about having the design view removed. What has happened is that a huge decision has been made that will change the way that people work with only minor and delayed communication from Microsoft that many view as inadequate. Imagine if Microsoft said a year ago that this could be the direction that they were going and they wanted some feedback? Imagine if more guidance was issued beforehand to ensure that existing solutions on SharePoint 2010 were not making use of this functionality as it posed an upgrade risk? Wouldn’t we all feel better? Now think of this when you roll out SharePoint to your end users without adequate communication throughout the entire process. The same feeling of being screwed, shafted, or any other term that you can conjure happens in far too many SharePoint projects.

Lack of an alternative Lets go back to our SharePoint end user. They come in, see that their fileshare has been locked down and now they are forced to use this new system called SharePoint (this has happened). Now there are simply things that they cant do in SharePoint or don’t work as easily as it did on the fileshare (we are facing an issue with AutoCad files for a client for example). They ask their organization what they should do and the response is “Sorry that’s how you have to do it now, go figure out how to make this work” The same has happened in this design view situation. People are annoyed because there really isn’t an alternative at the moment. Yes there are different technologies that could replace this (Apps and Napa for example) but without communication from Microsoft or discussion about an alternative people are feeling that they are getting this shoved down their throats. Why not sponsor focus groups beforehand to discuss alternatives? Why not engage experts to find out if the alternatives are feasible? Taking something away from people without and alternative sucks, but what is worse is the feeling of powerlessness when there isn’t an alternative.

Lack of engagement People don’t like two things when it come to change: being planned at rather than with and being surprised. In

this case we got both! No one was really aware of the planned changes and when we were informed we were universally surprised. In the same way that you have to engage your end users so that they feel that decisions that impact them are being made by them in a SharePoint project, Microsoft should of really engaged the community a little more about the issues and potential pitfalls of this decision. Most people, even if they don’t agree with the decision being made, would be much more comfortable in understanding why the decision was made. Engagement with users must occur otherwise regardless of the decision made you will achieve no buy in at any level.

Conclusion So whether you agree with the decision to remove the design view or not the whole thing has been handled pretty poorly, in the same way that SharePoint Change Management is handled quite poorly. For us consultants or creators of solutions on SharePoint remember how important it is to engage and communicate to your stakeholders and end users. Otherwise a small technical decision, such as this one, can have a much greater impact. I would love to hear your thoughts since there is a lot of passion around this issue so lets hear it!!

Collé à partir de <http://www.sharepointanalysthq.com/2012/10/sharepoint-2013-design-view-changes-and-change-management-101/>





RSD lundi 15 octobre 2012 12:32

News, events, training | RSD Information Governance http://www.rsd.com/en/about-rsd/news-events-training Capture d'écran effectuée : 15/10/2012 12:33

Apply information governance to SharePoint without impeding its benefits lundi 15 octobre 2012 12:34

http://www.rsd.com/en/about-rsd/news-events-training



Governance Services for SharePoint® 2010 | RSD Information Governance http://www.rsd.com/en/products/governance-services-sharepoint-2010 Capture d'écran effectuée : 15/10/2012 12:34

HarePoint Analytics For SharePoint 2013 mercredi 17 octobre 2012 16:15

HarePoint Analytics For SharePoint 2013 Current version: 15.0.0.1, released on 8/20/2012, 15119 KB HarePoint Analytics for SharePoint 2013 is a solution for collecting and analysing data about the usage of site collections of SharePoint 2013 product family. DownloadOverview

Collé à partir de <http://www.harepoint.com/Downloads/Default.aspx>

HarePoint Analytics for SharePoint 2013/2010/2007 Administrator Guide This manual contains information for the successful installation of HarePoint Analytics for SharePoint. We ask that you read the contents of this manual carefully before starting the installation process. This manual includes technical information regarding installation, upgrade, migration and configuration of the product. It is intended for SharePoint and SQL Server administrators. Download PDF

HarePoint Analytics for SharePoint 2010/2007 User Guide

http://www.rsd.com/en/products/governance-services-sharepoint-2010

http://www.harepoint.com/DownloadProducts/HarePointAnalyticsForSharePoint2013.zip

http://www.harepoint.com/DownloadProducts/HarePointAnalyticsForSharePoint2013.zip

http://www.harepoint.com/Downloads/Default.aspx

http://www.harepoint.com/Products/HarePointAnalyticsForSharePoint/HarePoint_Analytics_Admin_Guide_EN.pdf



This guide helps to understand how to work with HarePoint Analytics for SharePoint: quick start, reports selection and generation, filters usage, data grouping and sorting, etc. It will be helpful for all initial users of the solution. Download PDF: English

Collé à partir de <http://www.harepoint.com/Products/HarePointAnalyticsForSharepoint/Documentation.aspx>

dSHIFT migration et management lundi 22 octobre 2012 10:30

dSHIFT Admin Tool for SharePoint | dSHIFT http://new.dshift.com/solutions/sharepoint-admin-tool/ Capture d'écran effectuée : 22/10/2012 10:30

Microsoft Outlook Baseline Diagnostic lundi 22 octobre 2012 11:42

Collé à partir de <http://support.microsoft.com/kb/2680810/EN-US>

http://www.harepoint.com/Products/HarePointAnalyticsForSharePoint/HarePoint_Analytics_User_Guide_EN.pdf

http://www.harepoint.com/Products/HarePointAnalyticsForSharepoint/Documentation.aspx

http://new.dshift.com/solutions/sharepoint-admin-tool/

http://support.microsoft.com/kb/2680810/EN-US



[SDP 3][2c425a45-1620-42a4-ae4d-63b453394935] Microsoft Outlook Baseline Diagnostic Article ID: 2680810 - View products that this article applies to.

Expand all | Collapse all

On This Page

Summary More information Third-party add-ins that are installed for Outlook Third-party modules that are running under Outlook Autodiscover configuration information Autorun information Background Intelligent Transfer Service (BITS) information Outlook-Exchange delegate configuration Environment variables Application log BITS event log System log Updates that are installed on the computer Outlook configuration summary Processes that are running on the computer Windows registry keys Networking details Information about important Outlook and MAPI files DLL files that are running under the Outlook.exe process Robust Office Inventory Scan output Common Support Conditions Tested by the Diagnostic References Properties Give Feedback

<style>.tocTitle, #tocDiv{display: none;}</style>

Summary

This Support Diagnostics Platform (SDP) manifest file collects configuation settings, registry keys, client

networking configuration information, event logs, and important file details that are used by the

following Microsoft Office applications:

o Microsoft Outlook

http://support.microsoft.com/kb/2680810/EN-US#appliesto



























Also, to help troubleshoot common support issues, a series of configuration checks are run to check

whether you may be encountering the conditions that are specified by the checks.

Note When you run the Outlook Baseline Diagnostic, you may be prompted to select a version of

Microsoft Office if you have both Office 20013 (Click-to-Run) and an earlier version of Office installed.

Make sure that you select the version in which you are experiencing a problem with Outlook.

On the Data Collection Options page, you are prompted to select either Full or Custom for the data

collection. Always select the Full option unless you receive other advice from a support engineer.



Back to the top | Give Feedback

More information

Notes

o This diagnostic can be used on the following versions of Windows: Windows 8 Windows 7 Windows Vista Windows XP Windows Server 2003 Windows Server 2008

o All file names in the data collection are prefaced with <ComputerName>. This placeholder

represtens the name of the computer on which the Microsoft Support Diagnostic Tool is

run. o Some file names in the data collection include <full path>. This placeholder represents the

full path of the file on the hard disk. Third-party add-ins that are installed for Outlook

http://support.microsoft.com/kb/2680810/EN-US#top

http://support.microsoft.com/kb/2680810/EN-US#survey




Description File name

TXT file containing a list of third-party add-ins {Computername}_3rd_party_addins.txt

TXT file containing a list of Microsoft add-ins {Computername}_msft_addins.txt

Third-party modules that are running under Outlook


TXT file containing a list of third-party modules

running under the selected process

{Computername}_3rd_party_Modules.txt

Autodiscover configuration information

Note The diagnostic uses the default Outlook profile that is configured on your computer to retrieve

this information.


Autodiscover configuration {Computername}_Autodiscover.xml

Autodiscover related settings in the registry {Computername}_AutodiscoverSettings.txt

Autorun information

For more information about the Autoruns utility that is used to collect this information, go to the

following Microsoft TechNet website:

http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx


Autorun information in .htm file format {Computername}_Autoruns.htm

Autorun information in .xml file format {Computername}_Autoruns.xml

Background Intelligent Transfer Service (BITS) information

http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx



BitsAdmin log and registry data that is related to BITS


BitsAdmin Command to display

current jobs.

{Computername}_BitsClient_bitsadmin-list-allusers-

verbose.txt

BITS Client Registry Keys {Computername}_BitsClient_reg.txt

Details on Click-to-run installations of Office 2013

Configuration-related information about Office 2013 Click-to-run installations.


Text file containing Click-to-run configuration

details.

{Computername}_Click-To-

Run_Details.txt

Outlook-Exchange delegate configuration

Note The diagnostic uses the default Outlook profile that is configured on your computer to retrieve

this information.


Delegate configuration details. File is in .txt format. {Computername}_DelegateInfo.txt

Environment variables



Text file that contains environment variables and their values. The same set of environment variables is

a subset of the values that are displayed by running the Set command in a command prompt window.

Description File

Text file containing environment variables

and their values.

{Computername}_EnvironmentVariables.txt

Application log

Events from the last 15 days that were recorded in additional formats (.csv, and .txt) and in the full

Application log (.evtx).


Export of the Application event log in .csv format. {Computername}_evt_Application.csv

Export of the Application event log in .evtx format.

Use Event Viewer to read.

{Computername}_evt_Application.evtx

Export of the Application event log in .txt format. {Computername}_evt_Application.txt

BITS event log

Events from the last 15 days are recorded in additional formats (.csv, and .txt) and in the full System

log (.evtx).


Export of the Bits-Client Operational event log in

.csv format.

{Computername}_evt_BitsClient-

Operational.csv




.evtx format. Use Event Viewer to read.


Operational.evtx


.txt format.


Operational.txt

Microsoft Office Alerts log files

Events over the last five (5) days from the Microsoft Office Alerts log files.


Export of the Microsoft Office Alerts event log file in

.csv format.

{Computername}_evt_OAlerts.csv


.evtx format.

{Computername}_evt_OAlerts.evtx


.txt format.

{Computername}_evt_OAlerts.txt

System log

Events from the last 15 days are recorded in additional formats (.csv, and .txt) and in the full System

log (.evtx).


Export of the System log in .csv format. {Computername}_evt_System.csv

Export of the Application log in .evtx format. {Computername}_evt_System.evtx

Export of the Application log in .txt format. {Computername}_evt_System.txt

Resultant Set of Policy (RSoP) generated by GPResult.exe




Output from running GPResult.exe. File is in .htm

format.

{Computername}_GPResult.htm

Output from running GPResult.exe. File is in .txt format. {Computername}_GPResult.tx

Updates that are installed on the computer


List of updates that are installed on the client in .csv format. {Computername}_Hotfixes.csv

List of updates that are installed on the client in .htm format. {Computername}_Hotfixes.htm

List of updates that are installed on the client in .txt format. {Computername}_Hotfixes.txt

Identity logging

If "Identity" logging has been enabled, the baseline will collect the logs generated by this logging. This

logging information is specific to Office 2013 account functionality configurable in the backstage.


Zip file containing the MsoidLiteTrace log file and

MsoCredProv.txt.

{Computername}_IdentityLogging.zip

Internet Explorer proxy settings


Text file summarizing the proxy settings on the

Local Area Network (LAN) Settings dialog box.

{Computername}_IE_Proxy_Settings.txt

Installed products on the computer




List of installed products on the client in .csv

format.

{Computername}_Installed_Products.csv

Junk e-mail Safe Senders, Safe Recipients, and Blocked Senders lists

Note: The diagnostic uses the default Outlook profile to retrieve this information.


Text file containing the entries from the Safe

Senders, Safe Recipients, and Blocked Senders lists

(junk e-mail settings).

{Computername}_Junkmail_Settings.txt

Module signatures

Note: The diagnostic uses the default Outlook profile to retrieve this information.


Text file containing the Authenticode

signature status of each module loaded by

the Outlook.exe process.

{Computername}_Module_Signature_Status.txt

Microsoft add-ins installed for Outlook




TXT file containing a list of Microsoft add-ins {Computername}_msft_addins.txt

Outlook Configuration Analyzer Tool (OCAT) result files

For additional information about the OCAT tool, please see the following article in the Microsoft

Knowledge Base:

2659007 Outlook Configuration Analyzer Tool information http://support.microsoft.com/kb/2659007/EN-US


HTML version of the OCAT scan. A shortcut to a

locally saved copy of this file is also created on

the user's desktop.

{Computername}_OCAT_Report.html

OCAT scan result file. {Computername}_OCAT_Results.xml

OCAT scan log file. {Computername}_OCAT_Results.xml.log

Outlook configuration summary


Text file that contains a summary report of

profile settings

{Computername}_Outlook_Configuration

_Summary.txt

Processes that are running on the computer





List of processes and related services that are running on the

computer

{Computername}_Processes.txt

Windows registry keys

Text files that contain exported keys from the Windows registry.


HKEY_CURRENT_USER\Software\Microsoft\Exchange {Computername}_reg_Outlook_HKCU_Exchange.reg

{Computername}_reg_Outlook_HKCU_Exchange.txt

HKEY_CURRENT_USER\Software\Microsoft\Office {Computername}_reg_HKCU_Office.reg

{Computername}_reg_HKCU_Office.txt

HKEY_CURRENT_USER\Software\Policies {Computername}_reg_HKCU_Policies.reg

{Computername}_reg_HKCU_Policies.txt

HKEY_LOCAL_MACHINE\Software\Clients

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Clients

{Computername}_reg_Outlook_HKLM_Clients.reg

{Computername}_reg_Outlook_HKLM_Clients.txt

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\

Windows Messaging Subsystem

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Messaging

Subsystem

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\

Windows Messaging Subsystem

{Computername}_reg_Outlook_MsgSubSys.reg

{Computername}

_reg_Outlook_MsgSubSys.txt

HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Windows NT\

CurrentVersion\ProfileList\S-1-5-21-124525095-708259637-

1543119021-5094

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows

NT\

CurrentVersion\ProfileList\S-1-5-21-124525095-708259637-

1543119021-5094

{Computername}_reg_RoamingProfileSettings.reg

{Computername}_reg_RoamingProfileSettings.txt



HKEY_LOCAL_MACHINE\Software\Microsoft\

Windows NT\CurrentVersion\Image File Execution Options

HKEY_LOCAL_MACHINE\Software\Wow6432Node\

Microsoft\Windows NT\CurrentVersion\Image File Execution Options

{Computername}_reg_HKLM_IFEO.reg

{Computername}_reg_HKLM_IFEO.txt

HKEY_LOCAL_MACHINE\Software\Microsoft\

Office

HKEY_LOCAL_MACHINE\Software\

Wow6432Node\Microsoft\Office

{Computername}_reg_HKLM_Office.reg

{Computername}_reg_HKLM_Office.txt

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\

Office

{Computername}_reg_HKLM_Policies.reg

{Computername}_reg_HKLM_Policies.txt

Networking details


Text file containing network-related parameters. {Computername}_SMB-Info.txt

Text file containing TCP/IP related information from the

computer.

{Computername}_TcpIp-Info.txt

Information about important Outlook and MAPI files

Text and .csv files that contain details about important files used by Outlook. File details include the

following:

o Version o Location o Description o Size o Date o Company


Details on the files in Office specific

folders (for example, Office14) in the

\Program Files\Common

Files\Microsoft Shared folder.

{Computername}_sym_CommonProgramFilesOffice.csv

{Computername}_sym_CommonProgramFilesOffice.txt



Details on the files in the \Program

Files\Common Files\System folder.

{Computername}_sym_CommonProgramFilesSystem.csv

{Computername}_sym_CommonProgramFilesSystem.txt


Files\Common Files\Microsoft

Shared\VSTO folder.

{Computername}_CommonProgramFilesVSTO.csv

{Computername}_CommonProgramFilesVSTO.txt



\Program Files (x86)\Common

Files\Microsoft Shared folder.

{Computername}_sym_CommonProgramFilesx86Office.csv

{Computername}_sym_CommonProgramFilesx86Office.txt


Files (x86)\Common Files\System

folder.

{Computername}_sym_CommonProgramFilesx86System.csv

{Computername}_sym_CommonProgramFilesx86System.txt

Dtails on the files in the \Program Files

(x86)\Common Files\Microsoft

Shared\VBA folder.

{Computername}_CommonProgramFilesx86VBA.csv

{Computername}_CommonProgramFilesx86VBA.txt


Files (x86)\Common Files\Microsoft

Shared\VSTO folder.

{Computername}_CommonProgramFilesx86VSTO.csv

{Computername}_CommonProgramFilesx86VSTO.txt



\Program Files\Microsoft Office or

\Program Files (x86)\Microsoft Office

folder.

{Computername}_sym_ProgramFilesOffice.csv

{Computername}_sym_ProgramFilesOffice.txt



\Program Files\Microsoft

Office\Office14\Addins or \Program

Files (x86)\Microsoft

Office\Office14\Addins folder.

{Computername}_sym_ProgramFilesOfficeAddins.csv

{Computername}_sym_ProgramFilesOfficeAddins.txt

Details on the dll files in the

\Windows\system32 folder.

{Computername}_sym_System32.csv

{Computername}_sym_System32.txt

Details on the dll files in the

\Windows\SysWow64 folder.

{Computername}_sym_Syswow64.csv

{Computername}_sym_Syswow64.txt


Files\Microsoft Office

15\root\vfs\programfilescommonx64

folder and its subfolders. Files are only

collected on Click-to-Run installations

of Office 2013.

{Computername}_Sym_C2R_ProgramFilesCommonx64.CSV

{Computername}_Sym_C2R_ProgramFilesCommonx64.TXT




Files\Microsoft Office

15\root\vfs\programfilescommonx86

folder and its subfolders. Files are only

collected on Click-to-Run installations

of Office 2013.

{Computername}_Sym_C2R_ProgramFilesCommonx86.CSV

{Computername}_Sym_C2R_ProgramFilesCommonx86.TXT

DLL files that are running under the Outlook.exe process


List of DLL files that are currently running under the

Outlook.exe process. File is in .csv format.

{Computername}_sym_Outlook_Process.csv

List of DLL files that are currently running under the

Outlook.exe process. File is in .txt format.

{Computername}_sym_Outlook_Process.txt

Robust Office Inventory Scan output


Text file that contains a list of all installed applications of

the supported Office families.

{Computername}_ROIScan.log

Uploaded files

Zip file containing one or more files you elected to upload to Microsoft.

Description File

Zip file containing the file(s) you selected to have uploaded to

Microsoft.

{Computername}_File.zip



Common Support Conditions Tested by the Diagnostic The Outlook Baseline Diagnostic performs a series of checks to determine whether your computer

configuration matches configurations that cause known issues in Outlook. If there is a fix available for a

detected issue, you can click Apply this fix to fix the issue. If the diagnostic does not have a fix for a

detected issue, you are given a link to an article in the Microsoft Knowledge Base on the issue. You can

use the information in the article to address the issue.

The following checks are performed by the Outlook Baseline Diagnostic.

o Outlook can't run with AppCompat enabled

This check looks to see if Outlook is configured to run in compatibility mode. This issue is

documented in the following article in the Microsoft Knowledge Base.

252304 You may receive an error message and Outlook does not start when you try to

start Outlook on a computer that is running Windows XP

http://support.microsoft.com/kb/252304 o Performance problems due to indexing online mailboxes

If your Outlook 2007 profile is configured in Online mode, your Outlook 2007 client may

exhibit performance issues if you also have certain group policies configured for Windows

Desktop Search.

If this problem is detected, you are directed to the following Microsoft blog on this issue.

http://blogs.technet.com/b/mikelag/archive/2009/05/04/windows-desktop-search-and-

the-implications-on-wan-performance.aspx o Outlook is crashing due to an incompatibility with the Dpofeedb.dll file

If the Dpofeedb.dll file is running under the Outlook.exe process, as a result of the

installation of a third-party add-in, Outlook may crash when you work with shared

calendar folders. This check examines the data in your application event log to see if you

have any crashes due to this file.

Please see the following article in the Microsoft Knowledge Base for additional

information.

2621487 Outlook 2007 crashes when you open a shared calendar

http://support.microsoft.com/kb/2621487 o Collaboration Data Objects 1.2.1 installed

If you are using Outlook 2010 and you have Collaboration Data Objects (CDO) 1.2.1

installed, the Office Baseline diagnostic will alert you of this unsupported configuration.

Please see the following article in the Microsoft Knowledge Base for additional details on

http://support.microsoft.com/kb/252304

http://blogs.technet.com/b/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx

http://blogs.technet.com/b/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx




this problem.

2028411 Collaboration Data Objects (CDO) 1.2.1 is not supported with Outlook 2010

http://support.microsoft.com/kb/2028411 o Cannot add an additional mailbox to a MAPI profile

If your Outlook profile is missing the 101e6613 binary registry value (registry path

depends on your Outlook version), you will not be able to add an additional Exchange

mailbox to your profile. If detected, the Office Baseline diagnostic will alert you to this

problem and refer you to the following article in the Microsoft Knowledge Base:

833399 Cannot add an additional mailbox to a MAPI profile in Exchange 2000 Server

http://support.microsoft.com/kb/833399 o Less than 2 months Free/Busy being published

Publishing less than 2 months of free/busy information is not recommended as it is less

than the default publishing timeframe (2 months). If this situation is detected and you click

Apply this fix, the following data is written to your Windows registry.

Key: HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Preferences

DWORD: FBPublishRange

Value: 2

Note, x.0 in the above registry key path represents the version of Outlook installed. For

example, if you have Outlook 2010 installed, then x.0 would be 14.0 in the registry.

Also, if this registry value is detected under the \Policies hive in the registry, the diagnostic

will not be able to update the Windows registry. In this configuration, you will see a

warning similar to the following if you click Apply this fix.

This setting was originally configured via group policy and cannot be changed by this

diagnostic. The FBPublishRange value was found under the following key:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Preferences. Please

contact your system administrator for assistance in modifying the FBPublishRange value to 2

or higher. o Google Apps Sync for Microsoft Outlook disables Outlook search

The installation of the Google Apps Sync for Microsoft Outlook may disable the ability of

Outlook to search Outlook data using the Windows Desktop Search index.

If this situation is detected byt the diagnostic, and you click Apply this fix, the following

data is written to your Windows registry.

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows

Search

DWORD: PreventIndexingOutlook

Value: 0

Please see the following article in the Microsoft Knowledge Base for additional

information.





972814 Google Apps Sync for Microsoft Outlook disables Outlook to search the Outlook

data

http://support.microsoft.com/kb/972814 o Items may remain stuck in the Outbox when DelegateSentItemsStyle is set

When you are using Outlook with an Online mode profile for your Exchange account, you

may encounter issues sending email if the DelegateSentItemsStyle registry value exists

with a value of 1. If this situation is detected and you click Apply this fix, the following data

is written to your Windows registry.

Key: HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Preferences

DWORD: DelegateSentItemsStyle

Value: 2

Notex.0 in the above registry key path represents the version of Outlook installed. For

example, if you have Outlook 2010 installed, then x.0 would be 14.0 in the registry.


will not be able to update the Windows registry. In this configuration, you will see the

warning similar to the following if you click Apply this fix.

This setting was originally configured via group policy and cannot be changed by this

diagnostic. The DelegateSentItemsStyle value was found under the following key:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Preferences.

Please contact your system administrator for assistance in modifying the

DelegateSentItemsStyle value to 0.

For additional information on the DelegateSentItems registry value, please see the

following article in the Microsoft Knowledge Base.

972148 When you send an e-mail message from a shared mailbox in Outlook 2007, the

sent message is not saved in the Sent Items folder of the shared mailbox


The information after Important discusses the problem with using this registry value with

an Online mode profile. The article is written for Outlook 2007, but it also applies to

Outlook 2003 and 2010. o Check for Exchange 2003 Components

Having Microsoft Exchange 2003 components on the same computer as Microsoft

Outlook is not a supported configuration. Please see the following article in the Microsoft

Knowledge Base for details on this issue.

266418 Microsoft does not support installing Exchange Server components and Outlook

on the same computer

http://support.microsoft.com/kb/266418 o Outlook may not shut down properly due to third-party add-in

When you try to exit or close Microsoft Office Outlook 2010 or Microsoft Office Outlook






2007, the process does not end as expected or it seems to take a long time to complete. If

the Outlook process is forced to end, you may receive one of the following errors message

the next time that you start Outlook:

A data file did not close properly the last time it was used and is being checked for problems.

Performance might be affected while the check is in progress.The data file <data file name>

was not closed properly. This file is being checked for problems.

If you click OK in the message window, the following notification may be displayed in the

notification area:

Data file check in progress

This problem may occur if both of the following conditions are true: You have installed the Apple iTunes or other add-in that logs on to a MAPI shared

session and passes the MAPI_LOGOFF_SHARED parameter to IMAPISession::Logoff

when Outlook attemps to close You have another MAPI application running. For example, you have Microsoft Office

Communicator running.

For additional information on this problem, please see the following article in the

Microsoft Knowledge Base:

2449281 Outlook does not close after you install iTunes or another add-in

http://support.microsoft.com/kb/2449281 o Outlook may not be up to date

If you do not have all of the most recently availble updates for Outlook and Office, you will

see a message that resembles the following in the Outlook Baseline diagnostic.

Update Outlook binaries to the latest build.

How to install the latest applicable updates for Microsoft Outlook.

If you click How to install the latest applicable updates for Microsoft Outlook, the

following Microsoft Knowledge Base article is displayed in your browser:

2625547

How to install the latest applicable updates for Microsoft Outlook (US English only )

Use the links in this article to update your Outlook installation with the most recent

updates for Outlook and related Office components. o Some settings for the Visual Basic Editor are disabled in Office 2010

After you upgradae to Office 2010, you notice that some settings for the Microsoft Visual

Basic Editor are disabled in the application. This includes settings such as the Require

Variable Declaration option and the Compile on Demand option.

For more information about this problem, click the following article number to view the

article in the Microsoft Knowledge Base:

978753

Some settings for the Visual Basic Editor that you enabled in an earlier version of an Office

application are disabled in Office 2010






o The ExtractOrganizedMeetings registry value is set to 1

When you are processing meetings in Outlook, you may encounter unexpected results if

the ExtractOrganizedMeetings registry value exists and has a value of 1. If this situation is

detected and you click Apply this fix, the following data is written to your Windows

registry:

Key:

HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Options\Calendar

DWORD: ExtractOrganizedMeetings

Value: 0

Note The placeholder x.0 in the this registry key path represents the version of Outlook

that you have installed. For example, if you have Outlook 2010 installed, the value of x.0 in

the registry is 14.0.


will not be able to update the Windows registry. In this configuration, you will see a

warning if you click Apply this fix. This warning advises you that you will have to speak to

your administrator to make a change to the registry.

For more information about the ExtractOrganizedMeetings registry value, click the

following article number to view the article in the Microsoft Knowledge Base:

2646698

Outlook Issues that occur when you use the ExtractOrganizedMeetings registry value o You may be running an out-of-date version of Office

If you are running Office 2003 and it is detected by the Outlook Baseline diagnostic, you

will be advised to check the Microsoft Lifecycle page

for more information. o Items that are deleted from a shared mailbox go to the wrong folder in Outlook

When you use Microsoft Outlook, you delete items from a mailbox folder of another user

for which you have deletion privileges, and you see an error message. This occurs when

the DelegateWasteBasketStyle registry value is set to 4 and you do not have author

permissions to the Deleted Items folder in the mailbox in which you are deleting items.

For more information, click the following article number to view the article in the Microsoft

Knowledge Base:

202517

Items that are deleted from a shared mailbox go to the wrong folder in Outlook o Office 2010 prerequisites validation

If you are using Outlook 2010 on Windows XP, a check is made to determine the service

pack level for Windows. Office 2010 requires Windows XP to be at the Service Pack 3 level.

For more information, go to the following Microsoft TechNet website:

System requirements for Office 2010 o Outlook Configuration Analyzer Tool (OCAT) scan


http://support.microsoft.com/lifecycle


http://technet.microsoft.com/en-us/library/ee624351.aspx



OCAT contains numerous rules that detect known Outlook issues on a computer. The

results of this scan are saved locally to your computer. To view the scan results, double-

click the shortcut to Outlook Configuration Analysis Report that is created on your

desktop. The scan report opens in your default browser.

For more information about the Outlook Configuration Analyzer Tool, click the following

article number to view the article in the Microsoft Knowledge Base:

2659007

Outlook Configuration Analyzer Tool information Collé à partir de <http://support.microsoft.com/kb/2680810/EN-US>

Run Office diagnostics lundi 22 octobre 2012 11:45

To make it easier to run Office diagnostics, we have added a link to the Fix it Center Pro (FICP) portal

on the Events tab of the Telemetry Log tool. The link in the Telemetry Log tool is a customized link that

exposes only Office diagnostic packages in the FICP portal.

Note: You need to be a member of the local administrators group to run a diagnostic package.

1. Open the Office 2013 Telemetry Log tool via Start - All Programs - Microsoft Office 2013 -

Office 2013 Tools.

2. On the Events tab, click Diagnose Office Programs.

3. When prompted, sign in with your Windows Live ID account.

4. On the Analysis packages page, click the link for the Baseline Diagnostic package you want to

run.

5. Enter any name for the analysis session. This is just a friendly name so you can keep things

organized in the portal.

6. After you have downloaded and run the diagnostic package, click Upload the data now to have

your configuration analyzed.

7. Wait approximately 15 min for the Progress column to change to Completed (you might have

refresh the page)

The analysis results will be displayed in the bottom half of the page on the Details tab. If any problems

were found, you should be provided a link to documentation about the issue so you can take any

necessary action to fix the problem.

If you have any questions about this process, please post them in this discussions group.

Collé à partir de <http://innovation.connect.microsoft.com/Office15Diagnostics/Thread/View.aspx?ThreadId=8010>

Discussions under Diagnostics lundi 22 octobre 2012 11:52

Latest post:

Aug 6

4:48 PM

1 post



http://innovation.connect.microsoft.com/Office15Diagnostics/Thread/View.aspx?ThreadId=8010



Launching Office Diagnostics from the Telemetry Log tool

First post: gregm [MSFT] wrote: Hi,To make it easier to run Office diagnostics, we have added a link to

the Fix it Center Pro (FICP) portal on the Events tab o...

Jump to: First Post Topics: Diagnostics , Fix it Center Pro , Telemetric Log

Latest post:

Aug 1

5:31 PM

2 posts

Office diagnostics published

First post: gregm [MSFT] wrote: Hi,As promised, here is an update on the publishing of the Office

diagnostic packages.Office client diagnostic packages (except...

Latest post: Wendy [MSFT] wrote: Here are the details for tomorrow’s event:Title:Diagnosing Problems

in Office 2013Level (100-400):200Primary Target Audience:IT...

Jump to: First Post · Latest Post Topics: Diagnostics , Fix it Center Pro

Latest post:

Jul 24

7:30 PM

3 posts

A first discussion about Office Diagnostics

First post: gregm [MSFT] wrote: Hi,The support team has developed some very cool diagnostic

packages to help collect data and analyze it for known issues. We w...

Latest post: ArunGG_MVP wrote: That's good to hear

Jump to: First Post · Latest Post Topics: Diagnostics

Collé à partir de <http://innovation.connect.microsoft.com/Office15Diagnostics/discussions/topics/408/diagnostics>

lundi 22 octobre 2012 11:53

Office diagnostics published

Topics: Diagnostics, Fix it Center Pro

gregm

[MSFT]

Aug 1

at 5:27

PM

Hi,

As promised, here is an update on the publishing of the Office diagnostic

packages.

Office client diagnostic packages (except for Outlook) have been published. (The

Outlook diagnostic is published, but it will not work on Windows 8) You can run these diagnostic packages from the Fix it Center Pro portal. Just

sign in with a Windows Live ID account. https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase

You can run these diagnostics against Office 2013 (Click-to-run or msi), and

Office 2010, Office 2007, or Office 2003. They support all versions of Windows, including Windows 8, but the links to the

diagnostics in the Fix it Center Pro portal currently do not work on Windows 8. You need to be a local administrator to run them.

Please give them a spin and let us know if you have any problems or questions.

Reply Reply

with

quote


http://innovation.connect.microsoft.com/site/users/view/gregm%20%5bMSFT%5d

http://innovation.connect.microsoft.com/Office15Diagnostics/Thread/View.aspx?ThreadId=8010&ANCHOR#Post50513

http://innovation.connect.microsoft.com/Office15Diagnostics/discussions/topics/408/diagnostics

http://innovation.connect.microsoft.com/Office15Diagnostics/discussions/topics/410/fix-it-center-pro

http://innovation.connect.microsoft.com/Office15Diagnostics/discussions/topics/409/telemetric-log



http://innovation.connect.microsoft.com/site/users/view/Wendy%20%5bMSFT%5d




http://innovation.connect.microsoft.com/Office15Diagnostics/discussions/topics/410/fix-it-center-pro



http://innovation.connect.microsoft.com/site/users/view/ArunGG_MVP







https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase



We are also giving a presentation tomorrow (Thursday, August 2) on the

integration of diagnostics in Office 2013. Please check the event schedule for

details on the time and place.

Thanks

greg

Wendy

[MSFT]

Aug 1

at 5:31

PM

Here are the details for tomorrow’s event:

Title: Diagnosing Problems in Office 2013

Level (100-400): 200

Primary Target Audience: IT Pro

Secondary Target Audience: IW

Abstract: Professional-level SKUs of Office 2013 include a new data collection

tool called Office 2013 Telemetric Log. When you open this tool (using Excel

2013) the main worksheet includes a “Diagnose Office Problems” link that, when

clicked, takes you to the Fix it Center Pro (FICP) portal with a customized link just

for Office customers. In this portal, you can select from nine (9) different Support

Diagnostic Platform (SDP) packages that collect and analyze data from the client

on which the package is run. For example, if you run the Outlook Baseline

diagnostic, the data discussed in http://support.microsoft.com/kb/2680810/EN-

US is collected and analyzed, and a report of the analysis is provided to you in

the FICP portal shortly after the diagnostic has uploaded your data to Microsoft.

This presentation primarily discusses the use of SDP packages that you can

utilize to help you quickly identify known issues in Office 2013 (and 2010, 2007,

2003) and possible solutions to problems identified on computers where the

packages are run.

Homework (any advance activity that you can do, read, explore, or think about

that will enhance your participation):

In advance of this presentation, please familiarize yourself with the FICP portal

and the available Office diagnostic packages using the following articles in the

Microsoft Knowledge Base.

2711676 Troubleshooting Office application issues with automated diagnostics

http://support.microsoft.com/kb/2711676/EN-US 2672837 Microsoft Fix it Center Pro automated diagnostic portal

http://support.microsoft.com/kb/2672837/EN-US Resources:

All available resources and transcripts for this event are located here.

A summary page containing a description of all recorded events and links is

located here.

-Wendy

From: gregm [MSFT] [email removed]

Sent: Wednesday, August 01, 2012 8:27 AM

To: Wendy Stidmon (Xtreme Consulting Group Inc)

Subject: Office diagnostics published [Office15Diagnostics:7972]

From: gregm [MSFT]

Hi,

As promised, here is an update on the publishing of the Office diagnostic

packages.

Office client diagnostic packages (except for Outlook) have been published. (The

Outlook diagnostic is published, but it will not work on Windows 8)







http://connect.microsoft.com/office/Downloads/DownloadDetails.aspx?DownloadID=45206

http://connect.microsoft.com/office/content/content.aspx?ContentID=27663



You can run these diagnostic packages from the Fix it Center Pro portal. Just

sign in with a Windows Live ID account. https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase

You can run these diagnostics against Office 2013 (Click-to-run or msi), and

Office 2010, Office 2007, or Office 2003. They support all versions of Windows, including Windows 8, but the links to the

diagnostics in the Fix it Center Pro portal currently do not work on Windows 8. You need to be a local administrator to run them.

Please give them a spin and let us know if you have any problems or questions.

We are also giving a presentation tomorrow (Thursday, August 2) on the

integration of diagnostics in Office 2013. Please check the event schedule for

details on the time and place.

Thanks

greg

Collé à partir de <http://innovation.connect.microsoft.com/Office15Diagnostics/Thread/View.aspx?ThreadId=7972>

Quest mardi 30 octobre 2012 15:31

SharePoint 2013 Migration and Pre-Migration Readiness http://www.quest.com/sharepoint/sharepoint-2013.aspx#

https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase


http://www.quest.com/sharepoint/sharepoint-2013.aspx




Quest Migration Suite for SharePoint 2013 Preview mardi 30 octobre 2012 15:51

Quest Migration Suite for SharePoint 2013 Preview Thank you for downloading the SharePoint 2013 Preview Edition of Quest Migration Suite for SharePoint. You should have already received an email including your license number and activation code. This license will enable you to migrate unlimited files and up to five gigabytes (GB) of content to SharePoint 2013 and Office 365, and it will be valid for as long as the SharePoint 2013 Preview is available. By default, the license will be limited to one installation. If you would like to request more gigabytes or installations, please contact product manager [email protected]. This license cannot be used for migrations to SharePoint 2010 or SharePoint 2007. To get started moving content from SharePoint 2007/2010, Exchange public folders and Windows file shares, use these resources to help: Product Quick-Start Videos– Watch short videos to learn how to install and use Migration Suite for SharePoint. SharePoint for All Community Discussion Forums– Get all your questions answered by your SharePoint peers and Quest experts. SharePoint 2013 Readiness Webcast Series – Learn five specific actions you should take to ensure you are prepared for SharePoint 2013. Note: This download will be supported by the SharePoint for All community only. Also, certain items and customizations in your SharePoint environment (e.g. third-party web parts, custom workflows, branding, etc.) might not be compatible with or transfer properly to the SharePoint 2013 Preview. These may need to be recreated manually after content migration is complete. Collé à partir de <https://www.quest.com/common/registration.aspx?requestdefid=45052>

Licensing Quest mardi 30 octobre 2012 16:38

français Traduire le message Désactiver pour : anglais


http://communities.quest.com/community/sharepointforall/migration?view=overview#/?tagSet=undefined

http://communities.quest.com/community/sharepointforall/migration?view=discussions

https://www.quest.com/landing/?ID=5413


https://www.quest.com/common/registration.aspx?requestdefid=45052



Thank you for evaluating Migration Suite for SharePoint during your SharePoint 2013 Preview project.

Join the Community! The SharePoint for All community is your single destination for Quest SharePoint product updates, how-to videos,

quick-start guides and engaging discussion forums. Best of all, it’s easy to join! Click here to get started.

LICENSING INSTRUCTIONS: You have been assigned the following license number. Please keep a record of this number for future

correspondence.

License Number: xxxxxxxxxxx

Activation Code: xxxxxxxxxxxxxx

This license will enable you to migrate unlimited files and up to five gigabytes (GB) of content to SharePoint 2013, and it will be valid for as long as the SharePoint 2013 Preview is available. Note: certain items and

customizations in your SharePoint environment (e.g. third-party web parts, custom workflows, branding, etc.) might not be compatible with or transfer properly to the SharePoint 2013 Preview. These may need to be

recreated manually after content migration is complete.

This license cannot be used for migrations to SharePoint 2010 or SharePoint 2007. By default, the license will

be limited to one installation. If you would like to request more gigabytes or installations, please contact product manager [email protected].

This download will be supported by the SharePoint for All community only. For issues or questions

regarding license keys, please contact your sales representative or [email protected]. To get started moving content from SharePoint 2007/2010, Exchange public folders and Windows file shares,

use these resources to help:

Product Quick-Start Videos– Watch short videos to learn how to install and use Migration Suite for

SharePoint. SharePoint for All Community Discussion Forums– Get all your questions answered by your

SharePoint peers and Quest experts. SharePoint 2013 Readiness Webcast Series – Learn five specific actions you should take to ensure

you are prepared for SharePoint 2013. For questions or problems, call: (800) 306-9329

Thank you, Quest Software

For Questions or Problems Call: (800) 306-9329

Quest Software is now part of Dell Worldwide Headquarters 5 Polaris Way | Aliso Viejo, CA 92656 | U.S.A

Quest Software has offices in over 27 countries. Find your local sales representative at www.quest.com

This email message contains confidential and privileged information and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and

destroy all copies of the original message.

© Quest Software Incorporated. ALL RIGHTS RESERVED.

Quest, Quest Software, and the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc. in the U.S.A. and/or other countries. For a complete list of Quest’s trademarks, please visit http://www.quest.com/legal/trademarks.aspx. All other

trademarks and registered trademarks are property of their respective owners. View Quest Software's Privacy Policy

http://communities.quest.com/community/sharepointforall/

http://communities.quest.com/community/sharepointforall/




http://communities.quest.com/community/sharepointforall/migration?view=overview#/?tagSet=undefined


http://www.quest.com/landing/?ID=5413

http://www.quest.com/

http://www.quest.com/company/contact-us.aspx

http://www.quest.com/legal/trademarks.aspx

http://www.quest.com/legal/privacy.aspx



Collé à partir de <https://mail.google.com/mail/?shva=1>

Capacity Planning Guide spreadsheet for Windows Azure Caching mercredi 31 octobre 2012 07:08

Download Capacity Planning Guide spreadsheet for Caching from Official Microsoft Download Center http://www.microsoft.com/en-us/download/details.aspx?id=30000 Capture d'écran effectuée : 31/10/2012 07:08

https://mail.google.com/mail/?shva=1

http://www.microsoft.com/en-us/download/details.aspx?id=30000

Outils sp2013

Technology

Transcript of Outils sp2013