Microsoft Office Recipe
105 replies, 21970 views
Posted on February 1, 2013
Edited by Unidesk employee Rob Zylowski on September 7, 2016
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

This Micorosft Office Recipe is intended to aid customers and partners to develop a strategy and then install Office in their Unidesk environments .  This recipe covers all versions of Microsoft Office. Installation, licensing, activation, updating and layering strategy are all discussed.

Remember that thorough testing in your environment with your configuration is critical to providing a stable computing environment.

Keywords: Office 2003 Office 2007 Office 2010 Office 2013 2016 VAMT ospp.vbs KMS

There is an issue with Office KMS Activation on Windows 8.1 and Windows 10 desktops when the VMware View Agent is installed.  For some reason with the View Agent installed Office will not activate on first run or via the ospp.vbs script.  The system thinks it has no product key installed for office.  To solve this problem we developed a script that can be run during build or boot of the desktop.  The script performs the following actions:

  1. Changes to c:\windowws\setup\scripts
  2. Stops the View Agent Service
  3. Runs MofComp.exe to Rebuild the Office WMI database if it exists (only in Office 2010)
  4. Runs Winword /r (This registers word but more importantly configures the office installation)
  5. Inputs the included office KMS keys using ospp.vbs /inpkey: based on the existence of flag files
  6. Activates Office (any of the apps with keys installed) using ospp.vbs /act against KMS
  7. Starts the View Agent Service
  8. Changes back to the kmsdir folder

You can deploy this fix as part of the OS layer and your Office layers or in a separate application layer. We would recommend adding the script to your OS layer, then adding the appropriate flag files (see below) to your Office layers.

The best way to deploy these scripst is using the new Gold Image Tools Version 5.x.  To download goto http://www.unidesk.com/forum/scripts-and-utilities/unidesk-gold-image-tools-v501-experimental .  Direction are included wiht the recipe. - Rob

 

1-26-2016 Updated to reflect using Gold Image Tools version 5.x for Office Activation.

Updated 2-18-2016 Fixed some confusing wording

Updtaed 9-7-2016 for elastic layering

 

 

Posted on February 8, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

Rob,

  Great recipe!  I found the disable hardware graphics acceleration very interesting.  We never really had any issues with leaving this enabled in Office 2010; however, Office 2013 was different story all together and I would highly recommend disabling it.

Posted on February 11, 2013
aromond
Registered user
Joined: October 15, 2012

These Recipe's are great. Any chance of having a single page for all of them?

Posted on February 11, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010
Posted on May 6, 2013
Strickland
Registered user
Joined: February 6, 2013

Do I apply the cscript KMS commands to the Office 2010 layer in the runato.cmd file or do I apply it to the Gold image?

Posted on May 15, 2013
rhosysadmin
Registered user
Joined: January 8, 2013

Having issue with "NoReReg" script in your recipe, although I could have sworn that it worked for me once.  The first line does not work.  I get an "ERROR: Access is denied" when the following line is run:

reg load "hku\temp" "%USERPROFILE%\..\Default User\NTUSER.DAT"

Then the remaining lines of the script fail of course.

I've tried running this as administrator and not, and opening a command prompt as administrator first (and not as admin) then running the script.  I get the same error every time.

Has anyone else seen this?

 

Posted on May 15, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi,

Where are you trying to run the script?  You would want to create the script and add it to the setupcomplete.cmd to run after the optimization script is run and you would want to include office when building a desktop.  It will then run with system permissions and should work.  Let me know if it does not and I will set up some tests.

 

Rob

Posted on May 15, 2013
rhosysadmin
Registered user
Joined: January 8, 2013

I'm running it on my install machine after installing Office in a new app layer.

 

Posted on May 6, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Jason are you doing persistent or non persistent desktops.  Normally for persistent desktops you dont have to do anything for KMS to work when the user first opens the app and it licenses on first use.  For non persistent desktops add this line to the c:\windows\setup\scripts\kmsdir\runato.cmd right after the windows activation.

cscript://h:cscript

call slmgr /ato 1>>runato.log 2>>runato.error

call "c:\program files\microsoft office\office14\ospp.vbs" /act

cscript://w:cscript

 

Rob

Posted on May 6, 2013
Strickland
Registered user
Joined: February 6, 2013

I will have both persistent & non persistent desktops. Since I have both, do I put it in the OS layer runato file or in the Office layer runato file.

Posted on May 6, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

I would always make changes to things under c:\windows\scripts in the OS layer.  It will help you keepo changes straight.

Posted on May 6, 2013
Strickland
Registered user
Joined: February 6, 2013

Thanks. Unidesk is all new to me. I do really really appreciate all the support ya'll provide on these forums.

Posted on May 6, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Your welcome Jason we want you to be successful and Happy :)

Posted on July 2, 2013
Edited by Steven Goodson on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  We have recently upgraded our MM's to Office 2013.  While it has worked perfectly with our persistent desktops, I have had a strange issue with deployment on nonpersistent desktops.  When a NP is created with the Office 2013 layer, it seems to work just fine; however, subsequent reboots are causing Office 2013 to execute the Configuration Process  Configuring Microsoft Office.  It then proceeds to chew up most of the disk space assigned to the personalization layer (2GB).  Once the configuration is completed, it then states that it is not licensed.  We are using KMS.  Any ideas?

