silent office 2010 install and activation

Semua Balasan

• 31 Mei 2012 21:27

   

   
  

  0

  Hi Mike,

  install a KMS. This way the client machines only have to activate to a server inside your network.
  Only use MAK (which requires activation to MS internet servers) if KMS is unsuitable for you.

  If you must use MAK, then you will need to ensure that the account being used by ConfigMgr to install Office on the client, has unauthenticated internet access to perform activation via MS servers. the account most likely being used in the LocalSystem account, which would be the computer account in the domain, do you may need to add "Domain Computers" into your proxy permit list, or, add the various MS URL's into your proxy unauth list so anything/everything can surf to the activation URL's.

  Also, the config.xml line you sampled, is still commented (the <! means "commented")

  Auto-activation is troublesome for a lot of people (which is why we recommend KMS instead of MAK), but some success is possible if your deployment includes some form of scripting which would be like:
  <start script>
  setup.exe
  cscript ospp.vbs /act
  <end script>

  refer: http://technet.microsoft.com/en-us/library/ee624350

  most likely it works for you when you do it manually, because you are logged in as you (and your account has proxy/internet access).
  this is why a lot of deployments work "manually" but fail when ConfigMgr tries it (because CM is logged on as the computer account and not as your account)

  ---

  Don

  
  
  
  
  
  

  • Diedit oleh Don - tesgroupMicrosoft Community Contributor 31 Mei 2012 21:40
  •  
  • Balas
  • Kutip

   
• 01 Juni 2012 11:36

   

   
  

  0

  So what should that line look like?

  -- <Setting Id="AUTO_ACTIVATE" Value="1" /> --

  KMS is not an option for us at this time.

  Where would I put this scripting you mention. I've seen this on a couple of other posts, but nobody says where this would go. 

  ---

  Mike in IT

  • Balas
  • Kutip

   
• 01 Juni 2012 18:29

   

   
  

  0
  Okay I got it to partially work. I deployed to 5 computers and on 2 it installed and activated. On the other 3 it errorred out still. I can check the logs on those three, but they don't really tell me anything.

  ---

  Mike in IT

  • Balas
  • Kutip

   
• 01 Juni 2012 22:55

   

   
  

  0

  So what should that line look like?

  -- <Setting Id="AUTO_ACTIVATE" Value="1" /> --

  the syntax you need is:

  <Setting Id="AUTO_ACTIVATE" Value="1" />

  If you are using ConfigMgr to deploy Office, then you will have a package/program/advert.
  The properties of the program will include the command that the program will execute.
  This will be setup.exe, or maybe setup.exe /stuff /morestuff /evenmorestuff
  This needs to be changed, to be something like setupofficeandactivate.cmd, or, some similar script file.
  Then you create the script file and place that script file into the package source with setup.exe, then update the package to re-distribute it with the new content.
  So, instead of the CM program running setup.exe, it will run a script, and the script will do 2 things, first runs setup.exe and second, it will run ospp.vbs /act

  ---

  Don

  • Balas
  • Kutip

   
• 01 Juni 2012 23:00

   

   
  

  0

  Okay I got it to partially work. I deployed to 5 computers and on 2 it installed and activated. On the other 3 it errorred out still. I can check the logs on those three, but they don't really tell me anything.

  Errored?
  what error occurred? at what stage? which logfiles are you looking at?
  a) is office installed successfully by this program? (even if not activated, did it install ok?)
  b) was the activation attempted? (check office setup logfile)
  c) you can expect to have problems if your pc clients are WinXP, because the licensing service doesn't autostart on WinXP. What OS are the clients?
  d) are you able to confirm if the issue is due to activation not firing, or due to hitting your proxy/firewall and blocking?

  another option might be for you to deploy via CM but remotely activate client pc's via VAMT?

  ---

  Don

  
  

  • Diedit oleh Don - tesgroupMicrosoft Community Contributor 01 Juni 2012 23:01
  •  
  • Balas
  • Kutip

   
