Jump to content

Activating Office 2010 Via the sysprep.xml help required.


Recommended Posts


I think the problem is the space inside "Program Files"!

You can use quotes.Like this:


<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /inpkey:PRODUCT KEY</CommandLine>
<Order>4</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act</CommandLine>
<Order>5</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>

Or like this:


<CommandLine>cscript //b C:\"Program Files"\Microsoft Office\Office14\ospp.vbs /inpkey:PRODUCT KEY</CommandLine>

Or you can use %PROGRAMFILES%

Edited by myselfidem
Link to comment
Share on other sites

I think the problem is the space inside "Program Files"!

You can use quotes.Like this:


<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /inpkey:PRODUCT KEY</CommandLine>
<Order>4</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act</CommandLine>
<Order>5</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>

Or like this:


<CommandLine>cscript //b C:\"Program Files"\Microsoft Office\Office14\ospp.vbs /inpkey:PRODUCT KEY</CommandLine>

Or you can use %PROGRAMFILES%

Thank you sir, worked like a champ.

Link to comment
Share on other sites

  • 8 months later...

How would the the sysprep file look on Windows 7 64?

<SynchronousCommand wcm:action="add">

<CommandLine>cscript //b "C:\"Program Files (x86)"\Microsoft Office\Office14\ospp.vbs" /inpkey:PRODUCT KEY</CommandLine>

<Order>4</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

<SynchronousCommand wcm:action="add">

<CommandLine>cscript //b "C:\"Program Files (x86)"\Microsoft Office\Office14\ospp.vbs" /act</CommandLine>

<Order>5</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

Link to comment
Share on other sites

You can find help about Microsoft Office 2010 32 bit or 64 bit, here:

Tools to configure client computers in Office 2010

Troubleshooting Office installation failures

Extract:

2) From an elevated command prompt, run command lines similar to the following (if you are running 32-bit Office 2010 on a 64-bit operating system, the path should include Program Files (x86)):

%windir%\System32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your 25 digit MAK product key for Office 2010)

%windir%\System32\cscript.exe "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act

If you are using the x86 version of Office Professional Plus 2010 on an x64 version of Windows operating system, follow these steps:

a. At the command prompt, run the following command:

cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /inpkey:<Product_Key>

Note: <Product_Key> represents the product key that you want to install.

b. Run the following command:

cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /act

In other situations, follow these steps:

a. At the command prompt, run the following command:

cscript "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /inpkey:<Product_Key>

b. Run the following command:

cscript "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /act

Understanding 64-Bit Office

Extract:

For these reasons, we recommend running 32-bit Office 2010 even on 64-bit Windows operating systems for better compatibility.

On 64-bit Windows, more applications and documents may be opened at once, and switching among them will be faster because the machine can have more physical memory

for the processes to share. When the 64-bit ecosystem for Office is more mature, you’ll be able to easily migrate to 64-bit Office!

Edited by myselfidem
Link to comment
Share on other sites

So can I insert these into my sysprep file like you have them and they will work? Sorry for so many dumb questions. i new to this Windows 7 sysprep

Thanks for all your help!

%windir%\System32\cscript.exe "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your 25 digit MAK product key for Office 2010)

%windir%\System32\cscript.exe "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /act

Link to comment
Share on other sites

You can keep the file you've made.

Be careful with the quotes!


<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /inpkey:PRODUCT KEY</CommandLine>
<Order>4</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /act</CommandLine>
<Order>5</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>

Link to comment
Share on other sites

I took the quotes out. but it still does not activate. Should there be a space between the program files and (x86)?

<SynchronousCommand wcm:action="add">

<CommandLine>cscript //b "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /inpkey:PRODUCT KEY</CommandLine>

<Order>4</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

<SynchronousCommand wcm:action="add">

<CommandLine>cscript //b "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /act</CommandLine>

<Order>5</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

Link to comment
Share on other sites

Yes there is a space between Program Files and (x86).

About Activation Microsoft Office 2010 with Volume Licence Edition you can use opps.vbs script:

Volume activation overview for Office 2010

For your personnal copy of Microsoft Office 2010 (and Windows 7) you can use the tool made by Rico.JohnnY

LicRestore.rar

http://www.msfn.org/...kuprestoration/

Microsoft technet

Edited by myselfidem
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...