Posted on July 2, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Steven you arent using Symantec AV are you?  Are there any errors in the event log?

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  No, there is actually no AV on the NP MM.  I looked at the runato error logs and nothing is there.  I'll check the windows logs and see what it may be barking about.  It seems strange that the first login after the NP is created, works like a charm, it is only after subsequent Rebics that the issue shows up.  I'll post back with any info that may be of use from the Windows logs.

Posted on July 2, 2013
Ron Oglesby
Unidesk employee
Joined: April 20, 2010

So is it a subsequent rebic or reboot? (wait what version are you using?) in 2.0 there is no rebic on non-pers after logout of the user, just a reboot.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

 We are using 2.1.1.  Sorry about the rebic comment, I'm still adjusting to the 2. environment.  The only thing I have seen in the log that may be an issue is event 1056  Security-SPP.  Two entries state  Some data has been reset.   and then a Event 1022 Security-SPP The system has been tampered.

Posted on July 2, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

The thing that seems starnge is that I would expect the changes to jsut be applied the same way with each logout/reboot as they should jsut be set back.  However I wonder is something is changed in KMS that it thinks it shoudl already be set on the client.  What happens if you deploy new NP desktops.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  When I creat a new NP and the creation process has been completed.  Office is working as expected, it is only after the 1st and subsequent reboots that the issue is happening. Per my previous post to Ron, if I manually run the ospp.vbs /act on the NP, problem fixed; however, I am in the process of confirming this for consistency.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  It appears that if I run the ospp.vbs /act directly from the NP, the problem does not occur.  I am rebooting again to confirm this.  Originally, I had placed this in the runato.cmd file on the OS layer, per the recipe.

Posted on July 2, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

I would think if that required you will have to run it with every boot on a NP desktop becasue it wont stick.  I will be interested to see what happens.

Posted on July 2, 2013
rhosysadmin
Registered user
Joined: January 8, 2013

Did you try adding the "NoReReg" registry options mentioned in the Office recipe?

 

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

No, I do not see that in the Office recipe.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

 This was my own idiocy, I failed to scroll down below the blank page to see the NoReReg portion.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

 Not consistent,  I rebooted the NP and ran the ospp.vbs /act right off the bat.  It was not happy, and stated it had been tampered with.  I went ahead an launched Word,  it did it's configuration as previously described.

Posted on July 2, 2013
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

When you did the update did you open any office Apps?  I wonder if it now has the CMID defined in the layer.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  No, I learned my lesson on that one when we first started our journey.  We do not even look sideways at an Office app, before we finalize it. I have the norereg document and will execute this configuration.  I will post back with the results and thanks for all the input from everyone.

Posted on July 2, 2013
Charlie Smith
Registered user
Joined: April 27, 2011

What is the recommended way to do multiple office layers? We are running into some issues. We have our base Office 2010 layer, and one off's like Visio, Sharepoint Designer, etc, etc. And also in the progress of migrating to Project 2013 and when you try to put these on a MM together it gets stuck in a configuring loop. Any recommended way of getting this accompished?

Posted on July 2, 2013
Ron Oglesby
Unidesk employee
Joined: April 20, 2010

Typically, you have a base office package. That is the base for all other office packages. Contrary to popular belief Project, visio, etc are ALL Office. they use an unerlying license system that all share.

Best bet is use that base office layer as the pre-requisite for all other office layers. This base layer should be one that everyone would get that would use any office product. That then contains the licensing and if Visio or Project copies that file into the next layer (to modify it) it is not as if office wasn't already there and installed.

Make sense? I'm pretty sure there was another discussion about this specific topic here on the forum somewhere also.

Posted on July 2, 2013
Charlie Smith
Registered user
Joined: April 27, 2011

Should all of the Office layers, and extra layers be pre-req's to each other, or just the office layer depenedant to the others.

Posted on July 2, 2013
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Think hard about what combinations you really need to offer.  As Ron said, they all share common DLLs and licensing files, and as you surmised, that could lead to some real prerequisite complexity.  Rather than trying to figure out how to provide every possible combination of Office components, think about what your users really need.  In a number of situations, we wound up recommending just having independent Office-plus layers.  It might be that everyone using Project would also be using Visio and Sharepoint, so rather than trying to keep them separate, they had Office+Project+Visio+Sharepoint as one layer, Office alone as one layer, Office+Access+Sharepoint as another.  As long as you don't realistically need to provide all the permutations, that list of Office-plus layers might be tractable. 

Or you might be fortunate enough that your list of dependencies is linear, so that you have a simple model for prerequisites.  Some A might require Office, and B would require Office and A, and in no case would you deploy B without A.

The basic rule of prerequisites is that if you build layer Y with X as a prerequisites, you should not deploy Y to a desktop without X.  You can see how trying to provide all the permutations would necessarily leave you with situations where prerequisites in layer creation wouldn't actually be assigned to a desktop.  So the right starting place is deciding what you really need, and whether you can do it with prerequisites, or combination layers, or both (e.g. Office always stands alone, but your other packages are combined into layers that all use Office as a pre-req).  There's no standard answer.

