Endpoint Protection

 View Only
  • 1.  Push deployment wizard and Windows Server 2003 R2

    Posted Oct 16, 2009 06:31 AM
    I cannot able to push the client 11.0.4202.75 on Windows Server 2003 R2 clients
    These servers use 11.0.3001.2224 and, cause the "install package" upgrade option is not working, I need to use Push Deployment wizard to upgrade them.
    The tool works fine on a Windows XP Sp3 machines but not over the W2k3 servers.
    Why?
    I have administrators rights and the "remote registry" and "secondary logon" services are running.
    What else?

    The tool (PDW), complete the installation without errors, showing the Complete message. The server still run the old client.

    Paolo


  • 2.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 16, 2009 06:36 AM
    Hello Paolo,

    The push deployment will just push the package from the server to the client.
    the location will be c:\temp
    once the source is placed in the location, installation will then run
    i think the push is successful however the upgrade is rolling back ( installation)
    analyzing the SEP_INST.log file wil help to figure out the cause
    on the 2k3 server
    go to start
    run
    %temp%
    Enter
    Look for SEP_INST.log file ( should be the latest one, check the date)
    open it
    look for return value 3, paste the 15 lines about and below of this return value if you find it.
    Lets see , why the installation is rolling back.


  • 3.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 16, 2009 06:45 AM
    MSI (s) (1C:3C) [11:50:28:144]: Adding new sources is allowed.
    MSI (s) (1C:3C) [11:50:28:144]: Package name retrieved from configuration data: 'Symantec AntiVirus.msi'
    MSI (s) (1C:3C) [11:50:28:144]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (s) (1C:3C) [11:50:28:144]: Note: 1: 2729
    MSI (s) (1C:3C) [11:50:28:160]: Note: 1: 2729
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding IsAdminPackage property. Its value is '1'.
    MSI (s) (1C:3C) [11:50:28:160]: Machine policy value 'DisableMsi' is 1
    MSI (s) (1C:3C) [11:50:28:160]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (1C:3C) [11:50:28:160]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (1C:3C) [11:50:28:160]: Product {49C27FB0-CEEF-4A11-8114-0BFE336D3884} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (1C:3C) [11:50:28:160]: Product {49C27FB0-CEEF-4A11-8114-0BFE336D3884} is managed.
    MSI (s) (1C:3C) [11:50:28:160]: Running product '{49C27FB0-CEEF-4A11-8114-0BFE336D3884}' with elevated privileges: Product is assigned.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding SETUPEXEDIR property. Its value is 'C:\WINDOWS\TEMP\Symantec'.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\WINDOWS\TEMP\Symantec'.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '7984'.
    MSI (s) (1C:3C) [11:50:28:160]: TRANSFORMS property is now:
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
    MSI (s) (1C:3C) [11:50:28:160]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '301'.
    MSI (s) (1C:3C) [11:50:28:175]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Application Data
    MSI (s) (1C:3C) [11:50:28:175]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Favorites
    MSI (s) (1C:3C) [11:50:28:175]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\NetHood
    MSI (s) (1C:3C) [11:50:28:175]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\My Documents
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\PrintHood
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Recent
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\SendTo
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Templates
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data
    MSI (s) (1C:3C) [11:50:28:191]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\My Documents\My Pictures


  • 4.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 16, 2009 07:01 AM
    The DisableMSi value is 1 so per user installation should be allowed
    I dont see any return value 3 here, is it possible for you to paste 10 lines above and below
    "return value 3"

    do a search for "return value 3"


  • 5.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 20, 2009 09:28 AM
    No results for "return value 3".

    I found this one:
    [15:11:04:517]: Doing action: AppSearch
    Action ended 15.11.04: SetInstallStateFailed.1CBEC0D3_E547_4E51_828B_44B9C47C0EA5. Return value 1.
    Action start 15.11.04: AppSearch.

    I see many "failed" messages near some "Executing op" or "serviceIsRunning: OpenService FAILED with error 1060".

    Any other suggestions?

    Paolo


  • 6.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 20, 2009 09:57 AM


  • 7.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 20, 2009 10:20 AM
    But, I have no "return value 3".
    Usually the value is 1.
    The last one is: "Action ended 15.12.40: INSTALL. Return value 1."

    Is it possibile all the Windows Server 2003 R2 have a defective LU installation? The clients, running MR3 version, are able to update the virus definitions every day without errors.

    Do you need the log file?

    Paolo


  • 8.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 20, 2009 10:23 AM
    Please paste the install log


  • 9.  RE: Push deployment wizard and Windows Server 2003 R2

    Posted Oct 20, 2009 10:58 AM
    Sorry, the log is 22660 lines long. Too big and IE become not stable.
    Any other way to send it?

    Paolo