New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Office click to run issue after BIS-F seal #56

Closed
matthias-schlimm opened this Issue Aug 28, 2018 · 60 comments

Comments

@matthias-schlimm
Copy link
Collaborator

matthias-schlimm commented Aug 28, 2018

Starting to see an issue in recent Office click-to-run installations when sealing with BIS-F. After publishing the images, Office apps won't launch and event viewer shows "application was unable to start correctly (0xc0000142). Click OK to close the application".
BIS-F.zip

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 28, 2018

can you run a additional test with BIS-F but disable  Citrix optimizer inside the BIS-F Policy, i will check if the issue comes from BIS-F or Citrix Optimizer

@brettkmolitor

This comment has been minimized.

Copy link

brettkmolitor commented Aug 28, 2018

bis-fnooptimizer.zip

Okay - test was done without Citrix Optimizer and issue remained. I attached logs here.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 28, 2018

Inside of your BIS-F installation, please replace 96_PrepBISF_Rearm.ps1
and 10_PersBISF_OfficeKMS.ps1 with, take a backup of the old files before replace
https://github.com/EUCweb/BIS-F/blob/6.2.0_Bugs_Bunny/Framework/SubCall/Preparation/96_PrepBISF_Rearm.ps1

https://github.com/EUCweb/BIS-F/blob/6.2.0_Bugs_Bunny/Framework/SubCall/Personalization/10_PersBISF_OfficeKMS.ps1

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 28, 2018

out of the replacement of the 2 files above, please check if the Windows Update Service is running on the PVS Target Device, if not start the service and test if Office can be executed without any issue.

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 28, 2018

I have checked windows update service and it is running. Office works just fine after the online repair. I replaced the two files, and ran the script again. Office broke again. I included the most recent log files.

Pers_BIS_2016PVSGOLD_GEN_20180828-150813.zip

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 28, 2018

ok, currently not a Idea where it come from. Do you deploy office, as describes here https://msandbu.wordpress.com/2016/02/04/office365-on-terminal-server-done-right/ ?

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 28, 2018

I will dig into that. We call a bat file that reads an xml. here is the contents of the xml. and it also runs a reg setting i will paste below the xml contents.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Internet]
"OnlineStorage"=dword:00000003

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General]
"sharedtemplates"=hex(2):48,00,3a,00,5c,00,46,00,6f,00,72,00,6d,00,73,00,2d,00,
53,00,74,00,64,00,73,00,5c,00,54,00,65,00,6d,00,70,00,6c,00,61,00,74,00,65,
00,73,00,5c,00,57,00,6f,00,72,00,64,00,00,00

[HKEY_CURRENT_USER\Software\IM Providers]
"DefaultIMApp"="Lync"

Madison: 608-298-xxxx (5400 – 5439)

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 28, 2018

looks like contents of xml where yanked. here is the file.

SRF-RDS.zip

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

looks good so far

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

Please check the following on the PVS Server:

  1. Select the vDisk in the Console, then right-click and select File Properties. The vDisk File Properties dialog appears.
  2. Click the Microsoft Volume Licensing tab and send me the selected Licencing Mode
@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

KMS is the licensing option. I am checking out the link you sent. And latest updates should be applied.
But to mention again, Office works till i run BIS-f, then it breaks. I can then run an office online repair and it works again. Then can run the script to break it again, and continue that cycle as long as I want.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

I can, and then try to run the script again?

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

and to mention after i run the script, the shortcuts to the offices apps are removed.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 29, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

where do i remove the office scripts? thx. i found the cleanup starmenu, so that answers why the disappear.

@EUCweb

This comment has been minimized.

Copy link
Owner

EUCweb commented Aug 29, 2018

please remove:

C:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\Preparation\96_PrepBISF_Rearm.ps1

C:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\Personalization\10_PersBISF_OfficeKMS.ps1

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

ok, i kind of did this a little different and only had it run the 97_PrepBISF_PRE_BaseImage script, and it breaks office. so i will try what you said and see what that does.

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 29, 2018

I repaired office and confirmed it work. Ran the script without those 2 being processed. It broke again.

@EUCweb

This comment has been minimized.

Copy link
Owner

EUCweb commented Aug 30, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 30, 2018

immediately.

@EUCweb

This comment has been minimized.

Copy link
Owner

EUCweb commented Aug 30, 2018

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 30, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Aug 30, 2018

image

i disabled .net, didnt work. which Ghost device should i disable, all 3?

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Aug 31, 2018

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 20, 2018

creating Fix, take a Copy and test (line 813 function Create-AllusersStartmenuPrograms)https://github.com/EUCweb/BIS-F/blob/develop/Framework/SubCall/Preparation/97_PrepBISF_PRE_BaseImage.ps1

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

I enabled the start menu policy. I copied the contents of the script into 97_PrepBISF_PRE_BaseImage.ps1 and executed the initial script. It still broke office.

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

Office apps will not start.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

i have never tried to create the folder manually. not sure which folder i need to created.

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

image

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

as @MathiasSVA descibribes above

--snip--I think I can contribute the solution to this, because I have sort of run into this too. In my case it wasn't directly BIS-F itself, but the same approach, just executed through Ivanti EM instead of BIS-F.
The problem lies in the deletion of the AllUsersStartmenu. As the office clicktorun installer utilizes parts of App-V/App-X technology what they basically do is to use their virtualization technology from App-V to overlay some folders onto physical ones.
If you remove the program C:\ProgramData\Microsoft\Windows\Start Menu\Programs every office clicktorun component will fail to start with the outlined error.
Furthermore you will se an error entry in the eventlog which says:
Process XXXX failed to start due to Virtual Filesystem subsystem failure. Package ID {9ac08e99-230b-47e8-9721-4577b7f124ea}. Version ID {1a8308c7-90d1-4200-b16e-646f163a08e8}. Error: 0x8F10252A-0x2
Where the very last part of the error "0x2" is in App-V Error id the information: file not found.
So long story short: If you delete the allusers startmenu you have to at least to recreate the folder "Programs" inside C:\ProgramData\Microsoft\Windows\Start Menu to make an office c2r installation working.
Hope this clarifies a bit how to work around the issue. Maybe BIS-F could also extend the logic to recreate the "Programs" folder again, after deletion of the allusers startmenu…
--snap--

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

sorry, i went back and read that also. i previously posted a screenshot of that folder. there is a programs folder there.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

can you check the NTFS rights if the Programs Folder has the same rights. Otherwise replace the NTFS manually and check of office works

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

i checked permissions against a working server and they appear to be the same.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

and if you disbale the "Remove AllusersStartmenu" in ADMX, it should work, i must check it in my lab, but time only for this on weekend

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

i disabled that option in ADMX and it works as expected.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 22, 2018

can you get a copy of the content from the Programs folder and if you enable the policy and bis-f is run, please copy the content back to see if office works.

If it works, please remove folder step-by-step to see, which folder of it affect the office installation

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 22, 2018

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 23, 2018

it seems to be working now. i copied contents of that script file to older ps1 file. made sure start menu and citrix optimization were enabled in GP. ran gpupdate /force and rebooted. then ran the initial launch script for BIS as an administrator and office worked fine. did it on my 2 other images and everything worked fine also. so i think all is well now.

@matthias-schlimm

This comment has been minimized.

Copy link
Collaborator Author

matthias-schlimm commented Oct 23, 2018

ok, thx for your reply. so this issue can be closed now ?

@trhymers

This comment has been minimized.

Copy link

trhymers commented Oct 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment