Did my O365 Pro Plus install on a RDS Server die... orrr????

[thecomputerguy]

I'm trying to install proplus on an RDS server and I followed the instructions on the TechNet support page to install it with the configuration.xml file as shown below ...

<Configuration>

<Add OfficeClientEdition="32" Branch="Current">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="True" />
<Property Name="SharedComputerLicensing" Value="1" />

</Configuration>

Per these instructions:

http://blog.powerbiz.net.au/office-...inal-server-using-shared-computer-activation/

Ran the setup.exe /download configuration.xml

At an elevated command prompt, it asked me for permission, then I saw files of about 250MB dump into the folder I ran the exe from. Now the command prompt is just sitting there ... the task manager shows Microsoft Office (32 bit) growing in memory size then starting over and growing again.

The connection is like 75/15 so it isn't slow by any means but I've been waiting for almost 2 hours and still no office ... no error ... should I start it again?

 

[thecomputerguy]

The file sizes in the data folder are also not growing...

 

[YeOldeStonecat]

Follow my thread here..
Your config file above isn't complete...you need a path for it.
https://www.technibble.com/forums/threads/office-365-for-multipoint-server-2011.65463/#post-510498

 

[thecomputerguy]

Follow my thread here..
Your config file above isn't complete...you need a path for it.
https://www.technibble.com/forums/threads/office-365-for-multipoint-server-2011.65463/#post-510498

Hey thanks for the info @YeOldeStonecat

I just wanted to post here in case anyone saw it in the future ... I was able to get the O365 Pro Plus files finally downloaded. I didn't actually change anything except download it from another computer using the same configuration file as I posted above.

You don't actually need a path for the files to download. Without a path the files will download to whatever directory your run your setup.exe /download configuration.xml and create their own paths.

Not saying what you posted is wrong, but it isn't required.

 

[YeOldeStonecat]

I have them expand to that network share...and it stays there for all future deployments to workstations...or for pushing out via GPO installs.