officedev / office-it-pro-deployment-scripts Goto Github PK

When attempting to create the Install Wrapper in the Install Toolkit the generator is unable to find the Wix compiler and generates the error:

Wix compiler/linker cannot be found

OS: Windows 10 Pro (Version 1607 Build 14393.321)

dear,

I'm using Office 2016 Standard version. I cannot get the script to run. Please help to verify which Product ID should i use for Office 2016 Standard Version.

When choosing "sign installer" the "valid from" date on the code sign certificate is a future date. I just generated one using the Install Toolkit on 12th of April 2016 but the code sign certificate tells me the certificate is valid from 4th of November 2016.

Could this be a regional date/time issue? In Europe day/month is used, while in US month/day.

Hey people

First, thanks for the great tool you created!
Now i got a problem, i can't launch the installation. If i generate the .xml file, i want to click on "Launch Installation", after it starts downloading and installing, i get this error message:

PLATFORM VERSION INFO
Windows : 10.0.10586.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1078.0 built by: NETFXREL3STAGE
clr.dll : 4.6.1080.0 built by: NETFXREL3STAGE
dfdll.dll : 4.6.1038.0 built by: NETFXREL2
dfshim.dll : 10.0.10586.0 (th2_release.151029-1700)

SOURCES
Deployment url : file:///C:/Users/username/Downloads/OfficeProPlusInstallGenerator.application
Deployment Provider url : http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/OfficeProPlusInstallGenerator/OfficeProPlusInstallGenerator.application
Server : GitHub.com
Application url : http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/OfficeProPlusInstallGenerator/Application%20Files/OfficeProPlusInstallGenerator_2_0_0_36/OfficeProPlusInstallGenerator.exe.manifest
Server : GitHub.com

IDENTITIES
Deployment Identity : OfficeProPlusInstallGenerator.application, Version=2.0.0.36, Culture=neutral, PublicKeyToken=7e4875a70752af6e, processorArchitecture=msil
Application Identity : Microsoft.CIE.Run.exe, Version=2.0.0.36, Culture=neutral, PublicKeyToken=7e4875a70752af6e, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Installable application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\username\Downloads\OfficeProPlusInstallGenerator.application resulted in exception. Following failure messages were detected:
+ File, OfficeInstallGenerator.dll, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [07/09/2016 08:47:28] : Activation of C:\Users\username\Downloads\OfficeProPlusInstallGenerator.application has started.
* [07/09/2016 08:47:28] : Processing of deployment manifest has successfully completed.
* [07/09/2016 08:47:28] : Installation of the application has started.
* [07/09/2016 08:47:28] : Processing of application manifest has successfully completed.
* [07/09/2016 08:47:30] : Found compatible runtime version 4.0.30319.
* [07/09/2016 08:47:30] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [07/09/2016 08:48:25] System.Deployment.Application.InvalidDeploymentException (HashValidation)
- File, OfficeInstallGenerator.dll, has a different computed hash than specified in manifest.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Could anybody help me ?

Thanks in advance!

Best regards,
SBA

Deploying 10-ExampleRemovePreviousAndUpgradeSCCM.ps1 using SCCM 1606 to deploy C2R. I have 'Deferred' element specified within script and on 1st run, it correctly creates configuration.xml with desired settings. For testing or due to reactive issue, if I uninstall Office 365 ProPlus and rerun install, the temp files from previous run reside in the C:\windows\temp directory and on second run incorrectly sets the channel to ''Current".

Perhaps there is a reason why we shouldn't detect and delete presence of existing configuration.xml in temp directory?

Command in script
Generate-ODTConfigurationXml -Languages AllInUseLanguages -TargetFilePath $targetFilePath | Set-ODTAdd -Version $NULL -SourcePath $SourcePath -Channel Deferred | Set-ODTDisplay -Level Full -AcceptEULA $true | Set-ODTProductToAdd -ProductId "O365ProPlusRetail" -ExcludeApps ("Groove", "OneDrive") | Out-Null

configuration.zip

Add-ODTProductToAdd ist not able to add InfoPathRetail

Hi

I've used your install generator to make a silent office2016 executable installer, and it worked like a charm!
However, I'd like to also make one for Office2013, and i can't seem to figure out whether or not this is possible, as the configuration.xml files seems to be identical, no matter what you do.

Any helps appreciated!

The software shortcuts created by users are not deleted by default by offscrubc2r.vbs. I have to execute a script to remove shortcuts from desktop, taskbar and start menu. example