Posted on July 2, 2013
Steven Goodson
Registered user
Joined: May 11, 2011

  I hear you Gunther; unfortunately, these are student desktops used for labs and classes. They need all of the Office products complete, so we package them in a single layer. Of course they also use otherMS programs like SQL, Web Expressions, ect. 

  We do keep all of the Office products at the same version and hadn't had any issues with this, until testing the new Office 2013 layer.  It looks like the NoReReg is going to be the solution, we did not have this issue with 2007 or 2010.  The best part is, this is all in testing, so we can find the issues and get them corrected.

Posted on December 27, 2013
Edited by Fredster on December 27, 2013
Fredster
Registered user
Joined: December 27, 2013

I've got Office 2013 as a layer.  Trying to update Office by adding a layer version.  I first get an error message at boot up "The ordinal 599 could not be located in the dynamic link library iertutil.dll"  Click OK twice to get past it, now I have no network.  Thinking my Install machine is broke I try our secondary with the same result.  Try updating a different App layer and I'm fine on network.  I've got 3 OS layers (just one live one, 2 old are kept in case).  Tried all 3 and I have the same problem.  Am I going to have to create a new Office layer?

Posted on December 27, 2013
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Do you mean that you're trying to create a second app layer to contain updates for your Office Layer?  You should always update a program using a new version of the layer it's already in.  So go to your Office Layer, Add Version, and do your updates in that. 

I've never seen an error with iertutil.dll, so I don't have a pat solution for you, but it makes me suspicious of the update history here.

So I'd want a little history on the Office layer.  What version of your OS layer was it originall built with, if you recall?  When you built the Office layer, did you apply MS updates?  One possibility here is that you built Office originally with an old OS layer, and you accidentally installed some MS updates in the Office layer when you did Office updates.  Then later you updated the OS layer with even newer updates from MS.  Now the OS layer you're building from has newer stuff, but the Office layer is forcing you backwards to the updates it had installed.  So you have a patchwork of updates some of which are newer than others, some of which conflict with others.  The Office layer's updates will always supersede the OS layer's.  And that could be how your iertutil.dll is missing an ordinal that other parts of Windows and/or IE believe absolutely has to be there.

Unfortunately, if that's the case, then yes, you need to recreate your Office layer and be more careful to be absolutely sure you don't include any OS updates when you're updating Office.

If that really doesn't seem possible, then let me know in more detal exactly what you're doing - click by click if necessary.  Add Version or Create Layer, prerequisites or no prerequisites, etc.

Posted on December 27, 2013
Fredster
Registered user
Joined: December 27, 2013

I inheritted this mess.  So I couldn't tell you what version of what.  I've been painstakingly and very cautiously updating.  I also edited my origional post, I see how I misspoke about the layers, I was indeed adding a version for updates.  It's broken.  I've since created a new layer and will be doing testing to make sure it's all good.  I'm worried though that any user preferences that were in the old layer will be gone?  or is that hopefully saved outside the layer anyway?

But yes, moving forward OS updates will be in a OS Layer version and Office updates in the Office layer versions.

 

Posted on December 27, 2013
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Your user settings, which will all be in HKU in the registry, should be fine.  Removing and re-adding a layer only pulls the files and settings that were captured in the layer.  We couldn't possibly be intelligent enough to (or want to) figure out what settings are associated with an application and remove them too.  All that user-specific stuff is stored in the User Layer, outside of the app layers.  You should be fine there.

Posted on December 31, 2013
Edited by Fredster on January 6, 2014
Fredster
Registered user
Joined: December 27, 2013

Creating a whole new Office 2013 layer and then runing office updates and assigning this layer to users has caused them to have to reactivate office.   I'm skeptikal that user settings were saved if using a test acount it asks for reactivation.

Posted on December 31, 2013
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Activation and user settings are stored in very different places.  Activation is a hash of various bits of system information that is stored in an encrypted system database called the Secure Store.  We do not under any circumstances overwrite the Secure Store, so a desktop will always have the Secure Store that it has evolved with.  Activation breaks when Windows looks at your current system information and decides that "too much" (as defined secretly by Microsoft) has changed from the state captured in the Secure Store.  Since other Microsoft software, like Office, is part of the system information that Windows checks, a wholesale change in Office can cause activation to break.  Reactivating is easy enough.  But it's important to realize that the layer operation itself did not break activation.  The layer change caused a change in the desktop VM that Windows interpreted as too suspicious and it deactivated the machine.  That extra step in the middle, where Windows did its thinking, is important: we preserved everything that was there; it's up to Windows to interpret what it means.

User information is just HKU and random files, and unless the specific files and registry settings are alse in the layer, they will not be touched by removing and re-adding the layer.  Anything that is specifically part of the layer, though, will get replaced by your new layer.  So any settings that are in HKLM will likely get superseded, but anything in HKU, as well as all files, will remain just fine.

Posted on January 2, 2014
Fredster
Registered user
Joined: December 27, 2013

Ok all the persistent desktops are now fine with the new Office layer.

