Automate acivation licence office 2013 for user computer
Hi Everybody !
I would like to know how to do for automate the activation of Microsoft Office 2013 license automatically without the user should be computer administrator
and do not bring up the launch of Office 2013 to the parameters of the windows update .. "Next" ...
i set up configure my .msp with the product license key
Thanks guys :)
I would like to know how to do for automate the activation of Microsoft Office 2013 license automatically without the user should be computer administrator
and do not bring up the launch of Office 2013 to the parameters of the windows update .. "Next" ...
i set up configure my .msp with the product license key
Thanks guys :)
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jagadeish
9 years ago
Posted by:
Silencer001
9 years ago
In Dell KACE, I created the following "application" with this commandline parameter: cscript Activate_Microsoft_Office.vbs
This is the content of the VBS-file which should activate the productkey which you have set in the .MSP
On Error Resume Next '****************************************************************************************** '*** INITIALISATION *** '****************************************************************************************** Set WshShell = Wscript.CreateObject("Wscript.Shell") Set fso = CreateObject("Scripting.FileSystemObject") Set WshSysEnv = WshShell.Environment("SYSTEM") sSystemDrive = WshShell.ExpandEnvironmentStrings("%SystemDrive%") sProgramFiles = sSystemDrive & "\Program Files" sProgramFilesX86= sSystemDrive & "\Program Files (X86)" sCurrentFolder = fso.GetParentFolderName(WScript.ScriptFullName) sComspec = WshSysEnv("Comspec") '########################################################################################## '### Start of script ### '########################################################################################## ' Check Office Version (Based on "winword.exe". This will represent the value of the whole office suite) Err.Clear vOfficeInstallPath=WshShell.RegRead("HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\winword.exe\Path") If Err = 0 Then 'Path to MS word found, thus MS Office is installed. Activate MS Office with the MAK-Key set during the installation (Done in Reference Image) WshShell.Run sComspec & " /c " & "cd " & chr(34) & vOfficeInstallPath & chr(34) & " & cscript " & "ospp.vbs /act",0,true Else 'No Office version detected. End If |
Posted by:
Lapin62
9 years ago
This is my congfiguration for the script
and is the message that appears when I run the command manually
Why this message?
Thx
and is the message that appears when I run the command manually
Why this message?
Thx
Comments:
Posted by:
Lapin62
9 years ago
for information, the users of the computer are not Admin
Comments:
-
that should not be an issue.. - jagadeish 9 years ago
Posted by:
Lapin62
9 years ago
Hello,The script usually works :)My last concern is the " custom.msp " file that does not work after the office deployment on the client machine .The configuration of the key, the personalized parameters are not worse effect.The file " custom.msp " Yet the root of the compressed folder , how do you explain this?
Posted by:
Lapin62
9 years ago
Comments:
-
Keep the custom.msp file in "Updates" folder and then just call setup.exe - jagadeish 9 years ago
Posted by:
Lapin62
9 years ago
Hi !
Im Sorry but keep the "custom.msp" in "updates folder" is doent not work !
I launched the personalized configuration in kace "setup.exe" and uncheck "Do not add the prefix msiexec.exe"
installation on the remote odinateur is done correctly except when the application is installed, the Welcome window, to update and activation key appears! Then I set all these parameters in the "custom.msp": /
I really do not know where does the problem, I feel around in circles ..
Thank you all
Im Sorry but keep the "custom.msp" in "updates folder" is doent not work !
I launched the personalized configuration in kace "setup.exe" and uncheck "Do not add the prefix msiexec.exe"
installation on the remote odinateur is done correctly except when the application is installed, the Welcome window, to update and activation key appears! Then I set all these parameters in the "custom.msp": /
I really do not know where does the problem, I feel around in circles ..
Thank you all