Standalone Project/Visio 2013 package using Office Deployment Toolkit?

Hello all,
As per the title, is it possible to use ODT to produce standalone Project/Visio 2013 packages without Office in there? I've tried it couple of times now but it will always ended up having the rest of the office suite in there.
Here's an example of the configuration.xml used:
<Configuration>
<Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
    <Product ID="ProjectProVolume">
      <Language ID="en-us" />
    </Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Any ideas? I've tried using the Sequencer to sequence Visio by itself but everytime it launches, the wizards will run on every launch even though I've already ran them once.
Thanks in advance!

No. You can restrict the application using the XML configuration.
Steve Thomas, Senior Consultant, Microsoft
App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat
http://blogs.technet.com/gladiatormsft/
The App-V Team blog: http://blogs.technet.com/appv/
The MED-V Team Blog: http://blogs.technet.com/medv
The SCVMM Team blog: http://blogs.technet.com/scvmm/
“This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

Similar Messages

App-V 5.0 SP2 (Office Deployment Toolkit) - Unable to create Project and Visio with different package ID

We would like to create 2 App-V packages with the
Office Deployment Tool
- Visio Std 2013
- Project Std 2013.
The App-V packages are created successfully, the problem is that the package-id of both packages is the same.
When we deploy for example, Visio to a client and afterwards Project, Visio gets replaced in App-V by Project.
Is anyone else facing this issue ?

