- Message Boards
- Package KB
- Software KB
- Free Videos
- MSI Errors
- Tools
- Tech Home Pages
- Reviews
- Downloads
- Articles
- FAQs
- Tips & Tricks
- Services
- News
- Newsletter
Search AppDeploy
Sharepoint Designer 2010 14.x
| Company: | Microsoft |
| Setup Type: | Legacy setup with switch support |
| Package Difficulty Rating: | TBD [ Rate It or View Ratings ] |
| Most Commonly Reported Method: | not yet established |
| Record Created On: | 7/28/2010 |
| Number of Views: | 519 |
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.
Software Knowledge Base
Software Knowledge BaseFull Name: Microsoft SharePoint Designer 2010
Version: 14.0.4763.1000
Publisher: Microsoft Corporation
Uninstall String: "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall SHAREPOINTDESIGNER /dll OSETUP.DLL
Categories: Unknown
Threat: Unknown
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.
| Utilise the XML / MSP type of deployment. 1: First, extract the SharePointDesigner.exe source. SharePointDesigner.exe /extract:c:\test c:\test as an example.. 2: The admin folder will need to be copied from an Office 2010 source to use the OCT tool for patch creation. 3: c:\test\setup.exe /admin 4: Create a patch msp within the admin tool that includes... Silent, license options and configurations. 5: Modify the config.xml file to include the silent, MAK license options...no need for KMS license, configurations of features and properties like: ROOTDRIVE=c:\ and REBOOT=Never Simple Example: <Configuration Product="SharePointDesigner"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <USERNAME Value="Authorised User" /> <COMPANYNAME Value="YourCompany" /> <OptionState Id="WAC_SPD" State="local" Children="force" /> //sharepoint designer <Setting Id="SETUP_REBOOT" Value="Never" /> </Configuration> 6: Create an uninstall xml file. An example: <Configuration Product="SharePointDesigner"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <COMPANYNAME Value="YourCompany" /> <OptionState Id="WAC_SPD" State="absent" Children="force" /> //sharepoint designer <Setting Id="SETUP_REBOOT" Value="Never" /> </Configuration> 7: Install Command Line = setup.exe /config .\sharepointdesigner.ww\config.xml /adminfile c:\test\patch_name_from_step_4.msp 8: UnInstall Command Line = setup.exe /uninstall sharepointdesigner /config .\sharepointdesigner.ww\uninstall.xml TIP: Office 2010 products like Access Runtime, Sharepoint Designer etc all have the same folder structure and if you have the Office 2010 Suite, you can copy the SharePointDesigner.en-us and SharepointDesigner.WW to root of the Office suite which saves duplication of folders such as: Office64.en-us, Office.en-us, Rosebud.en-us etc. You will need to create multiple patches/xml files for each install as above. | ||||
| Above Entry Provided on 7/30/2010 by tron2ole | Rate It | Rating 0 | ||
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.
| Recipe, http://www.viridisit.se/eng/blog/?p=661 | ||||
| Above Entry Provided on 7/30/2010 by nucko | Rate It | Rating 0 | ||
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