Non-persistant however are asking for activation every time.  I followed the recipe but I think I'm lost on this part for the non-persistent.  I've got 70 of these.  Would it just be easier for me to recreate them?  Or should I setup KMS for these? 

Posted on January 2, 2014
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Recreate them.  Our nonpersistent machines have frozen the bad licensing state, and no amount of fixing them will alter the fact that every time they reboot, they revert to the previous state.

Posted on January 6, 2014
Fredster
Registered user
Joined: December 27, 2013

Per the recipe, regarding non-persisten desktops.

If not using KMS activation can be added to the setupcomplete.cmd script in the c:\windows\setup\scritps directory. 

If using MAK volume keys

When using MAK keys you must first enter the product key then activate within your script. This script can be called from the setupcomplete.cmd or the runato.cmd if using KMS for Windows 7 activation.

call "c:\program files\microsoft office\office14\ospp.vbs" /inpkey:xxxxx- xxxxx-xxxxx-xxxxx-xxxxx

call "c:\program files\microsoft office\office14\ospp.vbs" /act 

Where does this go?  I know what directory it goes into, but does it go in the OS layer or the Office layer? (does is matter?) Specifically I'm now creating an Office layer version (rahter than rebuilding the office layer again) and putting this script in.  Hopefully this will fix my non-persistent desktop activation issues?

 

Posted on January 6, 2014
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

It doesn't matter where it goes.  Unidesk treats SetupComplete.cmd as a normal file, so if it shows up in multiple app layers, it is not merged.  It is "highest priority wins".  But whatever version of SetupComplete.cmd that wins is the one that will be processed by Windows at the end of mini-setup.  So however it gets there is fine with us.

Your two concerns are:

1. If you put it in your OS layer, and you deploy a desktop which doesn't have Office installed, what happens?  I've never tested that myself, but (since the commands are "call"ed from the CMD file) I believe it will cheerfully fail those two commands and continue processing.

2. If you put it in your Office App layer, you need to make sure you don't decide to similarly edit another app layer for its own purposes.

If you want to get really creative, you could do something like create a LayerScripts directory under Windows\setup\scripts, have individual layers put their own CMD files there, and put something like this in SetupComplete.cmd instead:

for %X in (C:\Windows\Setup\Scripts\LayerScripts\*.cmd) do call %X >> C:\Windows\Setup\Scripts\LayerScripts.log

And each script might look like this:

@echo off
some activation command or whatever >> C:\Windows\Setup\Scripts\LayerScripts\MyLayer.log

But the simple answer for you, today, is probably "Just put it in the OS layer."

Posted on January 6, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Steve,

 

Whenever you are modifying the build files like setupcomplete.cmd I would recommend making the changes in the OS layer.  Since its for Office you will probably want it to run for all desktops so you dont have to worry about it running or not.

If you did want to run it for just some desktops I would still make the changes in teh OSD layer but I would add a flag file to run it in the App layer.  For example if you only wanted to run a script for some desktops add a line like this in your code.

If EXIST C:\windows\setup\scripts\runapp1.txt (

call some code

)

 

Then to make it run you just add the C:\windows\setup\scripts\runapp1.txt file in your app layer.

Again probably not necessary here.

Posted on April 30, 2014
spatel99
Registered user
Joined: April 1, 2014

tying to follow the Recipe for our Office 2003 install for non-presistent deskops. following command don't work for our windows 7 pro. 

reg load "hku\temp" "%USERPROFILE%\..\Default User\NTUSER.DAT" 
 
I get access denied message even if run under administrator account. Do i need to put this commands into setupcomplete.cmd file ?
Posted on April 30, 2014
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Are you explicitly running your CMD As Administrator?  Just being logged in as the local administrator may not be sufficient.  You may have to also Run As Administrator.  But you should be able to load that hive.  You could also run Regedit as Administrator and load the hive from the File menu, too (click on HKLM first, and remember to unload your hive when you're done).

Posted on April 30, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi,

You will need to run these somewhere in the build process not in a layer itself.  The Setupcomplete.cmd woudl be an OK place to lauch the script from.

That said the purpose of the norereg is only to support having multiple office versions running at the same time.  Most people wont need these settings at all.  

Are you having a problem you are trying to solve?

 

Posted on June 10, 2014
Kyleigh96
Registered user
Joined: June 10, 2014

Microsoft Word is a word processor and was previously considered the main program in Office. Its proprietary DOC format is considered a de facto standard, although Word 2007 can also use a new XML-based, Microsoft Office-optimized format called.
Testking 70-178

Testking 70-243

Testking 70-246

Posted on July 22, 2014
pheng
Registered user
Joined: January 12, 2012

I think there's a typo in the recipe. In the GPO for Office 2013, the last line it tells us to Enable Outlook cache mode.  I think it should be disable so that Office is configured to be online rather than cache anything.  It's a VDI so caching is pointless.

Posted on July 22, 2014
Matt Allen
Unidesk employee
Joined: June 17, 2010

Thanks for pointing that out. Yes, the Outlook Cache should be disabled because, as you say, you want it running in online mode. I'll update the doc, nice catch.

Posted on July 23, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

I posted an updated version with the cache mdoe disabled

Posted on September 18, 2014
dasunsrule32
Registered user
Joined: March 28, 2014

So I've imported the Office GP's and I cannot find the Account Settings for Exchange anywhere. I've searched and don't see that in the policies. Any ideas? Thanks :)

