Office 365 Installing Office 365 to your RDP Servers

Warning: Uninstall all previous versions of office, that includes 2013 and 365 demos before proceeding
Users must be admins on their systems temporarily for the GPO to work.

Create a shared folder on your central server for example \\SRV-UTIL01\OfficeDeploy\

Download the Office Deployment Tool and extract to \\SRV-UTIL01\OfficeDeploy\

http://www.microsoft.com/en-us/download/details.aspx?id=36778

Create 2 XML files with the options

The first is Download.XML which sets your path, 32 or 64 bit, and is used for the download process:

<Configuration>
<Add SourcePath="\\SRV-UTIL01\OfficeDeploy\" OfficeClientEdition="64" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>

The second is RDPConfiguration.xml used to deploy Office 365 ProPlus package
Note: The example that is included with the Office Deployment Tool might as well be blank since it is rem’d out with the <!— and --!> Here is what it should look like when ready to use:

<Configuration>
<Add SourcePath="\\SRV-FS01\OfficeDeploy\" OfficeClientEdition="64" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="\\SRV-FS01\OfficeDeploy\" />
<Display Level="None" AcceptEULA="True" />
<Property Name="SharedComputerLicensing" Value="1" />
<Logging Path="%temp%" />
</Configuration>

Now to create your local copy of the media run the following command:
Setup.exe /Download Download.xml

Note: when you run the above command above it will create \\SRV-UTIL01\OfficeDeploy\Office\Data\Version\ and under that folder will have the large stream.x32 or .x64 files. This runs in a plain cmd line window with no output on status. So be patient as it will be downloading approx. 2GB of data or more.

While that is downloading you can modify or create your deployment script and GPO

For example RDPOfficePush.bat as shown below:

RDPOfficePush.bat

_______________________________________________________________

echo off

Rem Created by Kevin Oppihle http://Koppihle3.blogspot.com
If EXIST "C:\Program Files\Microsoft Office 15\ClientX64\officeclicktorun.exe" goto 365Complete else goto :365Needed
:365Needed
Echo Installing Office 365 >c:\365.txt
\\SRV-Util01\OfficeDeploy\Setup.exe /configure \\SRV-Util01\officedeploy\RDPconfiguration.xml >>c:\365.txt
:365Complete
Echo Office 365 Installed >c:\365.txt

Exit

________________________________________________________________

The batch file above first confirms if office is already installed. If it is then if you open the txt file c:\365.txt it will say “Office 365 installed”. However if office is not installed it will use the deployment path outlined in the batch file to run the installation. While the installer is running the 365.txt file will say “installing Office 365” when the installation is completed the 365.txt file will change to “Office 365 Installed”. It is set to run minimized so to verify when it is completed reference the 365.txt file. The installation time depends on the network and PC speed but expect an average of 10 minutes. The office icons appear before the installer is completed. If you open an office application before the completion of the installer it will slow the process as it may download from online.

Note: this will install once and activate for each Office 365 user as they log on. So they must have an active Office 365 account. The installation may take a few minutes so please be patient.

Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more