• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

office snapin problem

Scheduled Pinned Locked Moved Unsolved
FOG Problems
4
9
2.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O
    oraniko
    last edited by Mar 22, 2017, 12:32 PM

    Server
    • FOG Version: 1.3.3
    • OS: centos 6.4
    Client
    • OS: windows 7
    Description

    hi
    i have a problem with office snapin deployment, here is a little information:

    1. i created the .exe office file using sfxmaker
    2. when i try to manual run it on the target computer (double click) it’s working perfect.
    3. when i try to: basic task - > advanced - > singel snapin - > create singel snapin, i can see on the target machine that “office 2016 succefully installed” but it doesn’t.
    4. when i try to deploy to the same computer googlechrome.msi package from the fog server - > singel snapin deployment, it’s working perfect.
    5. i already tried to change the /quite to /qn and it doesn’t work also.
    6. i changed the time out to 1800 (it should take much less) and also it doesn’t work
      i’ve attacked a part of the fog log file:
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     22/03/2017 14:30 Client-Info Client Version: 0.11.8
     22/03/2017 14:30 Client-Info Client OS:      Windows
     22/03/2017 14:30 Client-Info Server Version: 1.3.3
     22/03/2017 14:30 Middleware::Response Success
     22/03/2017 14:30 SnapinClient Snapin Found:
     22/03/2017 14:30 SnapinClient     ID: 19
     22/03/2017 14:30 SnapinClient     Name: Office 2016
     22/03/2017 14:30 SnapinClient     Created: 2017-03-22 12:07:23
     22/03/2017 14:30 SnapinClient     Action: 
     22/03/2017 14:30 SnapinClient     Pack: False
     22/03/2017 14:30 SnapinClient     Hide: False
     22/03/2017 14:30 SnapinClient     Server: 
     22/03/2017 14:30 SnapinClient     TimeOut: 1800
     22/03/2017 14:30 SnapinClient     RunWith: msiexec.exe
     22/03/2017 14:30 SnapinClient     RunWithArgs: /i
     22/03/2017 14:30 SnapinClient     Args: /qn
     22/03/2017 14:30 SnapinClient     File: office2016.exe
     22/03/2017 14:30 Middleware::Communication Download: http://132.70.33.80/fog/service/snapins.file.php?mac=5C:F9:DD:75:0D:C2||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=19
     22/03/2017 14:31 SnapinClient C:\Program Files (x86)\FOG\tmp\office2016.exe
     22/03/2017 14:31 Bus {
      "self": true,
      "channel": "Notification",
      "data": "{\r\n  \"title\": \"Installing Office 2016\",\r\n  \"message\": \"Please do not shutdown until this is completed\"\r\n}"
    }
     22/03/2017 14:31 Bus Emmiting message on channel: Notification
     22/03/2017 14:31 SnapinClient Starting snapin...
     22/03/2017 14:31 SnapinClient Snapin finished
     22/03/2017 14:31 SnapinClient Return Code: 1620
     22/03/2017 14:31 Bus {
      "self": true,
      "channel": "Notification",
      "data": "{\r\n  \"title\": \"Office 2016 Installed\",\r\n  \"message\": \"Installation has finished and is now ready for use\"\r\n}"
    }
     22/03/2017 14:31 Bus Emmiting message on channel: Notification
     22/03/2017 14:31 Middleware::Communication URL: http://132.70.33.80/fog/service/snapins.checkin.php?taskid=19&exitcode=1620&mac=5C:F9:DD:75:0D:C2||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
    ------------------------------------------------------------------------------```
    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Wayne Workman Mar 22, 2017, 8:27 AM Mar 22, 2017, 2:27 PM

      You don’t need to use sfxmaker to deploy office via snapins. You could use snapin packs, or you could just deploy a script that calls the installer components from a share.
      Here are some resources:
      https://technet.microsoft.com/en-us/library/dd630736.aspx
      https://gallery.technet.microsoft.com/office/PowerShell-to-InstallUninst-0536b17b
      https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • O
        oraniko
        last edited by Mar 22, 2017, 3:12 PM

        ok
        i already have a silent installation of office.
        i use winzip to zip all the files, then i upload it as snapin pack like in the picture i attached.
        in the task managment i see that the task is running, but it’s running forever.
        and the office is not being installed on the target machine.
        another thing is that when i click to see the snapin, then the snapin pack template is changed to the default option, when i try to switch it back to EXE and press on update, it change again to the default option “pease select an option”
        0_1490195594649_Capture.JPG

        1 Reply Last reply Reply Quote 0
        • K
          KnightRaven
          last edited by Mar 22, 2017, 3:16 PM

          From what I see(although I am a snapins novice) you were/are trying to run an .exe with msiexec. Msiexec should be used with .msi packages. I could be misinterpreting the logfile though. Also I have had issues when trying to repack .exe files into an .msi and the repacked/wrapped file not installing in the manner you described. Using AD software install, it would push/run but the .msi wouldn’t actually install. Since you don’t need to repack it, like Wayne mentioned, Try using a script to call the exe, or Office has a builtin .msi. In the list of folders for your office setup there should be a ‘version.WW’ folder(so enterprise.ww or maybe proplus.ww, etc.) that will have .msi and .xml files for configuration.

          It looks like Wayne’s links also point to info on doing silent installs or setup options. In short you can call your officesetup.exe /admin and get to the config tool to create a .msp file to use with setup, although I haven’t tried that with the .msi version(just the .exe).

          Just my $0.02 worth,
          Jason

          A wise man knows he can always grow wiser.

          99 little bugs in the code, 99 little bugs
          Fix one bug, save it again…
          101 little bugs in the code

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Joe Schmitt Mar 22, 2017, 11:04 AM Mar 22, 2017, 5:04 PM

            @oraniko said in office snapin problem:

            and the office is not being installed on the target machine.
            another thing is that when i click to see the snapin, then the snapin pack template is changed to the default option, when i try to switch it back to EXE and press on update, it change again to the default option “pease select an option”

            Templates don’t “stick”. That is, when you click a specific template, it just sets the fields to some defaults, and that’s it. It doesn’t remember which template its using since you could change any one of those fields.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            1 Reply Last reply Reply Quote 1
            • O
              oraniko
              last edited by Mar 22, 2017, 6:03 PM

              why should i use a script to call the exe?
              can i just use the setup.exe that located inside the zip file?

              1 Reply Last reply Reply Quote 0
              • J
                Joe Schmitt Senior Developer
                last edited by Joe Schmitt Mar 22, 2017, 12:48 PM Mar 22, 2017, 6:48 PM

                @oraniko if you use a Snapin Pack like you are now, then you can directly call the exe. @KnightRaven was talking about if you used just a regular snapin and hosted the office files on a network share.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                O 1 Reply Last reply Mar 22, 2017, 8:32 PM Reply Quote 1
                • O
                  oraniko @Joe Schmitt
                  last edited by Mar 22, 2017, 8:32 PM

                  @Joe-Schmitt so why it doesn’t work with the exe. file like i did?
                  what do you think could be the problem?

                  W 1 Reply Last reply Mar 23, 2017, 12:34 AM Reply Quote 0
                  • W
                    Wayne Workman @oraniko
                    last edited by Wayne Workman Mar 22, 2017, 6:36 PM Mar 23, 2017, 12:34 AM

                    @oraniko When a snapin or snapinpack runs forever, usually this means it’s waiting for input. And snapins are not allowed to receive input, nor interact with the end-user in any way.

                    So, to troubleshoot, Step back and start without even involving fog. Unzip all these files to somewhere - open an elevated command prompt, cd to the directory and run setup.exe and see what happens. If it doesn’t “just go” without asking for any input whatsoever - then it needs work. Once you have it “just going” without any help, take that work and those commands and make a snapin or snapinpack with them. The links I posted below are full of resources & ideas.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    1 Reply Last reply Reply Quote 1
                    • 1 / 1
                    1 / 1
                    • First post
                      4/9
                      Last post

                    160

                    Online

                    12.1k

                    Users

                    17.3k

                    Topics

                    155.4k

                    Posts
                    Copyright © 2012-2024 FOG Project