Posted on September 18, 2014
dasunsrule32
Registered user
Joined: March 28, 2014

I don't seem to have the option of server settings and the exchange cached mode. Any ideas? I've impored and reimported the GP's. Thanks :)

 

Posted on September 18, 2014
dasunsrule32
Registered user
Joined: March 28, 2014

I'm not seeing the account settings options in the GP's. Any ideas?

Posted on September 18, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

I wrote this a long time ago shoudl still apply

Posted on September 18, 2014
dasunsrule32
Registered user
Joined: March 28, 2014

Ok, I'm trying this post without the image. I don't have the option in the MS GP's for Office 2010, to disable Cached mode. They don't exist in the policies. What am I missing? Thanks :)

Posted on September 18, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Sounds like you need to download the outlook admx files and add them to your domain.  For 2010 its outlk14.admx

http://www.microsoft.com/en-us/download/confirmation.aspx?id=18968

Posted on September 18, 2014
dasunsrule32
Registered user
Joined: March 28, 2014

Yeah, I ended up getting it fixed. Sorry about the extra posts. The forum was not updating and showing my posts at all. I tried in three different browsers on two different systems with the same results. Deleting the comments are not working either... :(

Posted on September 29, 2014
agresbach
Registered user
Joined: February 1, 2012

I had a question in regards to if/when we need to replace one office layer w/ another for an existing persistent desktop.   For example, if Desktop A currently has Office 2010 layer assigned and then needs to be changed to the Office + Visio 2010 layer.  Currently when we do this, the first time the user runs an Office app (ie. Word, Excel), they have to sit through a 2 min "Configuring Microsoft Office Professional Plus 2010" window before the app launches.  it seems as though it only runs that one time but hoping theres a way to avoid this.   I saw in the recipe that there is a section that talks about something similar and a resolution by adding some registry entries.  would those help in this case? and if so are they added into the Office Layer or OS layer?

 

thank you!

Posted on September 30, 2014
Matt Allen
Unidesk employee
Joined: June 17, 2010

You would add these entries into the Office layer. There are also some local group polices that can be enabled to suppress some of that initial startup wizard as well.

Posted on September 30, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Andrew,

I am not sure there is any way to supress at least one "configuring Office" when you change versions.  The norereg registry entries only stop that from running every time you launch a different office versiosn but even with those you get one "configuring office" task running.

You might try to use the reinstall command when you deploy the new layer.  This will remove the old licensing files in the UEP and replace them with the once from the layer.  If you think about it when office 2010 is run on the desktop the first time it will update its licensing files by getting a license frmo KMS so that will pull all the lkicense files into the UEP.

Then when you swap out versions the licensing files dont know about Visio.  So if you use the reinstall maybe the configuring tasks wont be necessary.

Let us know if that helps.

Rob

Posted on October 20, 2014
Edited by snakedoc on October 20, 2014
snakedoc
Registered user
Joined: August 7, 2013

In the receipe, it states that "when packaging Office for an image installation as we do with Unidesk, the best option is to install the application but not run it. Then when the application is run the first time on each desktop it will create the CMID on that desktop."

This is exctly what I did for an Office 2013 install on an App layer with Windows 7 x64 SP1.

Problem is that I cannot patch or update Office 2013 via Windows Updates. The section "Give me updates for Microsoft products" is not available until Office runs at least once and the option "install recommended updates" is picked.

Does this happen to anyone else? What's your workaround? Active and rearm? Grab the updates and patch manually?

Thanks!

 
Posted on October 27, 2014
Jeff Pitsch
Unidesk employee
Joined: March 28, 2012

So following this thread and I finally able to confirm that you do not need to run Office to get Windows Updates for other Microsoft Updates.  In fact, whenever I create a gold I always enable this setting ahead of time.  When Windows 7 is first installed and you pull up Windows Updates there is an option to 'Get updates for other Microsoft products.  Find out more'.  The find out more is a link that brings up IE and a web page that allows you to select that yes you want to receive updates for Office, and other products.  You check the box that you agree to the licensing terms, click Next and then you can choose how Windows will install updates and you are done.  From that point on the gold image will be set to apply updates for Windows and other products.  I couldn't upload my images but I've attached a Word doc that has the pics in it that always show up when I run through the above process.

 

Jeff

 

Posted on October 28, 2014
snakedoc
Registered user
Joined: August 7, 2013

I get the option but when I clicked on it (get updates for toher Microsoft productions. Find out more", it simply takes me to a page telling to go to Start - All Programs - blah blah blah. See attached for a screen cap.

 

Running W7 x64 SP1 Enterprise. Maybe you have something liked silvertlihgt installled.

Thanks!

Posted on October 28, 2014
Jeff Pitsch
Unidesk employee
Joined: March 28, 2012

No this is a clean install of Win7 so no sliverlight.  In fact, that's how I get silverlight on the system is by doing the process I stated.  I'm wondering if this is a difference between Pro and Enterprise.  I'm building up an Enterprise desktop now to see if it changes behavior.

Posted on October 28, 2014
Jeff Pitsch
Unidesk employee
Joined: March 28, 2012

Ok installed a Win7 x64 Sp1 Ent VM and I still get the option as I specified.  This is straight from ISO install.  I'm wondering what other changes you have made to your gold before hand that would be affecting the ability to turn this on.

Posted on October 28, 2014
Jeff Pitsch
Unidesk employee
Joined: March 28, 2012

Ok after some Google-Fu and some testing it appears the problem is IE11 itself.  It does not appear that the web page is compatible with IE11.  Now Rob and I have had different results but I think this solution should work.  If you add 'microsoft.com' under the compatibility view settings, that should take care of the problem.  Would you be able to give that a try?

Posted on October 29, 2014
snakedoc
Registered user
Joined: August 7, 2013

Yep. That worked. I didn't actually add any sites to the compatibility list. I just checked the box that says "Use Microsoft compatibility lists" under Compatibility View Settings.

I'll update this in the next OS layer updates.

Thanks for you help!

Posted on October 20, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Scott,

The recipe was writtten using Office 2010.  I will do soem testing using 2013 and reply back when i can.  You idea of activating then rearming sounds like it would work.

Rob

Posted on October 21, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Scott I looked at Office 2013.  I could not find any other way to add in the Office Update functionality to Windows update except to run office once.  You dont need to activate just run it.  Then as you said do a rearm.

For those who need it the rearm command is c:\program files\microsoft office\office15\ospprearm.exe or the same path in program files(x86) for 64 bit.

I will update the recipe to reflect this.

Thanks for posting Scott.

Rob

Posted on October 21, 2014
snakedoc
Registered user
Joined: August 7, 2013

Thanks Rob. Just thought maybe there are other ways of doing this...

A note on rearm. You can only rearm 5 times before it forces you to activate via KMS. So eventually one will have to activate via KMS first then rearm.

http://technet.microsoft.com/en-us/library/dn385362(v=office.15).aspx

Cheers!

Posted on October 22, 2014
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Scott I dont think you will ever have to start office again or rearm again.  After you rearm it doesnt change the windows update setting back.  SO this shoudl just eb something we have to do teh first time we install office into a layer.  

Thankfully.

Posted on March 5, 2015
Keith Asche
Registered user
Joined: July 24, 2012

So my only issue at the moment, is even with only Office 2013 ever being the only version of office installed, and with the NoReReg added, it still wants to re-register. It is activating fine.

Posted on March 5, 2015
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Keith what OS are you using.  There is anm issue with Office 2013 and Windows 8.1 that requires special attention to get to work correctly.  We have a solution defined in our latest Office recipre using some scripting we created.  If you are using Windows 6.1 take a look at that and let me know if you have any questions.  You can post here or email me directly or put in a support ticket.

Rob

Posted on March 12, 2015
Bnoll
Registered user
Joined: October 10, 2013

Anyone having issues getting to www.virtualdesktopmanagement.net/scripts ? says access is denied. 

Posted on March 12, 2015
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Sorry 'bout that.  Typo in that URL.  It should read http://www.virtualdesktopmanagement.net/scripts.aspx instead.  Rob will get the main page updated at some point.

Posted on March 12, 2015
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Sorry Brandon,

I updated the doc to the correct URL.

Rob

Posted on April 3, 2015
Edited by dasunsrule32 on April 3, 2015
dasunsrule32
Registered user
Joined: March 28, 2014

Ok, I'm on pulling my hair out on this one. I'm using VAMT to manage licensing currently, since we use MAK licensing. I've been having issues with it recognizing Office on the Unidesk VDI's and haven't been able to nail down what is the cause of the issue. I've blew away every layer and started from scratch to no avail.

When I try to detect the licenses installed on the newly created VDI's, Windows 7 Pro shows up just fine and I can activate it successfully. Office 2010 never shows up and I cannot activate it.

I've gone ahead and rearmed it and it still doesn't show up for activation purposes. It worked at one time, but no longer does. Has anyone else run into his and what was the work around?

By the way, I've installed it in it's own layer, moved it into the OS Layer with all the same issues... Thank you in advance! :)

 

EDIT: If it makes any difference, I'm installing the 32-bit Office 2010 install on Windows 7 Pro 64-bit.

Posted on April 3, 2015
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Aaron,

After rearming the layer, when you deployed it did you check there-install box?  If you didnt then i dont think the rearm woudl matter becasue the office licening layers get pulled up into th epersonali8zaiton layer.  I woudl try two things wiht the rearmed layer.  On an existing desktop edit the desktops and when you apply the new layer check re-install.  See what happens.  Also create a new desktop with the layer and see what happens.

If those tests are negative try creating a desktop wit nothing but office to rule out a spossible layer conflict.

Rob

 

Posted on April 7, 2015
dasunsrule32
Registered user
Joined: March 28, 2014

Hi Rob,

 

Thanks for the reply. I've gone ahead and removed every layer, and built new VM's with the re-armed layer. I finally got it, but I had to delete the old Office layer, then create a new one. Once I did this, I was able to activate successfully. What a pain... :(

Posted on May 1, 2015
Edited by mplane on May 1, 2015
mplane
Registered user
Joined: May 1, 2015

Hi Rob,

Office 2013 SP1 on Windows 8.1 (up to date as of this post)

I've followed the recipe an used the AppConfig utility, but I'm still having issues with Office actvation after a newer layer is added or updated, or if Office isn't the newest (top priority) layer in the deployment. I’ve got the new scripts in the OS layer, and it works well to allow office to activate. The problem I’m having now is every time I add a layer to a desktop after office has been added, it throws out the office activation and we’re back to the same problem. I’ve done a few things to get it working again without repairing or rebuilding, I just wonder if these scripts could be adjust to work with the Unidesk tools and services to automate the process.

Here’s what I needed to do after adding another layer after Office (or when office isn't top priority it seems) to get Office activation to work properly:

I deleted the two ‘Done’ files in the scripts directory, then ran the OfficeActivate.cmd file again. That got half the job done, but it still hadn’t activated with the server.
I found this at the end of your script, but it didn’t run with the rest even though it looked like it’s only condition was supposed to be made active during first part applying to Office 2013 Pro Plus
cscript "c:\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /act

So that got the job done and will work after each time a layer is added to a desktop, but is there something else I’m missing or a way to automate this process each time a layer is added?

Posted on May 1, 2015
Keith Asche
Registered user
Joined: July 24, 2012

I found that with my persistent desktops, after running the AppConfig, Office works fine. I created a separate layer (per recommendations from Unidesk Support) for my non-persistent optimizations. I found that after setting up those scripts, I then had to re-run the AppConfig. I did make the NP Optimizations layer require that the Office layer be present while creating the NPO.

Posted on May 1, 2015
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Michael,
Are you using NP or Persistent Desktops? Its a little strange that subsequent layers would break office activation unless they include an office application. If any of them do then that is normal and will always cause an issue. Our current recommendation for office is that you create separate layers for each set of Office Apps you need to deploy together. That makes it much easier to keep the appropriate license files in tact and its only a little more effort to patch.

If you change office layers then that will also cause Microsoft to want to reconfigure because the licensing files which are copied into the UEP are then different from the layer licensing files. If that happens on a persistent desktop the reconfigure will happen once then office should activate and be ok. If its a NP machine you must rebuild with the new layer.

If this doesn't ring any bells for your issues I thin you should enter a support ticket and work with support to figure out whats going on in your particular case.
Rob

Posted on May 4, 2015
mplane
Registered user
Joined: May 1, 2015

Hi Rob,

We are using persistant desktops. I've only got one layer with anything for Office. It's Office 2013 Pro Plus, being activated by KMS. It works fine when the office layer is initially. It's only affected by adding other layers. I only have one version of my one office layer.

As an example, I had a persistant desktop set up. Everything was working properly and office was activated. I removed the VLC app layer. All it had installed was VLC Player. After doing that, office now complains that it needs to be activated again.

Posted on May 13, 2015
gstrouth
Registered user
Joined: May 19, 2011

I've been fighting this same problem since last fall. What I've run into is that any edit to a desktop will break the office licensing. Its been to the point where I haven't touched my desktops for months because its a pain. I can get office activated again by running the activation scripts but its a pain every time. I see the guide has recently been updated so I'm going to see if these new steps help fix anything.

Posted on May 4, 2015
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Michael,

Did you ever try to have office in your OS layer then remove it? The only thing i can think of is something like that. You shoudl probably create a support ticket and have support work with you to try to figure out whats going on.

Posted on December 2, 2015
Elliot alan
Registered user
Joined: December 2, 2015

I work on machines installed after you install Office in the new app.

Pass4sure 300-070

642-997 Dumps

Posted on January 27, 2016
Jeff.Kasey
Registered user
Joined: October 31, 2014

Rob

Not sure if I missed it but where are the directions located?

Posted on January 27, 2016
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Jeff in the first post at the top there is a download file link.  That has the recipe.

Posted on February 8, 2016
mikeg@houstonplating.com
Registered user
Joined: May 13, 2014

We use Office 365 E3 licenses which does not activate with KMS or MAK but through cloud activation. I too have an issues with each office layer update that office complains it is not activated. office then wants a repair, clicking repair twice eventually resolves the issue but it states that it is not activated until you close and reopen office application such as outlook, word etc. Does this recipe work with E3 licensing? Sorry if this question has been asked but i have not seen it anywhere, i have tried the recipe and find it has not worked for me. Has anyone else attemped this with E3 licenses?

Posted on February 9, 2016
Mike Ryan
Registered user
Joined: July 22, 2014

Internesting. We have Office 365 with E3 licenses and are also experiencing the exact same issue that you've detailed. If we update the Office 365 app layer and then deploy to desktops, users are prompted at least twice (I've been told sometimes 3 times) to repair Office. Initially, we were thinking that it had something to do with having Lync in the initial Office 365 layer and then Skype in the latest Office 365 update(s).

Posted on February 9, 2016
mikeg@houstonplating.com
Registered user
Joined: May 13, 2014

We went as far a creating a new layer and tested with users and still find the issue happens so i do not believe it has anything to do with lync or skype. I know this is jsut taking a stab in the dark however it almost seems that the cloud authentication in the user layer sees the version chage in the app layer and thinks it is licensed incorrectly. 

Posted on February 9, 2016
Mike Ryan
Registered user
Joined: July 22, 2014

I believed we tried that also. At least I'm not alone, I guess, with this issue. I did do some research awhile back, though I didn't uncover anything of relevance.

Posted on February 9, 2016
mikeg@houstonplating.com
Registered user
Joined: May 13, 2014

I am testing my theory, although it is not extensive testing. Here is what i am planning.

1) Test by placing Office directly in the OS layer. Then update and see if same issue occurs.

2) Test by installing office in user layer then test update and see if issue occurs.