Function UnPinFromTaskBar(strFFilePath)
strFolder = objFSO.GetParentFolderName(strFFilePath)
strFile = objFSO.GetFileName(strFFilePath)

If objFSO.FileExists(strFFilePath) Then
    Set objFolder = objShell.Namespace(strFolder)
    Set objFolderItem = objFolder.ParseName(strFile)
    Set colVerbs = objFolderItem.Verbs

' MsgBox objverb
For Each objVerb in colVerbs
If Replace(objVerb.name, "&", "") = "Détacher de la barre des tâches" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "Désépingler de la barre des tâches" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "Unpin from Taskbar" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "von taskleiste lösen" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "desanclar de la barra de tareas" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "odepnout z hlavního panelu" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "frigør fra proceslinje" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "van de taakbalk losmaken" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "poista kiinnitys tehtäväpalkista" Then objVerb.DoIt
If Replace(objVerb.name, "&", "") = "rimuovi dalla barra delle applicazioni" Then objVerb.DoIt
Next
End If
End Function

The .msi installs the Microsoft Office 365 ProPlus Installer, which lives in "%ProgramFiles(x86)%\Microsoft Office 365 ProPlus Installer". The files in this folder are an executable and an xml file.
One of the very first tasks generated by this executable is to stage some files under "%windir%\Temp", after which it begins the installation process.
If this installation is run more than once, the installer will fail. Personally, I encountered this issue when I tried to install an x86 version, but the Office 365 installer complained about an x64 plugin that was already installed. So I moved an x64 installer over to this machine, and the ProPlus Installer would no longer work with either version. I've also tested using this installer on a fresh Windows 7 VM, installing Office 365 ProPlus successfully, uninstalling the product, and then attempting to use the ProPlus Installer a second time. The same issue was encountered.

The error that is generated by the "Office 365 ProPlus Installer", which does not appear to be logged anywhere, is:
`Extracting Install Files...ERROR: System.IO.IOException: Cannot create a file when that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
at InstallOffice.MoveFile(String rootDirectory, String md5Hash, String fileName)
at InstallOffice.GetEmbeddedItems(String targetDirectory)
at InstallOffice.Initialize()
at InstallOffice.RunProgram()
at InstallOffice.Main(String[] args)`
This error message shows up in a command prompt briefly, but can be seen if you open a command prompt first, and run the executable at "%ProgramFiles(x86)%\Microsoft Office 365 ProPlus Installer\InstallOfficeProPlus.exe".

Uninstalling the Microsoft Office 365 ProPlus Installer and reinstalling it does not clear out the files in the "%windir%\Temp" directory. Running the "InstallOfficeProPlus.exe" executable with the "/uninstall" parameter also generates the above error, and also does not remove any files in the "%windir%\Temp" directory.

After investigation with ProcMon, it turns out the files it's trying to overwrite are the staging files in the "%windir%\Temp" directory.

The Microsoft Office 365 ProPlus installer should be able to either use these files, or it should be able to overwrite them instead of only checking if the target exists, and then silently failing.

The Microsoft Office 365 ProPlus Installer should also generate a log for errors such as these, as opening the .msi will very briefly display this error inside of a command prompt, and then the command prompt will close upon process termination due to the error. A "/log=[PATH]" parameter would also help. The only logs produced from this process are the logs generated by the actual Office 365 ProPlus installation.

Receive the below error output when trying to run the install from EXE installer after extracting files. I've been able to re-produce the error on 5 Windows 7 systems, but worked on a WIndows 10 system.

C:\Windows\System32>"C:\Program Files (x86)\BigFix Enterprise\BES Client__BESDa
ta\actionsite__Download\OfficeProPlus64.exe"
Extracting Install Files...ERROR: System.IO.IOException: Cannot create a file wh
en that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalMove(String sourceFileName, String destFileName, Bo
olean checkHost)
at InstallOffice.MoveFile(String rootDirectory, String md5Hash, String fileNa
me)
at InstallOffice.GetEmbeddedItems(String targetDirectory)
at InstallOffice.Initialize()
at InstallOffice.RunProgram()
at InstallOffice.Main(String[] args)

Having a hard time finding the intended deployment method for the "10-RemovePreviousandUpgrade.ps1" deployment script. It does work when run manually. Are these intended to be startup scripts? Thanks.

When creating MSI and EXE package, based on pre-defined XML file, the generated file are reported as incompatible with 64-Bits Windows 10 with the general message, as described:

