clivebuckwheat Posted June 15, 2010 Share Posted June 15, 2010 HiI am trying to activate Office 2010 via the sysprep.xml fileI know the following commands work because I manually ran them from a login state. Now I am trying to activate Office via the sysprep.xml file.It's not working.Do I need quotes around the office path?sysprep32nopk.txt Link to comment Share on other sites More sharing options...
myselfidem Posted June 15, 2010 Share Posted June 15, 2010 (edited) 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 June 15, 2010 by myselfidem Link to comment Share on other sites More sharing options...
clivebuckwheat Posted June 15, 2010 Author Share Posted June 15, 2010 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 More sharing options...
myselfidem Posted June 16, 2010 Share Posted June 16, 2010 Fine! Thanks Link to comment Share on other sites More sharing options...
Cochise Posted March 2, 2011 Share Posted March 2, 2011 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 More sharing options...
myselfidem Posted March 2, 2011 Share Posted March 2, 2011 (edited) You can find help about Microsoft Office 2010 32 bit or 64 bit, here:Tools to configure client computers in Office 2010Troubleshooting Office installation failuresExtract: 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" /actIf 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" /actIn 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" /actUnderstanding 64-Bit OfficeExtract: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 March 2, 2011 by myselfidem Link to comment Share on other sites More sharing options...
Cochise Posted March 3, 2011 Share Posted March 3, 2011 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 sysprepThanks 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 More sharing options...
myselfidem Posted March 3, 2011 Share Posted March 3, 2011 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 More sharing options...
Cochise Posted March 3, 2011 Share Posted March 3, 2011 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 More sharing options...
myselfidem Posted March 3, 2011 Share Posted March 3, 2011 (edited) 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 2010For your personnal copy of Microsoft Office 2010 (and Windows 7) you can use the tool made by Rico.JohnnY LicRestore.rarhttp://www.msfn.org/...kuprestoration/Microsoft technet Edited March 3, 2011 by myselfidem Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now