3) Build standalone VM (not in unidesk) install office then test update.

 

These three tests should show if it is inconsistncies from layer (App or OS) to the user layer settings probably in regestry from incorrect version and cloud activation.

Let me know if anyone aggrees or disagrees with this test.

 

 

Posted on February 18, 2016
jirvin
Registered user
Joined: November 10, 2015

We are experiancing the same issue after updating our Office 365. I opened a case with Unidesk support today. We post back if we get it resolved. Thank you

Posted on June 16, 2016
JayMan
Registered user
Joined: February 18, 2014


When updating the Office Layer, do we need to redo the re-arming & Office2013/Win8.1/10 batch file? Or are they only needed when first creating the layer?

Posted on June 16, 2016
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi Jason,

In my environment whwnever i update office 2013 it seems to activate so I have to rearm it.  You can check first before rearming by using: cscript ospp.vbs /dstatus  if it says its licensed then run ospprearm.exe.

Posted on June 16, 2016
JayMan
Registered user
Joined: February 18, 2014

No worries, will check that out. Thanks for the quick reply.

Posted on September 13, 2016
Kheenan Halvorson
Registered user
Joined: November 5, 2015

For the most part I have no issues for Office 2016 but the only problem I am having is getting the shortcuts on the desktop.  I can use every AD template for it and those all work but no shortcuts.  I have tested multiple different ways and no luck.  As soon as i apply one of those GPO's to a real physical machine with Office 2016 installed the shortcuts appear on the desktop.  So is there a known issue at all with this specific feature?  Is there a different more effective way to do it?  Any help would be greatly appreciated. 