This app can't run on your PC
To find a version to your PC, check with the software published

Regarding 32 bits of the generated files, there's no problem with them.

Generate-ODTConfigurationXml on System with O365HomePremRetail installed adds O365ProPlusRetail in the config.xml
Only one O365 Office is allowed

The following script is used to assign 'tags' for Office Telemetry: https://gallery.technet.microsoft.com/Add-Tags-Labels-for-Office-09c81574

It is officially advertised on the respective TechNet article for Office Telemetry here: https://technet.microsoft.com/en-us/library/ff394407(v=office.16).aspx

It would be nice if it could be ported to Powershell and updated to support Office 2016 while adding it to this GitHub project. Thank you!

When trying to embed the downloaded source files (from the download section)
I am constantly receiving invalid source files, they are over 1 gb in size and the path is correct?
can you advise please

can someone advise where I am going wrong with this please?
Thanks

Not sure what is going on, but the script is failing and timing out when it get to downloading the v32.cab to find the version information.
Error: : Exception calling "GetResponse" with "0" argument(s): "The operation has timed out

I put together my own workaround by replacing the 'downloadfile' function with the built in 'Start-BitsTransfer' command in PowerShell. Was a perfect drop in replacement, just had to change the function and parameter names but used the same variables. Not sure if it works with the error handling or not but, got me downloading again.

For example, replace:
DownloadFile -url $XMLDownloadURL -targetFile $XMLFilePath
With
Start-BitsTransfer -Source $XMLDownloadURL -Destination $XMLFilePath

Then, delete the entire Function downloadfile block:
function DownloadFile($url, $targetFile) {...}

Why not make 'Start-BitsTransfer' the default for the file download? Yes you have to have BITS enabled, but I don't know that anyone disables it.

Using the Install Toolkit to generate a Windows Installer file and deploying that file/app through Windows 10 MDM (via Intune in this case) installs the Windows Installer package OK; however, the custom action for SETUP.EXE fails and Office 365 does not install.

From the log file, it looks like InstallOfficeProPlus.exe is launched but terminated very quickly thereafter. The same installer works when manually running it on the same machine.

Extract from the Windows Installer log below.

Action start 10:22:55: InstallFinalize.
SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI6094.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action Microsoft.OfficeProPlus.MSIGen!CustomActions.InstallOffice
SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI6160.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action WixSharp!WixSharp.ManagedProjectActions.WixSharp_AfterInstall_Action
Cannot access session details from a non-immediate custom action
Action ended 10:22:56: InstallFinalize. Return value 1.
Action ended 10:22:56: INSTALL. Return value 1.

I have been trying to utilize your very helpful Office365 Install Toolkit msi generator, it was to be a great help in our initial testing of Windows 10/Office2016.

Over many frustrating hours of downloading, modifying and creating MSI's that would all fail in the same manor, I started to have a look at the configuration file being embedded into the MSI with your viewing tab. When you look at the xml config from your tab view on the final page of the generator, it looks perfect and as should be.

However, when you copy to clipboard and then paste, it has an error in the coding for the update section.

When I compared this to other information available, it should be this: Office_2016" /> and not Office_2016">

I would very much like to utilize your msi builder, but in the meantime I have made my network deployment using ODT methods with properly formatted XML and will hope to have your msi builder available again someday.

Line 45 of the Copy-OfficeGPOSettings.ps1 script has what looks to be temporary placeholder help text: Additional explanation. Long and indepth examples should also go here.

imo you should replace that with a link to https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts

I would like to build setup only for Visio / Project, without Office suite. Unfortunately I cannot deselect Office Suite nor modify the XML file. Even if I load the configruation.xml without Office it will still be added during configuration in the wizard.

The separate Get-OfficeVersion script detects the installation of 2016 msi (not click to run).

Running the Remove-PreviousOfficeInstalls script doesn't appear to detect 2016 msi installation for removal and just seems to do nothing.

`PS C:\Deferred> . .\Get-OfficeVersion.ps1
PS C:\Deferred> Get-OfficeVersion

ComputerName : COMPUTER-NAME
InstallPath : C:\Program Files (x86)\Microsoft Office
ClientCulture :
Bitness : 32-Bit
DisplayName : Microsoft Office Professional Plus 2016
ClickToRunUpdateUrl :
Version : 16.0.4266.1001
ClickToRunUpdatesEnabled :
ClickToRun : False

PS C:\Deferred> .\Remove-PreviousOfficeInstalls.ps1
Detecting Office installs...
PS C:\Deferred>`

