Great when u r going to post the commands for office 2013 scripting .THX keep up the good work... one thing more how to get commands for different apps used in scripting in setupcomplete.cmd THX
I have the scripting for a silent Office 2013 SP1 pro plus install. However with the various commands I used at times Universal Silent Switch Finder 1.5.0.0 along with some simple research into each program for their switches. It works in conjunction with KMS Pico which activates both Windows 8.1 and Office 2013 at the same time.
You need to create a Install.MSP which can facilitate the silent install. Then you call it with the following command: start /wait %windir%\Setup\scripts\Apps\Microsoft\Office2013\setup.exe /adminfile Install.MSP start = start whatever exe /wait = wait until complete The path being used that will end in setup.exe /adminfile = script for office 2013 Install.msp = the silent MSP you made to make it happen
I just use a config.xml, in my batch I have: Code: start /wait %~dp0Office2013ProPlusSP1_32bit\setup.exe /config config.xml My basic config.xml: Code: <!-- Office 2013 Pro Plus SP1 --> <Configuration> <Display Level="Basic" CompletionNotice="No" SuppressModal="No" AcceptEula="Yes" /> <USERNAME Value="." /> <USERINITIALS Value="" /> <COMPANYNAME Value="." /> <PIDKEY Value="your key here, no dashes" /> <Setting Id="AUTO_ACTIVATE" Value="0" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <INSTALLLOCATION Value="" /> <OptionState Id="ACCESSFiles" State="Local" Children="force" /> <OptionState Id="EXCELFiles" State="Local" Children="force" /> <OptionState Id="XDOCSFiles" State="Local" Children="force" /> <OptionState Id="LyncCoreFiles" State="Local" Children="force" /> <OptionState Id="OneNoteFiles" State="Local" Children="force" /> <OptionState Id="OUTLOOKFiles" State="Local" Children="force" /> <OptionState Id="PPTFiles" State="Local" Children="force" /> <OptionState Id="PubPrimary" State="Local" Children="force" /> <OptionState Id="GrooveFiles2" State="Local" Children="force" /> <OptionState Id="VisioPreviewerFiles" State="Local" Children="force" /> <OptionState Id="WORDFiles" State="Local" Children="force" /> <OptionState Id="SHAREDFiles" State="Local" Children="force" /> <OptionState Id="TOOLSFiles" State="Local" Children="force" /> </Configuration> Just tweak Config.xml to your needs...
I need to put that into my copy of Office 2010 for silent installs as I could never get the msp working.
Edit proplus.ww\config.xml as follows. Code: <Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="REBOOT" Value="ReallySuppress"/> </Configuration> Note: If Retail, Configuration Product= "ProPlusr" "PrjPror" "VisPror"
The next challenge is getting Visio to install with office 2013 Pro Plus. Getting the required folders is simple enough as you can get it from the %temp%. However setting up the config.xml to accept Visio is a bit more difficult.
Looks good I'll give it a spin. I'm thinking about updating the OEM Pack to fit with the current way I do the scripting which has expanded of late I keep busy hehe
I'm going to launch the universal OEM pack. This will make it possible for an OEM pack to be able to detect which copy of windows is being loaded / installed. And mean we can mate an OEM pack to a Super AIO like what murphy78 made. This could conceivably be called a Super OEM Pack. We will have Windows Version Detection, Windows Edition Detection, and Windows Architecture detection this will drastically simplify every OEM pack for windows.
I've gathered the required scripting along with the parts needed to the rest of the scripting. The only things left to do will be converting the starter and setupcomplete to powershell. That will make it possible for the detection needed to make such a universal pack. For the purposes of this we are going to go the legit route. The framework aka scripting will be released when I get around to finishing the script for the pack. Also those that are thinking... wait you can't do a oem pack without a setupcomplete.cmd. Well guys you make a setupcomplete.cmd that only calls the setup.ps1 so that the powershell does everything instead of the setupcomplete.cmd.
Ok the ball is rolling. I'm beginning testing on the universal pack. The reward for making one is immense as it can be joined to the Super AIO Images. In order to spur the development I will post the complete script required to make it happen. This means we will begin to hopefully see Windows ISO images with an oem pack that can detect each copy of windows on it. The testing will be expanded to the following later: Windows Server 2008 Windows Server 2008 R2 Windows XP The current support will be the following: Windows Vista Windows 7 Windows 8 Windows 8.1 Windows 10 Server 2012 Server 2012 R2 If I can get this to work we can expand this project to other areas of the forum as well.
Ok so I'm still working on the Windows 7 side but things are looking good. I should be able to move on to Windows 8.1 soon.
Now for an update on progress. Due to the immense nature of the scripting involved I am making it architecture neutral so it does not have that added in yet. However it will be added later. Also because this is a simple OEM Pack thread the Universal OEM Pack will be posted on a separate thread. The other reasoning is that unlike most OEM packs which utilize command line / batch scripting this pack uses command line just to launch power shell. This effectively means there is only about 5 lines of command line (with 1 file completely written in PS) while the rest is Power Shell. In regards with compatibility it will support any Windows Operating System that has power shell on it while making use of the OEM folder which was introduced in Vista. The problem with vista is that by default it does not come with Powershell which is easily fixable. Now for those of you who are not used to powershell... get used to it lol. I will probably have to ask for the character amount to be raised by staff as well. The entire project is modular that means you can add modules to the design. That being said don't be hasty as I am still fine tuning what will be inside of it. Also there will be a good amount of standardization coming out of this as the entire thing needs to be very well organized. I'm still working on the Pack as the following is working: Windows 7 Windows 8 Windows 8.1 Windows 10 (build 9901) Server 2012 Server 2012 R2 The following are a work in progress: Server 2008 Server 2008 R2 The following will need more work which will be done a bit later: Windows Vista The following are untested but probably work and need scripting added for it: Windows Embedded 7 Windows Embedded 8 Windows Embedded 8.1 @ Help from people: Wait until all the scripting is done for Version recognition and Architecture recognition as it is still in progress. Then things will get interesting because this will be the first Universal OEM pack that you will be able to move from Windows 7 to Windows 10 or to Server 2012 R2 without changing anything inside the OEM Folder. In other words it will go on a Super AIO and not even be phased by every OS that is on it. I am envisioning this to be the last OEM pack ever made in terms of structure. This will take time to do however so please be patient. Testing will start when everything has been verified to be ready to go. In addition this pack will comply with forum rules.
That looks to be the case as this will be completey open to changes. I never liked the cmd way because you can't go through the wmi or other stuff that easily. I will say that 95% of the pack is PowerShell. We could go through cmd but it's easier to do it in ps. This project won't fall flat hehe.