Posted on September 29, 2016
wrekdoll
Registered user
Joined: July 21, 2016

any additions to this for ver 4.0.x?

Posted on September 30, 2016
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

its been updated.  When you use Office with Elastic Layering you will want to add the c:\windows\setup\scripts\officeactivate.cmd to the layer's srcript setting sotht office will activate after the layer is attached.  You still needto follow the rest of the directions.

For MCS Offce must be activted on the master image.

Posted on December 27, 2016
David Thacker
Registered user
Joined: September 27, 2016

In 4.0.7 I can't get it to run the cmd file when the layer is added as part of a pre-built NP image, or added elastically. Office will fail to run, then mentions it can't activate, but if I run the script manually, the activation works ok. and the _done file is create in the scripts directory. This worked ok under 4.0.6. I've created new layers for Win10 and Server 2012R2, and both exhibit the same problem -- the officeactivate.cmd is not running as part of the layer script.

I am running full MS stack (NP VDI and Elastic RDSH) and Unidesk 4.0.7.

Posted on December 27, 2016
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Hi David,

Did you run the prep command when you created your office layer.  Both Windows 10 and Sever 2012R2 requier that you run the

Office2013Windows81_PREP.cmd

What this does is make a copy of the windows store and the officeactivate script will put that in as the store on your VMs.  That way the licenses match.