• 04 Juni 2012 17:18

   

   
  

  0

  I have checked the Execmgr.log to see if it was at least running. On some of them there is no log from when I advertised the program, even if they did install and activate. I don't know which other one(s) to check to see if there was an attempt at installation. I am installing on both XP and win7, both had the same problems. Some would install and some wouldn't, doesn't seem to matter which OS. On the ones where it installed they were activated, I can't find where an error code or something would be to help trouble shoot why I didn't install on the others. 

  I don't know how to write scripts, can you give me an example of how or a link to where I get help in this area. If I just install then use VAMT to activate do the computers have to on and logged into, or can this be done if I just tell everyone to leave their computers on over night?

  ---

  Mike in IT

  • Balas
  • Kutip

   
• 04 Juni 2012 21:16

   

   
  

  0

  ok, sure.
  if installation of office is not completing successfully, then that's a little different from failure to activate.
  either way, there are some diagnostic steps that are common.
  if execmgr.log isn't revealing that the advert fired the program to install office, then there's something other than office setup.exe giving you trouble, so diagnose that first.

  if office setup.exe is being fired, but install is not successful, or, install succeeds but activation fails, then check the office setup logfiles:
  http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx

  you can use VAMT to perform activation remotely.
  The way this would work, is that you install office on the client pc (say via ConfigMgr), and then after the install is completed, use your pc (where you are logged in with client pc admin rights or domain admin or whatever), run VAMT, and VAMT will connect to the client pc over your LAN and perform activation of the client pc. this requires the client pc to be powered on, and you must have an account/privileges on the client pc that has admin rights. the user does not have to be logged on at the client pc.
  Or, you can use ospp.vbs to perform remote (LAN) activation.
  http://technet.microsoft.com/en-us/library/ee624350

  this blog by Blair might also help you:
  http://blair-muller.blogspot.com.au/2011/04/how-to-deploy-office-2010-from-system.html

  ---

  Don

  • Ditandai sebagai Jawaban oleh Mike in IT 12 Juni 2012 15:58
  •  
  • Balas
  • Kutip

   
• 06 Juni 2012 14:41

   

   
  

  0

  Okay, so I've tried the starting the logging feature, but I'm not getting anything. SCCM says that all 4 computers have received the package, but it's been 3 hours and they haven't started running yet. Is there a log somewhere I can check to see if there was some kind of error? I tried to just install office and then I was going to activate with VAMT, but It's not even running the program to install.

  I've already done everything in Blair's blog, and the tools I'm going to try the VAMT. I don't want to go through every computer with the ospp.vbs, that would take forever. I do have a question about VAMT, I've run the discovery and it has gotten into all of our machines. I've updated their info and found what most of them are running. I saved as and choose a name. when I close it and reopen it doesn't automatically populate, and when I try to import I get the error: 

  'An item with the same key has already been added'

  But I've not added a key yet I've only just opened the tool. How do I get this to work so I don't have to waste 20 -30 minutes discovering and updating every time I reopen VAMT?

  ---

  Mike in IT

  • Balas
  • Kutip

   
• 06 Juni 2012 21:09

   

   
  

  0

  if clients are nor running the program to install Office, then return to client-side CM logs to find out why.
  (check execmgr.log etc)
  run a Last-1000-messages-report for the specific computer to see what events/messages have been sent up to the MP/db.

  I don't use VAMT myself, so I'm not sure what you're seeing. I thought the discovered data persisted, and that you only did an import/export when you wanted to move activation data between 2 separated/isolated environments.

  Or maybe you could try the new VAMT which apparently uses a SQL express db (which implies it would preserve data across sessions)

  ---

  Don

  • Balas
  • Kutip

   
• 11 Juni 2012 14:58

   

   
  

  0
  I don't know what the difference is, but when I run just the install with SCCM it works. Then I was able to activate using the VAMT tool. But now I've found another problem. If they have a 64 bit version of Access, Office 2010 32bit will not install. Is there a work around for this, or will I just have to uninstall the 64bit version?

  ---

  Mike in IT

  • Ditandai sebagai Jawaban oleh Mike in IT 12 Juni 2012 15:58
  •  
  • Balas
  • Kutip

   
• 12 Juni 2012 15:57

   

   
  

  0
  Looks like I have to uninstall the 64bit Access to install 32bit Office. Thankfully we don't have too many with 64 Access!

  ---

  Mike in IT

  • Ditandai sebagai Jawaban oleh Mike in IT 12 Juni 2012 15:58
  •  
  • Balas
  • Kutip