I appreciate your quick efforts in previous issues that I have brought up with these scripts. I look forward to you being able to get this one resolved as well.

Thanks!

There are some illegal characters in this script Lines 331, 1161, 1456,

Also error on Line 331:
$defaultDisplayPropertySet = New-Object System.Management.Automation.PSPropertySet(�DefaultDisplayPropertySet�,[string[]]$defaultDisplaySet

And issue on line 1454:
If (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(`
[Security.Principal.WindowsBuiltInRole] Administrator))

The script assumes that the Configuration Manager console and PS module are located on C drive. Please update to check if PS module has already been loaded or create a variable to define PSM location.

My configuration out of the toolkit:

<Configuration> <Add OfficeClientEdition="32" Channel="Current"> <Product ID="O365ProPlusRetail"> <Language ID="de-de" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="OneNote" /> <ExcludeApp ID="Outlook" /> <ExcludeApp ID="PowerPoint" /> <ExcludeApp ID="Project" /> <ExcludeApp ID="Publisher" /> <ExcludeApp ID="Visio" /> <ExcludeApp ID="OneDrive" /> </Product> </Add> <Updates Enabled="FALSE" Channel="Current" /> <Display Level="Full" AcceptEULA="True" /> <Property Name="PinIconsToTaskbar" Value="FALSE" /> <Property Name="AUTOACTIVATE" Value="1" /> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Property Name="SharedComputerLicensing" Value="0" /> <Logging Level="Standard" Path="%temp%" /> </Configuration>

If I create the exe wrapper, this installed the 64bit version of office -.-

I´m working on Win Server 2012 R2 Standard 64bit.

See this thread on TechNet: Thread

Basically the issue is this:

After running the vb script for 2010 the fonts are removed. (I am focused on Arial Narrow but there are many)

Manually uninstalling Office 2010 via Programs and Features does not remove the fonts, they stay in place.

After 2016 CTR was installed via SCCM with the github deployment scripts, the fonts were not installed.

After 2016 MSI was installed, the Arial Narrow font was installed.

After 2016 CTR was installed manually with the same exact source as the SCCM application, the fonts were installed.

The problem must be between the removal of 2010 via the vb script and the installation of 2016 CTR via the github powershell scripts or something to do with the fact that it is SCCM deploying the software.

In the Exclude section, one cannot select OneDrive, only Groove (OneDrive for Business), which removes OneDrive for business but leaves the "standard" OneDrive package in place.

Generate -> Configuration is also non-editable. Leaving no work around.

Right now the script does not provide any option to download the latest DC 'extended' build, e.g. Version 1509 (Build 6001.1082), without explicitly referencing the exact version number you want.
It would be nice if there was some creative way to automatically determine the latest 'extended' build number built into the script. That way you wouldn't have to search for the build number manually on TechNet, which will only be published there on the day the build is released. Thank you!

As title..

the pinappstotaskbar is missing....

The Get-OfficeVersion script doesn't detect Office 2013 Click to Run install.

I have a test VM with a clean install of both Office 2010 and Office 2013 Click to Run.

When I run Get-OfficeVersion, it only detects the 2010 installation. This seems to break the removal of 2013 CTR because it doesn't detect it as being installed. I am trying to use the Remove-PreviousOfficeInstalls script to remove both 2010 and 2013 CTR.

Is this expected behavior when using the Remove-PreviousOfficeInstalls script or should it be detecting the 2013 CTR install and removing it as well? Perhaps I need to call/run the Remove-OfficeClickToRun script in addition to the other script in order to remove both installations of Office in this scenario?

The link to Powershell for Office in README.MD is currently broken. It points to https://poweshell.office.com/. After fixing the typo, the url must also be changed, as attempting to browse https://powershell.office.com/ results in an ssl warning from your favourite browser because the cert is only valid for *.azurewebsites.net.

The link should point to http://powershell.office.com/.

when i run this to manage local installation - i get the following error get-officeversion parsing C:\program files(x86)\Notepad++ odtconfigurationxml.ps1: 150 charge 26

The Install Toolkit doesn't provide a way to add additional Product IDs and importing an existing configuration.xml with more than one Product ID (e.g. Office 365 Business + Skype for Business) strips out the additional product IDs.

See the example below where Skype is stripped out by the Install Toolkit:

<Configuration> <Add OfficeClientEdition="32" Channel="Deferred"> <Product ID="O365BusinessRetail"> <Language ID="en-us"/> <ExcludeApp ID="OneDrive"/> <ExcludeApp ID="Groove"/> <ExcludeApp ID="Access"/> </Product> <Product ID="SkypeforBusinessRetail"> <Language ID="en-us" /> </Product> </Add> <Display Level="None" AcceptEULA="TRUE"/> <Logging Level="Standard" Path="C:\Windows\Temp"/> <Updates Enabled="TRUE" Channel="Deferred"/> </Configuration>

I've read the readme and checked all the examples.

Running as admin results in exactly no results:

PS C:\Scripts> . .\Get-OfficeVersion.ps1

PS C:\Scripts>

Running against a valid computer name results in nothing:

PS C:\Scripts> . .\Get-OfficeVersion.ps1 -ComputerName molsen-vm

PS C:\Scripts>

I'd love to know what I'm doing wrong.

Downloaded from git today.

Running the Remove-PreviousOfficeInstalls doesn't appear to work with Office 2013.

Get-OfficeVersion seems to return the correct installed version of 2013 but doesn't seem to call the VBS script for removal. The script doesn't do anything as far as removing the installed version of Office 2013.

The script works fine with Office 2010.

Feature request: The usefullness of the script could be expanded by providing two modes of operation: One captures the current state of Office 365 ProPöus (implemented), the other one captures the state of an older veriosn of Office (e.g. Office 2010 MSI) and creates a coressponding configuration.xml.

Example: Office 2010 Professional Plus as well as Project 2010 (both x86) are installed on a machine, both with two language packs, but the Access 2010 feature of Office 2010 is not installed. When you run GenerateODT with a new "captureoldversion=14" switch it will generate a configuration.xml, which contains two Add-sections (one for O365ProPlusRetail, one for Project365Retail, both x86), has Exclude App ID=Access set as well as the two language packs.

Most customer projects want to start with a like-for-like apprioach, this addition to the script would help.

Same issue as here:
#158

The user just appears to never respond..

I am getting this failure as well... Mine was:
You cannot call a method on a null-valued expression.
At C:\Users\Desktop\Office-ProPlus-Deployment\Deploy-OfficeClickToRun
\Generate-ODTConfigurationXML.ps1:1311 char:54

$OfficeVersion = $OfficeVersion.Version.Split <<<< (".")[0]
CategoryInfo : InvalidOperation: (Split:String) [], ParentConta insErrorRecordException
FullyQualifiedErrorId : InvokeMethodOnNull

I went as far to see the data in $OfficeVersion and it returned this (mind you all compact)...:
@{ComputerName=WIN7X64;
InstallPath=C:\Program Files (x86)\Microsoft Office;
ClientCulture=;
Bitness=32-Bit;
DisplayName=Microsoft Office Professional Plus 2007;
ClickToRunUpdateUrl=;
Version=12.0.6612.1000;
ClickToRunUpdatesEnabled=;
ClickToRun=False}

@{ComputerName=WIN7X64;
InstallPath=C:\Program Files (x86)\Microsoft Office;
ClientCulture=;
Bitness=32-Bit;
DisplayName=Microsoft Office Visio Standard 2007;
ClickToRunUpdateUrl=;
Version=12.0.6425.1000;
ClickToRunUpdatesEnabled=;
ClickToRun=False}

@{ComputerName=WIN7X64;
InstallPath=C:\Program Files (x86)\Microsoft Office;
ClientCulture=;
Bitness=32-Bit;
DisplayName=Microsoft Office Project Standard 2010;
ClickToRunUpdateUrl=;
Version=14.0.6029.1000;
ClickToRunUpdatesEnabled=;
ClickToRun=False}

So looks like get-officeversion is returning too much information/all office apps installed... Just prelim..

I synced the scripts to the latest versions and performed the following test:
Installed Office 2010 excluding OneNote and Publisher 2010. I expected the script to replace the existing configuration with Office 2016 configuration. This did not happen and I ended with a full Office 2016 configuration.

When you have application like notepad++ installed, the script fails becuase of the logical expression (-match) used in this line.

It might be a good idea to limit the $PathList to Office only... I got around the error by adding a line $installReg = $installReg.Replace('+', ')')
But this only solves the issue for folders with a + in the name... There might be other foldernames that could cause the exact same issue...

In "https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html" you can choose language for Kazakh that add value: Language ID="kk-kh" ,but this is incorrect. With this configuration installation will fail.
Correct: Language ID="kk-kz"

More information:
https://technet.microsoft.com/en-us/library/cc179219.aspx

Thanks! :)

For the primary update location the script currently only checks the registry keys which are set by defining them in the installation XML file:

• Office 2016: HKLM\Software\Microsoft\Office\ClickToRun\Configuration!UpdateUrl
• Office 2013: HKLM\Software\Microsoft\Office\15.0\ClickToRun\Configuration!UpdateUrl

Customers also have the option to define the update location via GPO though, which are written to a different location in the registry:

• Office 2016: HKLM\Software\Policies\Microsoft\Office\16.0\Common\OfficeUpdate!UpdatePath
• Office 2013: HKLM\Software\Policies\Microsoft\Office\15.0\Common\OfficeUpdate!UpdatePath

The Office update engine takes the both paths into account, in fact prioritizing the path set by GPO over the path set by the XML (GPO path > XML path). The script however only checks the XML path at the moment. I'd suggest adding checks for the GPO paths with the same kind of prioritizing logic (GPO > XML). Thanks!

Hi,
I've received similar feedback from two customers regarding the script Update-Office365Anywhere around how errors are handled/returned:

• Is it possible to add actual return codes to the script if it fails? At the moment it always returns 0.
• Can we add better explanations why a failure occurs? For example, when you call with the script with these parameters -EnableUpdateAnywhere $false -UpdateToVersion 16.0.6741.2071 and this particular version is not available in the primary update source, it should output/log that it "didn't find the version in the update source"
  Thanks!

This isn't so much an issue more so a question regarding the Update-Office365Anywhere script. It was my understanding that the script had the ability to determine what channel the client was running then build the correct channel share path. Working my way through this script in testing, it finds a channel folder but not the correct channel that is installed.

Edit: After additional research, I see that Change-UpdatePathToChannel calls Detect-Channel and returns the value found. I know on this test box that it has the June 6th Current Channel build installed. However, Detect-Channel is returning Deferred as the channel found.

Edit: The CDNBaseUrl is set to the address of the Deferred Channel, this install started as Deferred channel then updated to Current channel using c2rclient.exe. I would assume that it would update the CDNBaseUrl though. Looking at the StreamPackageUrl values these show the correct address that would match for Current Channel.

When trying to generate an installation with embedded installation files I receive a "Object reference not set to an instance of an object" error. Generating installs without embedded files works fine.

I’m getting an error on a test machine that has more than just a single version of Office. Office 2010 is installed along with Project 2010 or Visio 2010 and when the script is executed I get the following error:.
You cannot call a method on a null-valued expression.
At C:\temp\Generate-ODTConfigurationXML.ps1:1305 char:54

•     $OfficeVersion = $OfficeVersion.Version.Split <<<< (".")[0]
  

  • CategoryInfo : InvalidOperation: (Split:String) [], ParentContainsErrorRecordException
  • FullyQualifiedErrorId : InvokeMethodOnNull

If I uninstall either Project or Visio it works just fine.

Is it possible to include this option in the Toolkit? I see it throws it to %temp% but it would be awesome to have the option to dump this to a network drive. Would help in large deployment

XML reference of Office Deployment Tool for Click-to-Run use for Updates and Add elements of XML configuration file value "Validation" for First Release for Current Branch for Business. But XML editor use value "FirstReleaseBusiness". Both of them work actually, but this should be clarified if someone want trust to consistent update Branches. Because what to set to GPO? This is text field, not drop down list.

Hi Russell.
First off, thanks for such an awesome script. I ran it in my test lab and all of the ADMX settings came across. However, I did have some GP push items in there that did not get copied over. I did note that there was a couple of system.string errors that occurred that may be related to this.

Method invocation failed because [System.String] does not contain a method named 'RemoveAll'
At C:\temp\CopyOfficeGPO2013to2016\Copy-OfficeGPOSettings.ps1:866 char:17

Method invocation failed because [System.String] does not contain a method named 'RemoveAll'.
At C:\temp\CopyOfficeGPO2013to2016\Copy-OfficeGPOSettings.ps1:867 char:17

Cheers.

object reference not set to an instance of an object when trying to download 64bit Office365ProPlus - current branch
32 bit downloads fine
I seem to be having a lot of trouble deploying 64bit in general. Why 64bit? We currently use 64bit 2010 and would like to keep it the same.
let me know if anyone knows anything about this!