For elastic layering to run teh scritps you must add c:\windows\setup\scripts\officeactivate.cmd to your scritps path in the layer.

Rob

Also for thodr OSes when using Office 2013 or later you must rearm after ever time you add a version to the layer.

Posted on December 27, 2016
David Thacker
Registered user
Joined: September 27, 2016

I will go back and make sure I am running the prep command. I tried several different permutations the other day and I'm not sure if I left that in my final attempt or not.

I do have the elastic layer calling the officeactivate.cmd file, and it's not running. If I look in the scripts directory. the _Done file isn't created. If I run the script manually, it activates perfectly and the _Done file is created, indicating it did run.

Posted 3 weeks ago
David Thacker
Registered user
Joined: September 27, 2016

I figured it out. For some reason the GVLK wasn't present in the installation. I made sure to run cscript ospp.vbs /inpkey and put it in, along with the rest of the instructions, and it started working. Initially, the app would come up and say it wasn't activated, but after a couple of minutes the activation would take place and it would show activated after that. I verified the acitvateoffice.cmd is running when the elastic layer is used.

Posted 3 weeks ago
Rob Zylowski
Unidesk employee
Joined: June 21, 2010

Thats a little weird as the script enters the key as long as you create the correct flag file in the layer using the optimizer.

Login to post comments