Dean

Dean

Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Dean
    Participant
    Post count: 1

    hello Aldin,

    I’m running into some detection issues with your PADT when install Office 365 2016. I’ve essentially copied your .ps1 and deployed it to a few test machines in my environment. Most of my machines have Office 2013 (VL) with Skype 2015 installed. The office scrub works very well and rips out all Office that is initially on the machine.

    The part that gets stuck is shown in the logs files for PADT:

    [Pre-Installation] :: Bypassing Installation Prompt [Mode: NonInteractive]… This will install Microsoft Office 365 ProPlus 2016 for you. Please note that the installation can take up to 45 minutes.
    All previous Office versions will be uninstalled first.
    Save all your work and click OK to continue. Show-InstallationPrompt 4/17/2017 2:15:08 PM 1276 (0x04FC)

    [Pre-Installation] :: Evaluate disk space requirements. Show-InstallationWelcome 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Retrieve free disk space for drive [C:]. Get-FreeDiskSpace 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Free disk space for drive [C:]: [22014 MB]. Get-FreeDiskSpace 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Successfully passed minimum disk space requirement check. Show-InstallationWelcome 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Check for running application(s) [ose,osppsvc,sppsvc,msoia,excel,groove,onenote,infopath,onenote,outlook,mspub,powerpnt,winword,winproj,visio,iexplore]… Get-RunningProcesses 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Application(s) are not running. Get-RunningProcesses 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Finished checking running application(s). Get-RunningProcesses 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Microsoft Office 2010 was detected. Will be uninstalled. Deploy Application 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: [cscript.exe] successfully resolved to fully qualified path [C:\WINDOWS\system32\cscript.exe]. Execute-Process 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Working Directory is [C:\WINDOWS\system32]. Execute-Process 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Executing [C:\WINDOWS\system32\cscript.exe “C:\WINDOWS\ccmcache\4z\SupportFiles\OffScrub10.vbs” ProPlus,Pro,Standard,SINGLEIMAGE /S /Q /NoCancel /Bypass 1]… Execute-Process 4/17/2017 2:15:13 PM 1276 (0x04FC)

    [Pre-Installation] :: Execution completed successfully with exit code [0]. Execute-Process 4/17/2017 2:17:42 PM 1276 (0x04FC)

    [Pre-Installation] :: Microsoft Office 2013 was detected. Will be uninstalled. Deploy Application 4/17/2017 2:17:42 PM 1276 (0x04FC)

    [Pre-Installation] :: [cscript.exe] successfully resolved to fully qualified path [C:\WINDOWS\system32\cscript.exe]. Execute-Process 4/17/2017 2:17:42 PM 1276 (0x04FC)

    [Pre-Installation] :: Working Directory is [C:\WINDOWS\system32]. Execute-Process 4/17/2017 2:17:42 PM 1276 (0x04FC)

    [Pre-Installation] :: Executing [C:\WINDOWS\system32\cscript.exe “C:\WINDOWS\ccmcache\4z\SupportFiles\OffScrub_O15msi.vbs” ProPlus,Pro,Standard,SINGLEIMAGE /S /Q /NoCancel /Bypass 1]… Execute-Process 4/17/2017 2:17:42 PM 1276 (0x04FC)

    [Pre-Installation] :: Execution completed successfully with exit code [0]. Execute-Process 4/17/2017 2:21:39 PM 1276 (0x04FC)

    [Installation] :: [C:\WINDOWS\ccmcache\4z\Files\Setup.exe] is a valid fully qualified path, continue. Execute-Process 4/17/2017 2:21:39 PM 1276 (0x04FC)

    [Installation] :: Working Directory is [C:\WINDOWS\ccmcache\4z\Files]. Execute-Process 4/17/2017 2:21:39 PM 1276 (0x04FC)

    [Installation] :: Executing [C:\WINDOWS\ccmcache\4z\Files\Setup.exe /configure ProPlus-InstallConfig.xml]… Execute-Process 4/17/2017 2:21:39 PM 1276 (0x04FC)

    It gets stuck at this spot where its trying to install Office 365 2016 using the setup.exe with the /configure .xml file applied.

    On the computer that’s getting Office 365 installed, the basic UI shows up and it eventually shows that it completes the install. However the log file above still reports it as Executing. This makes the SCCM software center hang on “Installing” and the end user is forced to restart their machine in order to move on to installing other Office 365 apps like Visio Pro or Project Pro.

    Have you ran into this issue before? Is there some type of powershell timer that I can implement into the script to essentially “jolt” it to move on?

    Thanks
    Dean

Viewing 1 post (of 1 total)