So I wanted to bring everybody up to speed on some changes. You can manage multiple Office packages by generating different PACKAGEGUID attributes (https://technet.microsoft.com/en-us/library/jj219426.aspx?f=255&MSPPError=-2147217396)
using the Office Deployment Toolkit BUT - the following still applies:
Only one Office package can be deployed to a machine at a time.
Only VL and Subscription Pro options are available for packaging via App-V.
Steve Thomas, Senior Consultant, Microsoft
App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat
http://blogs.technet.com/gladiatormsft/
The App-V Team blog: http://blogs.technet.com/appv/
The MED-V Team Blog: http://blogs.technet.com/medv
The SCVMM Team blog: http://blogs.technet.com/scvmm/
“This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
Steve is there any chance this stance may change, or is there any feedback we can give (we have already followed up with our TAM and have also put in tickets but effectively have not gone anywhere other then to explain what the model of support is)?
To be perfectly honest its a very hard model to support since users are licenses for Visio and Project separately, not to mention the lack of user publishing (targeting) and Office Standard support.
We have put in advisory and problem tickets with MS for months in hopes of using the ODT packages in our non persistent VDI environment but I don't believe it will possible.
In short if we have to separate our images or pools to support the various possibilities we are losing what App-V gains us: on demand (per user) publishing to limit the number of gold images we need.
The loss of Office Standard support also leaves us in a tricky spot, because at the end of the day we have to find a way to support those users.
Not looking to put you on the spot, just hoping there is a way to give effective feedback or discuss how to use the ODT packages in a way that makes life easier, not more restrictive.

Steps to deploy Lync for users who own Office 365 E1/E2 licenses, but don't have Office 365 E3, using Office Deployment tool.

After many hours of debugging with Microsoft support the system to install the Lync Client silently can be done with a SINGLE LINE command. The steps to take are below. It should be an easy next step to put this as GPO installation since
it is a simple command.
Comments appreciated.
side question: Why is there no Lync 2013 or Lync Office 365 forum?
Basic steps to deploy Lync for users who own Office 365 E2 licenses, but don’t have Office 365 E3, using Office Deployment tool.
This also applies for other Office 365 service types where the full office suite download is not included. In April 2015 This was impossible to find online and not know by the Lync support team.
Steps are:
Download the Office deployment tool from
http://www.microsoft.com/en-in/download/details.aspx?id=36778 and extract it to a folder. For this
example we will use the \\server\sharename
location.
Extracting it creates a setup.exe file and it show a sample XML file.
2. Create XML file and give it a name such as LyncEntryRetail.xml
Note: The key is the productID that has to be the “LyncEntryRetail”. Other product IDs will download a version that needs another office 365 license. The productID “LyncRetail” needs an E3 license of Office 365.
<Configuration>
<Add SourcePath="\\server\sharename" OfficeClientEdition="32" >
    <Product ID="LyncEntryRetail">
      <Language ID="en-us" />
    </Product>
</Add>
</Configuration>
3. From the folder where you extracted the Office deployment tool, run the following command on the command prompt to download the source files and store them on the shared drive:
(on single line)
Setup.exe /download LyncEntryRetail.xml
(This is the name of the XML file created above)
One can also run the same on a server share by using UNC path names such as (on single line)
\\servername\sharename\Setup.exe /download
\\servername\sharename\LyncEntryRetail.xml
(This is the name of the XML file created above)
4. Run the following command on the command prompt on a machine where you want to install the software: (on single line)
\\servername\sharename\Setup.exe /configure
\\servername\sharename\LyncEntryRetail.xml
(This is the name of the XML file created above)
Once you are comfortable that it all works, you may want to edit the XML file if you want to have silent installation and add the following lines.
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
Regards
Bart
Bart Louwagie

Hi Chudly，
For the office365 issue, I also recommend you can post in dedicated forum for more efficient support:
http://community.office365.com/en-us/f/166.aspx
If you want to modify the powershell script, please post the current script and the issue, we will notice and continue to follow up.
If there is anything else regarding this issue, please feel free to post back.
If you have any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Does Visio 2013 work with Office 2010?

Does Visio 2013 work with Office 2010?

Tuesday 01/06/2015
Take a look at this Microsoft KB
KB2784668
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version
KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
Forum 1
Forum 2
(How to determine which version 32-bit or 64-bit version of Office is installed
Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the
server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio,
when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant.
Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dll’s from the application were not registered. If that didn’t
fix it they suggested a reimage. After registering the dll’s, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it
to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops.
I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didn’t see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office
2010 SP2
I’m not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KB’s and support forums, different version interops
do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users
who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems.
Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the “ghost” issues where Visio 2013 is the root cause, but nothing is really going to scream it.

Update win of windows 7 use Microsoft Deployment Toolkit.

Hi all !
I have computers run winodows 7 join domain. Because security, I have disconnected internet of computer run windows 7 , never.
But, I want to automatic update win for windows 7. Can i use Microsoft Deployment Toolkit to do it ?
So, Can you help me ?
Thanks and best regards .

The MDT ZTIWindowsUpdate.wsf script can automatically update your client machine. However it will require network access to update. BY default it will connect to the MIcrosoft Windows UPdate servers, or you can redirect the client machine to go to a local
WSUS (WIndows Server Update Services) Machine.
If you do not want to support any network access, you can manually add all updates as applications and install them manually via ZTIApplications.wsf
Keith Garner - keithga.wordpress.com

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Project Server 2013 - Out of Office Sync - Only two months in future?!?

Hello there guys,
after Long Long search for the problem, I've found out that our Project Server 2013 only syncs the out of Office time from our Exchange Calendar for the next two months.
But for our Project planning we Need of course a more longtime synchronization, at least 6 or better 12 months.
I didnt find any Option where I could set it to sync more then 2 months of the out of Office times in the calendars.
I've spent already so much time on this Problem... When I set the Project Server time 2 weeks(!) in the future, then the sync will also sync two more weeks in the future, but not more.
The timesheet periods are also set for the next 12 month.
Does anybody have an Information/help regarding this Problem for me?
How can I set the Out of Office sync to synchronize more then just 2 months?
THANK YOU VERY MUCh!!
Regards
Lukas Meyer
PS: Using the current October 2013 CU.

I've searched the Verbose Log and found the following:
12/17/2013 14:38:16.32 Microsoft.Office.Project.Server (0x0928) 0x1A6C Project Server Exchange Sync aaubf Verbose PWA:https://servername/PWA, ServiceApp:Project Server-Dienstanwendung, User:PROJECTSERVER\system,
PSI: Calling service.GetUserAvailability() for user:2c3909bc-d6fb-e211-b239-000c296be823 for period:12/17/2013 00:00:00-02/17/2014 00:00:00, LogLevelManager Warning-ulsID:0x00014045 has no entities explicitly specified. 3a2f619c-f4a0-f018-b62b-b2d1299a489f
So the Project Server is only asking for two months of User Availability on the Exchange. Where can I Change this Setting so that the Project Server syncs more then 2 months?
Otherwise this functionality is quite useless in my view as we are planning our Projects longer then only 2 months...
Thank you!

Ref: Having trouble to install visio 2013 alongside with office 2007

Hi,
I am trying to install Visio standard 2013 on a desktop computer which has already MS Office Suite Pro 2007 installed. Every time i try to install it, it keeps pop up the window saying that i need to uninstall per-release or beta version in order
to install Visio 2013. I have checked my computer all the way and even i have run fix it from Microsoft.Still popping up the same window...Any suggestion..Please

Did you install the Visio Professional 2010/2013 trial version before even you have removed it? Office trial version cannot coexistent with Office production final release.
I notice that you have run fix, could you tell me the hotfix package you've tried?
At this point, please try to remove Office 2007 totally by the
http://support.microsoft.com/kb/928218/en-us and then install Visio Stardard 2013 first.
Tony Chen
TechNet Community Support

"dtutil", how to tell which configuration file for packages using after deployment?

Hello All,
Trying to achieve this feature,
Using DOS command to automatic my deployment process--glad I found dtutil. However, it doesnt give you any chance to identify which configuration file to be used by SSIS packages after deployment.
Deployment Method: file deployment
Configuration sued: XML file and SQL Table. IN XML file, it tells which DB connection for packages to look up the configuration table.
Who can share some thoughts on this?
Derek

It is NOT about sequence.
It is about how to point which configuration file to be used by deployed packages as during the "dtutil.exe"
deployment, you dont have chance to identify which physical location confg files to be used.
Derek
That you do only at the time of execution of packages. By default it uses configuration settings created at design time within the package. If you want to override it, you can use \Configfile switch of dtexec for that. You can also set explicit values for
properties using /SET switch
http://technet.microsoft.com/en-us/library/ms162810(v=sql.105).aspx
See this to understand how configs are applied in runtime
http://technet.microsoft.com/en-us/library/ms141682(v=sql.105).aspx
and this to understand behaviour difference in ssis 2008
http://technet.microsoft.com/en-us/library/bb500430(v=sql.105).aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Download O365 installer files using Office Deployment Tool times out...

Hi,
We need to deploy O365ProPlus as part of an operating system image using MDT. I was pointed to this page for instructions:
https://technet.microsoft.com/en-us/library/dn314789.aspx
We first needed to download the source files, so I first downloaded the Office Deployment Tool and used this to download the O365ProPlus image to my MDT server.
I created the following config file (O365x64.xml):
<Configuration>
<Add SourcePath="X:\O365\" OfficeClientEdition="64">
   <Product ID="O365ProPlusRetail" >
     <Language ID="nb-no" />
   </Product>
</Add>
</Configuration>
And I invoke the command to run the Office Deployment Tool:
.\setup.exe /download X:\O365.x64.xml
Then the process creates a folder X:\O365\Office\Data with a couple of 16kb CAB files, but nothing happens apart from this.
What am I doing wrong...? I expect the Office folder to be alteast a gigabyte...
Thanks for comments
Tor

Please first check your network or switch to a different network, then try again.
Additionally, you might want to check if your network setting/firewall setting is blocking any Office 365 IP address/URL:
https://technet.microsoft.com/en-us/library/hh373144.aspx
Regards,
Kapaal

Installing Onenote 2013 while using Office 2010 Pro.

Is it possible to install Onenote2013 while using Microsoft Office 2010?

It probably is generally not recommended to mix application versions but this thread indicates it does work with Office 2010 and OneNote 2013.
http://social.technet.microsoft.com/Forums/office/en-US/7f79f7e2-f9b8-4f3d-b41f-acedb5c65749/exchange-2003-with-office-2010-and-onenote-2013?forum=exchangesvrgenerallegacy
Kind Regards, Rich ... http://greatcirclelearning.com

How do I activate Office 2013 that I have deployed using ODT and App-V onto a Remote Desktop Server?

I am setting up a demo Server 2012 R2 environment (1 DC server, 2 RDSH servers, 1 App-V server).
I have created an Office 2013 volume license App-V package using the latest Office Deployment Toolkit. I have deployed the App-V package to an RDS server and it all works fine. However, I am unable to activate Office 2013 using the MSDN Office 2013 retail
key because it tells me the product key is invalid for this version of Office. I've looked at the alternative of using the App-V Sequencer to create the Office 2013 package, but from what I've read this is not a Microsoft supported method.
Is there any way that I can activate Office 2013 (volume license on RDS) using the method I've outlined above, or is there any way of using the Office2013 download from MSDN such that it can be packaged by the ODT (or App-V Sequencer) for successful deployment
using App-V and activation using the retail Office 2013 product key on MSDN?

True, VL channel media can't be activated with MSDN Retail pkeys (that's what I was trying to get you to understand, I figured you would be attempting that, as so many people do :(
I've not attempted your scenario myself.
It sounds like you aren't following the supported scenarios as (poorly) described by MS;
The way I read their guide, for an RDS scenario, you must use a VL key [either MAK or KMS] (since a subscription product+key can't be used on RDS):
i.e.: <Product ID="ProPlusVolume">
http://support.microsoft.com/kb/2772509
http://support.microsoft.com/kb/2915745
http://technet.microsoft.com/library/dn481351.aspxhttp://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
So, that all means that for RDS, you can't use anything other than VL "product" (in
the form of an ODT-generated output) with a VL pkey. So, for your RDS demo setup, you need to use real product and real pkeys.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Can't open Project Server 2013 word documents with office 2010 installed

hello forum members,
we having issues opening a word document in a Project Server 2013 . we have Office 2010 on our computers installed.
when I click on a document link, i get a message "The webpage cannot be displayed". the only way to open a document is to right click on link and select "Open".
Does Project Server 2013 require Office 2013 installed? If not, is there a way to open documents in Project Server 2013 without right clicking on links?
tatiana
tatiana

Hi Tatiana,
This is the know issue. I have experienced this issue with one of our client. The cause of issue as below -
Scenario
You have 2007 Microsoft Office installed on a computer.
On the same computer, you also have a Microsoft Office 2013 application installed, such as Microsoft Lync 2013 or Microsoft Word 2013.
SOLUTION
To work around this issue, remove the Microsoft SharePoint Foundation Support program component from the Office 2013
installation on the affected computer or computers. To do this, follow the “Install or remove individual Office program components” section of the following Microsoft Office website:
Install or remove individual Office
programs and components
(http://office.microsoft.com/redir/HA010354261.aspx)
After you complete these steps, repair 2007 Office. For more information about how to repair the installation, click
the following article number to go to the article in the Microsoft Knowledge Base:
924611
(http://support.microsoft.com/kb/924611/ )
How to install the individual 2007 Office features or to repair the installed 2007 Office programs
Note When
you follow these steps, set the Microsoft SharePoint Foundation Support
component within Office Tools to Not Available.
This solution doesn't apply to scenarios in which SharePoint Designer 2013 is installed on the affected computer.
You can find further details here at Microsoft support site -
http://support.microsoft.com/kb/2888015
Hope this helps you.
Cheers, Badal

Using multiple resource cost rates in Project Server 2013

Greetings,
We use Project Server 2013 to manage resources that often perform multiple roles within projects and also have different rates between projects. The Standard Rate from the user's profile is somewhat helpful but, as we all know, it carries over to every
project that the resource is part of.
I have tried opening Project Professional 2013 and using the additional Cost tabs in the user's information to enter different rates in tabs, B, C, D and E (tab A is the default Standard Rate from Project Server).
My experience has been that as soon as I close and check in the project file, this data disappears. Next time I open the file the default rate is available but tabs B-E are blank. This behavior does not occur if I open a stand-alone project
file not connected to Project Server.
I realize that Project is not meant to be a financial management tool and has its limitations but I'm looking for suggestions and would appreciate any feedback.
Thanks
Ray

Dale is right in that an Enterprise Resource can only have its rates (or any details) set by the administrator. Unfortunately you are limited to 5 rates (A-E).
I have done a macro for a client that reads rates for a resource for a project from a database (or Excel) every time the project is opened. So you see the correct rates and calculated costs.
These rates get over-written next time you open the project, hence the need for the macro to update rates every time the project is opened.
Another option in the macro is to zero the rates so a copy can be emailed to clients etc without sensitive rates data.
Rod Gill
Author of the one and only Project VBA Book
www.project-systems.co.nz

Can't open Project Professional 2013 projects in SharePoint 2013

I can't open Project 2013 documents from SharePoint2013.
My environment is:
Project Professional 2013 32 bit
Office Professional 2013 32 bit
IE 9 32 bit
Windows 7 Enterprise 64 bit
All other documents (Word, Excel) can be checked out and edited from SharePoint.
When I check out and edit a Project document I get the following error:
Project cannot open the file.
check that the file name a path are correct.
check that the file format is recognized by Project.
Also, I get the same error when trying to open a project document from a mapped SharePoint drive.
Note: This was working on a fresh install of Office 2013 and Project Professional 2013 UNTIL a windows update (Office 2013 SP 1 and other updates)
Am I missing an update?
Thanks!
Ken

Hi Ken,
I would try first to repair MS Project from the control panel to see if it fixes your issue.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Standalone Project/Visio 2013 package using Office Deployment Toolkit?

Similar Messages

Maybe you are looking for